Foundry NetIron MLX Series Installation and Basic Configuration Guide
7-38
© 2008 Foundry Networks, Inc.
December 2008
The following section discuss how to manage the IronWare image synchronization in these situations.
Synchronizing the Interface Modules IronWare Images During Bootup
By default, the router checks the IronWare images in the interface module’s flash memory during boot to ensure
they are is the same as the IronWare images in the management module’s flash memory. If an interface module
does not have an IronWare image, the system automatically downloads the image from the management module’s
flash memory to the interface module’s flash memory.
If an interface module has different IronWare images, the system prompts you to do the following:
•
If you want to update the primary and secondary IronWare images in the interface module’s flash memory
with the images in the management module’s flash memory, enter the
lp cont-boot sync
<slot-number>
command at the Privileged EXEC prompt.
•
If you want to retain the IronWare images in the interface module’s flash memory, enter the
lp cont-boot no-
sync <slot-number>
command at the Privileged EXEC prompt.
Specifying an Immediate Synchronization
You can immediately synchronize the IronWare images between the management module and one or all interface
modules. For example, to immediately synchronize the IronWare images between the management module and
all interface modules, enter the following command at the Privileged EXEC level:
NetIron# lp sync all
Syntax:
lp sync all | <slot-number>
The
all
keyword indicates that the immediate synchronization applies to all interface modules in the NetIron MLX
Series.
The <slot-number> parameter specifies the router’s slot number that contains the interface module to which the
immediate synchronization applies. You can specify 1 – 16.
Scheduling a System Reload
In addition to reloading the router manually, you can configure the system to reload itself at a specific time or after
a specific amount of time has passed.
NOTE:
The scheduled reload feature requires the system clock. You can use a Simple Network Time Protocol
(SNTP) server to set the clock or you can set the device clock manually.
Reloading at a Specific Time
To schedule a system reload for a specific time, use one of the following methods.
To schedule a system reload from the primary flash module for 6:00:00 AM, January 19, 2006, enter the following
command at the Privileged EXEC level of the CLI:
NetIron# reload at 06:00:00 01-19-06
Syntax:
reload at <hh:mm:ss> <mm-dd-yy> [primary | secondary]
<hh:mm:ss> is the hours, minutes, and seconds.
<mm-dd-yy> is the month, day, and year.
primary | secondary
specifies whether the reload is to occur from the primary code flash module or the
secondary code flash module. The default is
primary
.
Reloading After a Specific Amount of Time
To schedule a system reload to occur after a specific amount of time has passed on the system clock, use one of
the following methods.
