Managing HP Serviceguard A.11.20.20 for Linux, May 2013

NOTE: After the configuration is complete, you cannot add the nodes.
• Does not set up lock LUN or quorum server.
• Does not ensure that all other network connections between the servers are valid.
Before You Start
IMPORTANT: The nodes which are given as inputs should not have cluster configured in them.
Before you start, you should have done the planning and preparation as described in previous
sections. You must also do the following:
• Install Serviceguard on each node that is to be configured into the cluster; see “Installing and
Updating Serviceguard ” (page 135).
You must have superuser capability on each node.
• Make sure all the nodes have access to at least one fully configured network.
• Make sure all the subnets used by the prospective nodes are accessible to all the nodes.
Using cmpreparecl to Configure the System
The following example illustrates how to prepare two nodes using the cmpreparecl command:
1. Verify the prerequisites for cluster configuration:
cmpreparecl –n <node1> —n <node2> -p
2. Run the cmpreparecl command with the nodes on which the cluster needs to be configured:
cmpreparecl –n <node1> —n <node2>
3. The cmpreparecl command performs the following actions:
a. Verifies the availability of ports required by Serviceguard. For information about port
requirements on Red Hat Enterprise Linux Server and SUSE Linux Enterprise Server, see
HP Serviceguard A.11.20.20 for Linux Release Notes.
b. Confirms the runlevels of xinetd and set xinetd to run at boot.
c. Enables the ident protocol daemon. Starts authd on Red Hat Enterprise Linux Server
and starts identd on SUSE Linux Enterprise Server.
d. Restarts the xinetd service.
e. Sets the Serviceguard manual pages paths.
f. Sets the AUTOSTART_CMCLD=1. In SUSE Linux Enterprise Server 11 environment, the
RUN_PARALLEL parameter in the /etc/sysconfig/boot file, is set to "NO".
g. The host names of the nodes and quorum if specified, their IP addresses are validated
and updated in the /etc/hosts file.
h. The /etc/lvm/lvm.conf and /etc/lvm/lvm_$(uname -n).conf files are updated
to enable VG Activation Protection.
i. Creates and deploys the firewall rules.
If firewall is disabled on the system, the rules are stored at /tmp/sg_firewall_rules.
An appropriate log message is displayed on how to run this file for the rules to be applied.
NOTE: The modified files are backed up in the same directory as the original files with
".original" extension and the output is logged to the /tmp/cmpreparecl.log file. This log
file is a cumulative log of the configuration done on the node. Each time you run
cmpreparecl, logs are appended with appropriate time stamp.
For more information, and other options, see manpages for cmpreparecl (1m).
4.7 Cluster Configuration Planning 87