Managing Serviceguard Eighteenth Edition, September 2010

NOTE: The procedures that follow assume you are using LVM rather than LVM 2.0.
For information about LVM 2.0 specifically, see the white paper LVM 2.0 Volume Groups
in HP-UX 11i v3, which you can find under www.hp.com/go/hpux-core-docs.
For more information on using LVM in general, including LVM 2.0, see the Logical
Volume Management volume of the HP-UX System Administrator’s Guide at
www.hp.com/go/hpux-core-docs. For more information about the tasks covered
in this section, see Chapter 3 of that guide, and particularly the section on “Common
LVM Tasks”.
Using the EMS Disk Monitor
The Event Monitoring Service HA Disk Monitor allows you to monitor the health of
LVM disks. If you intend to use this monitor for your mirrored disks, you should
configure them in physical volume groups. For more information, see Using High
Availability Monitors at the address given in the preface to this manual.
Using Mirrored Individual Data Disks
The procedures that follow use physical volume groups to allow mirroring of individual
disks such that each logical volume is mirrored to a disk on a different I/O bus. This is
known as PVG-strict mirroring.
Before you proceed, make sure your disk hardware is configured in such a way that a
disk to be used as a mirror copy is connected to each node on a different bus from the
bus that is used for the other (primary) copy.
Creating Volume Groups
NOTE: You can create volume groups by means of the cmpreparestg (1m)
command. See “Using Easy Deployment Commands to Configure the Cluster” (page 211)
for more information. If you use cmpreparestg, you can skip this step and proceed
to “Making Physical Volume Group Files Consistent” (page 238).
Obtain a list of the disks on both nodes and identify which device files are used for the
same disk on both. Use the following command on each node to list available disks as
they are known to each system:
lssf /dev/d*/*
In the following examples, we use /dev/rdsk/c1t2d0 and /dev/rdsk/c0t2d0,
which happen to be the device names for the same disks on both ftsys9 and ftsys10.
In the event that the device file names are different on the different nodes, make a
careful note of the correspondences.
232 Building an HA Cluster Configuration