Configuration Map - HP e3000 MPE/iX Manual

The SYSGEN (io) configured SCSI target & LUN that is being used on a
primary path cannot be configured in the (io) section of SYSGEN on the
alternate path. (Configuration restriction #3)
For example, if the path for Ldev 1 were 8.0.0, and the alternate path were 48,
then one should not use 48.0.0 for any of the Ldevs on that path. None of the
Ldevs 101-103 could be configured as 48.0.0. A correct configuration would be
to make Ldevs 1, 30, and 31 be 8.0.0, 8.1.0, and 8.2.0. Then make Ldevs 101,
102, 103 be 48.3.0, 48.4.0, and 48.5.0. Now Ldevs 1, 30, and 31 can failover to
path 48 and Ldevs 101–103 can failover to path 8 with no conflicts.
Again, HAFO does not address the hardware configuration of the array itself. In
the example above, the array itself would have to be pre-configured to allow the
top controller to talk to the Ldevs on the bottom and to allow the bottom
controller to talk to the Ldevs on the top.
Each controller on the array that is to be used must be connected to a single host
adapter card. All host adapters to be used in HAFO configuration must be
configured in SYSGEN and present at the time you issue an ISL>START
command to boot MPE/iX.

Configuration Map

Creation of a configuration map is crucial. Proper planning, mapping, and
maintenance of the map are critical to the successful use of HAFO. Without a
proper plan and up-to-date map, troubleshooting will be difficult and system
availability will not be optimized.
The following is a checklist of the steps required to enable HAFO:
1. Select the array and volume-set(s) to be configured for HAFO. Ldev 1 and
the system volume set can be configured for HAFO. HAFO depends on
information stored in MPE/iX Disk Volume Labels. New Volumes or
Volume Sets must be created using VOLUTIL before a disk Ldev is
configured in HAFO.
2. Identify the logical data paths of the Host Bus Adaptors for each pair of
controllers in the array. One path will be the primary path, fully qualified,
and the other will be the alternate data path.
3. Ensure that all paths (I/O adapter cards and Ldevs) are configured and
recognized when the system is booted..
4. Create a map of exactly how the layout will look, including the path pairs
and each Ldev on each path. Include the addresses of each card and Ldev,
and clearly show the failover scheme.
Configuration
Planning
19