HP Serviceguard Version A.11.19 Release Notes, July 2009

in Chapter 4, and (for legacy packages only) “Configuring Cross-Subnet Failover” in
Chapter 7.
See also the white paper Technical Considerations for Creating a Serviceguard Cluster that
Spans Multiple IP Subnets, which you can find at the address below. This paper discusses
and illustrates supported configurations, and also potential mis-configurations.
IMPORTANT: Although cross-subnet topology can be implemented on a single site,
it is most commonly used by extended-distance clusters, and specifically site-aware
disaster-tolerant clusters, which require Metrocluster (HP add-on software).
Design and configuration of such clusters are covered in the disaster-tolerant
documentation delivered with Serviceguard. For more information, see the following
documents at http://www.docs.hp.com -> High Availability:
• Understanding and Designing Serviceguard Disaster Tolerant Architectures
• Designing Disaster Tolerant HA Clusters Using Metrocluster and Continentalclusters
• Using Serviceguard Extension for RAC
• The white paper Configuration and Administration of Oracle 10g R2 RAC Database in
HP Metrocluster
About the VxVM Volume Monitor
Simply monitoring each physical disk in a Serviceguard cluster does not provide
adequate monitoring for volumes managed by Veritas Volume Manager from Symantec
(VxVM), because a physical volume failure is not always a critical failure that triggers
failover (for example, the failure of a mirrored volume is not considered critical).
For this reason, and because VxVM allows you to resize a volume while it is online, it
can be very difficult to determine which physical disks must be monitored to ensure
that a logical volume is functioning properly. The HP Serviceguard VxVM Volume
Monitor, first introduced in a patch to Serviceguard A.11.18, provides a means for
effective and persistent monitoring of VxVM volumes.
Monitor Usage
You configure the VxVM Volume Monitor as a service within a package which requires
access to a VxVM volume.
When a monitored volume fails or becomes inaccessible, the monitor service will exit,
causing the package to fail on the current node. The package’s failover behavior depends
on its configured settings, as with any other failover package.
Syntax:
cmvxserviced [-h, --help] [-v, --version]
[-O, --log-file <log_file>]
[-D, --log-level <1-7>]
Features Introduced Before A.11.19 39