Managing Serviceguard 14th Edition, June 2007

Planning and Documenting an HA Cluster
Cluster Configuration Planning
Chapter 4156
NODE_NAME The hostname of each system that will be a node in the
cluster. Do not use the full domain name. For example,
enter ftsys9, not ftsys9.cup.hp.com. A Serviceguard
cluster can contain up to 16 nodes (though not in all
third-party configurations; see “Veritas Cluster Volume
Manager (CVM)” on page 119, and the latest Release
Notes for your version of Serviceguard).
IMPORTANT Node names must be 39 characters (bytes) or less, and
are case-sensitive; for each node, the NODE_NAME in the
cluster configuration file must exactly match the
corresponding node_name in the package configuration
file (see Chapter 6, “Configuring Packages and Their
Services,” on page 271) and these in turn must exactly
match the hostname portion of the name specified in
the node’s networking configuration. (Using the above
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).
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 “Changing the Cluster Networking
Configuration while the Cluster Is Running” on
page 353.
HEARTBEAT_IP
IP notation indicating the subnet that will carry the
cluster heartbeat. Note that heartbeat IP addresses
must be on the same subnet on each node. A heartbeat
IP address must be an IPv4 address.
For information about changing the configuration
online, see “Changing the Cluster Networking
Configuration while the Cluster Is Running” on
page 353.