Managing HP Serviceguard for Linux, Tenth Edition, September 2012

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 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 76) 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 145) under“About Package Weights”
118 Planning and Documenting an HA Cluster