HP Serviceguard Version A.11.18 Release Notes, September 2008

on installing a guest depot.) Serviceguard uses information it derives from the VM
guest depot to set the timeout to the optimal value. If any VM node does not have a
VM guest depot, Serviceguard may not be able to obtain the information it needs to
set the optimal timeout, and in that case it sets the additional timeout to the maximum
value, 70 seconds.
IMPORTANT: This additional timeout extension represents a net addition to the time
it takes for the cluster to re-form. For example, if the cluster typically took 40 seconds
to re-form before any VM nodes were added, it will take about 80 seconds when one
or more VM nodes are members of the cluster, if all those nodes have a VM guest depot.
If any VM node without a VM guest depot is a member of the cluster, it will take about
110 seconds. This is true whenever VM nodes are cluster members, whether or not the
re-formation is caused by the failure of a VM node.
For more information about HP Integrity Virtual Machines, see HP Integrity Virtual
Machines Installation, Configuration, and Administration at http://docs.hp.com ->
HP Virtual Server Environment (VSE) -> HP Integrity Virtual
Machines.
About the 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, supplied with the patches listed under “September 2008 Patch” (page 13),
provides a means for effective and persistent monitoring of VxVM volumes. The VxVM
Volume Monitor supports Veritas Volume Manager versions 3.5, 4.1, and 5.0, as well
as Veritas Cluster Volume Manager (CVM) versions 3.5, 4.1, and 5.0.
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>]
What’s in this Release 49