CSCvf33653 - Controller port error, Power given, but State Machine Power Good wait timer timed out - 2

[LizsanderRoque1725]

Having this bug also running 16.12.4 on multiple 3850's. Work around was to power cycle that stack member. After power cycling POE was restored on all the ports. This is not a permanent solution and would like a more stable solution. As mentioned before this bug has not been resolved using ver 16.12.4

[Leo Laohoo]

@LizsanderRoque1725, 16.12.5 is now out.

[KUNG-AN LIN]

I faced the same issue with 3850 switch and C9130 WAPs. IOS XE 16.12.5 is released on 31-Jan-2021. Has someone validated if the new release fixes this issue? Thanks.

[Leo Laohoo]

I am testing 16.12.5 for the last 2 weeks.  
I will have a good indication if this bug is really fixed in this version after 12 weeks of trouble-free uptime.

[OsmanHashmi5811]

Hi Leo- how did you go with testing out 16.12.5?

I have a WS-C3850-24P POE switch running 16.12.4 and yet the end point I have connected to the port is giving me the same headache as mentioned by previous members. I have tried bouncing the interface, statically set duplex/speed settings, yet it only stays up for about a minute.

Please get back to us with your findings on the new IOS, thanks.

[Leo Laohoo]

---

@OsmanHashmi5811 wrote:

Hi Leo- how did you go with testing out 16.12.5?

---

I am sorry to say that I have not yet "concluded" my tests.  

The switches were upgrade on the first week of February 2021 and I will not be satisfied until 12 weeks of no-fault uptime and 12 weeks would mean some time in May 2021.  

NOTE:  The 3850 I am testing 16.12.5 not just have PoE but DOT1X in them.  Having Dot1X on a 3650/3850 is not really a good idea.  

[danielwise]

We have run into the same POE issue that you were testing.  How have your tests been so far? We'll likely upgrade to 16.12.5 since that's what our TAC agent suggested.  Also could you explain what you meant by :
Having Dot1X on a 3650/3850 is not really a good idea.  

[Art Astafiev]

Hi, 

Don't go to 16.12.5 code - it has three major bugs. Go to 16.12.5b which is currently recommended by TAC. 

Below is link to my other post on same topic - you can see there that unfortunately 16.12.5 code didn't completely fixed this POE issue. 

Looks like issue is coming back in about 4 weeks after reboot. We will still upgrade all our 3850's to 16.12.5b, so we can engage TAC on next round of troubleshooting. 

https://community.cisco.com/t5/switching/cisco-3850-16-12-3a-poe-issues/m-p/4392157#M504089

One of the major bugs which was fixed in 16.12.5b is related to 802.1X.