Managing HP Serviceguard for Linux, Tenth Edition, September 2012

NOTE: As of release A.11.16.07, Serviceguard for Linux provides functionality similar
to HP-UX exclusive activation. This feature is based on LVM2 hosttags, and is available
only for Linux distributions that officially support LVM2.
All of the disks in the volume group owned by a package must be connected to the
original node and to all possible adoptive nodes for that package.
Shared disk storage in Serviceguard Linux clusters is provided by disk arrays, which
have redundant power and the capability for connections to multiple nodes. Disk arrays
use RAID modes to provide redundancy.
Supported Disk Interfaces
The following interfaces are supported by Serviceguard for disks that are connected to
two or more nodes (shared data disks):
• MSA (Modular Smart Array) 2000 family
• FibreChannel.
For information on configuring multipathing, see “Multipath for Storage ” (page 94).
Disk Monitoring
You can configure monitoring for disks and configure packages to be dependent on the
monitor. For each package, you define a package service that monitors the disks that
are activated by that package. If a disk failure occurs on one node, the monitor will
cause the package to fail, with the potential to fail over to a different node on which the
same disks are available.
Monitoring LVM Disks Through Generic Resources Monitoring Service
If you are using LVM, you can configure disk monitoring to detect a failed mechanism
by using the disk monitor capabilities of the System Fault Management, available as a
separate product, and integrating it in Serviceguard by configuring generic resources
in packages. Monitoring can be set up to trigger a package failover or to report disk
failure events to Serviceguard by writing monitoring scripts, which can be configured as
a service in a package.
Monitoring scripts are user-written scripts that must contain the core logic to monitor a
resource and set the status of a generic resource using the generic resource commands,
cmgetresource(1m) and cmsetresource(1m).
For more information, see:
• “Using Generic Resources to Monitor Volume Groups” (page 98)
• “Monitoring Script for Generic Resources” (page 340)
• “Getting and Setting the Status/Value of a Simple/Extended Generic Resource”
(page 128) and the manpages
30 Understanding Hardware Configurations for Serviceguard for Linux