HP Serviceguard manual Failure and Recovery Detection Times

…

Route Connectivity (no probing was performed):

IPv4:

116.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 109) 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

NOTE: This is not the default. If cmquerycl does not detect a gateway for the subnet in question, it sets IP_MONITOR to OFF, disabling IP-level polling for this subnet; if it does detect a gateway, it populates POLLING_TARGET, enabling target polling. See SUBNET under “Cluster Configuration Parameters ” (page 109) for more information.

The IP Monitor section of the cluster configuration file will look similar to the following in the case of a subnet on which IP monitoring is disabled:

SUBNET 192.168.3.0

IP_MONITOR OFF

NOTE: This is the default if cmquerycl does not detect a gateway for the subnet in question; it is equivalent to having no SUBNET entry for the subnet. See SUBNET under “Cluster Configuration Parameters ” (page 109) for more information.

Failure and Recovery Detection Times

With the default NETWORK_POLLING_INTERVAL of 2 seconds (see “Cluster Configuration Parameters ” (page 109)) the IP monitor will detect IP failures typically within 8–10 seconds for Ethernet and within 16–18 seconds for InfiniBand. Similarly, with the default

How the Network Manager Works 75