Managing HP Serviceguard for Linux, Seventh Edition, July 2007

IPv6 Network Support
Network Configuration Restrictions
Appendix E364
Network Configuration Restrictions
Serviceguard supports IPv6 for data links only: the heartbeat IP address
must be IPv4, but the package IP addresses can be IPv4 or IPv6.
The restrictions for supporting IPv6 in Serviceguard for Linux are:.
• The heartbeat IP address must be IPv4. IPv6-only nodes are not
supported in a Serviceguard environment.
• The hostnames in a Serviceguard configuration must be IPv4.
Serviceguard does not recognize IPv6 hostnames.
• Auto-configured IPv6 addresses are not supported in Serviceguard.
as STATIONARY_IP addresses. IPv6 addresses that are part of a
Serviceguard cluster configuration must not be auto-configured
through router advertisements, for example. Instead, they must be
manually configured in
/etc/sysconfig/network-scripts/ifcfg-<eth-ID> on Red Hat
or /etc/sysconfig/network/ifcfg-<eth-ID> on SUSE. See
“Configuring IPv6 on Linux” on page 366 for instructions and
examples.
• Link-local IP addresses are not supported, either as package IP
addresses or as STATIONARY_IP addresses. Depending on the
requirements, the package IP address could be of type site-local or
global.
• Serviceguard supports only one IPv6 address belonging to each scope
type (site-local and global) on each network interface (that is,
restricted multi-netting). This means that a maximum of two IPv6
STATIONARY_IP addresses can be mentioned in the cluster
configuration file for a NETWORK_INTERFACE:, one being the site-local
IPv6 address, and the other being the global IPv6 address.
NOTE This restriction applies to cluster configuration, not package
configuration: it does not affect the number of IPv6 relocatable
addresses of the same scope type (site-local or global) that a package
can use on an interface.