High Availability FailOver/iX Manual (32650-90911)

Recovering From a Failover

Special Considerations

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

High Availability Failover Device Status

Ldev Primary Path Alternate Path Pri. Status Alt. Status

===== ==================== ================== =============== ===============

350 0/4/0/0.70954.24 0/6/0/0.73289 Ready Validated

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

This indicates that Ldev 351 has failed over from path 0/4/0/0.70954 to path

0/6

/0/0.73289. Because path 0/4/0/0 has suffered a hardware failure, Ldev 351

may NOT mount if the system is rebooted before the hardware is repaired. If the

system must be rebooted before the hardware is repaired, then there must be

some changes made in the "io" section of SYSGEN. Ldev 351 must be

configured onto path 0/6

/0/0. For example:

io> mdev 361 path=0/6/0/0.73289.24

io> hold

io> e

sysgen> keep

Now when the system is rebooted, Ldev 351 will mount on path 0/6/0/0 and will

be available for access.

NOTE

Near the end of the boot process, there will be an error message stating:

Invalid Primary Path for this Ldev. - (HAFOERR 500)

This is because Ldev 351 is still configured in the HAFOCONF file as having

0/4/0/0 as it's primary path. In this special case this error can be ignored.

However, Ldev 351 is not covered by HAFO and path 0/4

/0/0 should be

repaired as soon as possible. (Note also that Ldev 350 is also not covered by

HAFO since path 0/4/0/0 is physically broken.)