VPLEX: VMware Storage VMotion Fail reporting Loss of volume access on VPlex

A storage VMotion task failed, of a VM from a datastore to a new datastore, both presented by VPlex. User encounter the following error message:

Loss of volume access 5xxxxxxx-xxxxxxxx-xxxx-xxxxxxxxxxxx (Vxxxxxxxxxx1) because of Connectivity issues. An attempt to Is in progress and the result will be transmitted to very soon.

On VPlex a stream of stdf/41 in the firmware logs against the target datastore LUN.

xxx.xxx.xxx.68/cpu0/log:5988:W/"00601661363310745-2":3157776:<4>2017/02/15 14:19:37.29: stdf/41 xcopy malformed command, target lu not supported, ITL fcp: (0x100000xxxxxxxxxx)(0x500014xxxxxxxxxx)(0x0, VPD83T3:6000144xxxxxxxxxxxxxxxxxxxxxxxxx)

stdf/41 event "xcopy malformed command, target lu not supported" would be logged if any of the following conditions are met: 

1. WWN provided in the target descriptor does not correspond to any LU.   
2. STDFLU private data pointer is NULL. 
3. If the LU is not exported. (Does not belong to a storage view or not masked through this director) 

This validation happens for both source LU and target LU. 
The xcopy command which arrives on a director should have both the source and target LU to be in exported state, i.e. both source LU and target LU must be exported through the same directors in the storage views.

NOTE: The stdf/41 event currently prints the LUN on which the xcopy CDB has arrived i.e. target LU, the customer should advise on the source LUN.

Confirm that both source LU and target LU must be exported through the same directors in the storage views.