Managing HP Serviceguard A.11.20.20 for Linux, May 2013

package weight to determine if the package can run on that
node.
CAPACITY_NAME name can be any string that starts and
ends with an alphanumeric character, and otherwise
contains only alphanumeric characters, dot (.), dash (-),
or underscore (_). Maximum length is 39 characters.
CAPACITY_NAME must be unique in the cluster.
CAPACITY_VALUE specifies a value for the
CAPACITY_NAME that precedes it. It must be a floating-point
value between 0 and 1000000. Capacity values are
arbitrary as far as Serviceguard is concerned; they have
meaning only in relation to the corresponding package
weights.
Capacity definition is optional, but if CAPACITY_NAME is
specified, CAPACITY_VALUE must also be specified;
CAPACITY_NAME must come first.
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).
98 Planning and Documenting an HA Cluster