Hitless os upgrade configuration steps, Loading the software onto the switch, Performing a hitless upgrade – Brocade FastIron Ethernet Switch Administration Guide User Manual
Page 122: Syslog message for hitless management events
Hitless OS upgrade configuration steps
The following is a summary of the configuration steps for a hitless OS software upgrade.
1. Copy the software image that supports hitless software upgrade from a TFTP server to the FastIron
Loading the software onto the switch
2. Install the software image in flash memory on the active and standby management modules.
3. Enter the hitless-reload command on the active management module. The command triggers the
events described in the section
What happens during a Hitless OS upgrade
Loading the software onto the switch
Hitless OS upgrade loads from the primary and secondary images on the FSX 800 and FSX 1600
Management modules. If you will be using the hitless-reload command to perform the hitless
upgrade, you must first copy the software image that supports hitless software upgrade onto the flash
memory of the active and standby management modules. For instructions, refer to the release notes.
Performing a hitless upgrade
After loading the software image onto the flash memory of the active and standby management
modules, you can begin the process of performing a hitless OS upgrade using the hitless-reload
command. For example,
device#hitless-reload primary
Syntax: hitless-reloadprimary | secondary
The primary parameter specifies that the management module will be reloaded with the primary
image.
The secondary parameter specifies that the management module will be reloaded with the secondary
image.
NOTE
The hitless-reload command is accepted only when the running configuration and startup
configuration files match. If the configuration file has changed, you must first save the file (write
mem ) before executing a hitless reload. Otherwise, the following message will display on the
console.Error: Running config and start-up config differs. Please reload the system or save the
configuration before attempting hitless reload.
Syslog message for Hitless management events
The following Syslog message is generated as a result of a switchover or hitless OS upgrade.
SWITCHOVER COMPLETED - by admin - Mgmt Module in slot
slotnum
is now Active
The following Syslog message is generated as a result of a failover.
SWITCHOVER COMPLETED - by active CPU failure - Mgmt Module in slot
slotnum
is now Active
Hitless OS upgrade configuration steps
122
FastIron Ethernet Switch Administration Guide
53-1003075-02