Managing Serviceguard A.11.20, March 2013

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 ” (page 232)) 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 (SITE, NETWORK_INTERFACE, HEARTBEAT_IP,
STATIONARY_IP, CLUSTER_LOCK_LUN,
FIRST_CLUSTER_LOCK_PV,
SECOND_CLUSTER_LOCK_PV, CAPACITY_NAME, and
CAPACITY_VALUE) apply specifically to the node identified
by the preceding NODE_NAME entry.
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 disaster-tolerant cluster,
which requires Metrocluster (additional HP software); see
the documents listed under “Cross-Subnet Configurations”
(page 29) for more information.
If SITE is used, it must be used for each node in the cluster
(that is, all the nodes must be associated with some defined
site, though not necessarily the same one).
If you are using SITEs, you can restrict the output of
cmviewcl (1m) to a given site by means of the -S
<sitename> option. In addition, you can configure a
site_preferred or
site_preferred_manualfailover_policy (page 241)
for a package.
NETWORK_INTERFACE The name of each LAN that will be used for heartbeats or
for user data on the node identified by the preceding
NODE_NAME. An example is lan0. See also
HEARTBEAT_IP, STATIONARY_IP, and “About Hostname
Address Families: IPv4-Only, IPv6-Only, and Mixed Mode”
(page 111).
118 Planning and Documenting an HA Cluster