High Availability Failover Training Session

Recovering from a HAFO Event

Timeout Failover

• Treat this as if it was a hardware

failure. Collect system and diagnostic

log information. This information along

with performance data is needed to

prove that the I/O timeout is due only

to the fact that the storage array can’t keep up with the I/O load

of MPE and is not another cause masquerading as Timeout.

Only after proper diagnostic should you attempt to delete Ldev

451 (DELCONF command) and add it back into HAFO using the

timeout parameter set to FALSE. Remember, setting the parm to

False decreases HAFO protection.

• Ldev 350 and 351 have

encountered an array error and

have switched over successfully.

• Ldev 451 switched over because of

an I/O timeout.