Foundry FastIron SuperX, Руководство по установке оборудования

Страница: 103 / 198

Using a Redundant Management Module
December 2008 © 2008 Foundry Networks, Inc. 6 - 3
Removal and Replacement of an Active Management Module
If you remove the active management module, the standby module automatically assumes the role of the active
module. After you insert a replacement module in the slot from which the original active module was removed, the
replacement module becomes the standby module. The module boots from the source specified for the active
module. The active management module boots from the active management module’s flash memory.
NOTE: Before removing the active management module, Foundry recommends that you first issue the command
switch-over-active-role . For details, see “Manually Switching Over to the Standby Management Module” on
page 6-5.
After the replacement module boots, the active module compares the standby module’s flash code and system-
config file to its own. If differences exist, the active module synchronizes the standby module’s flash code and
system-config file with its own.
Removal and Replacement of a Standby Management Module
You can remove a standby management module without causing a switchover to occur. The active module
continues to function as is. Communication between the active module and the removed module stops until the
new module is installed in the chassis. After the new module is installed, it assumes the role of standby module.
The module boots from the source specified for the active module. The active management modules boot from the
active management module’s flash memory.
After the module boots, the active module compares the standby module’s flash code and system-config file to its
own. If differences exist, the active module synchronizes the standby module’s flash code and system-config file
with its own.
Switchover Implications
After the role of the active management module switches from one module to another, you must be aware of
implications that affect the following areas:
• Management sessions
• Syslog and SNMP traps
• MAC addresses
The following sections explain the implications for these areas.
Management Sessions
You can establish management sessions with the active management module’s management port. If a switchover
occurs, the management port on the original active module shuts down and all open CLI, Web management
interface, and IronView Network Manager sessions with that port close. You can open new sessions with the new
active module, provided that the new active module has the same management port connections. (For example, if
you were accessing the Web management interface via a PC connected to the original active module’s
management port, you can open a new session if a PC is connected to the new active module’s management
port.)
In the scenario described above, you can open a new session using the same IP address you were using before
the switchover. (You configure an IP address for the active module only; if a switchover occurs, the IP address is
used by the new active module.)
Syslog and SNMP Traps
When a switchover occurs, the system sends a Syslog message to the local Syslog buffer and also to the Syslog
server, if you have configured the system to use one. In addition, if you have configured an SNMP trap receiver,
the system sends an SNMP trap to the receiver.
When the system is powered on or otherwise reset normally, the system sends a cold start message and trap.
However, if the system is reset as the result of switchover to the standby management module, the system instead
sends a warm start message and trap.