MPX Redundancy
Page 2-10
The primary MPX has the ability to transfer files to and from the secondary MPX. In the condi-
tion where the secondary MPX has an older version of software (Software Fallback), it is not
desirable to update the configuration file of the secondary. It is therefore the default not to
update the configuration file on the secondary if the secondary is running an earlier version
of software. You can force the update using appropriate commands in the mpm menu. (See
Chapter 6, “Configuring Management Processor Modules,” for more information on commands
in the mpm menu.)
♦ Note ♦
Do not remove a primary MPX without performing a
renounce command (described in Chapter 6, “Configur-
ing Management Processor Modules”) first.

MPX Redundancy Commands

A set of commands exists to monitor the primary and secondary MPXs. These commands are
covered in detail in Chapter 6, “Configuring Management Processor Modules.” Note that you
can attach a terminal to both MPXs in a chassis; however, you will see a different responses
depending on which is primary and which is secondary. You should execute all UI
commands from the primary MPX except for those commands specifically addressing the
secondary MPX. For example, commands are available to control and monitor the secondary
MPX from the primary MPX (e.g., the sls command lists files on the secondary MPX from the
primary MPX).
MPX State Requirement for State
Redundant Both MPXs are running the same version of software
and the configurations are in sync.
Configuration Fallback Both MPXs are running the same version of software
but the configurations are different.
Software Fallback The MPXs are running different versions of software,
and their configurations may be the same or different.
None There is only one MPX installed in the chassis.