Managing HP Serviceguard for Linux Ninth Edition, April 2009

The “group ID” field identifies the multicast group. Some frequently used multicast
groups are the following:
All Node Addresses = FF02:0:0:0:0:0:0:1 (link-local)
All Router Addresses = FF02:0:0:0:0:0:0:2 (link-local)
All Router Addresses = FF05:0:0:0:0:0:0:2 (site-local)
Network Configuration Restrictions
Serviceguard supports IPv6 for data and heartbeat IP.
The restrictions on support for IPv6 in Serviceguard for Linux are:
• Auto-configured IPv6 addresses are not supported in Serviceguard. as
HEARTBEAT_IP or 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” (page 322) for instructions and examples.
• Link-local IP addresses are not supported, as package IPs, HEARTBEAT_IPs, or
STATIONARY_IPs. 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 HEARTBEAT_IP or STATIONARY_IP
addresses can be listed 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.
• Bonding is supported for IPv6 addresses, but only in active-backup mode.
• Serviceguard supports IPv6 only on the Ethernet networks, including 10BT, 100BT,
and Gigabit Ethernet.
Network Configuration Restrictions 321