Managing Serviceguard Eighteenth Edition, September 2010

NOTE: You should not configure a second lock volume group or physical volume
unless your configuration specifically requires it. See “Dual Lock Disk” (page 64).
If your configuration requires you to configure a second cluster lock, enter the following
parameters in the cluster configuration file:
SECOND_CLUSTER_LOCK_VG /dev/volume-group
SECOND_CLUSTER_LOCK_PV /dev/dsk/block-special-file
where volume-group is the name of the second volume group and
block-special-file is the physical volume name of a lock disk in the chosen
volume group. These lines should be added for each node; for example:
SECOND_CLUSTER_LOCK_VG /dev/vglock
SECOND_CLUSTER_LOCK_PV /dev/dsk/c4t0d0
or (using agile addressing; see About Device File Names (Device Special Files)”
(page 106)):
SECOND_CLUSTER_LOCK_VG /dev/vglock
SECOND_CLUSTER_LOCK_PV /dev/disk/disk100
NOTE: If you are using cDSFs, the device file would be in the /dev/rdisk/ directory;
for example /dev/rdisk/disk100. See About Cluster-wide Device Special Files
(cDSFs)” (page 135).
See also “Choosing Cluster Lock Disks” (page 225).
Specifying a Lock LUN
A cluster lock disk, lock LUN, or Quorum Server, is required for two-node clusters.
The lock must be accessible to all nodes and must be powered separately from the
nodes. See also “Cluster Lock (page 62); and see “Setting Up a Lock LUN” (page 226)
for configuration information and restrictions.
To specify a lock LUN in the cluster configuration file, enter the lock LUN information
following each node name, for example:
NODE_NAME hasupt21
NETWORK_INTERFACE lan1
HEARTBEAT_IP 15.13.173.189
NETWORK_INTERFACE lan2
NETWORK_INTERFACE lan3
CLUSTER_LOCK_LUN /dev/dsk/c0t1d1
Configuring the Cluster 247