Managing Serviceguard 14th Edition, June 2007

Building an HA Cluster Configuration
Configuring the Cluster
Chapter 5 235
-w full lets you specify full network probing, in which actual
connectivity is verified among all LAN interfaces on all nodes in the
cluster. This is the default.
-w none skips network querying. If you have recently checked the
networks. this option will save time.
For more details, see the cmquerycl(1m) man page.
The example above creates an template file, by default
/etc/cmcluster/clust1.config. In this output 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.
The cmquerycl man page for the command further defines 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 you filled in on the cluster
worksheet.
NOTE HP strongly recommends that you modify the file so as to send heartbeat
over all possible networks.
Specifying a Lock Disk
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 “Cluster Lock” in Chapter 3 for additional
information.
To create a lock disk, 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 connected to all cluster nodes;
if there is more than one, the disk is chosen on the basis of 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.