06-17-2012 01:53 PM - edited 03-07-2019 07:17 AM
Guys,
we're upgrading over 40 of our 3550/3560 switches to the 3560x platform - what I have noticed is that we get quite a few PoE issues when migrating the site - for instance, 90 - 95% of the site's Cisco's phones will come up but not all of them - the best way to resolve that issue is to identify the ports that haven't came up and then shut - wait 10 secs and no shut. This is obviouisly not ideal...has anyone else noticed this issue?
Thanks,
06-17-2012 02:13 PM
Hi,
there is this troubleshooting steps in the Cisco website that might help:
Step 1 Verify all electrical connections from the switch to the powered device. Any unreliable connection results in power interruptions and intermittent powered device operations, such as powered device disconnects and reloads.
Step 2 Verify that the total cable length from the switch front panel to the connected device (powered device) is not more than 100 meters. For more information, see the cable diagnostics section in the switch software configuration guide.
Step 3 Notice what might be changing in the electrical environment at the switch site. What is happening at the powered device when the disconnect occurs?
Step 4 Use the show log privileged EXEC command to review messages and events. Notice whether any other error messages are reported by the switch at the same time that a disconnect occurs.
Step 5 Verify that a Cisco IP Phone is not losing access to the call manager immediately before the reload occurs. (It might be a network problem, not a PoE problem.)
Step 6 Connect a non-PoE device to the port, and verify that it works. If a non-PoE device has link problems or a high error rate, the problem might be an unreliable cable connection between the switch port and the user.
plz Rate if it helped.
Soroush.
06-17-2012 03:11 PM
I hoped one of the answers above would have helped but unfortunately everything appears to be fine and a shut no shut resolves the problem MOST of the time but not all the time. The capacity is generally no more than 75%
It's a weird one as you can remove the cable from the phone port and plug it back in and it will turn back on so it's nothing to do with the cabling at the switch side of things - that's what has got me baffled
06-17-2012 03:52 PM
maybe there is a network problem rather than power, if its only affecting ip phones, could be ur call manager's connection, so ip phones can not connect n maintain their connection as they should, network congestion, bad route or sth... dont know, double check that... n check ur logs.
06-17-2012 08:27 PM
Need more information.
What happens if you run the command "sh power inline"?
Have you tried running a TDR test?
06-18-2012 12:14 AM
I don't believe we're over utilising the power - this has happened to atleast 90% of the 3560x deployments so not an isolated issue. Before the site upgrades there is never an issue:
gh2-3560x-48-1#sh power inline
Available:462.0(w) Used:226.8(w) Remaining:235.2(w)
so in the case above you can see we have more than enough capacity.
and as previously stated usually a shut/no shut on the interface brings the port to life...
06-19-2012 12:37 AM
I don't believe we're over utilising the power - this has happened to atleast 90% of the 3560x deployments so not an isolated issue. Before the site upgrades there is never an issue:
gh2-3560x-48-1#sh power inline
Available:462.0(w) Used:226.8(w) Remaining:235.2(w)
so in the case above you can see we have more than enough capacity.
and as previously stated usually a shut/no shut on the interface brings the port to life...
That is not what I'm looking at. Can you please post the output to the command "sh power inline"?
Otherwise, please run the TDR as posted on my previous link.
06-19-2012 01:18 AM
gh2-3560x-48-1#sh power inline
Available:462.0(w) Used:226.8(w) Remaining:235.2(w)
Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi0/1 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/2 auto off 0.0 n/a n/a 30.0
Gi0/3 auto off 0.0 n/a n/a 30.0
Gi0/4 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/5 auto on 6.3 IP Phone 7960 n/a 30.0
Gi0/6 auto on 6.3 IP Phone 7960 n/a 30.0
Gi0/7 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/8 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/9 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/10 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/11 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/12 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/13 auto on 6.3 IP Phone 7960 n/a 30.0
Gi0/14 auto on 6.3 IP Phone 7960 n/a 30.0
Gi0/15 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/16 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/17 auto off 0.0 n/a n/a 30.0
Gi0/18 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/19 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/20 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/21 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/22 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/23 auto on 6.3 IP Phone 7960 n/a 30.0
Gi0/24 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/25 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/26 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/27 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/28 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/29 auto on 6.3 IP Phone 7940 n/a 30.0
Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Gi0/30 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/31 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/32 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/33 auto off 0.0 n/a n/a 30.0
Gi0/34 auto on 6.3 IP Phone 7960 n/a 30.0
Gi0/35 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/36 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/37 auto off 0.0 n/a n/a 30.0
Gi0/38 auto off 0.0 n/a n/a 30.0
Gi0/39 auto on 6.3 IP Phone 7960 n/a 30.0
Gi0/40 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/41 auto off 0.0 n/a n/a 30.0
Gi0/42 auto off 0.0 n/a n/a 30.0
Gi0/43 auto off 0.0 n/a n/a 30.0
Gi0/44 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/45 auto off 0.0 n/a n/a 30.0
Gi0/46 auto on 6.3 IP Phone 7940 n/a 30.0
Gi0/47 auto off 0.0 n/a n/a 30.0
Gi0/48 auto off 0.0 n/a n/a 30.0
gh2-3560x-48-1#
Thanks very much for your support it is appreciated.
Thomas.
06-19-2012 09:12 PM
Thanks.
I don't see any issues with the output to the "sh power inline" command (particularly any ports reporting as "IEEE"). And the ports have PoE enabled.
So the next guess would be the TDR result. Let me know the outcome.
06-19-2012 09:49 PM
Hey Thomas,
Apart from TDR you may also try debugging PoE (if you really want to dig down ).
You need to use below given configuration before adding the IP phone to switch
Configuration:
#debug interface Gix/x - Interface where IP phone will be connected
#debug ilpower controller
#debug ilpower events
Additionally to capture the complete output add the following:
#conf t
#logging buff
#no logg console
#exit
At this point connect the IP phone and if we see the same behaviour do a shut and no shut on interface. Wait for IP phone to boot up and fianlly turn off the debug:
#un all
Collect the show log output and paste it.
Regards,
rajeevsh.
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