Symptoms

File or Block Import Session failure messages in Unisphere: VNX SANCopy Host has not been created for the remote system connection. (Error Code:0x6500219) The specified lun is part of consistency group. (Error Code:0x6500229) Create VDM Import session .......FailedFailed: The source import interface cannot be reached from the target import interface. (Error Code:0x900017a) Create VDM Import session ...... FailedFailed: Cannot find an appropriate source interface to create import session. Create a network interface whose name starts with 'nas_migration_' on the data mover of the source VDM and attach it to the source VDM. Ensure it is in the 'up' state. (Error Code:0x9000144)Create VDM Import session ...... FailedFailed: The source import interface whose name starts with 'nas_migration_' must be in 'up' state. (Error Code:0x9000301)Create VDM Import session ...... FailedFailed: At least one source production interface whose name does not start with 'nas_migration_' must exist and be in 'up' state on the source VDM. (Error Code:0x9000150)Create VDM Import session .......FailedFailed: Create session fails with {0} error(s). Please check message by scp {1}@{2}:{3}/.migration/precheck_vdm_{4}.log. (Error Code:0x9000194) Start VDM Import session ........FailedFailed: Import validate failed : delta time exceeds 5 seconds limitation between import target and source. (Error Code:0x900014f) Start VDM Import session ........FailedFailed: The specified target pool is not big enough to accommodate all UFS64 file system. (Error Code:0x900012d)Create VDM Import session .......FailedFailed: Only one active import session can exist on each storage processor. (Error Code:0x9000184) Create VDM Import session .......FailedFailed: Current value of server parameter nfs.v3xfersize is different between source and destination. Use 'server_param -facility nfs -modify v3xfersize -value ' on source or use '/nas/bin/server_param ALL -facility nfs -modify v3xfersize -value ' on destination to make them equal. (Error Code:0x900019b)

Cause

Various causes, with resolutions outlined below.

Resolution

1) Refer to the following KB for additional information on Best Practices when using the Unity Inband Mobility Tool (IMT), more commonly known as our Import/Migration tool:KB 526213 How to Have A Successful IMT Migrationhttps://emcservice.my.salesforce.com/knowledge/publishing/articleOnlineDetail.apexp?id=kA5f1000000H0xK2) Apply the appropriate resolution from the list below for your Block or NFS Import issue:Common Block Import Issues:No iSCSI Connection Pairs between Source VNX SPs and Unity SPs:VNX SANCopy Host has not been created for the remote system connection. (Error Code:0x6500219)Resolution: a) Ensure that Source VNX SPs and Target Unity SPs have iSCSI IP addresses configuredb) Ensure that iSCSI ports have network cables attached to LAN networkc) Create iSCSI connection pairs from Source VNX SPs to Unity SPsUnisphere > All Systems > rightclick system name > iSCSI > Connections Between Storage Systems > Add: Create iSCSI pairs, Source to Target, between SPA and then SPBd) Update Unity Import > Connections > More Actions > Verify and UpdateTrying to Import Block LUN as Standalone when a member of a CG:The specified lun is part of consistency group. (Error Code:0x6500229)Resolution: a) Import the LUNs from the Consistency Group selection in Import wizard Common File Import Issues:-->There are a number of potential issues that can cause the VDM Import session create, or session start, to failLack of Network Connectivity between VNX VDM interfaces and Unity Mobility Interfaces:Create VDM Import session .......FailedFailed: The source import interface cannot be reached from the target import interface. (Error Code:0x900017a)Resolution: a) Check network cabling, ensure IP addresses are correct, make sure ping succeedsb) Determine what the Interface ID is for the Unity Mobility Interface, then use Ping to verify IP connectivityspa:~> uemcli /net/if showspa:~> uemcli /net/util ping -srcIf if_20 -addr xxx.xxx.xxx.xxxxOperation completed successfully.Source Data Mover does not have an interface configured:Create VDM Import session .......FailedFailed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.227:/home/sysadmin1/.migration/precheck_vdm_V58NFS1.log. (Error Code:0x9000194)# cat /home/sysadmin1/.migration/precheck_vdm_V58NFS1.logError: V58NFS1: DNS server(s) of svt.lab.com is(are) not reachable through the network interface(s) not attached to the VDM. After migration to Unity, the network interfaces attached to the VDM will also get migrated. Other clients of the Data Mover cannot connect to the DNS server(s). Create another network interface on the Data Mover, and if applicable, correct routes and VLAN functions, to make sure it can connect to the DNS server(s).Resolution: a) The Source Data Mover must have at least one network interface configured that is not part of the VDM being migrated. Create an interface on the Source VNX Data Mover.Source Data Mover must have an Interface named nas_migration_xx attached to VDM & be in "UP" state:Create VDM Import session ...... FailedFailed: Cannot find an appropriate source interface to create import session. Create a network interface whose name starts with 'nas_migration_' on the data mover of the source VDM and attach it to the source VDM. Ensure it is in the 'up' state. (Error Code:0x9000144)Create VDM Import session ...... FailedFailed: The source import interface whose name starts with 'nas_migration_' must be in 'up' state. (Error Code:0x9000301)Resolution:a) Create a Source VNX Data Mover interface with a name beginning as nas_migration_xx b) The nas_migration_xx interface must be attached to the VDM that is being imported# nas_server -vdm vdm2 -attach nas_migration_28c) In addition, the nas_migration_xx must be UP and have network connectivitySource Data Mover must have a Production Interface UP and attached to the VDM:Create VDM Import session ...... FailedFailed: At least one source production interface whose name does not start with 'nas_migration_' must exist and be in 'up' state on the source VDM. (Error Code:0x9000150)Resolution:a) Create an interface on the Source Data Mover and attach to the VDM# nas_server -vdm vdm2 -attach xxx.xxx.xxx.xxxb) In addition, the interface must be UP and have network connectivityNTP Time differs by more than 5 seconds between VNX Data Mover (hosting VDM) and Unity:Start VDM Import session ........FailedFailed: Import validate failed : delta time exceeds 5 seconds limitation between import target and source. (Error Code:0x900014f)Resolution: a) Make sure than the Source Data Mover that is hosting the VDM server is configured with the same NTP servers as the Unity system and that the times are in sync within 5 seconds. b) Go to Sessions > More Actions > Resume to start the File Import Session after correcting the NTP Time issue.Target Pool is not large enough for the Migration:Start VDM Import session ........FailedFailed: The specified target pool is not big enough to accommodate all UFS64 file system. (Error Code:0x900012d)Resolution: a) Create a Unity Pool that is large enough to contain the VDM Server and all its File SystemsOnly (1) File Import Session per Unity SP is Allowed:Create VDM Import session .......FailedFailed: Only one active import session can exist on each storage processor. (Error Code:0x9000184)Resolution:a) Only one active File Import Session is allowed for each Unity SP. Create a 2nd session on the Peer SP.Server Parameter checks fail:Create VDM Import session .......FailedFailed: Current value of server parameter nfs.v3xfersize is different between source and destination. Use 'server_param -facility nfs -modify v3xfersize -value ' on source or use '/nas/bin/server_param ALL -facility nfs -modify v3xfersize -value ' on destination to make them equal. (Error Code:0x900019b)Resolution: -->A comparison of server parameters are made between the Unity system and the Source Data Mover on which the VDM resides. Some parameter differences may prevent the Import Session creation from proceeding.1. Bypass parameter checking:When creating an Import Session from the GUI, you can uncheck the box for Allow comparison of Server Parameters , with the understanding that if certain parameters differ between Source and Target systems, NFS transparency cannot be guaranteed. In otherwords, Host access may be disruptive during Cutover operations.If creating a session from CLI, use the -skipServerParamCheck to bypass the parameter checks.2. Preserve parameters:If you wish to guarantee NFS transparency during the migration process, preserve the parameter checking. To pass a failing check, you can modify the parameter value on the Source VNX system to match that of the Unity system, or you can use the svc_param script on Unity to match the param value on the VNX side.Note: Some parameter changes may require a reboot of the VNX Data Mover/Unity SPa) Use the Service Script on Unity to determine the parameter valuespb:~> svc_param ALL -facility nfs -list |grep v3xfersizenfs.v3xfersizespb:~ > svc_param ALL -facility nfs -info v3xfersizeServer parameter value, v3xfersize="262144"b) Use the Server Param facility on the VNX system to determine the parameter value# server_param server_2 -facility nfs -list |grep v3xfersizev3xfersize nfs 131072 131072 131072c) Modify the VNX side or the Unity so that the parameters match each other:# server_param server_2 -facility nfs -modify v3xfersize -value 262144server_2 : doneWarning 17716815750: server_2 : You must reboot server_2 for v3xfersize changes to take effect.orspb:~> svc_param ALL -facility nfs -modify v3xfersize -value 131072Warning 17716815750: SVDM_A : You must reboot SVDM_A for v3xfersize changes to take effect.

Support Cases