Error Message

2011/01/28 08:37:13 VCS ERROR V-16-20062-48 (hostA) SVCCopyServices:SVC_ResourceA:online:Command /usr/sbin/vxdisk clearimport  failed, return code: 1, output:
VxVM vxdisk ERROR V-5-1-693 Incorrect usage
Usage:
      vxdisk [-f] clearimport accessname ...
2011/01/28 08:37:13 VCS ERROR V-16-20062-47 (hostA) SVCCopyServices:SVC_ResourceA:online:Could not update udid of the disk ; exiting;

The VCS SVCCopyServices agent relies on the LUN_SERIAL_NO shown in "vxdisk -p list" output to match the VDISK UID of the SVC disks.    In a VIOS (vscsi) environment, the LUN_SERIAL_NO is altered by the VIOS server and will not match the VDISK UID.  For example,

# vxdisk -p ibm_vscsi0_0
DISK           : ibm_vscsi0_0
LUN_SERIAL_NO  : 00f62a6e00004c000000012b878e42e1.1
DISK           : v_san_vc0_1
DISKID         : 1295890513.6.isvp12
LUN_SERIAL_NO  : 332136005076802830002800000000000000A04214503IBMfcp       <<< The LUN Serial Number is altered by the VIOS server
.....

In a VIOS environment, there are 5 extra bytes prepended to the LUN Serial Number and together with some extra bytes appended at the end.   In the above example, "33213" is prepended to the VDISK UID "6005076802830002800000000000000A".  "04214503IBMfcp" is appended to the VDISK UID.

The following is the corresponding VDISK UID shown in the svcinfo lsvdisk output.

IBM_2076:ISV7K4:admin>svcinfo lsvdisk -delim : 6

vdisk_UID:6005076802830002800000000000000A              <<< VDISK UID

The mismatch between LUN_SERIAL_NO and VDISK_UID causes the SVCCopyServices agent to fail to process the LUNs properly.  The VxVM command ran by the agent fails with the error messages.

The problem is fixed by extracting the correct VDISK UID from the LUN_SERIAL_NO.  The bytes added by the VIOS server are stripped by the agent.  The fix will be available in the future release of the SVCCopyServices agent.

Applies To

Veritas Cluster Service (VCS) environment with SVCCopyServices resource configured.