CockneyUSA

updated

9 years ago

C

CockneyUSA

1 Rookie

60 Posts

0

4394

January 30th, 2018 09:00

VNX CIFS migration issues

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?

  • aminr3

    11 Posts

    3649

    0

    Posted January 31st, 2018 00:00

    Please check the below KB:


    Dell EMC Unity : VDM Import failing to create, Reporting CIFS VDM incorrectly as NFS VDM (User Correctable) https://support.emc.com/kb/514379



    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

  • Rainer_EMC

    6 Operator

    8645 Posts

    3649

    0

    Posted January 30th, 2018 10:00

    I would suggest to open a service request

    In my experience this needs log file to be looked at

    Unity OE 4.2.2 just got released - It might be worth to try it or at least look at the release notes if something related is fixed there

  • CockneyUSA

    1 Rookie

    60 Posts

    3649

    0

    Posted January 30th, 2018 10:00

    Thanks.  I already did that. I'm awaiting assignment as it's low severity. Read the Release notes.

  • Rainer_EMC

    6 Operator

    8645 Posts

    3649

    0

    Posted January 31st, 2018 07:00

    yes - that would be a common mistake since on VNX you didnt have to attach the interface to a VDM unless you were doing NFS export via VDM

  • CockneyUSA

    1 Rookie

    60 Posts

    3649

    0

    Posted January 31st, 2018 08:00

    That was the problem. 

    [nasadmin@v340cs01 ~]$ nas_server -info -v vdm01

    id        = 1

    name      = vdm01

    acl       = 0

    type      = vdm

    server    = server_2

    rootfs    = root_fs_vdm_vdm01_1

    I18N mode = UNICODE

    Thank you.

  • aminr3

    11 Posts

    3649

    0

    Posted February 2nd, 2018 23:00

    Happy to help!

    -Ramya Amin

  • clignel

    7 Posts

    3144

    0

    Posted May 20th, 2019 08:00

    Hello,

    Hello,

    I have almost the same problem.

    Unisphere shows the VDM as "NFS" instead of "CIFS"

    here are the parameters of the VDM

    id = 1
    name = VDM01
    acl = 0
    type = vdm
    server = server_2
    rootfs = root_fs_vdm_VDM01
    I18N mode = UNICODE
    defined = enabled
    actual = loaded, active
    Interfaces to services mapping:
    interface=nas_migration_VDM01 :cifs
    interface=int_vdm02 :vdm

     

    Thank you very much for your help.

    Best regards

  • keeban

    1 Rookie

    66 Posts

    1917

    0

    Posted July 16th, 2020 07:00

    hi clignel,

    how to add nas_migration port to VDM

    id = 1
    name = VDM01
    acl = 0
    type = vdm
    server = server_2
    rootfs = root_fs_vdm_VDM01
    I18N mode = UNICODE
    defined = enabled
    actual = loaded, active
    Interfaces to services mapping:
    interface=nas_migration_VDM01 :cifs
    interface=int_vdm02 :vdm     <---------------this port.

    and how to add this interface to sub domain?is it required to create subdomain in domain controller?

     

  • keeban

    1 Rookie

    66 Posts

    1919

    0

    Posted July 16th, 2020 07:00

    hi all,

    am also facing issue with vnx to unity migration.

    i want know one thing.this below interface should be physical or virtual?

    nas_migration_xx interface

    below steps i followed but failed

    below steps i followed.

    requireed cifs perameters also changed in vnx

    01.DNS and NTP sync between vnx to unity xt

    02.enabled local admin in vnx

    server_cifs -add compname= ,domain= ,local_users

    03.Create nas migration port

    [nasadmin@VNX5400 ~]$ server_ifconfig server_2 -create -Device cge-1-1 -name nas_migration_vnx5400 -protocol IP 10.10.10.10 255.255.255.0 10.10.10.1

    04.Interface attached to the VDM

    [nasadmin@VNX5400 ~]$ nas_server -vdm vdm11 –attach nas_migration_vnx5400

    05.Create subdomain entry for nas_migration interface

    [nasadmin@VNX5400 ~]$ server_cifs vdm-1 -add compname=test,domain=test.lk,interface=nas_migration_vnx5400,dns=vnx.migration.test.lk

    from unity

    01 crated import interfaces with two ips(spa and spb)

    02 created import connection