Managing Serviceguard 12th Edition, March 2006

Building an HA Cluster Configuration
Configuring the Cluster
Chapter 5 225
Using Serviceguard Commands to Configure the
Cluster
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.
Node names must be 31 bytes or less. Here is an example of the
command:
# cmquerycl -v -C /etc/cmcluster/clust1.config -n ftsys9 -n
ftsys10
The example creates an ASCII template file in the default cluster
configuration directory, /etc/cmcluster. The ASCII file is partially
filled in with the names and characteristics of cluster components on the
two nodes
ftsys9 and ftsys10 . Do not include the domain name when
specifying the node name; for example, specify
ftsys9 and not
ftsys9.cup.hp.com . Edit the filled-in cluster characteristics as needed
to define the desired cluster. It is strongly recommended that you edit
the file to send heartbeat over all possible networks, as shown in the
following example.
NOTE In a larger or more complex configuration with many nodes, networks or
disks connected to the cluster, the cmquerycl command may require
several minutes to complete. In order 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.
-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 complete details, refer to the man page on cmquerycl(1m).