Managing Serviceguard Nineteenth Edition, Reprinted June 2011

Note that the clearimport is done for disks previously imported with noautoimport set on
any system that has Serviceguard installed, whether it is configured in a cluster or not.
Configuring the Cluster
This section describes how to define the basic cluster configuration using traditional Serviceguard
commands. 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).
NOTE: You can use Serviceguard Manager to configure a cluster: open the System Management
Homepage (SMH) and choose Tools-> Serviceguard Manager. See “Using Serviceguard
Manager” (page 23) for more information.
You can also use Easy Deployment commands; see“About Easy Deployment” (page 100) and “Using
Easy Deployment Commands to Configure the Cluster” (page 153).
To use traditional Serviceguard commands to configure the cluster, follow directions in the remainder
of this section.
Use the cmquerycl (1m) 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 the entry for NODE_NAME under “Cluster Configuration Parameters ” (page 105)
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 the heartbeat over all
possible networks. See also HEARTBEAT_IP under “Cluster Configuration Parameters ” (page 105),
and “Specifying the Address Family for the Heartbeat ” (page 178).
The cmquerycl(1m) manpage further explains the calling parameters as well as those that appear
in the template file. See also “Cluster Configuration Parameters ” (page 105). Modify your /etc/
cmcluster/clust1.conf file 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” below.)
-w none skips network querying. If you have recently checked the networks, this option will save
time.
Configuring the Cluster 177