Managing Serviceguard Seventeenth Edition, First Reprint December 2009

This value leads to a failover time of between
approximately 18 and 22 seconds, if you are using
a Quorum Server, or a Fiber Channel cluster lock,
or no cluster lock. Increasing the value to 25
seconds increases the failover time to between
approximately 29 and 39 seconds. The time will
increase by between 5 and 13 seconds if you are
you using a SCSI cluster lock or dual Fibre
Channel cluster lock).
Maximum supported value: 300 seconds
(300,000,000 microseconds).
If you enter a value greater than 60 seconds
(60,000,000 microseconds), cmcheckconf and
cmapplyconf will note the fact, as confirmation
that you intend to use a large value.
Minimum supported values:
• 3 seconds for a cluster with more than one
heartbeat subnet.
• 8 seconds for a cluster with more than one
heartbeat using CFS (see “Creating a Storage
Infrastructure with Veritas Cluster File
System (CFS)” (page 237) for more
information about CFS; see also the
“Considerations for CVM” under
HEARTBEAT_IP earlier in this section).
• 14 seconds for a cluster that has only one
Ethernet heartbeat LAN
• 22 seconds for a cluster that has only one IP
over Infiniband (IPoIP) heartbeat LAN
With the lowest supported value of 3 seconds, a
failover time of 4 to 5 seconds can be achieved.
NOTE: The failover estimates provided here
apply to the Serviceguard component of failover;
that is, the package is expected to be up and
running on the adoptive node in this time, but
the application that the package runs may take
more time to start.
Keep the following guidelines in mind when
deciding how to set the value.
Cluster Configuration Planning 155