|
|
Once the configuration file is built for a specific SYSGEN
base configuration, the ldevs must be configured for HAFO with their primary
and alternate paths. Fully qualified paths are required. Research
and obtain this information prior to configuration. The syntax is:
AD <LDEV> <LDEV primary device path> <alternate device
adapter card path>
A data path consists of the fast-wide host adapter and fast-wide
SCSI bus connected to the high-availability array. For example:
ha> ad 90 8.0.1 16
 |
NOTE: The second parameter is the fully qualified ldev path while the
third parameter is only the path of the device adapter card itself.
|
The hardware must be in place, configured through SYSGEN,
and initialized at system boot time before issuing this command.
The ldev specified must be mounted in the MEMBER or MASTER state.
Once added using addconf, the primary and alternate paths are checked
for availability against internal system I/O tables. If the ldev cannot be
accessed through both paths specified, then an error will be issued and the
ldev will NOT be added to the configuration. Although this makes
it much more difficult to make configuration mistakes, it also prohibits
the creation of HAFO configurations for other systems that are different
than the present system.
The example paths are simple. Actual paths in your environment
are probably more complicated. (See the Configuration Checklist
section of this chapter.) Any omission or error in the path could
result in an error during the doha command.
 |
NOTE: Because HAFO works in pairs, the very first successful
ADDCONF command that is entered (and applied, see the doha
command) links all the ldevs on those two paths. All ldevs on the primary path
specified must be configured to failover to the alternate path specified.
Further all the ldevs on the alternate path specified, if any exist, must be
configured to failover to the primary path specified in the first
ADDCONF command specifying these paths. See
Figure 4-1 "Configuring HAFO in Pairs" for
more information.
|
|