 | ||
| Command shipping | ||
|---|---|---|
| Prev | Configuring Cluster Volume Manager (CVM) | Next |
Clustered Volume Manager (CVM) designates one of the cluster nodes as the Master node for the cluster and all the other nodes become Slave nodes. The CVM architecture allows the administrative operations for cluster-shared disk groups (CSDGs), such as disk group creation and volume creation, only on the Master node. With the command shipping feature, the user can execute the supported commands from any of the nodes in the cluster.
The SFW configuration view may differ from node to node in the CVM cluster. For example, disk access (DA) names of the disks in cluster-shared disk groups can differ from node to node. Therefore, you cannot run the commands from the Slave nodes using the SFW configuration view on that node.
Note the following error handling for the commands that you issue from the Slave node, which CVM runs on the Master:
If the vxconfigd daemon on either the Slave node or on the Master node fails, the command exits. The instance of the command on the Master also exits. To determine if the command executed successfully, use the vxprint command to check the status of the VxVM objects.
If the Slave node that shipped the command or the Master node leaves the cluster while the Master executes the command, the command exits on the Master node as well as on the Slave node. To determine if the command executed successfully, use the vxprint command to check the status of the VxVM objects.