Managing HP Serviceguard A.11.20.20 for Linux, May 2013

For more details of the IPv6 address format, see “IPv6

Address Types” (page 285). 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 230).

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;

• 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).

Considerations for cross-subnet:

IP addresses for a given heartbeat path are usually on the

same subnet on each node, but it is possible to configure

the heartbeat on multiple subnets such that the heartbeat is

carried on one subnet for one set of nodes and another

subnet for others, with the subnets joined by a router.

This is called a cross-subnet configuration, and in this case

at least two heartbeat paths must be configured for each

cluster node, and each heartbeat subnet on each node must

be physically routed separately to the heartbeat subnet on

another node (that is, each heartbeat path must be physically

separate). See “Cross-Subnet Configurations” (page 27).

96 Planning and Documenting an HA Cluster