HP Serviceguard for Linux Version A.11.19 Release Notes, October 2009

IMPORTANT: This 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
HPVM nodes were added, it will generally take about 80 seconds when one or more
VM nodes are members of the cluster, if all those nodes have the hpvminfo software.
If any HPVM node without that software is a member of the cluster, it will take about
110 seconds. This is true whenever HPVM nodes are cluster members, whether or not
the re-formation is caused by the failure of an HPVM node.
For More Information
For more information, see the following documents on docs.hp.com. They can be found
under High Availability -> Serviceguard for Linux -> White Papers
unless otherwise stated.
• For important VMware configuration information, see the latest version of Using
Serviceguard for Linux with VMware Virtual Machines.
• For information about running Serviceguard for Linux on Xen hosts, see the latest
version of Designing High-Availability for Xen Virtual Machines with HP Serviceguard
for Linux. See also “About cmappmgr” (page 23).
• For more information about HP Integrity Virtual Machines, see the latest version
of HP Integrity Virtual Machines Installation, Configuration, and Administration under
HP Virtual Server Environment (VSE) -> HP Integrity Virtual
Machines. For instructions for installing hpvminfo and related HP software on
an HPVM guest, see Installing a Guest Depot in chapter 4 of that document. See also
Designing High Availability Solutions with HP Serviceguard and HP Integrity Virtual
Machines, under High Availability -> Serviceguard —> White Papers.
• For the latest compatibility information, see the
Serviceguard/SGeRAC/SMS/Serviceguard Manager Plug-in Compatibility and Feature
Matrix underHigh Availability -> Serviceguard for Linux ->
Support Matrixes, and the Serviceguard for Linux Certification Matrix at
www.hp.com/go/sglx/info.
Changes First Introduced in Older Releases
The following important changes may affect the upgrade from an earlier release.
• As of A.11.16, Serviceguard uses Access Control Policies to control access to, and
administrative control over, the cluster.
See “Access changes as of A.11.16” (page 35).
Access changes as of A.11.16
Serviceguard version A.11.16 introduced a new access method. As of A.11.16,
Serviceguard uses Access Control Policies, also known as Role-Based Access, rather
than cmclnodelist or .rhosts, to authenticate users.
Features Introduced Before A.11.19 35