Managing HP Serviceguard A.11.20.20 for Linux, May 2013

By default, IP_MONITOR parameter is set to OFF. If a
gateway is detected for the SUBNET in question, and
POLLING_TARGET entries are populated with the gateway
addresses, setting IP_MONITOR parameter to ON enables
target polling. For more information, see the description for
POLLING_TARGET.
HP recommends you use target polling because it enables
monitoring beyond the first level of switches, but if you want
to use peer polling instead, set IP_MONITOR to ON for this
SUBNET, but do not use POLLING_TARGET (comment out
or delete any POLLING_TARGET entries that are already
there).
If a network interface in this subnet fails at the IP level and
IP_MONITOR is set to ON, 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 67) 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 126) under“About
Package Weights” (page 120). 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 WEIGHT_NAME are the same
as those spelled out for CAPACITY_NAME earlier in this list.
These parameters are optional, but if they are defined,
WEIGHT_DEFAULT must follow WEIGHT_NAME, and must
be set to a floating-point value between 0 and 1000000.
If they are not specified for a given weight, Serviceguard
will assume a default value of zero for that weight. In either
4.7 Cluster Configuration Planning 103