HP Serviceguard A.11.20- Managing Serviceguard Twentieth Edition, August 2011

The cluster name must not contain any of the following
characters: space, slash (/), backslash (\), and asterisk (*).
NOTE: In addition, the following characters must not be
used in the cluster name if you are using the Quorum Server:
at-sign (@), equal-sign (=), or-sign (|), semicolon (;).
These characters are deprecated, meaning that you should
not use them, even if you are not using the Quorum Server,
because they will be illegal in a future Serviceguard release.
All other characters are legal. The cluster name can contain
up to 39 characters (bytes).
CAUTION: Make sure that the cluster 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.
In particular make sure that two clusters with the same name
do not use the same Quorum Server; this could result in one
of the clusters failing to obtain the Quorum Server’s
arbitration services when it needs them, and thus failing to
re-form.
HOSTNAME_ADDRESS_FAMILY Specifies the Internet Protocol address family to which
Serviceguard will try to resolve cluster node names and
Quorum Server host names. Valid values are IPV4, IPV6,
and ANY. The default is IPV4.
• IPV4 means Serviceguard will try to resolve the names
to IPv4 addresses only.
• IPV6 means Serviceguard will try to resolve the names
to IPv6 addresses only.
• ANY means Serviceguard will try to resolve the names
to both IPv4 and IPv6 addresses.
IMPORTANT: See “About Hostname Address Families:
IPv4-Only, IPv6-Only, and Mixed Mode” (page 106) for
important information. See also the latest Serviceguard
release notes at http://www.hp.com/go/
hpux-serviceguard-docs.
FIRST_CLUSTER_LOCK_VG,
SECOND_CLUSTER_LOCK_VG
The volume group containing the physical disk volume on
which a cluster lock is written. This parameter is used only
when you employ a lock disk for tie-breaking services in the
cluster. If you are creating two cluster locks, enter the volume
group name or names for both locks.
Use FIRST_CLUSTER_LOCK_VG for the first lock volume
group. If there is a second lock volume group, specify the
SECOND_CLUSTER_LOCK_VG on a separate line in the
configuration file.
110 Planning and Documenting an HA Cluster