Back-Rev Firmware on a SecureStack

[FAQ_User]

Article ID: 9687

Products
SecureStacks
B2-series, B3-series, C2-series, C3-series, A2-series

Goals
Provide the commands and reasoning that allow a SecureStack to go backwards in the firmware it will execute.
The SecureStack has no issue when upgrading from one firmware to a newer firmaware. The SecureStack will retain its configuration files with no manipulation on the Administrators part.
The SecureStack does have an issue when the device goes back to an older firmware revision. The SecureStack will not come up with its current configuration. The Administrator must manually activate the latest configuration file for the SecureStack.

Solution

1. Save off the configuration
   To save the configuration right onto the SecureStack device use the following commandB2(su)->
   B2(su)->show config outfile configs/100707.cfg
   B2(su)->
   This saves the current configuration on the SecureStack as 100707.cfg in the configs directory
   To verify if the file has been saved type the dir command and look at the output for the 100707.cfg fileB2(su)->dir
   Images:
   ==================================================================
   Filename: b2-series_04.00.60
   Version: 04.00.60
   Size: 7699456 (bytes)
   Date: Fri May 25 09:16:52 2007
   CheckSum: 12810fd9ac8c2032ea97226c4a8ddb42
   Compatibility: B2G124-24, B2G124-24P, B2G124-48, B2G124-48P, B2H124-48
   B2H124-48P, B3G124-24, B3G124-24P, B3G124-48, B3G124-48P
   
   Filename: b2-series_03.01.24 (Active) (Boot)
   Version: 03.01.24
   Size: 6622208 (bytes)
   Date: Thu Aug 31 14:22:07 2006
   CheckSum: ffcaad30312c326bb1fbf5e42a8ba7b0
   Compatibility: B2G124-24, B2G124-48, B2H124-48, B2G124-48P, B2H124-48P
   
   Files: Size
   ================================ ========
   configs:
   Enterasys.cfg 10341
   test.cfg 6245
   100707.cfg 2149
   logs:
   current.log 256017
   The file should also be saved to a TFTP server as a precautionary measure.
   The following command will copy the 100707.cfg file to a TFTP serverB2(su)->copy configs/100707.cfg tftp://134.141.90.59/100707.cfg
   File transfer operation completed successfully.
   
   
   • Download image
     The configuration is saved and now it is time to download the image.
     Use the dir command and make sure there is room for the image. Each SecureStack can hold up to two images. If there are two images already listed the non-active image will have to be deleted. In the above command the image c2-series_04.00.60 is not active. The following command will delete the image.B2(su)->
     B2(su)->delete b2-series_04.00.60
     B2(su)->
     There should only be one image on the switch and it should be the active image.
     Download the new image to the device.B2(su)->copy tftp://134.141.90.59/b2-series_03.00.75 system:image
     TFTP code transfer starting
     Verifying CRC of file in Flash File System
     TFTP receive complete... storing in Flash File System...
     File transfer operation completed successfully.
     B2(su)->
     There should now be two image files when you run the dir command. The active image and the image that was recently downloaded.
     Set the image that was downloaded to active with the following commandB2(su)->set boot system b2-series_03.00.75
     This command requires resetting the entire system.
     Do you want to continue (y/n) ?
     Answer yes if you want the downloaded image to become the active image.
     
   • Resolve the Reboot Issue
     The SecureStack will now try and reboot but it will not. It is in a loop where it keeps trying to reboot. The older image can not read the configuration files that are in a compression format that is not understood by the older code.
     The rebooting process will need to be broken.
     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.
     
   • Load and execute Configuration file
     Log into the boxusername:admin
     password:
     Type dir and make sure the device is on the firmware that is desired and that the configuration file is still accessible. If the configuration file is not listed in the Configs directory it can be TFTP?d down to the box with the following commandB2(su)->copy tftp://134.141.90.59/100707.cfg configs/100707.cfg
     To set the configuration file active type the followingB2(su)->
     B2(su)->configure configs/100707.cfg
     This command will reset the system and clear current configuration.
     Are you sure you want to continue (y/n) ?
     Upon the next successful boot the image should be the older image with the configuration that was saved and copied.
     
     To get device out of reboot see 9673.