Managing HP Serviceguard for Linux Ninth Edition, April 2009

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 118)) 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
and Monitored Subnets” (page 71) and the
descriptions of the package ip_ parameters
(page 205).
A heartbeat IP address can be either an IPv4 or
an IPv6 address, with the exceptions noted
below. For more details of the IPv6 address
format, see “IPv6 Address Types” (page 317).
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 247).
Heartbeat configuration requirements:
The cluster needs at least two network interfaces
for the heartbeat in all cases, using one of the
following minimum configurations:
• two heartbeat subnets;
or
• one heartbeat subnet using bonding in high
availability mode (or mode 1) with two
slaves.
Cluster Configuration Planning 107