Managing HP Serviceguard for Linux, Tenth Edition, September 2012

Target polling enables monitoring beyond the first level of switches, allowing you
to detect if the route is broken anywhere between each monitored IP address and
the target.
NOTE: In a cross-subnet configuration, nodes can configure peer interfaces on
nodes on the other routed subnet as polling targets.
HP recommends that you configure target polling if the subnet is not private to the cluster.
The IP Monitor section of the cmquerycl output looks similar to this:
…
Route Connectivity (no probing was performed):
IPv4:
1 16.89.143.192
16.89.120.0
…
Possible IP Monitor Subnets:
IPv4:
16.89.112.0 Polling Target 16.89.112.1
IPv6:
3ffe:1000:0:a801:: Polling Target 3ffe:1000:0:a801::254
…
The IP Monitor section of the cluster configuration file will look similar to the following
for a subnet on which IP monitoring is configured with target polling.
NOTE: This is the default if cmquerycl detects a gateway for the subnet in question;
see SUBNET under “Cluster Configuration Parameters ” (page 103) for more information.
IMPORTANT: By default, cmquerycl does not verify that the gateways it detects will
work correctly for monitoring. But if you use the -w full option, cmquerycl will
validate them as polling targets.
SUBNET 192.168.1.0
IP_MONITOR ON
POLLING_TARGET 192.168.1.254
To configure a subnet for IP monitoring with peer polling, edit the IP Monitor section of
the cluster configuration file to look similar to this:
SUBNET 192.168.2.0
IP_MONITOR ON
How the Network Manager Works 77