HP Serviceguard Version A.11.19 Release Notes, October 2009

NOTE: This also applies if HOSTNAME_ADDRESS_FAMILY is set to IPV6.
HPVM is not supported.
You cannot have a virtual machine that is either a node or a package if
HOSTNAME_ADDRESS_FAMILY is set to ANY or IPV6.
Restrictions if You Have Not Applied the July or later 2009 Patch
A.11.19 without the patch supports only IPv4–only and mixed-mode clusters; you
cannot configure an IPv6–only cluster.
In addition, you cannot use cmquerycl -q to configure IPv6 addresses (or hostnames
that resolve only to IPv6 addresses) for QS_HOST and QS_ADDR. You must generate
a cluster template file, edit it to set the appropriate (IPv6) values for QS_HOST and
QS_ADDR and set HOSTNAME_ADDRESS_FAMILY to ANY, and then use
cmapplyconf to apply the configuration. See the latest version of the HP Serviceguard
Quorum Server Version A.04.00 Release Notes on docs.hp.com > High
Availability > Quorum Server for more information.
IMPORTANT: Quorum Server Version A.04.00 is required if you are configuring a
second Quorum Server address (QS_ADDR). This is true whether QS_ADDR is an IPv4
or an IPv6 address.
The IP Monitor
In addition to monitoring network interfaces at the link level, Serviceguard A.11.19
can also monitor the IP level, checking Layer 3 health and connectivity for both IPv4
and IPv6 subnets. This is done by the IP Monitor, which is configurable: you can enable
IP monitoring for any subnet configured into the cluster, but you do not have to monitor
any. You can configure IP monitoring for a subnet, or turn off monitoring, while the
cluster is running.
For more information, see the section “Monitoring LAN Interfaces and Detecting Failure:
IP Level” in Chapter 3 of Managing Serviceguard.
New Online Cluster Configuration Capabilities
Serviceguard A.11.19 introduces new online cluster-management capabilities. The new
capabilities include:
Changing the Quorum Server configuration
Changing the lock disk configuration
Changing the lock LUN configuration
Changing an interface from IPv4 to IPv6, or vice versa
What’s in this Release 29