Managing Serviceguard Nineteenth Edition, Reprinted June 2011

See also “What Happens when a Node Times Out”
(page 85), “Cluster Daemon: cmcld” (page 39), and the
white paper Optimizing Failover Time in a Serviceguard
Environment (version A.11.19 and later) on http://
www.hp.com/go/hpux-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 how frequently the networks configured for
Serviceguard are checked.
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.
IMPORTANT: HP strongly recommends using the default.
Changing this value can affect how quickly the link-level
and IP-level monitors detect a network failure. See
“Monitoring LAN Interfaces and Detecting Failure: Link Level”
(page 66), “Monitoring LAN Interfaces and Detecting
Failure: IP Level” (page 70), and “Reporting Link-Level and
IP-Level Failures” (page 73).
Can be changed while the cluster is running.
CONFIGURED_IO_TIMEOUT_EXTENSION The number of microseconds by which to increase the time
Serviceguard waits after detecting a node failure, so as to
ensure that all pending I/O on the failed node has ceased.
This parameter must be set in the following cases.
• For extended-distance clusters using software mirroring
across data centers over links between iFCP switches;
it must be set to the switches' maximum R_A_TOV value.
NOTE: CONFIGURED_IO_TIMEOUT_EXTENSION
is supported only with iFCP switches that allow you to
get their R_A_TOV value.
• For switches and routers connecting an NFS server and
cluster-node clients that can run packages using the
NFS-mounted file system; see “Planning for
NFS-mounted File Systems” (page 125).
To set the value for the
CONFIGURED_IO_TIMEOUT_EXTENSION, you must
116 Planning and Documenting an HA Cluster