Managing Serviceguard Fifteenth Edition, reprinted May 2008

Planning and Documenting an HA Cluster
Cluster Configuration Planning
Chapter 4160
example, ftsys9 must appear in exactly that form in
the cluster configuration and package configuration
files, and as ftsys9.cup.hp.com in the DNS
database).
SITE The name of a site (defined by SITE_NAME) to which
the node identified by the preceding NODE_NAME entry
belongs. Can be used only in a site-aware
extended-distance cluster, which requires
additional software; see the documents listed under
“Cross-Subnet Configurations” on page 41 for more
information.
If SITE is used, it must be used for all nodes in the
cluster (that is, all the nodes must be associated with
some defined site, though not necessarily the same
one).
NETWORK_INTERFACE
The name of each LAN that will be used for heartbeats
or for user data. An example is lan0.
For information about changing the configuration
online, see Chapter , “Changing the Cluster
Networking Configuration while the Cluster Is
Running,” on page 367.
HEARTBEAT_IP
IP notation indicating a subnet that will carry the
cluster heartbeat.
A heartbeat IP address must be an IPv4 address.
Any subnet that is configured as a monitored_subnet
in a package configuration file (or SUBNET in a legacy
package; see “Package Configuration Planning” on
page 169) must be specified as either a STATIONARY_IP
or HEARTBEAT_IP.
For information about changing the configuration
online, see “Changing the Cluster Networking
Configuration while the Cluster Is Running” on
page 367.