Symptoms

Common Session Create or Session Start failures: Failed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.226:/home/sysadmin1/.migration/precheck_vdm_vdm1.log. (Error Code:0x9000194) # cat /home/sysadmin1/.migration/precheck_vdm_vdm1.log Error: vdm1: CIFS migration can not be used on the source VDM with NFS exports. Failed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.226:/home/sysadmin1/.migration/precheck_vdm_vdm1.log. (Error Code:0x9000194) # cat /home/sysadmin1/.migration/precheck_vdm_vdm1.log Error: vdm1: Bad value for parameter cifs.acl.extacl (should have bits 2,3 and 4 set) Error: vdm1: Unknown SID feature is not enabled (param cifs.acl.mappingErrorAction must be set to 0x0b) Failed: Checking CIFS username/password operation failed. (Error Code:0x900a31d) Failed: Destination NAS server does not have configured DNS to join CIFS server to Active Directory. (Error Code:0x90001f3) Failed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.241.166.223:/home/sysadmin1/.migration/precheck_vdm_vdm11.log. (Error Code:0x9000194) Non-importable since there is no network interface whose name start with 'nas_migration_' attached to source VDM. Failed: Create session fails with 2 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.226:/home/sysadmin1/.migration/precheck_vdm_vdm3.log. (Error Code:0x9000194) # cat /home/sysadmin1/.migration/precheck_vdm_vdm3.log Error: vdm3: No migration interface found in the CIFS server of the source VDM. Create a migration network interface and add it to the source CIFS server of the VDM. Failed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.226:/home/sysadmin1/.migration/precheck_vdm_vdm3.log. (Error Code:0x9000194) # cat /home/sysadmin1/.migration/precheck_vdm_vdm3.log Error: vdm3: Local users are not enabled on the source CIFS server. Failed: The specified operation could not be completed. Search for the error code on the support website or product forums, or contact your service provider, if available. (Error Code:0x4) # cat /home/sysadmin1/.migration/precheck_vdm_vdm3.log Error: vdm3: Local users are not enabled on the source CIFS server. Failed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.226:/home/sysadmin1/.migration/precheck_vdm_vdm4.log. (Error Code:0x9000194) # cat /home/sysadmin1/.migration/precheck_vdm_vdm4.log Error: vdm4: Too many CIFS servers in the source VDM. Failed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.226:/home/sysadmin1/.migration/precheck_vdm_vdm5.log. (Error Code:0x9000194) # cat /home/sysadmin1/.migration/precheck_vdm_vdm5.log Error: vdm5: The production interface and the migration interface are in the same domain in the source VDM. Failed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.227:/home/sysadmin1/.migration/precheck_vdm_vdm5800.log. (Error Code:0x9000194) Error: vdm5800: Bad value for parameter cifs.admin.shareC_RO (should not have value 1). The Source CIFS Server C$ Share needs to be set for Read Write access in order to support a CIFS VDM Import operation, so set cifs.admin.shareC_RO value to 0 to disable RO access on the source VDM. Failed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.227:/home/sysadmin1/.migration/precheck_vdm_vdm5800.log. (Error Code:0x9000194) Error: vdm5800: Bad value for parameter cifs.admin.shareC_NotCreated (should not have value 1). The source CIFS Server C$ share needs to be created in order to support a CIFS VDM Import operation, so set cifs.admin.shareC_notCreated value to 0 to allow C$ to be created on source VDM. Failed: Import source side error: specified file or directory does not exist. Please check that and make sure the source side control station is primary(use /nasmcd/sbin/t2slot and /nasmcd/sbin/getreason), if not, please switch it back to primary via '/nasmcd/sbin/cs_standby -takeover'. (Error Code:0x9000153) Dual Control Stations and remote connection failures: Failed: The remote sys user home directory does not exist. Solution: for dual-control station VNX, failover control station via command '/nasmcd/sbin/cs_standby -failover'. Delete and re-create VNX remote system. (Error Code:0x90001b6) Failed: Internal error: VNX command parser failed. (Error Code:0x900010b) Cutover failures:The system can not verify that specified computer name for renaming CIFS server is unique in the Active Directory domain. Please try again later. (Error Code:0x90001dc)

Cause

Failure to create an Import Session, or to start the Import Session, has many possible causes. Best practices for configuring and starting an import session are listed in the Resolution section.

Resolution

1. Refer to the following KB for additional information about Best Practices when using the Unity Inband Mobility Tool (IMT), more commonly known as our Import/Migration tool: Dell Unity: How To Have A Successful IMT Migration (User Correctable) 2. Apply the appropriate resolution to your CIFS/SMB VDM Import issue from the list below: Source VDM Contains NFS Exports: If there are NFS exports on the Source VDM, the SMB Import Session create fails.Failed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.226:/home/sysadmin1/.migration/precheck_vdm_vdm1.log. (Error Code:0x9000194) # cat /home/sysadmin1/.migration/precheck_vdm_vdm1.log Error: vdm1: CIFS migration can not be used on the source VDM with NFS exports. Resolution:Ensure that you permanently unexport NFS Exports on the Source VDM. # server_export vdm1 -unexport -perm -P nfs -name nfs1 /nfs1 Note: If you do not use "-perm," the Export does not show from CLI, but the database entry remains. You may also have to reexport the NFS entry before doing the permanent unexport. # cat /nas/server/vdm/vdm_1/export export "/nfs1" name="/nfs1" DNS Domains are the same for the CIFS Production interface and nas_migration interface: When adding the nas_migration_x interface to the Source CIFS Server instance, you must specify a DNS domain value, or subdomain, that is different from what is used by the production CIFS Server interface, even if you must create a new domain zone, as shown in the example below (with dynamic dns, the new zone is automatically added) Create Import Session fails: Failed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.226:/home/sysadmin1/.migration/precheck_vdm_vdm5.log. (Error Code:0x9000194) # cat /home/sysadmin1/.migration/precheck_vdm_vdm5.log Error: vdm5: The nas_migration interface must be added to the CIFS Server using a different DNS subdomain than the production interface. Use server_cifs -add compname=xxx,domain=company.domain.com, interface=nas_migration_x,dns=lab.domain.com Resolution:Ensure that the dns subdomain for the nas_migration interface is set to a different value than the production CIFS Server. # server_cifs vdm5 -add compname=v5,domain=svt.lab.com,interface=nas_migration_51,dns=test.svt.lab.com vdm5 : done The required Source Data Mover ACL Parameters are not set to the correct value: Failed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.227:/home/sysadmin1/.migration/precheck_vdm_vdm1.log. (Error Code:0x9000194) # cat /home/sysadmin1/.migration/precheck_vdm_vdm1.log Error: vdm1: Bad value for parameter cifs.acl.extacl (should have bits 2,3 and 4 set) Error: vdm1: Unknown SID feature is not enabled (param cifs.acl.mappingErrorAction must be set to 0x0b) Resolution: Set the acl.extacl parameter value to 28 and retry the Session Create (Bits 2, 3, 4 = decimal 28)Set the acl.mappingErrorAction parameter value to 11 and retry the Session Create (0xb=decimal 11) # server_param server_2 -facility cifs -modify acl.extacl -value 28 server_2 : done # server_param server_2 -facility cifs -modify acl.mappingErrorAction -value 11 server_2 : done Note: These parameter changes take immediate effect, no Data Mover reboot required. Incorrect Source CIFS Server Credentials Specified: Failed: Checking CIFS username/password operation failed. (Error Code:0x900a31d)Resolution:Verify local username account and password on the Source CIFS Server. Missing DNS Settings on Source Data Mover: Failed: Destination NAS server does not have configured DNS to join CIFS server to Active Directory. (Error Code:0x90001f3)Resolution:Set appropriate Active Directory DNS domain settings on the Source Data Mover. # server_dns server_2 svt.lab.com 10.240.160.160,10.240.160.161 server_2 : done Source Data Mover does not have an interface configured: Create VDM Import session X FailedFailed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.227:/home/sysadmin1/.migration/precheck_vdm_vdm11.log. (Error Code:0x9000194) # cat /home/sysadmin1/.migration/precheck_vdm_vdm11.log Error: vdm11: 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). Warning: vdm11: Domain Controller(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 Domain Controller(s). Create another network interface on the Data Mover to make sure it can connect to the Domain Controller(s). Resolution: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. Missing NAS Migration Interface on Source VDM and CIFS Server: Session Create Wizard shows failure right after selecting the Source VDM.Non-importable since there is no network interface whose name start with 'nas_migration_' attached to source VDM. Please go to Import > Connection > Discover Import and perform discover operation to refresh the source storage resource list and then try to create the Import Session.Resolution:Configure a nas_migration_x interface and attach to the Source VDM and to the VDM CIFS Server. # server_ifconfig server_2 -create -Device cxg-1-0 -name nas_migration_40 -p IP 10.240.160.40 255.255.255.0 10.240.160.255 # nas_server -vdm vdm3 -attach nas_migration_40 # server_cifs vdm3 -add compname=v3,domain=svt.lab.com,interface=nas_migration_40,dns=test.lab.com Note: DNS subdomain for migration interface must be different from CIFS server domain # nas_server -info -vdm vdm3 interface=nas_migration_40 :cifs vdm interface=10-240-160-26 :cifs vdm Missing NAS Migration Interface from Source CIFS Server: Failed: Create session fails with 2 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.226:/home/sysadmin1/.migration/precheck_vdm_vdm3.log. (Error Code:0x9000194) # cat /home/sysadmin1/.migration/precheck_vdm_vdm3.log Error: vdm3: No migration interface found in the CIFS server of the source VDM. Create a migration network interface and add it to the source CIFS server of the VDM. # nas_server -info -vdm vdm3 interface=10-240-160-169 :cifs vdm interface=nas_migration_191 :vdm Resolution:Add nas_migration_191 interface to Source CIFS Server. # server_cifs vdm3 -add compname=v3,domain=svt.lab.com,interface=nas_migration_191,dns=test.lab.com vdm3 : done Local Users Support is not enabled on Source CIFS Server: Create VDM Import Session fails.Failed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.227:/home/sysadmin1/.migration/precheck_vdm_vdm3.log. (Error Code:0x9000194) # cat /home/sysadmin1/.migration/precheck_vdm_vdm3.log Error: vdm3: Local users are not enabled on the source CIFS server. Resolution: Add Local Users Support on Source CIFS Server from CLI or UI, update local administrator password, add local administrator user to Backup Operators local groups # server_cifs vdm3 -add compname=v3,domain=svt.lab.com,local_users vdm3 : Enter Password:********* Enter Password Again:********* done Update local administrator password on CIFS Server using member domain server ctrl + alt + del sequence Change a Password > In the top box, enter user CIFS Server IP address or FQDN\user: v3.svt.lab.com\administratorAlternatively, once Local Users are enabled, use Computer Management from a domain Member Server to connect to the CIFS Server, and Set Password to change the password for the local administrator userUse Computer Management to add a local administrator user to the Backup Operators groupInstead of the local administrator user, you can also create a new local user for the VDM Import from Computer Management, create a password, update the password as in the above instructions, then add the user to the Groups >Administrators and Backup Operators Local Users Support enabled but temporary local administrator password not changed:Or, new Local user created but password not changed: Start VDM Import Session fails.Failed: The administrator password has expired on the source VNX. Please change the password and try again. (Error Code:0x900a332)Resolution: After enabling Local Users support on the CIFS server, ensure that the local administrator password is changed Update local administrator password on CIFS Server using member domain server ctrl + alt + del sequence (or change using Computer Management connected to the CIFS Server) Change a Password > In the top box, enter CIFS Server IP address or FQDN\administrator: v3.svt.lab.com\administrator Ensure that the Local User account used for the migration has been added to the Administrators and Backup Operators local groupsIf a new Local User was created for use with the migration, ensure to change the password Multiple CIFS Servers on the VNX VDM: Unity SMB Import supports only a single CIFS Server on the VNX VDMCreate Import Session fails Failed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.227:/home/sysadmin1/.migration/precheck_vdm_vdm4.log. (Error Code:0x9000194) # cat /home/sysadmin1/.migration/precheck_vdm_vdm4.log Error: vdm4: Too many CIFS servers in the source VDM. Resolution:You must reconfigure the Source VDM for only a single CIFS Server. Source VDM CIFS Server C$ Share is set to RO Access: Source CIFS Server C$ share is set to Read-Only access.Create VDM Import session X FailedFailed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.227:/home/sysadmin1/.migration/precheck_vdm_vdm5800.log. (Error Code:0x9000194)Resolution: Precheck log in VNX system explains the issue: # cat /home/sysadmin1/.migration/precheck_vdm_vdm5800.log Error: vdm5800: Bad value for parameter cifs.admin.shareC_RO (should not have value 1). The Source CIFS Server C$ Share needs to be set for Read Write access in order to support a CIFS VDM Import operation, so set cifs.admin.shareC_RO value to 0 to disable RO access on the source VDM. The Source Data Mover C$ access parameter must be set to 0 to enable RW access for Import migration # server_param server_2 -facility cifs -modify admin.shareC_RO -value 0 Note: Requires CIFS Stop and Restart on Source VNX Data Mover # server_setup server_2 -P cifs -o stop | start Source VDM CIFS Server C$ Share is Disabled: Source CIFS Server C$ share is disabled.Create VDM Import session X FailedFailed: Create session fails with 1 error(s). Please check message by scp sysadmin@storageDomain@10.240.160.227:/home/sysadmin1/.migration/precheck_vdm_vdm5800.log. (Error Code:0x9000194)Resolution: Precheck log in VNX system explains the issue: # cat /home/sysadminx/.migration/precheck_vdm_vdm5800.log Error: vdm5800: Bad value for parameter cifs.admin.shareC_NotCreated (should not have value 1). The source CIFS Server C$ share needs to be created in order to support a CIFS VDM Import operation, so set cifs.admin.shareC_notCreated value to 0 to allow C$ to be created on source VDM. Failure is seen in /EMC/CEM/log/cemtracer_migration.log Server parameter error: Parameter cifs.admin.shareC_NotCreated's current value on source(1) is different from it on destination(0).The Source Data Mover C$ share must be enabled to support VDM Import migration # server_param server_2 -facility cifs -modify admin.shareC_NotCreated -value 0 Note: Requires CIFS Stop and Restart on Source VNX Data Mover # server_setup server_2 -P cifs -o stop | start NAS Servers none default naming convention causes initial setup failure: (Error Code:0x9000153) Temporarily rename any none default nas-server back to the default naming convention for the migration to initiate properly.For example: # nas_server -rename CorpVNX2 server_2 Rerun Unity Unisphere rediscover and retry IMT setup.Alternatively, initiate the IMT session WITHOUT a param check bypasses this error. Error during Cut Over: Error 01: Import source side VDM mounted file system(s) configuration changed. (Error Code:0x900015e)Cause:Once VDM import session has been created with Unity, configuration changes are not permitted at the VNX. Above error, 0x9000015e will be thrown if any new FS added/Mounted to the VNX VDM after the Import Session was created (for example, during Cut Over).Resolution:Permanently unmount the source "new" file system(s) (server_umount vdm -permanent FS_Name) and retry the cut over. Error during Cut Over: Error 02: Source system has returned an invalid response. (Error Code:0x900a322)Cause:Invalid configuration on the VNX. One reason can likely be related with previous error 0x900015e. If a file system is unmounted but the share has not been unexported, this error can be seen.Review of /EMC/CEM/log/cemtracer_migration.log shows: DENY_SOURCE_SHARESResolution:On the Source VNX VDM NAS Server, unexport the cifs share (server_export vdm -P cifs -unexport -name <sharename>) and retry the cut over. Cutover Error: The system can not verify that specified computer name for renaming CIFS server is unique in the Active Directory domain. Please try again later. (Error Code:0x90001dc)Cause:Used FQDN name for user account, use only the "username"See the following article for more information:Dell Unity: Import Cutover fails with when renaming CIFS server (Error Code:0x90001dc) (Dell Correctable) Dual Control Station issues with creating Remote Import Connection to VNX: Failed: The remote sys user home directory does not exist. Solution: for dual-control station VNX, failover control station via command '/nasmcd/sbin/cs_standby -failover'. Delete and re-create VNX remote system. (Error Code:0x90001b6)Failed: Internal error: VNX command parser failed. (Error Code:0x900010b)See the following article for more information:Dell Unity: Performing VDM Migration tasks (File Import) with VNX dual Control Station environments can fail with Error Code:0x90001b6 or 0x900010b. (User Correctable) NFS and Block Import Issues: See the following article for more information about NFS VDM Import/Block Import (IMT) Issues and Resolutions:Dell Unity: NFS VDM Import/Block Import (IMT) Issues and Resolutions (User Correctable) Additional issues/items to watch out for: If your source VNX uses DHSM, ensure that file recalls are not disabled.If either your source or your destination has quotas enabled, ensure that the migration data does not exceed your quota, or the migration fails. If the migration cutover fails due to a Quota exceeded issue, you must increase the source VNX quotas, and then increase the destination Unity quotas.Ensure that you have more space in your destination file system than your source. Do not forget to account for space differences caused by variations in block storage size (that is you may end up using more storage space on the destination than you used on the source) so give yourself extra room on the destinationAlso note that Data Reduction (that is, Compression/Deduplication) is not automatically enabled on the Unity migration destination, so if your space calculations involve data reduction, ensure that you have adequate space on the destination before you start

Support Cases