SecureStack Reboot Loop After a Back-Rev to Older Firmware

FAQ_User — Tue, 26 Nov 2013 01:15:00 GMT

Article ID: 9673

Products
SecureStack B2, B3, C2, C3

Symptoms
SecureStack is in a constant reboot mode after downloading an image that is older than what was previously in use.

Cause
The older image can not read the configuration files that are in a compression format that is not understood by the older code.
The compression of files changed at the following code releases:
B2-series_04.00.70
B3-series_01.00.83
C2-series_05.00.69
C3-series_01.00.88

For example, on the B2 series back-revving between codes 04.00.79 .78 .77 and .76 creates no issue. Back-rev to .70 and earlier versions and the B2 will go into a constant reboot.

Solution/Workaround
This is accomplished by locally attaching to the SecureStack and selecting option 2 'Start Boot Menu' during the boot process.
When the two options appear, there is only a 2 second delay before the switch defaults to option 1 for 'Start Operational Code'.
The Boot Menu password is "administrator" in lower case.
The Start Boot Menu will have multiple options to select depending on the firmware.
Look for 'Restore Configuration to Factory Defaults'. Which is usually option 9
Type 9 and then hit the enter key
'Reset the system'. Which is usually option 8
Type 8 and hit the enter key and Y when asked if you are sure you want to reboot.
The device will now reboot to a clean configuration.

See 9687 for complete process to Back-Rev.

topic SecureStack Reboot Loop After a Back-Rev to Older Firmware in FAQs

SecureStack Reboot Loop After a Back-Rev to Older Firmware