Managing HP Serviceguard A.11.20.20 for Linux, March 2014

Can be changed while the cluster is running; see “What
Happens when You Change the Quorum Configuration
Online” (page 43) for important information.
QS_TIMEOUT_EXTENSION You can use the QS_TIMEOUT_EXTENSION to increase the
time interval after which the current connection (or attempt
to connect) to the quorum server is deemed to have failed;
but do not do so until you have read the HP Serviceguard
Quorum Server Version A.04.00 Release Notes, and in
particular the following sections in that document: “About
the QS Polling Interval and Timeout Extension”, “Network
Recommendations”, and “Setting Quorum Server Parameters
in the Cluster Configuration File”.
Can be changed while the cluster is running; see “What
Happens when You Change the Quorum Configuration
Online” (page 43) for important information.
SITE_NAME The name of a site to which nodes (see NODE_NAME) belong.
Can be used only in a site-aware disaster recovery cluster,
which requires Metrocluster (additional HP software); see
the documents listed under “Cross-Subnet Configurations”
(page 27) for more information.
You can define multiple SITE_NAMEs. SITE_NAME entries
must precede any NODE_NAME entries. See also SITE.
IMPORTANT: SITE_NAME must be 39 characters or less,
and are case-sensitive. Duplicate SITE_NAME entries are
not allowed.
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 169)) 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,
4.7 Cluster Configuration Planning 93