HP Serviceguard Version A.11.19 Release Notes, October 2009

will contain references to persistent device files, but Serviceguard’s functioning will
not be affected by this.
CAUTION: You cannot migrate to the agile addressing scheme during a rolling upgrade
if you are using cluster lock disks as a tie-breaker, because that involves changing the
cluster configuration. But you can migrate the cluster lock device file names to the new
scheme without bringing the cluster down. For the requirements and a procedure, see
“Updating the Cluster Lock Configuration” in Chapter 7 of Managing Serviceguard.
NOTE: It is possible, though not a best practice, to use legacy DSFs on some nodes
after migrating to agile addressing on others; this allows you to migrate different nodes
at different times, if necessary.
For more information about agile addressing, see following documents at
http://www.docs.hp.com.:
• the Logical Volume Management volume of the HP-UX System Administrator’s Guide
(in the 11i v3 -> System Administration collection)
• the HP-UX 11i v3 Installation and Update Guide (in the 11i v3 -> Installing
and Updating collection)
• the following white papers:
— The Next Generation Mass Storage Stack (under Network and Systems
Management -> Storage Area Management)
— Migrating from HP-UX 11i v2 to HP-UX 11i v3
— 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). HPVM
runs only on HP Integrity systems; it does not run on HP 9000 systems.
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 49).
48 Serviceguard Version A.11.19 Release Notes