Foundry NetIron MLX Series Installation and Basic Configuration Guide
7-26
© 2008 Foundry Networks, Inc.
December 2008
module only. If you specify all without a module-type, the router copies the appropriate STATS images to their
corresponding modules.
NOTE:
Use this command to upgrade the STATSOC FPGA image to a POS interface module.
6.
Once the FPGA upgrade is complete, the new FPGA images will take effect at the next system reload.
Alternately, you can make the FPGA image take effect on an interface module without reloading the
management module, by power cycling the interface module by either of the following two methods.
•
Power off and power on the Interface module by first using the
power-off lp
<slot> command and then
the
power-on lp
<slot> command.
•
Pull out and then reinsert the Interface module.
7.
Upon boot-up of the interface module, the
FPGA Version Check
utility is run to make sure that compatible
versions of the FPGA images are installed on the router. Upon boot-up or when the
show version
command
is typed, the following will be displayed.
Valid PBIF Version = 0.1, Build Time = 9/16/2005 10:18:0
Valid XPP Version = 0.2, Build Time = 9/25/2005 23:5:0
Valid XGMAC Version = 0.2, Build Time = 9/23/2005 12:3:0
Also, one of the following warnings will be displayed if there is a problem with your FPGA installation.
WARN: Invalid FPGA version = 1.2, Build Time = 9/13/2005 13:20:0 <<<---
If this warning message is displayed it indicates that you have an FPGA version mismatch, or one of the
versions is not up-to-date.
ERROR: failed to read FPGA versions from flash <<<---
If this warning message is displayed it indicates that you haven't done a mandatory FPGA upgrade yet.
Rebooting the Management Module
After upgrading one or more software images on the management or interface modules, you must reboot the
management module. After the management module reboots, it in turn reboots the interface modules.
To reboot the management module, enter one of the following commands:
•
reload
(this command boots from the default boot source, which is the primary code flash)
•
boot system flash
primary | secondary
During the management module reboot, the following synchronization events occur:
•
If you have a standby management module, the active management module compares the standby module’s
monitor, primary, and secondary images to its own. If you have updated these images on the active module,
the active module automatically synchronizes the standby module’s images with its own.
•
If you copied the primary and/or secondary IronWare image to all interface modules using the
copy
command
with the
all
keyword, the management module made a copy of the image and stored it in its code flash under
the names lp-primary-0 or lp-secondary-0. By default, the system checks the interface modules’ IronWare
images, which reside in the code flash of the interface modules and the management module to make sure
they are the same in both locations. (These IronWare images are stored on the management module only
and are not run by the management or interface modules.) If the IronWare images on the interface and
management modules are different, the system prompts you to do the following:
•
If you want to update the IronWare images in the interface module’s code flash with the images in the
management module’s code flash, 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 code flash, enter the
lp cont-boot no-
sync <slot-number>
command at the Privileged EXEC prompt.
After the management module finishes booting, do the following:
