Brocade Network OS Administrator’s Guide v4.1.1 - Manual (Page 85)

Configuring high availability
The following sections provide you with information on configuring High Availability (HA) support on
Brocade switches.
Using HA commands
A variety of high-availability (HA) commands are available on the switch in privileged EXEC mode.
• show ha displays the management module status.
switch# show ha
Local (M2): Active, Cold Recovered
Remote (M1): Standby, Healthy
HA enabled, Heartbeat Up, HA State synchronized
• ha failover forces the active management module to fail over. The standby management module will
take over as the active management module.
• reload system reboots the entire chassis. This command is supported only on the active
management module. This command is not supported on the standby management module. Both
management modules must be in sync for the HA reboot operation to succeed. In logical chassis
cluster mode, this command can be issued from the principal node to reset one remote node or all of
the remote nodes by specifying either the individual rbridge-id or "all".
• ha sync start enables HA state synchronization after an ha sync stop command has been invoked.
• show ha all-partitions displays details for all line cards and the MM HA state.
NOTE
For additional HA commands and related commands, refer to the Network OS Command Reference
Understanding expected behaviors for reload and failover
The following tables identify expected behaviors that result from controlled and uncontrolled reload and
failover conditions.
Expected behaviors for controlled reload and failover TABLE 7
Command syntax Behavior in fabric cluster and logical chassis cluster
reload Cold failover to standby management module (MM).
NOTE
When MMs are out of sync, the reload command does not work. Use the reload system
command to reboot the switch in this case.
reload standby Reboot the standby MM.
reload system Reboot both MMs. MMs will retain the HA roles.
ha failover Warm failover to standby MM.
Configuring high availability
Network OS Administrator’s Guide 85
53-1003225-04