Managing Serviceguard A.11.20, March 2013

NOTE: Any subnet that is configured in this cluster
configuration file as a SUBNET for IP monitoring purposes,
or as a monitored_subnet in a package configuration
file (or SUBNET in a legacy package; see “Package
Configuration Planning ” (page 131)) must be specified in
the cluster configuration file via NETWORK_INTERFACE and
either STATIONARY_IP or HEARTBEAT_IP. Similarly, any
subnet that is used by a package for relocatable addresses
should be configured into the cluster via
NETWORK_INTERFACE and either STATIONARY_IP or
HEARTBEAT_IP. For more information about relocatable
addresses, see “Stationary and Relocatable IP Addresses ”
(page 68) and the descriptions of the package ip_
parameters (page 246).
IMPORTANT: See “Cross-Subnet Configurations” (page 29)
for important information about requirements for such
configurations.
For information about changing the configuration online,
see “Changing the Cluster Networking Configuration while
the Cluster Is Running” (page 302).
HEARTBEAT_IP IP notation indicating this node's connection to a subnet that
will carry the cluster heartbeat.
NOTE: Any subnet that is configured in this cluster
configuration file as a SUBNET for IP monitoring purposes,
or as a monitored_subnet in a package configuration
file (or SUBNET in a legacy package; see “Package
Configuration Planning ” (page 131)) must be specified in
the cluster configuration file via NETWORK_INTERFACE and
either STATIONARY_IP or HEARTBEAT_IP. Similarly, any
subnet that is used by a package for relocatable addresses
should be configured into the cluster via
NETWORK_INTERFACE and either STATIONARY_IP or
HEARTBEAT_IP. For more information about relocatable
addresses, see “Stationary and Relocatable IP Addresses ”
(page 68) and the descriptions of the package ip_
parameters (page 246).
If HOSTNAME_ADDRESS_FAMILY is set to IPV4 or ANY, a
heartbeat IP address can be either an IPv4 or an IPv6
address, with the exceptions noted below. If
HOSTNAME_ADDRESS_FAMILY is set to IPV6, all heartbeat
IP addresses must be IPv6 addresses.
For more information about the IPv6 address format, see
“IPv6 Address Types” (page 384). Heartbeat IP addresses
on a given subnet must all be of the same type: IPv4 or IPv6
site-local or IPv6 global.
For information about changing the configuration online,
see “Changing the Cluster Networking Configuration while
the Cluster Is Running” (page 302).
Heartbeat configuration requirements:
Cluster Configuration Planning 119