Managing HP Serviceguard A.11.20.20 for Linux, May 2013

microseconds), keeping in mind that a value larger than
the default will lead to slower re-formations than the
default. A value in this range is appropriate for most
installations
See also “What Happens when a Node Times Out”
(page 75), “Cluster Daemon: cmcld” (page 34), and the
white paper Optimizing Failover Time in a Serviceguard
Environment (version A.11.19 and later) at http://
www.hp.com/go/linux-serviceguard-docs.
Can be changed while the cluster is running.
AUTO_START_TIMEOUT The amount of time a node waits before it stops trying to
join a cluster during automatic cluster startup. All nodes wait
this amount of time for other nodes to begin startup before
the cluster completes the operation. The time should be
selected based on the slowest boot time in the cluster. Enter
a value equal to the boot time of the slowest booting node
minus the boot time of the fastest booting node plus 600
seconds (ten minutes).
Default is 600,000,000 microseconds.
Can be changed while the cluster is running.
NETWORK_POLLING_INTERVAL Specifies the Interval at which Serviceguard periodically
polls all the LAN Interfaces (link-level and the ones
configured for IP MONITOR)
Default is 2,000,000 microseconds (2 seconds). This means
that the network manager will poll each network interface
every 2 seconds, to make sure it can still send and receive
information.
The minimum value is 1,000,000 (1 second) and the
maximum value supported is 30 seconds.
For example,
• If NETWORK_POLLING_INTERVAL is defined to be
6,000,000 (6 seconds), then the polling happens at
6th second, 12th second and so on.
If NETWORK_POLLING_INTERVAL is defined to be
9,000,000 (9 seconds), then the polling happens at
9th second, 18th second and so on.
• Serviceguard also uses this parameter to calculate the
number of consecutive packets that each LAN interface
can miss/receive to mark a LAN interface DOWN/UP.
When an interface is monitored at IP-Level, and the
NETWORK_POLLING_INTERVAL is defined to be 8
seconds or more, then the number of consecutive
packets that each LAN interface can miss/receive to
be marked DOWN/UP is 2.
For example,
If NETWORK_POLLING_INTERVAL is defined to be 10
seconds, then the detection of failure/recovery for a
interface at IP Level will happen between 10 to 20
seconds.
100 Planning and Documenting an HA Cluster