Managing HP Serviceguard for Linux Ninth Edition, April 2009

IP level and IP_MONITOR is set toON, the
interface will be marked down. If it is set to OFF,
failures that occur only at the IP-level will not be
detected.
Can be changed while the cluster is running;
must be removed if the preceding SUBNET entry
is removed.
POLLING_TARGET The IP address to which polling messages will
be sent from all network interfaces on the subnet
specified in the preceding SUBNET entry, if
IP_MONITOR is set to ON. This is called target
polling.
Each subnet can have multiple polling targets;
repeat POLLING_TARGET entries as needed.
If IP_MONITOR is set to ON, but no
POLLING_TARGET is specified, polling messages
are sent between network interfaces on the same
subnet (peer polling). HP recommends you use
target polling; see “How the IP Monitor Works”
(page 79) for more information.
NOTE: cmquerycl (1m) detects first-level
routers in the cluster (by looking for gateways
in each node's routing table) and lists them here
as polling targets. If you run cmquerycl with
the -w full option (for full network probing)
it will also verify that the gateways will work
correctly for monitoring purposes.
Can be changed while the cluster is running;
must be removed if the preceding SUBNET entry
is removed.
WEIGHT_NAME,
WEIGHT_DEFAULT
Default value for this weight for all packages that
can have weight; see “Rules and Guidelines”
(page 136) under“About Package Weights”
(page 128). WEIGHT_NAME specifies a name for
a weight that exactly corresponds to a
CAPACITY_NAME specified earlier in the cluster
configuration file. (A package has weight; a node
has capacity.) The rules for forming
116 Planning and Documenting an HA Cluster