IronWare Software Release 02.7.03a for Brocade BigIron RX Series Swtches
Release Notes v 1.0
Page 26 of 40
•
If there are protocol dependencies between neighboring nodes, it’s recommended that only each node
is upgraded: one node at a time.
•
After hitless upgrade, the BigIron RX switch will still have the same running configuration as it does
before the upgrade. A configuration that is not saved before hitless reload is not removed and the
existing startup configuration does not take effect. This behavior is the same as displayed by the
management module switchover feature.
The Hitless OS Layer 2 software process
Hitless OS Layer 2 upgrade of Multi-Service IronWare software is performed in the following steps.
•
Version 02.3.00 or later of the Multi-Service IronWare software is installed in flash memory to the
primary and secondary image on the active and standby management modules and interface modules.
•
The
hitless-reload
command is executed on the active management module.
•
The hitless upgrade process is begun on the active management module which initiates the upgrade
process on the standby management module.
•
The standby management module is reset.
•
The active management module is reset and the standby management module assumes control as the
active module.
•
Active console control is lost to the previously active management module as it becomes the standby
management module.
•
The active management module initiates the upgrade process on all interface modules.
•
The switch is now operating on the new Multi-Service IronWare software. The management module
that was initially configured as the standby management module is now the active management
module and the management module that was initially configured as the active management module
is now the standby.
Management module (MP) and Interface Module (LP) Hitless Upgrade Process provides a detailed
diagram of the Hitless reload process.
