Managing Serviceguard A.11.20, March 2013

NOTE: For information about heartbeat and networking requirements, see the sections listed
under “Before You Start” (page 166).
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 302).
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 164).
4. Create and start the cluster, configuring security and networking files, creating and deploying
shared storage for an LVM lock disk:
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 fully-qualified domain
name (see “Configuring Name Resolution” (page 173) for more information about node names
and hostnames). <network_template_file> is required when you need to configure
networks on the specified nodes; however, this is not mandatory for cluster deployment.
<vg>:<pv>, if used, must be, respectively, a volume group name that does not already exist,
and the name of a physical volume that is unused and is not configured into any volume
manager. HP recommends you use cluster-wide device special files (cDSFs); see “About
Cluster-wide Device Special Files (cDSFs)” (page 109). In any case, the device special file (DSF)
must use the agile addressing convention; see “About Device File Names (Device Special
Files)” (page 81).
For example:
cmdeploycl –c cluster1 –n ftsys9 –n ftsys10 -N $SGCONF/mynetwork –b
–L /dev/vglock:/dev/cdisk/disk13
This command in this example does the following:
• Calls cmapplyconf (1m) to configure the heartbeat subnets specified in $SGCONF/
mynetwork
• Updates $SGCONF/cmclnodelist, /etc/hosts, /etc/nsswitch.conf, and
/etc/inetd.conf on each node.
NOTE: You can also accomplish this by running cmpreparecl; cmdeploycl calls
cmpreparecl.
For more information, see “Configuring Root-Level Access” (page 171) and “Configuring
Name Resolution” (page 173). Those sections describe the “manual” (HP-UX command-line)
method of accomplishing what cmpreparecl does.
168 Building an HA Cluster Configuration