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

::1 localhost ipv6-localhost ipv6-loopback
• All addresses must be IPv6, apart from the node's IPv4 loopback address, which
cannot be removed from /etc/hosts.
• The node's public LAN address (by which it is known to the outside world) must
be the last address listed in /etc/hosts.
Otherwise there is a possibility of the address being used even when it is not
configured into the cluster.
• You must use $SGCONF/cmclnodelist, not ~/.rhosts or /etc/hosts.equiv,
to provide root access to an unconfigured node.
NOTE: This also applies if HOSTNAME_ADDRESS_FAMILY is set to ANY. See
“Allowing Root Access to an Unconfigured Node” in Chapter 5 of Managing
Serviceguard for more information.
• If you use a Quorum Server, you must make sure that the Quorum Server hostname
(and the alternate Quorum Server address specified by QS_ADDR, if any) resolve
to IPv6 addresses.
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.
What’s in this Release 17