Configuration Guide User guide

FastIron Configuration Guide 281
53-1002494-02
Brocade IronStack management
To remove this restriction, enter the no stack disable command.
Important notes about stacking images
Consider the notes in this section when upgrading from a pre-stacking release to a stacking
release, or when reverting from a stacking release to a pre-stacking release.
Refer to the release notes for instructions about upgrading the software.
Converting from a pre-stacking image to a stacking image
When you boot a stacking image (release 05.X or later) on a device with a pre-stacking (pre-release
05.X) startup-config.txt file, the system automatically converts the interface format from 0/X/X to
1/X/X. In addition, when a write memory command is issued, the pre-stacking startup-config.txt file
is renamed to start-config.v4 and saved as a backup file.
NOTE
If you enter the erase startup-config command or stack unconfigure clean command, all
startup-config txt-related files, such as startup-config.v4 and startup-config.old are erased. You will
no longer be able to recover pre-stacking startup-config.txt files.
Reverting from a stacking image to a pre-stacking image
To convert a device running a stacking image (release 05.X or later) to a pre-stacking (pre-release
05.X) image, use the stack unconfigure rollback command, which recovers the startup-config.v4
file that was saved when the write memory command was issued at the time the device was
upgraded to a stacking image. For more information, refer to “Recovering an earlier version of a
stack configuration” on page 288.
Encountering a problem after upgrading and reloading the software
If you encounter a problem after upgrading and reloading the software, make sure the device has
the correct boot code version and the following (if applicable) are installed correctly:
• EEPROM
• Memory DIMM
NOTE
If you do not have the correct EEPROM for the upgrade, you will need to recover your pre-stacking
image. For information about how to do this, refer to “Recovering an earlier version of a stack
configuration” on page 288.
If the stacking EEPROM is missing or is not installed correctly, or if you have installed the wrong
EEPROM, you will see output similar to the following.
FCX MEM size: 0x10000000
FCX Flash config....
FCX Boot Code Version 05.0.01
Enter ‘b’ to stop at boot....
BOOT INFO: load monitor from primary, size=103408
BOOT INFO: load image from primary..........
BOOT INFO: bootparam at 000543e8, mp_flash_size=002ee6c5
BOOT INFO: code decompression completed