Managing HP Serviceguard A.11.20.20 for Linux, March 2014

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 104)) 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
and Monitored Subnets” (page 62) and the descriptions of
the package ip_ parameters (page 182).
If HOSTNAME_ADDRESS_FAMILY is set to IPV4 or ANY, a
stationary IP address can be either an IPv4 or an IPv6
address, with the exceptions noted below. If
HOSTNAME_ADDRESS_FAMILY is set to IPV6, all the IP
addresses used by the cluster must be IPv6 addresses.
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.
A stationary IP address can be either an IPv4 or an IPv6
address. For more information about IPv6 addresses, see
“IPv6 Address Types” (page 289).
For information about changing the configuration online,
see “Changing the Cluster Networking Configuration while
the Cluster Is Running” (page 230).
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.
4.7 Cluster Configuration Planning 97