08-29-2007 08:52 PM - edited 07-03-2021 02:33 PM
In prepping for the upgrade to 4.1.185.0 I've got two controllers at different sites stuck in a boot loop after applying 4.0.219.0. Units will not even get to the <ESC> option menu.
ANy ideas?
09-04-2007 01:44 PM
Did you clear the configuration on the controller by using Option 5 in the boot menu? This will corrupt the boot image. You should not choose the clear config (option 5) from the boot menu on controllers running 3.2.78.0, 3.2.116.21, 3.2.150.6 or 3.2.150.10, 3.2.171.5 or 3.2.171.6, 4.0.155.5 or 4.0.179.8 and 4.0.179.11.
09-17-2007 07:43 AM
No, did not clear the config.
Cisco TAC has verfied the unit is now a boat anchor and has shipped a replacement. They are doing a n autopsy on theold unit to see what the problem is.
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