Managing HP Serviceguard A.11.20.10 for Linux, December 2012

subnets here. You can identify any number of subnets to be
monitored.
A stationary IP address can be either an IPv4 or an IPv6
address. For more information about IPv6 addresses, see
“IPv6 Address Types” (page 277).
For information about changing the configuration online,
see “Changing the Cluster Networking Configuration while
the Cluster Is Running” (page 221).
CAPACITY_NAME,
CAPACITY_VALUE
Node capacity parameters. Use the CAPACITY_NAME and
CAPACITY_VALUE parameters to define a capacity for this
node. Node capacities correspond to package weights;
node capacity is checked against the corresponding
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 172) or automatic as its
failback_policy (page 173).
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 115) 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.
4.7 Cluster Configuration Planning 93