VERITAS Volume Manager 3.1 Administrator's Guide

Cluster Functionality
Cluster-related Volume Manager Utilities and Daemons
Chapter 7320
vxconfigd daemon receives cluster-related instructions from the kernel.
A separate copy of the vxconfigd daemon resides on each node; these
copies communicate with each other through networking facilities. For
each node in a cluster, Volume Manager utilities communicate with the
vxconfigd daemon running on that particular node; utilities do not
attempt to connect with vxconfigd daemons on other nodes. During
startup of the cluster, kernel tells the vxconfigd daemon to begin cluster
operation and tells it whether it is a master or slave node.
When a node is initialized for cluster operation, the kernel tells the
vxconfigd daemon that the node is about to join the cluster and
provides the vxconfigd daemon with the following information (from the
cluster manager configuration database):
cluster ID
node IDs
master node ID
node’s role
network address of the vxconfigd on each node
On the master node, the vxconfigd daemon sets up the shared
configuration (i.e., imports the shared disk groups) and informs the
vxclustd daemon when it is ready for slaves to join.
On slave nodes, the kernel tells the vxconfigd daemon when the slave
node can join the cluster. When the slave node joins the cluster, the
vxconfigd daemon and the Volume Manager kernel communicate with
their counterparts on the master in order to set up the shared
configuration.
When a node leaves the cluster, the vxconfigd daemon notifies the
kernel on all the other nodes. The master node then performs any
necessary cleanup. If the master node leaves the cluster, the kernels
choose a new master node and the vxconfigd daemons on all nodes are
notified of the choice.
The vxconfigd daemon also participates in volume reconfiguration. See
“Volume Reconfiguration” for information on the role of the vxconfigd
daemon in volume reconfiguration.
vxconfigd Daemon Recovery
The Volume Manager vxconfigd daemon can be stopped and/or