Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Understanding Serviceguard Software Components
Volume Managers for Data Storage
Chapter 380
NOTE Do not use the MD lines in the Serviceguard package control scripts
for MD multipath. Instead, for multipath only, MD activation can be
done at system boot.
Monitoring Disks
The devices that are used for shared storage can be monitored by the
resource monitoring facility cmresmond. This daemon runs on all nodes
in the cluster and keeps track of the status of disks that are configured
for monitoring. A monitor server allows you to view the status of disks in
a standard web browser. Each package configuration includes
information about the disks that are to be activated by the package at
startup. If monitoring is used for a particular disk, or LUN, then the
health of the disk is checked at package startup. The package will fail if
the disk is not available.
The failure of a monitored disk will cause the monitor’s client service to
exit, with the consequent failure of the package on the node. When this
happens, the package may be restarted on another node. If AUTO_RUN is
set to YES, the package will start up on another eligible node, if it meets
all the requirements for startup. If AUTO_RUN is set to NO, then the
package simply halts without starting up anywhere else.
The process for configuring disk monitoring is described in “Creating a
Disk Monitor Configuration” on page 206.
More Information on LVM
Refer to the section “Creating the Logical Volume Infrastructure” in
Chapter 5 for details about configuring volume groups, logical volumes,
and file systems for use in Serviceguard packages.
Refer to the article, Logical Volume Manager HOWTO on the Linux
Documentation Project page at http://www.tldp.org for a basic
description of Linux LVM.