VERITAS Volume Manager 4.1 Administrator's Guide

Administering Cluster Functionality
Cluster Initialization and Configuration
Chapter 10364
• network address of the vxconfigd daemon on each node
On the master node, the vxconfigd daemon sets up the shared
configuration by importing shared disk groups, and informs the
vxclustd daemon when it is ready for the slave nodes to join the cluster.
On slave nodes, the vxconfigd daemon is notified when the slave node
can join the cluster. When the slave node joins the cluster, the vxconfigd
daemon and the VxVM kernel communicate with their counterparts on
the master node to set up the shared configuration.
When a node leaves the cluster, the vxclustd 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 as
described in “Volume Reconfiguration” on page 362.
vxconfigd Daemon Recovery
In a cluster, the vxconfigd daemons on the slave nodes are always
connected to the vxconfigd daemon on the master node. If the vxconfigd
daemon is stopped, volume reconfiguration cannot take place and other
nodes cannot join the cluster until it is restarted. If a cluster monitor is
enabled, it may try to fail over VxVM to another node in the cluster. It is
therefore inadvisable to stop the vxconfigd daemon on any cluster node.
Different actions are taken depending on which node the vxconfigd
daemon is stopped:
• If the vxconfigd daemon is stopped on the master node, the
vxconfigd daemons on the slave nodes periodically attempt to rejoin
to the master node. Such attempts do not succeed until the
vxconfigd daemon is restarted on the master. In this case, the
vxconfigd daemons on the slave nodes have not lost information
about the shared configuration, so that any displayed configuration
information is correct.
• If the vxconfigd daemon is stopped on a slave node, the master node
takes no action. When the vxconfigd daemon is restarted on the
slave, the slave vxconfigd daemon attempts to reconnect to the
master daemon and to re-acquire the information about the shared
configuration. (Neither the kernel view of the shared configuration
nor access to shared disks is affected.) Until the vxconfigd daemon