HP Serviceguard manual See IPv6 Address Types, Lock LUN page 189 for more information

	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 125)) 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 67) and the descriptions of the package ip_
	parameters (page 242).
	If you want to separate application data from heartbeat
	messages, define one or more monitored non-heartbeat
	subnets here. You can identify any number of subnets to be
	monitored.
	IMPORTANT: In a cross-subnet configuration, each
	package subnet configured on an interface (NIC) must have
	a standby interface connected to the local bridged network.
	See “Cross-Subnet Configurations” (page 30) for important
	information about requirements for such configurations.
	If HOSTNAME_ADDRESS_FAMILY is set to IPV4 or ANY, a
	stationary IP address can be either an IPv4 or an IPv6
	address. If HOSTNAME_ADDRESS_FAMILY is set to IPV6,
	all the IP addresses used by the cluster must be IPv6
	addresses. For information about the IPv6 address format,
	see “IPv6 Address Types” (page 378).
	For information about changing the configuration online,
	see “Changing the Cluster Networking Configuration while
	the Cluster Is Running” (page 297).
CLUSTER_LOCK_LUN	The path on this node for the LUN used for the cluster lock.
	Used only if a lock LUN is used for tie-breaking services.
	Enter the path as it appears on each node in the cluster (the
	same physical device may have a different name on each
	node). The path must identify a block device.
	You cannot create a dual cluster-lock configuration using
	LUNs.
	See “Setting Up a Lock LUN” (page 174) and “Specifying a
	Lock LUN” (page 189) for more information.
	Can be changed while the cluster is running; see “Updating
	the Cluster Lock LUN Configuration Online” (page 295). See
	also “What Happens when You Change the Quorum
	Configuration Online” (page 49) for important information.
FIRST_CLUSTER_LOCK_PV,	The path on this node for the physical volume within the
SECOND_CLUSTER_LOCK_PV	cluster-lock Volume Group that will have the cluster lock
	written on it (see the entry for FIRST_CLUSTER_LOCK_VG
	and SECOND_CLUSTER_LOCK_VG near the beginning of

Cluster Configuration Planning 117