HP Serviceguard manual See About Package Weights page 144 for more

	of four capacities per cluster, unless you use the reserved
	CAPACITY_NAME package_limit; in that case, you can
	use only that capacity throughout the cluster.
	For all capacities other than package_limit, the default
	weight for all packages is zero, though you can specify a
	different default weight for any capacity other than
	package_limit; see the entry for WEIGHT_NAME and
	WEIGHT_DEFAULT later in this list.
	See “About Package Weights” (page 144) for more
	information.
	Can be changed while the cluster is running; will trigger a
	warning if the change would cause a running package to
	fail.
MEMBER_TIMEOUT	The amount of time, in microseconds, after which
	Serviceguard declares that the node has failed and begins
	re-forming the cluster without this node.
	Default value: 14 seconds (14,000,000 microseconds).
	This value leads to a failover time of between approximately
	18 and 22 seconds, if you are using a Quorum Server, or
	a Fiber Channel cluster lock, or no cluster lock. Increasing
	the value to 25 seconds increases the failover time to
	between approximately 29 and 39 seconds. The time will
	increase by between 5 and 13 seconds if you are you using
	a SCSI cluster lock or dual Fibre Channel cluster lock).
	Maximum supported value: 300 seconds (300,000,000
	microseconds).
	If you enter a value greater than 60 seconds (60,000,000
	microseconds), cmcheckconf and cmapplyconf will note
	the fact, as confirmation that you intend to use a large value.
	Minimum supported values:
	• 3 seconds for a cluster with more than one heartbeat
	subnet.
	• 8 seconds for a cluster with more than one heartbeat
	using CFS (see “Creating a Storage Infrastructure with
	Veritas Cluster File System (CFS)” (page 199) for more
	information about CFS; see also the “Considerations
	for CVM” under HEARTBEAT_IP earlier in this section).
	• 14 seconds for a cluster that has only one Ethernet
	heartbeat LAN
	• 22 seconds for a cluster that has only one IP over
	Infiniband (IPoIP) heartbeat LAN

Cluster Configuration Planning 119