Viewing Node Status - Extreme Networks ExtremeWare XOS Guide Manual

Managing the Switch
Dynamic Checkpointing
After an application transfers its saved state to the backup MSM, dynamic checkpointing requires that
any new configuration information or state changes that occur on the master be immediately relayed to
the backup. This ensures that the backup has the most up-to-date and accurate information.
Viewing Checkpoint Statistics
Use the following command to view and check the status of one or more processes being copied from
the master to the backup MSM:
show checkpoint-data {<process>}
This command is also helpful in debugging synchronization problems that occur at run time.
This command displays, in percentages, the amount of copying completed by each process and the
traffic statistics between the process on both the master and the backup MSMs.

Viewing Node Status

ExtremeWare XOS allows you to view node statistical information. Each node installed in your system
is self-sufficient and runs the ExtremeWare XOS management applications. By reviewing this output,
you can see the general health of the system along with other node parameters.
To view node status, use the following command:
show node {detail}
Table 9 lists the node status collected by the switch.
Table 9: Node states
Node State Description
BACKUP In the backup state, this node becomes the master node if the master fails or enters the DOWN
state. The backup node also receives the checkpoint state data from the master.
DOWN In the down state, the node is not available to participate in leader election. The node enters this
state during any user action, other than a failure, that makes the node unavailable for
management. Examples of user actions are:
• Upgrading the software
• Rebooting the system using the
• Initiating an MSM failover using the
• Synchronizing the MSMs software and configuration in non-volatile storage using the
synchronize
FAIL In the fail state, the node has failed and needs to be restarted or repaired. The node reaches this
state if the system has a hardware or software failure.
INIT In the initial state, the node is being initialized. A node stays in this state when it is coming up
and remains in this state until it has been fully initialized. Being fully initialized means that all of
the hardware has been initialized correctly and there are no diagnostic faults.
MASTER In the master state, the node is responsible for all switch management functions.
STANDBY In the standby state, leader election occurs—the master and backup nodes are elected. The
priority of the node is only significant in the standby state.
ExtremeWare XOS 11.1 Concepts Guide
command
reboot
run msm-failover
command
command
54