HP Serviceguard Standby. HP recommends multiple heartbeats, Cluster that uses CVM is running

NOTE: Limitations:

• Because Veritas Cluster File System from Symantec (CFS) requires link-level traffic communication (LLT) among the nodes, Serviceguard cannot be configured in cross-subnet configurations with CFS alone. But CFS is supported in specific cross-subnet configurations with Serviceguard and HP add-on products; see the documentation listed under “Cross-Subnet Configurations” (page 30) for more information.

• IPv6 heartbeat subnets are not supported in a

	cross-subnet configuration.
	Considerations for CVM:
	• For Veritas CVM 4.1 or later, multiple heartbeats are
	permitted, and you must configure either multiple
	heartbeat subnets or a single heartbeat subnet with a
	standby. HP recommends multiple heartbeats.
	• You cannot change the heartbeat configuration while
	a cluster that uses CVM is running.
	• You can use an IPv6 heartbeat subnet with Veritas
	CVM/CFS on HP Serviceguard A.11.20 April 2011
	patches with Veritas Storage Foundation™ 5.1 SP1
	and later.
	NOTE: The use of a private heartbeat network is not
	advisable if you plan to use Remote Procedure Call (RPC)
	protocols and services. RPC assumes that each network
	adapter device or I/O card is connected to a route-able
	network. An isolated or private heartbeat LAN is not
	route-able, and could cause an RPC request-reply, directed
	to that LAN, to risk timeout without being serviced.
	NFS, NIS and NIS+, and CDE are examples of RPC based
	applications that are frequently used on HP-UX. Other third
	party and home-grown applications may also use RPC
	services directly through the RPC API libraries. If necessary,
	consult with the application vendor to confirm its usage of
	RPC.
STATIONARY_IP	This node's IP address on each subnet that does not carry
	the cluster heartbeat, but is monitored for packages.

116 Planning and Documenting an HA Cluster