Upgrading Software Images and Configuration Files
December 2008
© 2008 Foundry Networks, Inc.
7-37
•
Running-config – The running-config file resides in the NetIron MLX Series system memory.
The NetIron MLX Series and NetIron MLX Series routers allow you to do the following related to file
synchronization:
•
Compare files on the active module with files on the standby module and immediately synchronize any files
that are different.
•
Immediately synchronize all files between the active and standby modules.
The following sections explain how to perform these tasks.
Comparing and Synchronizing Files
You can initiate a comparison of the flash code, system-config file, and running-config file on the active
management module with the same files on the standby module and synchronize the files immediately if
differences exist. When you synchronize the files, the active module copies its files to the standby module,
replacing the files on the standby module.
To compare and immediately synchronize files between the active and standby modules if differences exist, enter
the following command at the Privileged EXEC level of the CLI:
NetIron# sync-standby
Syntax:
sync-standby
Synchronizing Files Without Comparison
You can synchronize the flash code, system-config file, and running-config file immediately without comparison.
When you synchronize the files, the active module copies its files to the standby module, replacing the files on the
standby module.
To immediately synchronize the files between the active and standby modules, enter the following command at the
Privileged EXEC level of the CLI:
NetIron# force-sync-standby
Syntax:
force-sync-standby
File Synchronization Between the Management and Interface Modules
An interface module can have two
IronWare images: primary and secondary. These images contain the layer 1 – 3
software that the interface modules run. These images reside in the interface module’s flash memory. Either the
primary or secondary image is run by the interface module from this location.
If you copy the primary and/or secondary IronWare image to all interface modules using the
copy
command with
the
all
keyword, the management module makes a copy of the file and stores it in its code flash under the names
lp-primary-0 or lp-secondary-0. The images are stored in this location only and are not run by the management
module or the interface modules. If you copy the primary and/or secondary IronWare image to a specified chassis
slot using the
copy
command with the <chassis-slot-number> parameter, the management module does not
make a copy of the file.
If the management module has a copy of the primary and/or secondary IronWare image in its code flash, by
default, the router synchronizes or prompts you to synchronize the interface modules IronWare images between
the management module and the interface modules during bootup. When the router synchronizes the IronWare
images, the management module copies the IronWare images from its code flash to the interface modules’ code
flash (the interface modules’ default boot source).
The system allows you to manage synchronization of the IronWare images between management and interface
modules in the following situations:
•
You are prompted to synchronize the IronWare images during bootup.
•
You want to initiate an immediate synchronization; for example, you want an immediate update of the
IronWare images on one or all interface modules.
•
You want to disable synchronization; for example, you have upgraded the IronWare image of one interface
module but want to continue running the older image on all other interface modules.
