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

For example, on the slave node, you run the following command, to create a volume

in a shared disk group. CVM ships the command to the master node, and CVM

executes the command on the master node.

# vxassist -g shareddg make shared-vol1 200M

On the CVM slave node, enter the following command to identify the shipped

command from the transaction log (translog):

# egrep CMDSHIP_REQUEST translog

In this example, the following entry was recorded in the transaction log on slave

node:

Thu Jul 15 06:30:16 2010

Clid = 5302, PID = 589906, Part = 0, Status = 0, Abort Reason = 0

DG_SET_CURRENT_ID shareddg

DG_SET_CURRENT shareddg

DG_GETCFG_ID 0xdde49f shareddg

DG_GETCFG_NAME 0xdde49f shareddg

DG_SET_CURRENT_ID shareddg

DG_SET_CURRENT shareddg

DG_SET_CURRENT_ID shareddg

DG_SET_CURRENT shareddg

DG_GETCFG_ALL 0x420

VOL_TRANS ds4700-0_7 ds4700-0_3 ds4700-0_

DG_GET_DEFAULT <no request data>

CMDSHIP_REQUEST Command Shipped = /usr/sbin/vxassist -g

shareddg make shared-vol1 200M

Default dg = nodg

DROPPED <no request data>

To locate the utility that issued this request on slave node, enter the following

command:

# egrep -n PID cmdlog | egrep Clid

In this example, enter the following command:

# egrep -n 589906 cmdlog | egrep 5302

7310#: 5302, 589906, Thu Jul 15 06:30:14 2010 /usr/sbin/vxassist -g

Logging commands and transactions

Associating CVM commands issued from slave to master node