cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2119
Views
0
Helpful
10
Replies

Port up and down

akhon0001
Level 1
Level 1

 I have a switch 3560g that has cameras connected to the ports.
Hikvision camera model.
and ports are constantly changed state to down and up.
How can I find out the reason?
The cameras work correctly.
 038509: Mar 4 09:57:45.256 ALMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/10, changed state to down
038510: Mar 4 09:57:46.263 ALMT: %LINK-3-UPDOWN: Interface GigabitEthernet0/10, changed state to down
038511: Mar 4 09:57:48.930 ALMT: %LINK-3-UPDOWN: Interface GigabitEthernet0/10, changed state to up
038512: Mar 4 09:57:49.937 ALMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/10, changed state to up
038513: Mar 4 10:02:46.284 ALMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/10, changed state to down



10 Replies 10

Leo Laohoo
Hall of Fame
Hall of Fame
Post the complete output to the command "sh interface G0/10 controll".

GigabitEthernet0/1 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 001c.f67b.7001 (bia 001c.f67b.7001)
MTU 9000 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 40000 bits/sec, 46 packets/sec
5 minute output rate 1093000 bits/sec, 95 packets/sec
4774358 packets input, 969905350 bytes, 0 no buffer
Received 462533 broadcasts (456890 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 456890 multicast, 0 pause input
0 input packets with dribble condition detected
10678924 packets output, 11207234091 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out

Transmit GigabitEthernet0/1 Receive
2617300269 Bytes 969905975 Bytes
8535102 Unicast frames 4311828 Unicast frames
2062271 Multicast frames 456891 Multicast frames
81553 Broadcast frames 5643 Broadcast frames
0 Too old frames 772047748 Unicast bytes
0 Deferred frames 155649555 Multicast bytes
0 MTU exceeded frames 1288530 Broadcast bytes
0 1 collision frames 0 Alignment errors
0 2 collision frames 0 FCS errors
0 3 collision frames 0 Oversize frames
0 4 collision frames 385422 Undersize frames
0 5 collision frames 0 Collision fragments
0 6 collision frames
0 7 collision frames 414876 Minimum size frames
0 8 collision frames 3528414 65 to 127 byte frames
0 9 collision frames 297042 128 to 255 byte frames
0 10 collision frames 574823 256 to 511 byte frames
0 11 collision frames 123567 512 to 1023 byte frames
0 12 collision frames 151915 1024 to 1518 byte frames
0 13 collision frames 0 Overrun frames
0 14 collision frames 0 Pause frames
0 15 collision frames
0 Excessive collisions 0 Symbol error frames
0 Late collisions 0 Invalid frames, too large
0 VLAN discard frames 69147 Valid frames, too large
0 Excess defer frames 0 Invalid frames, too small
250985 64 byte frames 0 Valid frames, too small
2323288 127 byte frames
250496 255 byte frames 0 Too old frames
244597 511 byte frames 0 Valid oversize frames
294843 1023 byte frames 0 System FCS error frames
6939829 1518 byte frames 0 RxPortFifoFull drop frame
374888 Too large frames
0 Good (1 coll) frames
0 Good (>1 coll) frames

 

Nothing wrong with Layer 1.
The camera going down and up could mean a hardware issue.

Thank you,

but checking showed that there are no problems with the camera.
Please tell me, maybe it’s such that some packets come in from the camera, in which there is a message about the disconnection. Is it possible to somehow check which packets are interrupted by communication, for example, using debug?
I need to understand why this is happening, because I already have 7 such cameras, and the messages in the logs already reach 16,000. Each port to which the camera is connected sends messages to the logs

Hi,

 

    Is the camera using PoE from the switch (from the log message, looks like not, but just to be sure). I see way too many multicast/broadcast packets from the camera, can you configure it and and disable those services doing this? Your camera is supposed to send the footage via unicast, right? 

 

Regards,

Cristian Matei.

Adding to other mates comments.

 

Do you have any auto discovery running in the network, i have seen some issue around the cameras

 

Some how when the scanner try to scan the device IP address, it drops and reboot some how (may be not the same case with you)

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

I don't have any auto discovery running in the network ...

 

Is the camera getting a valid IP address?

The camera has a static address, everything works correctly.

good afternoon

The cameras are powered exclusively by the switch
(Most likely, many multicast / broadcast packets come from the camera) - how does this affect the drop in interface? No storm-control policies are configured on the interface.

When the interface drops the power does not drop exactly. Notice the time interval when the interface changes from down to UP, 3 seconds. I do not understand what it means.

 

Review Cisco Networking for a $25 gift card