Triggering A Failover - HP e3000 MPE/iX Manual

Product Description
User Notification of Failover
HAFO event information and data structures are memory resident. This
eliminates the need for disk file access to perform high availability failover. This
is an advantage especially if the path should fail to Ldev#1.
To configure and manage the HAFO functions there is a new section of the
SYSGEN program for HAFO called "HA" (short for HAUTIL). The "ha"
section is accessed through SYSGEN's "io" menu. That is, you run SYSGEN,
type "io" at the SYSGEN prompt, then type "ha" at the "io" prompt. No failover
action is taken until the Ldevs are configured for HAFO in the "ha" section of
SYSGEN. Device data path and alternate data path information is entered and
saved in SYSGEN's HAFOCONF configuration file. HAFOCONF configurations
are read and validated during each subsequent system boot. Specific
configuration information is provided in the Chapter 4, "Configuration."
Figure 2-1 illustrates a sample configuration. This figure can be compared
against Figure 2-2, which illustrates a failover of the same system.
Figure 2- 1
Ldev 1
Ldev 30
File
System
Ldev 31
Volume
Mgmt
Ldev 101
Ldev 102
Ldev 103

Triggering a Failover

HAFO acts on only specific error types that indicate a data path failure. Any of
these three occurrences will generate a failover:
•
•
•
10
Normal System Layout
MPE/iX
DM
DM
DM
DM
DM
DM
Hung I/O
Failed high availability array controller (communicated by a SCSI reply status)
Failed host device adapter card
High Availability Array
Logical Physical
(view)
D
D
A
SCSI
A
bus
M FC
D
D
A
A
SCSI
M bus
FC
A
1
r
r
a
30
y
C
o
n
31
t
A 101
r
r
a
y
102
C
o
n
103
t