The vxclustadm command provides an interface to the CVM functionality of VxVM when VCS is used as the cluster monitor. It is also called during cluster startup and shutdown. In the absence of a cluster monitor, vxclustadm can also be used to activate or deactivate the CVM functionality of VxVM on any node in a cluster.
The startnode keyword to vxclustadm starts CVM functionality on a cluster node by passing cluster configuration information to the VxVM kernel. In response to this command, the kernel and the VxVM configuration daemon, vxconfigd, perform initialization.
The stopnode keyword stops CVM functionality on a node. It waits for all outstanding I/O to complete and for all applications to close shared volumes.
The setmaster keyword migrates the CVM master to the specified node. The migration is an online operation. Symantec recommends that you switch the 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: Node abort messages lists the various reasons that may be given for a node abort.
Table: Node abort messages
See the vxclustadm(1M) manual page.