Managing Serviceguard Eighteenth Edition, September 2010

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 168)) 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 90) and the descriptions of the package ip_
parameters (page 298).
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 475).
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 367).
Heartbeat configuration requirements:
A minimum Serviceguard configuration on
HP-UX 11i v2 or 11i v3 needs two network
interface cards for the heartbeat in all cases, using
one of the following configurations:
152 Planning and Documenting an HA Cluster