Upgrading Software Images and Configuration Files
December 2008
© 2008 Foundry Networks, Inc.
7-31
Performing a Hitless OS Software Upgrade,
To perform a Hitless OS software upgrade, you must perform the following tasks:
•
Copy Version 03.2.01 or later of the Multi-Service IronWare software to the primary and secondary image on
both the active and standby management modules and interface modules.
•
Set up a console connection to both the active and standby management modules. These connections can
be through a telnet, SSH, or serial console session.
•
Type the
hitless-reload
command at the console of the active management module.
Loading the Multi-Service IronWare Software onto the Router
Hitless OS Upgrade loads from the primary and secondary images on the management modules. The first step in
performing a Hitless OS Upgrade is to copy the Version 03.2.01 or later images into the flash memory of the active
and standby management modules.
For instructions for copying these files, see “Upgrading the Management Module’s Monitor and Boot Images” on
page 7-14 and“Upgrading the Management Module’s IronWare Image” on page 7-15.
Setting up Consoles
Hitless OS Upgrade is executed at the active management module. During the process of upgrading the image,
control of the router shifts to the standby management module. For this reason, you need to have management
sessions enabled on both the active and the standby management modules. When the reload is complete, the
management module that was in the standby condition at the beginning will be in the active state. If you want the
original management module to be active, you must manually fail-over control to it.
Executing the Hitless Upgrade Command
To begin the process of a Hitless Upgrade, use the following command:
NetIron(config)# hitless-reload mp primary lp primary
Syntax:
hitless-reload mp [primary | secondary ] lp [primary | secondary]
The
mp
parameter specifies that the management module will be reloaded with either the
primary
or
secondary
image as directed.
The
lp
parameter specifies that the management module will be reloaded with either the
primary
or
secondary
image as directed.
Loading and Saving Configuration Files
For easy configuration management, the router supports both the download and upload of configuration files
between the router and a TFTP server on the network. You can also copy the startup configuration file locally
between the management module’s code flash and a PCMCIA flash card inserted in the management module’s
slot 1 or 2.
You can upload either the startup configuration file or the running configuration to the TFTP server, code flash, or
a flash card for backup and use in booting the system.
•
Startup configuration file
– This file (startup-config) contains the configuration information that is currently
saved in the management module’s code flash. To display this file, enter the
show configuration
command
at any CLI prompt.
•
Running configuration
– This active configuration is in the system RAM but not yet saved to code flash.
These changes could represent a short-term requirement or general configuration change. To display this
configuration, enter the
show running-config
or
write terminal
command at any CLI prompt.
Each device can have one startup configuration file and one running configuration. The startup configuration file is
shared by both flash modules. The running configuration resides in DRAM.
