Managing HP Serviceguard A.11.20.20 for Linux, May 2013

NOTE: IPv6 heartbeat subnets are not supported in a
cross-subnet configuration.
NOTE: The use of a private heartbeat network is not
advisable if you plan to use Remote Procedure Call (RPC)
protocols and services. RPC assumes that each network
adapter device or I/O card is connected to a route-able
network. An isolated or private heartbeat LAN is not
route-able, and could cause an RPC request-reply, directed
to that LAN, to timeout without being serviced.
NFS, NIS and NIS+, and CDE are examples of RPC based
applications that are frequently used. Other third party and
home-grown applications may also use RPC services through
the RPC API libraries. If necessary, consult with the
application vendor.
STATIONARY_IP This node's IP address on each subnet that does not carry
the cluster heartbeat, but is monitored for packages.
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 285).
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
4.7 Cluster Configuration Planning 97