Extreme Networks ExtremeWare XOS 11.3, Manual

Page: 71 / 698

Understanding System Redundancy with Dual MSMs Installed—Modular Switches Only
ExtremeWare XOS 11.3 Concepts Guide
71
●
Health of secondary hardware components—This represents the health of the switch components,
such as power supplies, fans, and so forth.
●
Slot ID—The MSM slot where the node is installed (MSM-A or MSM-B).
Configuring the Node Priority
To configure the priority of an MSM node, use the following command:
configure node slot <slot_id> priority <node_pri>
If you do not configure any priorities, MSM-A has a higher priority than MSM-B. For the
slot_id
parameter, enter A for the MSM installed in slot A or B for the MSM installed in slot B. By default, the
priority is 0 and the node priority range is 1 through 100. The lower the value, the higher the priority.
Relinquishing Master Status
You can cause the master to failover to the backup, thereby relinquishing its master status. To cause the
failover, complete the following steps:
1 Use the
show switch {detail}
command to confirm that the nodes are synchronized and have
identical software and switch configurations before failover. The output displays the status of the
MSMs, with the master MSM showing
MASTER
and the backup MSM showing
BACKUP (InSync)
.
A node may not be synchronized because checkpointing did not occur, incompatible software is
running on the master and backup, or the backup is down.
●
If the nodes are not synchronized, and both MSMs are running ExtremeWare XOS 11.0 or later,
proceed to step
2 .
●
If the nodes are not synchronized, and one MSM is running ExtremeWare XOS 10.1 or earlier,
proceed to step
3 .
●
If the nodes are synchronized, proceed to step 3 .
2 Use the
synchronize
command to ensure that the backup has the same software in flash as the
master.
NOTE
On the BlackDiamond 10K switch, both the backup and the master MSMs must be running ExtremeWare XOS
11.0 or later to use the
synchronize
command.
The
synchronize
command:
●
Reboots the backup MSM to prepare it for synchronizing with the master MSM
●
Copies both the primary and secondary software images
●
Copies both the primary and secondary configurations
●
Reboots the backup MSM after replication is complete
3 Initiate failover from the master MSM to the backup MSM.
●
If both nodes are running ExtremeWare XOS 11.0 or later, use the
run msm-failover
command.
●
If one node is running ExtremeWare XOS 10.1 or earlier, use the
run msm-failover {force}
command. By specifying
force
, failover occurs regardless of the version of software running on
the MSMs.