VERITAS Volume Manager 3.5 Administrator's Guide (September 2004)

Administering Cluster Functionality

Cluster Initialization and Conﬁguration

Chapter 10 347

Cluster Initialization and Conﬁguration

Before any nodes can join a new cluster for the ﬁrst time, you must

supply certain conﬁguration information during cluster monitor setup.

This information is normally stored in some form of cluster monitor

conﬁguration database. The precise content and format of this

information depends on the characteristics of the cluster monitor. The

information required by VxVM is as follows:

• cluster ID

• node IDs

• network addresses of nodes

• port addresses

When a node joins the cluster, this information is automatically loaded

into VxVM on that node at node startup time.

NOTE The cluster functionality of VxVM requires that a cluster monitor (such

as provided by MC/ServiceGuard) has been conﬁgured. If

MC/ServiceGuard is chosen as your cluster monitor, no additional

conﬁguration of VxVM is required, apart from the cluster conﬁguration

requirements of MC/ServiceGuard.

The cluster monitor startup procedure effects node initialization, and

brings up the various cluster components (such as VxVM with cluster

support, the cluster monitor, and a distributed lock manager) on the

node. Once this is complete, applications may be started. The cluster

monitor startup procedure must be invoked on each node to be joined to

the cluster.

For VxVM in a cluster environment, initialization consists of loading the

cluster conﬁguration information and joining the nodes in the cluster.

The ﬁrst node to join becomes the master node, and later nodes (slaves)

join to the master. If two nodes join simultaneously, VxVM chooses the

master. Once the join for a given node is complete, that node has access

to the shared disks.