Managing HP Serviceguard A.11.20.20 for Linux, March 2014

NOTE: cmapplyconf will fail if any node defines a
capacity and any package has min_package_node as
its failover_policy (page 178) or automatic as its
failback_policy (page 179).
To specify more than one capacity for a node, repeat these
parameters for each capacity. You can specify a maximum
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 120) 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.
• 14 seconds for a cluster that has only one heartbeat
LAN
With the lowest supported value of 3 seconds, a failover
time of 4 to 5 seconds can be achieved.
98 Planning and Documenting an HA Cluster