Please check the below KB:  Dell EMC Unity : VDM Import failing to create, Reporting CIFS VDM incorrectly as NFS VDM (User Correctable) [URL]   If even after re-naming the VDM, in Unity while importing if it gives any error like "nas_migration_XX interface isn't attached", please check if the CIFS server's interface on the VDM is attached to VDM along with nas_migration_XX interface: $ nas_server -info -vdm  Interfaces to services mapping: interface=FSN1_102 :cifs          <<<<<  interface=nas_migration_002 :nfs  <<<<<<  Hope it helps.  -Ramya Amin
Hi.  I am trying to migrate a CIFS server from a VNX5600 to Unity 300.  Created new vdm for test. VNX VDM Name: vdm02 New CIFS server, file system and shares  After creating a connection on the Unity this VDM shows up in the session list as vdm02. Migration works fine and completes. This also worked for another vdm named vdmtest.  When it comes to migrating the production CIFS server I get the following issues.  VNX VDM Name: vdm01  After creating a connection on the Unity this VDM shows up in the session list as vdm01_1 (nfs)  Created another vdm. VNX VDM Name: vdm01_1  After creating a connection on the Unity this VDM shows up in the session list as vdm01_1_1 (nfs)  I cannot get vdm01 to show up as a CIFS source or even get the name correct.  I have followed the requirements from the documentation.  I've checked the differing vdms and CIFS servers and can see no differences.  Ideas?
VNX CIFS migration issues