High Availability FailOver/iX Manual (32650-90911)

Appendix-A
A Sample Failover and Recovery
The following scenario illustrates a possible HAFO situation.
Sample Scenario
The following is a sample HAFO status report extracted from a HASTAT
display. The report shows several failover statuses which are explained in
succeeding sections of this appendix. Troubleshooting advice for this sample
scenario is also provided.
High Availability Failover Device Status
Ldev Primary Path Alternate Path Pri. Status Alt. Status
===== ==================== ================== =============== ===============
350 0/4/0/0.70954.23 0/6/0/0.73289 Array Failure Ready
351 0/4/0/0.70954.24 0/6/0/0.73289 Array Failure Ready
352 0/6/0/0.73289.25 0/4/0/0.70954 Ready Validated
353 0/6/0/0.73289.26 0/4/0/0.70954 Ready Validated
450 0/6/2/1.3.3 0/6/2/0 Ready Validated
451 0/6/2/1.3.4 0/6/2/0 Timeout/No Reply Ready
452 0/6/2/0.3.5 0/6/2/1 Ready Validated
453 0/6/2/0.3.6 0/6/2/1 Ready Validated
Incidents Summary
Bus path "0/4/0/0" has failed and all configured HAFO Ldevs (Ldev 350 and
351) have detected the path failure and have successfully failed over to their
alternate path "0/6/0/0".
Ldev 352 and 353 are still operating using their primary paths and require no
action.
Ldev 451 has detected a timeout due to very slow array response time probably
caused by too many I/Os generated by the application for the array to handle.
Corrective Action: Failure on System Path "0/4/0/0…"
The system needs to be shutdown;use the diagnostics to isolate the failing
component in bus path "0/4/0/0.70954". Failing candidates are: host device
adapter card, cable, array controller or router. Each component needs to be
verified. (As per 7.5 Communicator, “FSCAN –h” and “TDUTIL” may be
helpful for FC devices.)
49