Managing Serviceguard 14th Edition, June 2007

IPv6 Network Support
Network Configuration Restrictions
Appendix H512
Network Configuration Restrictions
Serviceguard supports IPv6 for data links only. The heartbeat IP must
still be IPv4, but the package IPs can be IPv4 or IPv6.
To configure IPv6, the system should be set up in what is called a
dual-stack configuration, which requires the IPv6 product bundle.
The restrictions for supporting IPv6 in Serviceguard are listed below.
• The heartbeat IP address must be IPv4. Therefore, IPv6-only
operation nodes or 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. All IPv6 addresses that are part of a
Serviceguard cluster configuration must not be auto-configured
through router advertisements, for example. They must be manually
configured in /etc/rc.config.d/netconf-ipv6.
• Link-local IP addresses are not supported, either as package IPs or
as STATIONARY_IPs. Depending on the requirements, the package IP
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). Therefore, up to a maximum of two IPv6
STATIONARY_IPs can be mentioned in the cluster ascii file for a
NETWORK_INTERFACE: one being the site-local IPv6 address, and the
other being the global IPv6 address.
• Quorum server, if used, has to be configured on an IPv4 network. It
is not IPv6-capable. A quorum server configured on an IPv4 network
can still be used by Serviceguard IPv6 clusters that have IPv6
networks as a part of their cluster configuration.
• Serviceguard supports IPv6 only on the Ethernet networks,
including 10BT, 100BT, and Gigabit Ethernet