HP Serviceguard Version A.11.18 Release Notes, September 2008

The networking portion of the resulting clconfig.ascii file looks something like
this:
NODE_NAME ftsys9
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.3.17.18
#NETWORK_INTERFACE lan0
#STATIONARY_IP 15.13.170.18
NETWORK_INTERFACE lan3
# Possible standby Network Interfaces for lan1, lan0: lan2.
NODE_NAME ftsys10
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.3.17.19
#NETWORK_INTERFACE lan0
# STATIONARY_IP 15.13.170.19
NETWORK_INTERFACE lan3
# Possible standby Network Interfaces for lan0, lan1: lan2
You can now uncomment the entries and apply the new configuration; see “Changing
the Cluster Networking Configuration while the Cluster Is Running” in Chapter 7 of
Managing Serviceguard for more information.
New Online Timing-Configuration Capabilities
You can now change the following cluster-configuration parameters while the cluster
is running:
• NETWORK_POLLING_INTERVAL
• HEARTBEAT_INTERVAL
• NODE_TIMEOUT
• AUTO_START_TIMEOUT
NOTE: If you are using CVM or CFS, you cannot change HEARTBEAT_INTERVAL,
NODE_TIMEOUT, or AUTO_START_TIMEOUT while the cluster is running. This is
because they affect the aggregate failover time, which is only reported to CVM on
cluster startup.
See “Reconfiguring a Cluster” in Chapter 7 of Managing Serviceguard for more
information.
About Lock LUNs
The cluster lock is a tie-breaker that ensures that a cluster does not re-form into two
equal halves; see “Cluster Quorum to Prevent Split Brain Syndrome” in Chapter 3 of
Managing Serviceguard for details.
LUN stands for Logical Unit Number. The term can refer to a single physical disk, but
these days is more often used in a SAN (Storage Area Network) or NAS
What’s in this Release 45