06-23-2014 05:58 AM - edited 03-07-2019 07:48 PM
Hi friends,
We have a situation.
We have a 2960 Cisco switch on which we have 10 PTZ cameras (drawing 30 W) and 25 normal cameras connected (drawing 15.4 w).
Now, when the cameras are tuned for higher clarity, the switch ports goes down. As per the camera datasheet , the maximum power drawn is 22W.
Have anyone faced such an issue.?
Can it be something related to collision due to high data flow or something?
Appreciate any troubleshooting guidance. Thank you.
06-23-2014 03:28 PM
What exact model is your 2960 switch?
Can you also post the output to the command "sh interface <BLAH>" to one of the ports which would go down?
06-25-2014 12:46 AM
Hi Leo,
Thank you for the reply and sorry for the delay.
The switch model is Cisco Catalyst 2960S-48FPD-L.
Below is the sh interface output for the interface which went down.
GigabitEthernet1/0/41 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 5017.ff22.9ea9 (bia 5017.ff22.9ea9)
MTU 1500 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 never, 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: 1981
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 6743000 bits/sec, 905 packets/sec
2409235054 packets input, 3562635785604 bytes, 0 no buffer
Received 366038 broadcasts (355394 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 355394 multicast, 0 pause input
0 input packets with dribble condition detected
4638976920 packets output, 5756168176334 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
I couldn't find any problem in the switch.
please let me know if more outputs are required.
06-25-2014 03:12 PM
Ok, I need more outputs:
Next, I need you to do the following:
1. Command: test cable tdr interface Gi1/0/41;
2. Wait for approximately 5 to 7 seconds;
3. Command: sh cable tdr interface Gi1/0/41; and
4. Post the out put to #3.
NOTE: When you are running a TDR on a PoE port, the end-device will loose power. This is to be expected.
06-25-2014 01:56 AM
If you are 100% certain about each camera's watt usage, then all your cameras are drawing 685W. Your switch supports maximum of 740W.
Just to double check, use "show power inline" command to see how much wattage your cameras are currently using. It should not be more than 740W or close to it.
Also, use "spanning-tree portfast" under each camera's interface.
Let me know how it goes...
Abdullah,
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide