Managing Serviceguard Eighteenth Edition, September 2010

NOTE: The actions taken by the commands you will be using are logged to /var/
adm/cmcluster/sgeasy/easy_deployment.log, providing a useful record of
the changes to system files.
1. Obtain networking information for the cluster heartbeat:
cmquerycl –N <network_template_file>
For example:
cmquerycl –N $SGCONF/mynetwork
2. Edit the output file ($SGCONF/mynetwork in this example) to add entries for
additional heartbeats, if necessary.
NOTE: For information about heartbeat and networking requirements, see the
sections listed under “Before You Start” (page 210).
If you omit steps 1 and 2, and all the prospective nodes are connected to at least
one subnet, cmdeploycl behaves as follows (the configuration is actually done
by cmquerycl (1m) which is called by cmdeploycl).
• If multiple subnets are configured among the nodes, cmdeploycl chooses a
subnet with standby interfaces as the heartbeat.
• If multiple subnets are configured, but no subnet has standby interfaces,
cmdeploycl chooses two subnets for the heartbeat.
• If only one subnet is configured, cmdeploycl configures that subnet as the
heartbeat.
CAUTION: If the subnet has no standby interfaces, the cluster will run, but
will not meet high-availability requirements for the heartbeat. You must
reconfigure the heartbeat as soon as possible; see “Changing the Cluster
Networking Configuration while the Cluster Is Running” (page 367).
3. If you have not already done so, create cluster-wide device special files (cDSFs).
This step is optional, but HP strongly recommends it. For instructions, see “Creating
Cluster-wide Device Special Files (cDSFs)” (page 206).
4. Create and start the cluster, configuring security and networking files, creating
and deploying shared storage for an LVM lock disk, and configuring a sample
package:
cmdeploycl –c <clustername> –n <node1> –n <node2> -N
<network_template_file> –b –L <vg>:<pv>
<clustername> must be the unique name for this cluster. <node1> and <node2>
must be the hostname portion, and only the hostname portion, of each node's
212 Building an HA Cluster Configuration