cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
345
Views
1
Helpful
2
Replies

Cisco 9200L in stack no inline poe power available

Jochem Sparla
Level 1
Level 1

I have stacks of 9200L switches, all the same PoE models. Some of the switches in the same stack can't provide PoE. The switch works, looks normal, and non-PoE devices work fine.

'show env all' show the PSU for the switch (also all the same) as normal, model PWR-C5-600WAC, status, Sys Pwr and PoE Pwr all indicate 'OK' and 'Good'.

However, 'show power inline' shows 0.0 available watts for the switch (also 0.0 for used and remaining).

Other switches in the stack work fine. A cold start reboot of the switch (pulling the plug) resolves the problem.

Current firmware is 17.12.03.

Is this a known issue? (like CSCwk15432: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwk15432?)
Does a firmware upgrade to 17.12.04 fix this permanently? (i have upgraded, but since a reboot also solves the problem, it's hard to tell if the firmware is the solution)
Or are there any other solutions?

2 Replies 2

Leo Laohoo
Hall of Fame
Hall of Fame

@Jochem Sparla wrote:
A cold start reboot of the switch (pulling the plug) resolves the problem.

This is beginning to sound like the reintroduction of the old MOSFET bugs (CSCvd46008 & CSCvj76259).  

Cold reboot is a workaround and RMA is the solution.

Jochem Sparla
Level 1
Level 1

I found another workaround.

The 9200L switches we use have 2 PSU slots. I took the PSU from another switch, and added it to the switch that had PoE problems. After that, the 'power inline' command showed 740W PoE budget, which is normal for 2 PSU. 

So the first PSU, which was not showing any PoE budget at first, is now showing it's normal PoE budget after inserting a second PSU. No reset of the first PSU or the switch.

I then removed the second PSU, and the PoE budget changed to 370W, which is normal for 1 PSU.

So problem solved. I tested with two PoE devices, and they work. This is a handy workaround which does not require a reboot of the switch (with connection loss).

The underlying problem has not been identified, unfortunately.