Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)

■ role of the node
■ network address of the node
On the master node, the vxconfigd daemon sets up the shared configuration by
importing shared disk groups, and informs the kernel 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 kernel notifies the vxconfigd daemon on all
the other nodes. The master node then performs any necessary cleanup. If the
master node leaves the cluster, the kernels select 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” on page 443.
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. However, a new node can join the
cluster, as long as the vxconfigd daemon is running on the master node.
If the vxconfigd daemon stops, different actions are taken depending on which
node this occurred:
■ 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 on the slave node has successfully reconnected to the
vxconfigd daemon on the master node, it has very little information about
the shared configuration and any attempts to display or modify the shared
445Administering cluster functionality (CVM)
CVM initialization and configuration