Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Planning and Documenting an HA Cluster
Cluster Configuration Planning
Chapter 4108
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 cluster can
contain up to 16 nodes.
IMPORTANT Node names must be 39 characters 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 191) 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).
CLUSTER_LOCK_LUN
The pathname of the device file to be used for the lock
LUN on each node. This parameter is not used if
QS_HOST is used. The pathname can contain up to 255
characters.
NETWORK_INTERFACE
The name of each LAN that will be used for heartbeats
or for user data. An example is eth0.
For information about changing the configuration
online, see “Changing the Cluster Networking
Configuration while the Cluster Is Running” on
page 256.
HEARTBEAT_IP
IP notation indicating the subnet(s) that will carry the
cluster heartbeat.