Messages such as the following are written to the messages log:
Apr 17 02:29:52 xxxxxxxxxxx vxvm:vxconfigd: V-5-1-16766 Trying to import the disk group dg01 using configuration database copy from powerstore1_0
Apr 17 02:29:52 xxxxxxxxxxx vxvm:vxconfigd: V-5-1-20145 dg dg01 core db write: dgimport_cnt = 0.0 configtid = 0.1254
Apr 17 02:29:53 xxxxxxxxxxx vxvm:vxconfigd: V-5-1-20218 Read klog from powerstore1_0
Apr 17 02:29:53 xxxxxxxxxxx vxvm:vxconfigd: V-5-1-20218 Read klog from powerstore1_3
Apr 17 02:29:53 xxxxxxxxxxx vxvm:vxconfigd: V-5-1-20218 Read klog from powerstore1_0
Apr 17 02:29:53 xxxxxxxxxxx vxvm:vxconfigd: V-5-1-20218 Read klog from powerstore1_3
Apr 17 02:29:53 xxxxxxxxxxx vxvm:vxconfigd: V-5-1-16253 Disk group import of dg01 failed with error 373 - SCSI-3 PR operation failed
Apr 17 02:29:53 xxxxxxxxxxx kernel: VxVM vxio V-5-0-1910 Cleaning incomplete shared diskgroup dg01 dgiid 33792.32 :
When fencing is configured as CP server based, disk groups are still imported with SCSI3 reservations. This causes SCSI3 PR errors during the import and it will take long time due to retries.
Edit the file /opt/VRTSvcs/bin/CVMVolDg/actions/import file on all nodes in the cluster replacing the line
if [ "$usefence" -a $shared -eq 0 ]
with
if [ "$usefence" -a $scsipr3_state -eq 1 -a $shared -eq 0 ]