Dell EMC Unity: Cannot create File Import session if source VNX Data Mover does not have interface for Name Services
Summary: Dell EMC Unity: Cannot create File Import session if source VNX Data Mover does not have interface for Name Services, Error 0x9000194.
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Unity Import > Sessions > Create Import Session Failed......Details:
Failed: Create session fails with {0} error(s). Please check message by scp {1}@{2}:{3}/.migration/precheck_vdm_{4}.log. (Error Code:0x9000194)
UEMCLI create Import Session Failed:
spb:/> uemcli -u admin -p <passwd> /import/session/nas create -name vdm -srcSys RS_65596 -srcRes vdm2 -targetResPool pool_6 -targetImportIf if_26 -productionIfPortPairs 10-240-160-40:spa_eth2 -defaultProductionPort spa_eth2
Operation failed. Error code: 0x9000194
Create session fails with 3 error(s). Please check message by scp sysadmin@storageDomain@10.241.166.177:/home/sysadmin3/.migration/precheck_vdm_vdm2.log. (Error Code:0x9000194)
Job ID = N-1657
# cat /home/sysadmin3/.migration/precheck_vdm_vdm2.log
Error: vdm2: NIS server(s) of svt 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 NIS server(s). Create another network interface on the Data Mover to make sure it can connect to the NIS server(s).
Error: vdm2: 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 to make sure it can connect to the DNS server(s).
Cause
If the Source Data Mover is configured for DNS, NIS, or LDAP Name Services, but does not have additional active interfaces, except for those interfaces used for the current VDM Import operation (i.e., nas_migration_xx & production interface), then the File Import create session will not be allowed and will fail.
The GUI Details message is malformed and does not provide clear guidance on what to do. If you had used the CLI to perform the Session create, the failure message will provide the actual path (on the VNX) where the precheck log can be found, but does not otherwise explain the nature of the issue.
The GUI Details message is malformed and does not provide clear guidance on what to do. If you had used the CLI to perform the Session create, the failure message will provide the actual path (on the VNX) where the precheck log can be found, but does not otherwise explain the nature of the issue.
Resolution
On the Source VNX Data Mover that is used to host the VDM that is in the process of being migrated, create at least one interface that is not attached to any VDM, then retry the File Import Session create task.
Additional Information
Example of the precheck log (and path) that is generated on the Source VNX system, for File Import session creation:
# cat /home/sysadmin3/.migration/precheck_vdm_vdm2.log
Error: vdm2: NIS server(s) of svt 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 NIS server(s). Create another network interface on the Data Mover to make sure it can connect to the NIS server(s).
Error: vdm2: 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 to make sure it can connect to the DNS server(s).
The above output means that there is a NIS domain, and a DNS domain, defined on the physical Data Mover, and that there will not be any interfaces left to support name service resolution if the current VDM Import operation were to proceed, without first applying the resolution, which is to create an additional interface on the VNX Data Mover.
# cat /home/sysadmin3/.migration/precheck_vdm_vdm2.log
Error: vdm2: NIS server(s) of svt 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 NIS server(s). Create another network interface on the Data Mover to make sure it can connect to the NIS server(s).
Error: vdm2: 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 to make sure it can connect to the DNS server(s).
The above output means that there is a NIS domain, and a DNS domain, defined on the physical Data Mover, and that there will not be any interfaces left to support name service resolution if the current VDM Import operation were to proceed, without first applying the resolution, which is to create an additional interface on the VNX Data Mover.
Affected Products
Dell EMC Unity Family |Dell EMC Unity All FlashProducts
Dell Unity 300, Dell EMC Unity 300F, Dell EMC Unity 400, Dell EMC Unity 400F, Dell EMC Unity 500, Dell EMC Unity 500F, Dell EMC Unity 600, Dell EMC Unity Family |Dell EMC Unity All Flash, Dell EMC Unity HybridArticle Properties
Article Number: 000054764
Article Type: Solution
Last Modified: 04 Nov 2025
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.