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

master when the cluster is not handling VxVM configuration changes or cluster
reconfiguration operations.
The reinit keyword allows nodes to be added to or removed from a cluster without
stopping the cluster. Before running this command, the cluster configuration file
must have been updated with information about the supported nodes in the cluster.
The nidmap keyword prints a table showing the mapping between CVM node IDs
in VxVM’s cluster-support subsystem and node IDs in the cluster monitor. It also
prints the state of the nodes in the cluster.
The nodestate keyword reports the state of a cluster node and also the reason
for the last abort of the node as shown in this example:
# vxclustadm nodestate
state: out of cluster
reason: user initiated stop
Table 13-5 lists the various reasons that may be given for a node abort.
Table 13-5
Node abort messages
DescriptionReason
Missing disk or bad disk on the slave node.cannot find disk on slave node
The node cannot read the configuration data due
to an error such as disk failure.
cannot obtain configuration
data
Open of a cluster device failed.cluster device open failed
Clustering license does not match that on the
master node.
clustering license mismatch
with master node
Clustering license cannot be found.clustering license not
available
The join operation of a node refused by the master
node.
connection refused by master
A disk belongs to a cluster other than the one that
a node is joining.
disk in use by another cluster
The join operation of a node has timed out due to
reconfiguration taking place in the cluster.
join timed out during
reconfiguration
Cannot update kernel log copies during the join
operation of a node.
klog update failed
Administering cluster functionality (CVM)
CVM initialization and configuration
442