Managing Serviceguard Eighteenth Edition, September 2010

• Two heartbeat subnets; or
• One heartbeat subnet with a standby; or
• One heartbeat subnet using APA with two
physical ports in hot standby mode or LAN
monitor mode.
You cannot configure more than one heartbeat
IP address on an interface; only one
HEARTBEAT_IP is allowed for each
NETWORK_INTERFACE.
Do not mix APA LAN Monitor or hot standby
modes on the same network interfaces that are
configured for Serviceguard local LAN failover.
Since these monitoring and failover functions
work differently and do not communicate with
each other, unexpected failover results can occur.
HP supports mixing these LAN HA methods for
different subsets of network interfaces within a
cluster, but does not support mixing them for
the same set of interfaces.
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 on the host
using APA with two trunk members (HPVM),
or using NIC bonding in high availability mode
(or mode 1) with two slaves (VMware ESX
Server).
For information about changing the configuration
online, see “Changing the Cluster Networking
Configuration while the Cluster Is Running”
(page 367).
Considerations for cross-subnet:
Cluster Configuration Planning 153