Managing HP Serviceguard for Linux Ninth Edition, April 2009

NODE_NAME The hostname of each system that will be a node
in the cluster.
CAUTION: Make sure that the node name is
unique within the subnets configured on the
cluster nodes; under some circumstances
Serviceguard may not be able to detect a
duplicate name and unexpected problems may
result.
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 ” (page 189)) 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).
The parameters immediately following
NODE_NAME in this list
(NETWORK_INTERFACE, HEARTBEAT_IP,
STATIONARY_IP, CLUSTER_LOCK_LUN,
CAPACITY_NAME, and CAPACITY_VALUE)
apply specifically to the node identified by the
preceding NODE_NAME entry.
CLUSTER_LOCK_LUN The pathname of the device file to be used for
the lock LUN on each node. The pathname can
contain up to 255 characters.
See “Setting up a Lock LUN” (page 157) and
“Specifying a Lock LUN” (page 172)
Can be changed while the cluster is running; see
“Updating the Cluster Lock LUN Configuration
Cluster Configuration Planning 105