SecureStack C2 Continuously Resetting after Upgrade from version 3.x or 4.x to 5.02.01 or 5.02.02

FAQ_User — Fri, 22 Nov 2013 00:12:00 GMT

Article ID: 11493

Products
SecureStack C2, firmware 5.02.01.0006 and 5.02.02.0009

Changes
Upgraded from firmware 3.x or 4.x (e.g. 4.00.55) directly to 5.02.01.0006 or 5.02.02.0009

Symptoms
C2 will not fully boot.
In continuous reboot cycle.

Cause
The upgrade procedure did not consider the following information:

Firmware 5.02.05.0004 and 5.02.04.0005 release notes state, in the 'Upgrading from Previous Versions' section, as a correction to what is stated in earlier release notes:

Important Note:

5623

5605

5628

5623

Firmware 5.02.07.0006, 5.02.06.0004, 5.02.03.0012, 5.02.03.0010, and 5.02.02.0009 release notes state, in the 'Upgrading from Previous Versions' section:

Important Note:

Firmware 5.02.01.0006 release notes do not contain this warning, but the information does apply to this version as well.

Solution/Workaround
If the reboot condition is occurring, recovery requires clearing the configurations out of flash memory, as described in (otherwise unrelated) 9687. First, clear to default configurations per step 3, then if you had previously saved the configurations (as described in step 1), you may restore them per step 4. Otherwise, the non-default configurations will be lost and must be manually re-entered.

For long-term prevention of this problem, upgrade to firmware 5.02.03.0010 or higher.

Release notes state in the 'Firmware Changes and Enhancements' section:
"11450 Corrected an issue where upgrading a C2 from firmware revision 4.0.x.x to 5.2.x.x could potentially cause a continuous reset loop."

Despite any potential release notes mention of the "Important Note" cited above, the process of upgrading from 3.0x.xx or 4.00.xx to firmware 5.02.03.0010 or higher is free of the two-stage upgrade requirement.

See also: 5707.

topic SecureStack C2 Continuously Resetting after Upgrade from version 3.x or 4.x to 5.02.01 or 5.02.02 in FAQs

SecureStack C2 Continuously Resetting after Upgrade from version 3.x or 4.x to 5.02.01 or 5.02.02