Managing HP Serviceguard for Linux Ninth Edition, April 2009

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 118)) 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 71) and the
descriptions of the package ip_ parameters
(page 205).
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 317).
For information about changing the configuration
online, see “Changing the Cluster Networking
Configuration while the Cluster Is Running”
(page 247).
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
110 Planning and Documenting an HA Cluster