Table of Contents
Advertisement
•
If you copied the primary and/or secondary IronWare image to all interface modules using the
copy command with the all keyword, the management module made a copy of the image and
stored it in its code flash under the names lp-primary-0 or lp-secondary-0. By default, the BigIron
RX system checks the interface modules' IronWare images, which reside in the code flash of the
interface modules and the management module to make sure they are the same in both locations.
(These IronWare images are stored on the management module only and are not run by the
management or interface modules.) If the IronWare images on the interface and management
modules are different, the system prompts you to do the following:
•
If you want to update the IronWare images in the interface module's code flash with the
images in the management module's code flash, enter the lp cont-boot sync <slot-number>
command at the Privileged EXEC prompt.
•
If you want to retain the IronWare images in the interface module's code flash, enter the lp
cont-boot no-sync <slot-number> command at the Privileged EXEC prompt.
After the management module finishes booting, do the following:
•
Enter the show module command at any CLI level, and verify that the status of all interface
modules is CARD_STATE_UP.
•
Enter the show version command at any CLI level, and verify that all management and interface
modules are running the new software image version.
If you find that an interface module is in a waiting state or is running an older software image, then you
may have not entered the lp cont-boot sync <slot-number> command at the Privileged EXEC prompt.
You also need to upgrade the MBRIDGE FPGA on the management module.
Regenerating SSH v2 crypto key
If you are using SSH v2, you must clear the crypto key using the crypto key zeroize command after you
upgrade from any release 02.2.01 and later. Then, you must regenerate a new crypto key using the crypto
key generate command.
Hitless Layer 2 OS Upgrade
Hitless OS upgrades are supported for Layer 2 switching and Layer 2 protocols only. See the Upgrading
Software Images and Configuration Files chapter in the BigIron RX Series Installation Guide for
additional information. The hitless OS Layer 2 upgrade allows for upgrading the software in a system
between two patch releases of the operating system, which support this functionality and have compatible
data structures. A hitless OS Layer 2 downgrade may also be supported if the current and target code
releases have compatible data structures.
Note: Hitless OS upgrade is not supported between major releases. It is supported only within a release.
For example, Hitless OS Upgrade is available when upgrading from software release 02.8.00a to
02.8.00b. It is not available when upgrading from software release 02.7.00 to 02.8.00.
From time to time, it may become necessary when enhancing the software or adding new features to
change or add data structures making releases incompatible. In these cases, an upgrade or downgrade will
not be hitless, and will fall back to using the regular Brocade upgrade process – relying on fast reboot.
IronWare Software Release 02.8.00a for Brocade BigIron RX Series Swtches
Release Notes v 1.0
Page 25 of 40
Advertisement
Table of Contents
