Managing HP Serviceguard for Linux Ninth Edition, April 2009

Configuring the Cluster
This section describes how to define the basic cluster configuration. This must be done
on a system that is not part of a Serviceguard cluster (that is, on which Serviceguard
is installed but not configured). You can do this in Serviceguard Manager, or from the
command line as described below.
Use the cmquerycl command to specify a set of nodes to be included in the cluster
and to generate a template for the cluster configuration file.
IMPORTANT: See NODE_NAME under “Cluster Configuration Parameters ” (page 100)
for important information about restrictions on the node name.
Here is an example of the command (enter it all one line):
cmquerycl -v -C $SGCONF/clust1.conf -n ftsys9 -n ftsys10
This creates a template file, by default /etc/cmcluster/clust1.conf. 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.
NOTE: HP strongly recommends that you modify the file so as to send heartbeat over
all possible networks.
The manpage for the cmquerycl command further explains the parameters that appear
in this file. Many are also described in Chapter 4: “Planning and Documenting an HA
Cluster ” (page 93). Modify your /etc/cmcluster/clust1.configfile as needed.
cmquerycl Options
Speeding up the Process
In a larger or more complex cluster with many nodes, networks or disks, the cmquerycl
command may take several minutes to complete. To speed up the configuration process,
you can direct the command to return selected information only by using the -k and
-w options:
-k eliminates some disk probing, and does not return information about potential
cluster lock volume groups and lock physical volumes.
-w local lets you specify local network probing, in which LAN connectivity is verified
between interfaces within each node only. This is the default when you use cmquerycl
with the-C option.
(Do not use -w local if you need to discover nodes and subnets for a cross-subnet
configuration; see “Full Network Probing”.)
-w none skips network querying. If you have recently checked the networks, this
option will save time.
Configuring the Cluster 171