Managing HP Serviceguard A.11.20.20 for Linux, March 2014

NOTE: Be careful if you use YAST or YAST2 to configure volume groups, as that may cause all
volume groups to be activated. After running YAST or YAST2, check that volume groups for
Serviceguard packages not currently running have not been activated, and use LVM commands
to deactivate any that have. For example, use the command vgchange -a n /dev/sgvg00
to deactivate the volume group sgvg00.
Red Hat
It is not necessary to prevent vgscan on Red Hat.
To deactivate any volume groups that will be under Serviceguard control, add vgchange commands
to the end of /etc/rc.d/rc.sysinit; for example, if volume groups sgvg00 and sgvg01
are under Serviceguard control, add the following lines to the end of the file:
vgchange -a n /dev/sgvg00
vgchange -a n /dev/sgvg01
The vgchange commands activate the volume groups temporarily, then deactivate them; this is
expected behavior.
5.1.12.9 Setting up Disk Monitoring
HP Serviceguard for Linux includes a Disk Monitor which you can use to detect problems in disk
connectivity. This lets you fail a package over from one node to another in the event of a disk link
failure.
See “Creating a Disk Monitor Configuration” (page 198) for instructions on configuring disk
monitoring.
5.2 Configuring the Cluster
This section describes how to define the basic cluster configuration. 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). You can do this in Serviceguard Manager, or from the command line as described
below.
Use the cmquerycl 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 NODE_NAME under “Cluster Configuration Parameters ” (page 90) 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 /usr/local/cmcluster/clust1.conf (for Red Hat
Enterprise Linux) and/opt/cmcluster/clust1.conf (for SUSE Linux Enterprise Server). 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 heartbeat over all possible
networks.
The manpage for the cmquerycl command further explains the parameters that appear in this
file. Many are also described in Chapter 4: “Planning and Documenting an HA Cluster ” (page 79).
Modify your /etc/cmcluster/clust1.configfile as needed.
5.2 Configuring the Cluster 153