Cisco 3560-48PS lockout after power outage

[fredrikringberg]

We had a problem wih a very short Power outage (just a second). All our swicthes (in different buildings) made a coldstart except one model 3560-48PS. It never started. The solution was to unplugg the power cable and plugg it again. Then it worked!

This has happen 2 times. We have many other Cisco switching models (3560 48TS, 2960, 3548, 3550, 2924) with no problem.

Solution?

[Joseph W. Doherty]

Disclaimer

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.

Posting

UPS.  (Short duration power outages can be "iffy" to how equipment will restart.  An old rule of thumb was to wait 10 seconds before powering equipment back on.)

[fredrikringberg]

Thanks Joseph for your answer.

Yes ordinary power tests we wait 25-30 sec, this was not planned (some type of external power break that effected our building). And we don't know if it will happen again, and if, is there anything we can do to prevent this? Known "bug", sw image, commands, ..? We know it's a problem for 3560-48PS, perhaps this is a generally "problem"/safety-mechanism for all Cisco PoE switches?

[Joseph W. Doherty]

Disclaimer

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.

Posting

Sorry, I'm aware of any specific bug.  What you might try, if not already running it, is to use a late version of 12.2(55).  Those seem to be about the most solid IOS versions.

[fredrikringberg]

We are running 12.2(20) in those so upgrade would be one way. It would be very interest to get confirmed if there is known a bugfix in a later version.