Managing Serviceguard 12th Edition, March 2006

Building an HA Cluster Configuration
Configuring the Cluster
Chapter 5228
# Warning: There are no standby network interfaces for lan0.
NODE_NAME lodi
NETWORK_INTERFACE lan0
HEARTBEAT_IP 15.13.168.94
# List of serial device file names
# For example:
# SERIAL_DEVICE_FILE /dev/tty0p0
# Warning: There are no standby network interfaces for lan0.
# Cluster Timing Parameters (microseconds).
# The NODE_TIMEOUT parameter defaults to 2000000 (2 seconds).
# This default setting yields the fastest cluster reformations.
# However, the use of the default value increases the potential
# for spurious reformations due to momentary system hangs or
# network load spikes.
# For a significant portion of installations, a setting of
# 5000000 to 8000000 (5 to 8 seconds) is more appropriate.
# The maximum value recommended for NODE_TIMEOUT is 30000000
# (30 seconds).
HEARTBEAT_INTERVAL 1000000
NODE_TIMEOUT 2000000
# The FAILOVER_OPTIMIZATION parameter enables Failover Optimization,
# which reduces the time Serviceguard takes for failover. (Failover
# Optimization cannot, however, change the time an application
# needs to shut down or restart.)
#
# There are four requirements:
# * The Serviceguard Extension for Faster Failover product
# (SGeFF) must be installed on all cluster nodes.
# * Only one or two node clusters are supported.
# * A quorum server must be configured as the tie-breaker.
# * The cluster must have more than one heartbeat subnet,
# and neither can be a serial line (RS232).
#
# Other considerations are listed in the SGeFF Release Notes
# and the Serviceguard manual.
#
# You must halt the cluster to change FAILOVER_OPTIMIZATION
# parameter.
#