Managing Serviceguard 11th Edition, Version A.11.16, Second Printing June 2004

Building an HA Cluster Configuration
Configuring the Cluster
Chapter 5 221
# is also still supported for compatibility with earlier versions.)
# For example:
# OPS_VOLUME_GROUP /dev/vgdatabase
# OPS_VOLUME_GROUP /dev/vg02
The man page for the cmquerycl command lists the definitions of all the
parameters that appear in this file. Many are also described in the
“Planning” chapter. Modify your /etc/cmcluster/clust1.config file
to your requirements, using the data on the cluster worksheet.
In the file, keywords are separated from definitions by white space.
Comments are permitted, and must be preceded by a pound sign (#) in
the far left column. See the man page for the cmquerycl command for
more details.
Specifying a Lock Disk
A cluster lock is required for two node clusters like the one in this
example. The lock must be accessible to all nodes and must be powered
separately from the nodes. Refer to the section “Cluster Lock” in Chapter
3 for additional information. Enter the lock disk information following
the cluster name. The lock disk must be in an LVM volume group that is
accessible to all the nodes in the cluster.
The default FIRST_CLUSTER_LOCK_VG and FIRST_CLUSTER_LOCK_PV
supplied in the ASCII template created with cmquerycl are the volume
group and physical volume name of a disk chosen based on minimum
failover time calculations. You should ensure that this disk meets your
power wiring requirements. If necessary, choose a disk powered by a
circuit which powers fewer than half the nodes in the cluster.
To display the failover times of disks, use the cmquerycl command,
specifying all the nodes in the cluster. Do not include the node’s entire
domain name; for example, specify ftsys9 not ftsys9.cup.hp.com:
# cmquerycl -v -n ftsys9 -n ftsys10
The output of the command lists the disks connected to each node
together with the re-formation time associated with each.