Upgrading Software Images and Configuration Files
December 2008
© 2008 Foundry Networks, Inc.
7-29
Once the management and interface modules are up and running, their CPUs are able to send and receive
packets, even before the Hitless Upgrade process is complete.
•
Router configuration is not allowed to be changed during the entire Hitless Upgrade process.
•
System-max parameter changes or other configuration changes that require a system reload such as "cam-
mode" and cam-profile" changes do not take effect upon Hitless Upgrade.
•
FPGA images cannot be upgraded using the Hitless Upgrade process.
•
This feature cannot be used to downgrade an image to an older version than the version that the device is
currently running.
•
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 NetIron MLX router 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 Software Process
Hitless upgrade of Multi-Service IronWare software is performed in the following steps.
1.
Version 03.2.01 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.
2.
The
hitless-reload
command is executed on the active management module.
3.
The Hitless Upgrade process is begun on the active management module which initiates the upgrade process
on the standby management module.
4.
The standby management module is reset.
5.
The active management module is reset and the standby management module assumes control as the active
module.
6.
Active console control is lost to the previously active management module as it becomes the standby
management module.
7.
The active management module initiates the upgrade process on all interface modules.
8.
The router 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.
Figure 7.1 provides a detailed diagram of the Hitless reload process.
