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

IMPORTANT: You must use Quorum Server version A.04.00 or later. See the latest
Quorum Server release notes for more information; you can find them at
docs.hp.com under High Availability —> Quorum Server.
The Quorum Server itself can be an IPv6–only system; in that case it can serve
IPv6–only and mixed-mode clusters, but not IPv4–only clusters.
• If you use a Quorum Server, and the Quorum Server is on a different subnet from
cluster, you must use an IPv6-capable router.
• Hostname aliases are not supported for IPv6 addresses, because of operating
system limitations.
NOTE: This applies to all IPv6 addresses, whether
HOSTNAME_ADDRESS_FAMILY is set to IPV6 or ANY.
• Cross-subnet configurations are not supported in IPv6-only mode.
NOTE: This also applies if HOSTNAME_ADDRESS_FAMILY is set to ANY. See
“About Cross-Subnet Configurations” (page 29) for information about this type
of configuration.
• Virtual machines are not supported in IPv6-only mode. You cannot configure a
virtual machine as either a node or a package if HOSTNAME_ADDRESS_FAMILY
is set to ANY or IPV6.
• Serviceguard Manager does not yet support IPv6-only mode; see “Current
Limitations of Serviceguard Manager” (page 26).
Recommendation for IPv6-Only Mode
If you decide to migrate the cluster to IPv6-only mode, you should plan to do so while
the cluster is down.
Rules and Restrictions for Mixed Mode
• Red Hat 5 clusters are not supported.
NOTE: This also applies if HOSTNAME_ADDRESS_FAMILY is set to IPv6; Red
Hat 5 supports only IPv4-only clusters.
• The hostname resolution file on each node (for example, /etc/hosts) must
contain entries for all the IPv4 and IPv6 addresses used throughout the cluster,
including all STATIONARY_IP and HEARTBEAT_IP addresses as well any private
addresses. There must be at least one IPv4 address in this file (in the case of /etc/
hosts, the IPv4 loopback address cannot be removed).
In addition, the file must contain the following entry:
What’s in this Release 17