Following is the output that is displayed:

DEVICE_FILE UID S/F PORT TARG LUN SERIAL LDEV PRODUCT_ID /dev/rdsk/c5t0d0 0 F CL3-E 0 0 10053 321 OPEN-3

This output displays the mapping between the legacy DSFs and the CU:LDEVs. In this output the value for LDEV specifies the CU:LDEV without the : mark.

To determine the agile DSFs that are supported from HP-UX 11i v3 and CU:LDEV mapping information run the following command:

# ls /dev/rdisk/* raidscan -find -fx

Following is the output that you will see:

DEVICE_FILE UID S/F PORT TARG LUN SERIAL LDEV PRODUCT_ID /dev/rdisk/disk232 0 F CL4-E 0 0 10053 321 OPEN-3

NOTE: There must also be alternate links for each device, and these alternate links must be on different busses inside the P9000 or XP disk array. For example, these alternate links may be CL2-E and CL2-F.

Unless the devices have been previously paired either on this or another host, the devices will show up as SMPL (simplex). Paired devices will show up as PVOL (primary volume) or SVOL (secondary volume).

XP arrays (XP 10000/XP 12000 and beyond) and P9000 arrays support external attached storage devices to be configured as either P-VOL or S-VOL or both of a Continuous Access pair. From a Continuous Access perspective, there is no difference between a pair created from internal devices and a pair created on external devices.

Refer to the HP StorageWorks P9000 or XP documentation for information on the configuration requirements of external storage devices attached to P9000 or XP arrays and supported external storage devices.

10.Determine which devices will be used by the application package. Define a device group that contains all of these devices. It is recommended that you use a name that is easily associated with the package. For example, a device group name of “db-payroll” is easily associated with the database for the payroll application. A device group name of “group1” would be more difficult to relate to an application.

Edit the Raid Manager configuration file (horcm0.conf) in the above example to include the devices and device group used by the application package. Only one device group may be specified for all of the devices that belong to a single application package. These devices are specified in the field HORCM_DEV.

Also complete the HORCM_INST field, supplying the names of only those hosts that are attached to the P9000 or XP disk array that is remote from the disk array directly attached to this host. For example, with the Continentalclusters shown in Figure 30 (node 1 and node 2 in the source disk site and nodes 3 and node 4 in the recovery cluster), you would specify only nodes 3 and node 4 in the HORCM_INST field in a file you are creating on node 1 on the source disk site. Node 1 would have previously been specified in the HORCM_MON field.

Figure 30 Disaster Tolerant Cluster

166 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP