Managing HP Serviceguard A.12.00.00 for Linux, June 2014

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.12.00.00 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.8.2 Heartbeat Subnet and Cluster Re-formation Time
The speed of cluster re-formation depends on the number of heartbeat subnets.
If the cluster has only a single heartbeat network, and a network card on that network fails,
heartbeats will be lost while the failure is being detected and the IP address is being switched to
a standby interface. The cluster may treat these lost heartbeats as a failure and re-form without
one or more nodes. To prevent this, a minimum MEMBER_TIMEOUT value of 14 seconds is required
for clusters with a single heartbeat network.
If there is more than one heartbeat subnet, and there is a failure on one of them, heartbeats will
go through another, so you can configure a smaller MEMBER_TIMEOUT value.
NOTE: For heartbeat configuration requirements, see the discussion of the HEARTBEAT_IP
parameter later in this chapter. For more information about managing the speed of cluster
re-formation, see the discussion of the MEMBER_TIMEOUT parameter, and further discussion under
“What Happens when a Node Times Out” (page 73), and, for troubleshooting, “Cluster
Re-formations Caused by MEMBER_TIMEOUT Being Set too Low” (page 277).
4.8.3 About Hostname Address Families: IPv4-Only, IPv6-Only, and Mixed Mode
Serviceguard supports three possibilities for resolving the nodes' hostnames (and Quorum Server
hostnames, if any) to network address families:
86 Planning and Documenting an HA Cluster