HP Serviceguard Version A.11.19 Release Notes, October 2009

NOTE: CFS and CVM should not be installed on any system in an IPv6–only
cluster, even if they are not configured.
This also means that the Serviceguard component of bundles that include
Serviceguard cannot be configured in IPv6 mode.
• HPVM is not supported in IPv6-only mode. You cannot configure a virtual machine
either as a node or a package in an IPv6-only cluster.
• Serviceguard Manager does not yet support IPv6-only mode; see “Current
Limitations of Serviceguard Manager” (page 36).
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
• 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:
::1 localhost ipv6-localhost ipv6-loopback
For more information and recommendations about hostname resolution, see
“Configuring Name Resolution” in Chapter 5 of Managing Serviceguard.
• You must use $SGCONF/cmclnodelist, not ~/.rhosts or /etc/hosts.equiv,
to provide root access to an unconfigured node.
See “Allowing Root Access to an Unconfigured Node” in Chapter 5 of Managing
Serviceguard for more information.
• 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.
This also applies if HOSTNAME_ADDRESS_FAMILY is set to IPV6. See “About
Cross-Subnet Configurations” (page 41) for more information.
• CFS, CVM, VxVM, and VxFS are not supported.
28 Serviceguard Version A.11.19 Release Notes