Unsolved

This post is more than 5 years old

15 Posts

3324

February 3rd, 2014 07:00

clariion to vmax migration OR Hot Pull

Hi All,

Can someone  provide me  documents or guide me  through the steps for  migrating storage from  clariion to vmax using OR hot pull? 

Thank you in advance .

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

February 3rd, 2014 08:00

does not look it's customer accessible.

15 Posts

February 3rd, 2014 08:00

  Chris,

  I cannot access this document is there a way to access it .

1 Rookie

 • 

52 Posts

February 3rd, 2014 08:00

Please find step by step instructions starting on page 14 of the following document:

The example performs a hot pull from the VNX (which in your case, just substitute in your CX).

Regards,


Chris Papp

1 Rookie

 • 

52 Posts

February 3rd, 2014 13:00

My apologies.  The document is internal only.

Do you need step by step instructions?

Regards,


Chris

15 Posts

February 3rd, 2014 13:00

Chris,

I would appreciate if you can provide me steps by step instructions.

1 Rookie

 • 

52 Posts

February 4th, 2014 08:00

Ok..let's take a stab at this:

  1. Zoning: Just like a host HBA, the Symm FA needs to see the CX SPs over the Fabric, you need to create a new zone for each path, or add the FAs to the host zone(s) you're already using.  This needs to be stressed: Every FA that the Symm device(s) is mapped to must be able to see the CX just once, and after step 2 should see the target LUN(s) from each FA port.
  2. Target LUN presentation and identification: The VMAX FAs need to be added to the storage group in the CX.  KB article https://support.emc.com/kb/16282 explains what needs to be done inside the CX, including setting failover mode (i.e. ALUA).  The Target LUN WWID(s) also needs to be recorded.
  3. Once your zoning is correct, verify the FAs can see the LUNs.  Use 'symsan -sid list -sanports -dir xx -p y' to verify that the FA can see the CX SP.  Also the display will report how many LUNs are being presented.  To see if the correct LUNs are being shown, use 'symsan -sid list -sanluns -wwn -dir xx -p y'.
  4. Build your device file.  Each pairing will be one line followed by a carriage return.  An example follows: 'Symdev=000xxxxxxxxx:yyyy wwn= '.  List the full Symm SN in xxxxxxxxxx followed by a colon and the Symm device number yyyy.
  5. Once your device file is built, you can create your ORS session. 'symrcopy create -copy[or -precopy] -name -pull -hot -donor_update -file .  The donor_update option can be used if you've already cut over the host to the VMAX and updates from the host can overwrite the VNX target device (this is optional).  You can also put the session in -precopy to start the copy process once the create is issued.  Typically you'll use -copy.
  6. To start the copy process, use 'symrcopy activate -name '.  The data should start flowing to the VMAX now.  You can monitor progress with 'symrcopy query -name '.
  7. Once you have finished the migration and cut over to the VMAX on the host end, you can terminate the ORS session with 'symrcopy terminate -name '.  From there you can dezone the FAs from the CX SPs at your leisure.

Hope this helps,

Chris

15 Posts

February 4th, 2014 08:00

Thank You Much Chris. Appreciate your help.

15 Posts

August 9th, 2014 13:00

Hello Dynamox/Chirs,

One more question   ..so how do I add the  VMAX  FA in the clariion storage group via Navisphere GUI (any documents which I can follow)  also,  what are the ways we can have host not access the source luns (Clariion LUNs) after migration is completed other than removing the host to clarion zoning? Can we remove the host from the storage group ?

Regards,

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

August 9th, 2014 14:00

once you zone VMAX FAs to clariion, the WWN should automatically show up under "Initiators". If they do not show up you can tickle them by running "symsan list -sanports -sid 123 -dir ALL -p ALL"

you can drop zones from the host or remove it from the storage group.

15 Posts

August 9th, 2014 17:00

Dynamox,

please correct me if I am wrong..so completing  OR zoning will show the VMAX  FAs WWNs under "Host Initiator"  but don't we have to add these WWNs   in Clariion  storage group  for source  LUN masking  to the target FAs?

Regards,

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

August 9th, 2014 18:00

that is correct, you are treating VMAX FAs as if they were a host. You will need to register them (you can assign a dummy IP address, i also used failover mode 1, never tried 4) and then add this "dummy" host to the storage group so that VMAX FAs can read the data.  So you have decided on OR hot pull versus SANCopy ?

15 Posts

August 9th, 2014 19:00

Thank you Dyanamox. We are asked to use OR hot pull. I will keep posting  my queries here  if any .. hope you do not mind responding it.

Appreciate your support.

Regards,

15 Posts

August 9th, 2014 19:00

I am used to doing hot pull (DMX-VMAX,VMAX-VMAX) but not CX-VMAX. Thank you for your instructions and steps. It helped a lot.

Regards,

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

August 9th, 2014 19:00

i have not done OR hot-pull, hot push only ..so i may not be able to answer your questions, but other folks will be able to assist.

August 10th, 2014 21:00

Hi Papp,

Really very useful stuff
tanq so much. 

0 events found

No Events found!

Top