Failover Status Descriptions
MPE documents | |
 Complete PDF | |
| Table of Contents | |
| E0803 Edition 2 | |
| E1100 Edition 1 ♥ |
Array Failure
Failover Failed
GOBack started
Not HAFO dev
Ready
Unknown failure
Unknown status
Array Failure
When this status is generated, the device adapter reported its failure via a SCSI message that was monitored and acted upon by HAFO. Failover occurred and data requests to the high availability array have been rerouted to the alternate data path. Normal system I/O activity continues.
Failover Failed
This status means a failure has occurred on the primary path. When failover was attempted, the alternate path was unavailable. The alternate path has failed due to a data path fault or misconfiguration. Troubleshoot this instance by repairing the failure on the primary and alternate paths.
GOBack Started
This message appears only after the goback command has been executed. If goback is still running when a HAFO device status report is run (highly unlikely), this message will appear. Run the HAFO device status report again. The "Goback started" message should be replaced by the actual status.
Not HAFO dev
This status message indicates that the ldev on the path is not a high availability array. High availability failover is available only with the XP256.
Ready
The Ready status shown for LDEV 102 in the sample report (above) indicates that I/O is being processed via the primary path. No failure or failover has occurred. The Ready status is shown for all alternate paths in the sample report. This indicates that no change has occurred in the status of the alternate path since the doha command was last executed.
Unknown Failure
This state reflects the fact that the path not functioning due to a condition that could not be determined. Possible causes for this are:
The hose adapter is not responding
Cabling is broken or not carrying data
Array controller not responding
Unknown Status
The I/O subsystem has sent an unknown path status. Contact your HP Support representative to report the problem.
|
Failver Status Report |
Chapter 6 Recovering From a Failover |