Managing Serviceguard 12th Edition, March 2006

Planning and Documenting an HA Cluster
Cluster Configuration Planning
Chapter 4 157
The volume group containing the physical disk volume
on which a cluster lock is written. Identifying a cluster
lock volume group is essential in a two-node cluster. If
you are creating two cluster locks, enter the volume
group name or names for both locks. This parameter is
only used when you employ a lock disk for tie-breaking
services in the cluster.
Use FIRST_CLUSTER_LOCK_VG for the first lock volume
group. If there is a second lock volume group, the
parameter SECOND_CLUSTER_LOCK_VG is included in
the file on a separate line.
NOTE Lock volume groups must also be defined in
VOLUME_GROUP parameters in the cluster ASCII
configuration file.
NODE_NAME The hostname of each system that will be a node in the
cluster. The node name can be up to 31 bytes long. The
node name must not contain the full domain name. For
example, enter ftsys9, not ftsys9.cup.hp.com.
NETWORK_INTERFACE
The name of each LAN that will be used for heartbeats
or for user data. An example is lan0.
HEARTBEAT_IP
IP notation indicating the subnet that will carry the
cluster heartbeat. Note that heartbeat IP addresses
must be on the same subnet on each node. A heartbeat
IP address can only be an IPv4 address.
If you will be using VERITAS CVM 4.1 disk groups for
storage, multiple heartbeats are permitted. If you will
be using CVM 3.5, however, you can only use a single
heartbeat subnet. With version 3.5, the heartbeat
should be configured with standby LANs or as a group
of aggregated ports.