HP ProCurve 1600M, Management And Configuration Manual

Page: 443 / 690

Redundancy (Switch 8212zl)
Downloading a New Software Version
C a u t i o n
If you have booted one module out of primary flash and one module out of
secondary flash, and the secondary flash is running a prior software version
because the latest version was never copied over from the primary flash, you
will have an software version mismatch. The configuration file may not work
with that software version. See “Software Version Mismatch Between Active
and Hotswapped Module” on page 15-16 for more information.
Additionally, if a switchover occurs, or if you reboot to make the standby
module become the active module, any configuration file changes made may
not work on the active module if it has a different software version from the
standby module.
When you enter the
show redundancy
command and a software version
mismatch exists, a warning message is displayed, as shown at the bottom of
Figure 15-11.
When the Config Files are Different
You can also have a situation where you are running the same software on the
active and standby management modules, but the standby module is
configured to use a different configuration file from the active module. When
you enter the
show redundancy
command, this message displays:
Warning: Standby management module is set to use a
different configuration file. Configuration changes
are synchronized to a different configuration file that
the standby management module will not process upon
failover. See “show config files”.
When Both Software Version and Config File are Different
If the software version on the active management module is different from the
software version on the standby module, and the active management module
is configured to use a different configuration file from the standby
management module, this message displays:
Warning: Standby management module is running a
different software version and may be using a different
configuration file. Configuration changes on active
management module may not take effect on a failover.
15-19