Managing Serviceguard Eighteenth Edition, September 2010

‘2’ indicates that the scope is link-local. A value of “5” indicates that the scope is
site-local.
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.
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.
• 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. They must be manually configured in
/etc/rc.config.d/netconf-ipv6.
• Link-local IP addresses are not supported, as package IPs, HEARTBEAT_IPs, or
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 or HEARTBEAT_IPs
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.
• Serviceguard supports IPv6 only on the Ethernet networks, including 10BT, 100BT,
and Gigabit Ethernet
Network Configuration Restrictions 479