Managing HP Serviceguard for Linux, Tenth Edition, September 2012

cause problems for volumes used in a Serviceguard environment (for example, a volume
group for a Serviceguard package that is not currently running may be activated). To
prevent such problems, proceed as follows on the various Linux versions.
NOTE: You do not need to perform these actions if you have implemented volume-group
activation protection as described under “Enabling Volume Group Activation Protection”
(page 173).
SUSE Linux Enterprise Server
Prevent a vgscan at boot time by removing the /etc/rc.d/boot.d/S07boot.lvm
file from all cluster nodes.
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.
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 231) for instructions on configuring
disk monitoring.
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.
Configuring the Cluster 179