Managing HP Serviceguard A.11.20.20 for Linux, May 2013

“FF” at the beginning of the address identifies the address as a multicast address.
The “flags” field is a set of 4 flags “000T”. The higher order 3 bits are reserved and must be zero.
The last bit ‘T’ indicates whether it is permanently assigned or not. A value of zero indicates that
it is permanently assigned otherwise it is a temporary assignment.
The “scop” field is a 4-bit field which is used to limit the scope of the multicast group. For example,
a value of ‘1’ indicates that it is a node-local multicast group. A value of ‘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)
D.2 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. 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 288) 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.
IMPORTANT: For important information, see also “Cross-Subnet Configurations” (page 27), the
description of the HOSTNAME_ADDRESS_FAMILY, QS_HOST and QS_ADDR parameters under
Cluster Configuration Parameters (page 91), “Configuring Name Resolution” (page 137), and the
Release Notes for your version of Serviceguard for Linux.
For special instructions that may apply to using IPv6 addresses to connect your version of
Serviceguard for Linux and the Quorum Server, see “Configuring Serviceguard to Use the Quorum
Server” in the latest version HP Serviceguard Quorum Server Version A.04.00 Release Notes, at
http://www.hp.com/go/hpux-serviceguard-docs (Select HP Serviceguard Quorum Server Software).
D.3 Configuring IPv6 on Linux
Red Hat Enterprise Linux and SUSE Linux Enterprise Server already have the proper IPv6 tools
installed, including the /sbin/ip command. This section explains how to configure IPv6 stationary
IP addresses on these systems.
288 IPv6 Network Support