HP Serviceguard Version A.11.19 Release Notes, March 2009

— HP-UX 11i v3 Native Multi-Pathing for Mass Storage
— LVM Migration from Legacy to Agile Naming Model HP-UX 11i v3
See also the HP-UX 11i v3 intro(7) manpage.
Support for HP Integrity Virtual Machines (HPVM)
As of A.11.16, Serviceguard supports HP Integrity Virtual Machines (HPVM).
IMPORTANT: Serviceguard A.11.19 supports only version 3.5, 4.0, or 4.1 of HPVM.
See the Serviceguard/SGeRAC/SMS/Serviceguard Mgr Plug-in Compatibility and Feature
Matrix, on docs.hp.com -> High Availability, under the heading
Serviceguard -> Support Matrixes, for the most up-to-date compatibility
information.
Serviceguard A.11.19 supports an HPVM either as a package or as a cluster node. If
any Serviceguard cluster node is a virtual machine, the amount of time Serviceguard
needs to wait for a failed node’s I/O to complete increases; see “About HPVM and
Cluster Re-formation Time” (page 41).
About HPVM and Cluster Re-formation Time
When a node fails and the cluster re-forms, Serviceguard must wait a certain amount
of time to allow I/O from the failed node to be written out to the target storage device.
Only after that time has elapsed can Serviceguard allow an adoptive node access to
that device; otherwise data corruption could occur. The amount of time Serviceguard
waits is calculated by Serviceguard and is not user-configurable.
The above is true whether or not the cluster includes virtual machines (VMs), but using
VMs as Serviceguard nodes increases the amount of time Serviceguard needs to wait
before it is safe to allow another node access to the same storage. This additional wait
can increase cluster re-formation time by as much as 70 seconds.
The additional time Serviceguard needs to wait depends in part on whether or not a
VM guest depot is installed on the VM node. (See HP Integrity Virtual Machines
Installation, Configuration, and Administration, at the address given below, for information
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.
What’s in this Release 41