Managing HP Serviceguard A.11.20.10 for Linux, December 2012

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 100)) 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 59) and the descriptions of
the package ip_ parameters (page 176).
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 details of the IPv6 address format, see “IPv6
Address Types” (page 277). 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 221).
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.
You cannot configure more than one heartbeat IP address
on an interface; only one HEARTBEAT_IP is allowed for
each NETWORK_INTERFACE.
NOTE: The Serviceguard cmapplyconf, cmcheckconf,
and cmquerycl commands check that these minimum
requirements are met, and produce a warning if they are
not met at the immediate network level. If you see this
warning, you need to check that the requirements are met
in your overall network configuration.
If you are using virtual machine guests as nodes, you have
a valid configuration (and can ignore the warning) if there
is one heartbeat network on the guest, backed by a network
using NIC bonding as in the second bullet above (VMware
ESX Server).
4.7 Cluster Configuration Planning 91