Managing HP Serviceguard A.11.20.20 for Linux, March 2014

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 39
characters.
See “Setting up a Lock LUN” (page 143) and “Specifying a
Lock LUN” (page 155)
Can be changed while the cluster is running; see “Updating
the Cluster Lock LUN Configuration Online” (page 233). See
also “What Happens when You Change the Quorum
Configuration Online” (page 43) for important information.
NOTE: An iSCSI storage device does not support
configuring a lock LUN.
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 recovery cluster,
which requires Metrocluster (additional HP software); see
the documents listed under “Cross-Subnet Configurations”
(page 27) 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_manual
failover_policy (page 178) for a package.
IMPORTANT: SITE must be 39 characters or less, and
are case-sensitive; each SITE entry must exactly match with
one of the SITE_NAME entries. Duplicate SITE entries are
not allowed.
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 eth0. See also
HEARTBEAT_IP, STATIONARY_IP, and “About Hostname
Address Families: IPv4-Only, IPv6-Only, and Mixed Mode”
(page 88).
94 Planning and Documenting an HA Cluster