Building Disaster Tolerant Serviceguard Solutions Using Metrocluster with Continuous Access EVA
Preparing a Serviceguard Cluster for Metrocluster Continuous Access EVA
Chapter 4 255
/dev/dsk/c9t0d2 Active
/dev/dsk/c15t0d2 Active
/dev/dsk/c21t0d2 Active
/dev/dsk/c4t0d2 Active
/dev/dsk/c10t0d2 Active
/dev/dsk/c16t0d2 Active
/dev/dsk/c22t0d2 Active
From the output display identify the device file listing that corresponds
with the WWN of the vdisk in the DR group.
In the above sample listing there are eight device files that correspond to
different paths of the same vdisk. Use any one of the device file names
while creating a volume group, which is described in section, “Creating
Volume Groups using Source Volumes for Secure Path v3.0D, v3.0E, and
v3.0F”. The EVA CV display can be used to identify the WWN for a
vdisk.
Identifying Special Device Files for PVLinks Configuration
LVM PVlink feature can be used to handle path failovers to a storage
device. The following describes how to identify device files for a Vdisk
while setting up volume group using PVlinks. Use the RSM HV Mapper
Tool to display the special device files that correspond to the WWN of the
vdisk in the DR group with the following command:
# RSM_HV Mapper.pl
Collecting Host Volume info might take time. Please wait.
Collecting Host Volume info from mc-node1.cup.hp.com.
Collecting Host Volume info from mc-node2.cup.hp.com.
Collecting Host Volume info from mc-node3.cup.hp.com.
Collecting Host Volume info from mc-node4.cup.hp.com.
Collecting Host Volume data done.
See HostVolTable.txt for results.
The HostVolTable.txt output file provides a mapping of the devices file to
vdisks for all the hosts that are RSM enabled. In addition, the tool
displays the WWID of the vdisk and the storage system to which the
vdisk belongs.