Hashow - Brocade Communications Systems 8 Command Reference Manual

haShow

Displays control processor (CP) status.
Synopsis hashow
Description Use this command to display control processor status. The display includes:
•
•
•
•
•
•
Notes This command may not be supported on nonbladed systems.
Slot numbers for CP1 and CP0 vary depending on the hardware platform. On the Brocade 48000,
CP0 is in slot 5 and CP1 is in slot 6. On the Brocade DCX, CP0 is in slot 6 and CP1 is in slot 7. On the
Brocade DCX-4S, CP0 is in slot 4 and CP1 is in slot 5.
The execution of this command is subject to Virtual Fabric or Admin Domain restrictions that may
be in place. Refer to chapter 1, "Using Fabric OS commands" and Appendix A, "Command
Availability" for details.
Fabric OS Command Reference
53-1001764-02
Local CP state (slot number and CP ID), warm or cold, recovering or recovered.
Remote CP state (slot number and CP ID).
High Availability (enabled or disabled).
Heartbeat (up or down).
The Health of the standby CP is defined as follows:
Healthy The standby CP is running and the background health diagnostic has not
detected any errors.
Failed The standby CP is running, but the background health diagnostic has
discovered a problem with the blade. Check the logs to determine the
appropriate action. Failover is disabled until the standby CP is repaired.
Information about the failing device in the standby CP is displayed.
Unknown The standby CP health state is unknown because of one of the following
reasons: the standby CP does not exist, Heartbeat is down, or the Health
Monitor has detected a configuration file error.
HA synchronization status:
"HA State synchronized"
The system is currently fully synchronized. If a failover becomes necessary, it
is nondisruptive.
"HA State not in sync"
The system is unable to synchronize the two CPs. This may be caused by one
or more of the following conditions:
•
An Failover was issued. In this case the "HA State not in sync" state is
transitory.
•
The standby CP is faulty.
•
An HSyncStop command was issued.
•
A system error occurred.
If a failover becomes necessary while the CPs are not in sync, the standby CP
reboots, and the failover is disruptive.
2
haShow
389