IPv6 addresses
IPv6 addresses can be made visible as resources in the IBM®.NetworkInterface class and used for heartbeating and internal peer domain operations, as controlled by the IPv6Support attribute.
For each interface that has IPv6 addresses configured on it, one of these IPv6 addresses will be chosen for representation as a resource, if the IPv6Support attribute is set to 1 (True). If global addresses are configured on an interface in addition to its link-local address, the first global address (as displayed by ifconfig -a, for example) will be represented in preference to the link-local address.
All such interfaces represented as resources will be formed into
communication groups with full end-to-end connectivity as supported
by physical networking and routing. Communication groups that contain
IPv6 interfaces will be disjoint from communication groups that contain
IPv4 interfaces. By default, all such IPv6 interfaces will be used
for heartbeating and internal peer domain operations, under control
of their HeartbeatActive attribute and based on characteristics
of their underlying IP interfaces. In this regard, peer domain usage
of IPv6 interfaces is identical to that of IPv4 interfaces.
Note: The
configuration resource manager is set to ignore link-local IPv4 and
IPv6 addresses from being taken into account for heartbeat, trusted
host list (THL), and the IBM.NetworkInterface resource
class.