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

Table 13-5
Node abort messages (continued)
DescriptionReason
Master node aborted while another node was
joining the cluster.
master aborted during join
Cluster protocol version mismatch or unsupported
version.
protocol version out of range
Volumes that were opened by the node are still
recovering.
recovery in progress
Changing the role of a node to be the master
failed.
transition to role failed
Node is out of cluster due to an abort initiated by
the user or by the cluster monitor.
user initiated abort
Node is out of cluster due to a stop initiated by
the user or by the cluster monitor.
user initiated stop
The VxVM configuration daemon is not enabled.vxconfigd is not enabled
See the vxclustadm(1M) manual page.
Volume reconfiguration
Volume reconfiguration is the process of creating, changing, and removing VxVM
objects such as disk groups, volumes and plexes. In a cluster, all nodes cooperate
to perform such operations. The vxconfigd daemons play an active role in volume
reconfiguration. For reconfiguration to succeed, a vxconfigd daemon must be
running on each of the nodes.
See “vxconfigd daemon” on page 444.
A volume reconfiguration transaction is initiated by running a VxVM utility on
the master node. The utility contacts the local vxconfigd daemon on the master
node, which validates the requested change. For example, vxconfigd rejects an
attempt to create a new disk group with the same name as an existing disk group.
The vxconfigd daemon on the master node then sends details of the changes to
the vxconfigd daemons on the slave nodes. The vxconfigd daemons on the slave
nodes then perform their own checking. For example, each slave node checks that
it does not have a private disk group with the same name as the one being created.
If the operation involves a new disk, each node checks that it can access that disk.
When the vxconfigd daemons on all the nodes agree that the proposed change
is reasonable, each notifies its kernel. The kernels then cooperate to either commit
443Administering cluster functionality (CVM)
CVM initialization and configuration