Brocade Fabric OS Message Reference - Supporting Fabric OS v5.3.0 (53-1000437-01, June 2007)

Fabric OS Message Reference 235
53-1000437-01
Chapter
28
HAM System Messages
HAM-1001
Message <timestamp>, [HAM-1001], <sequence-number>, FFDC, CRITICAL, <system-name>,
Standby CP is not healthy, device <device name> status BAD, Severity = <Log="YES"
Class="NONE" Severity>
Probable Cause Indicates that a standby control processor (CP) device error is reported by the high-availability
manager (HAM) Health Monitor, with a specific device and Log="YES” Class=”NONE" Severity level.
The severity level can be “critical”, “major”, or “minor”.
The active CP will continue to function normally, but because the standby CP is not healthy,
non-disruptive failover is not possible.
Recommended
Action
Reboot the standby CP blade by ejecting the card and reseating it.
If the problem persists, replace the standby CP.
Severity CRITICAL
HAM-1002
Message <timestamp>, [HAM-1002], <sequence-number>,, INFO, <system-name>, Standby CP is
healthy.
Probable Cause Indicates that all of the standby control processor (CP) devices monitored by the high-availability
manager (HAM) Health Monitor report no error.
Recommended
Action
No action is required.
Severity INFO
HAM-1004
Message <timestamp>, [HAM-1004], <sequence-number>,, INFO, <system-name>, Processor
rebooted -
<Reboot Reason>.
Probable Cause This message records switch processor reboot reasons that were initiated by the user or the switch
errors. The switch processor reboots can be initiated by the firmwareDownload, fastBoot,
haFailover, and reboot commands. Some examples of errors that might initiate this message are
hardware errors, software errors, compact flash errors, or memory errors. The reboot reasons can
be any of the following:
• Hafailover