Veritas Volume Manager 5.1 SP1 Troubleshooting Guide (5900-1507, April 2011)

The output from the example shows a match at line 7310 in the command log.
Examining lines 7310 and 7311 in the command log indicates that the vxassist
make command was run on the shareddg disk group:
# sed -e ’7310,7311!d’ cmdlog
# 5302, 589906, Thu Jul 15 06:30:14 2010
/usr/sbin/vxassist -g shareddg make shared-vol1 200M
To determine the cluster monitor nodeid (CM nid) of the slave node, enter the
following command:
# /etc/vx/bin/vxclustadm nidmap
If the command uses disk access (DA) names, the shipped command converts the
DA names to unique disk IDs (UDID) or Disk media (DM) names. On the CVM
master node, the vxconfigd log shows the entry for the received command. To
determine the commands received from slave nodes on the master, enter the
command:
# egrep CMDSHIP_REQUEST /var/adm/messages
Note: The file to which the vxconfigd messages are logged may differ, depending
on where the messages are redirected.
In this example, the following received command would be recorded in the
vxconfigd log on master node:
07/15 06:29:02: V-5-1-0 receive_cmdship_message:
CMDSHIP_REQUEST: Received command:
Text - /usr/sbin/vxassist -g shareddg make shared-vol1 200M len = 53
CLID = 5302 SlaveID = 0 Defaultdg = nodg
The CVM master node executes the received command and sends the response to
the slave node.
To find the response that the master node sent to the slave node, enter a command
such as the following on the master node:
# egrep CMDSHIP_RESPONSE translog | egrep Slave-Clid
In this example, enter the following command to find the response that the master
node sent:
# egrep CMDSHIP_RESPONSE translog | egrep 5302
Thu Jul 15 06:29:03 2010
55Logging commands and transactions
Associating CVM commands issued from slave to master node