Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

VMWare migrate VMs to new SAN

Posted on 2011-02-19
6
Medium Priority
?
869 Views
Last Modified: 2012-05-11
I have a clustered pair of ESX servers connected to a SAN MD3000i but have connected a new SAN (Dell SUMO) to the network in order for me to VMotion the VMs to this new SAN. So I'm going from SAN to SAN.

This just came up so I'm having a hard time thinking about the steps involved at the last second.

Any help in how to present the new SAN Volume to the ESX Servers would allow me to VMotion them over.

Thanks a bunch
0
Comment
Question by:snyderkv
  • 3
  • 3
6 Comments
 
LVL 1

Expert Comment

by:ceesios
ID: 34932450
Hi there,

I would take the next steps:

Make sure that the SUMO is configured correctly (iSCSI Target, ip's of ESX allowed e.d.)

check your ip connectivity with the new san with vmkping on the console (tech support mode) or with the vma. Whatever you prefer.

Go to the configuration tab of the esx host, go to "storage adapters", Go to the "iSCSI Software adapter" and click properties below.

Click "Dynamic discovery", click "Add", Enter the ip of the SUMO, click ok, ok

If everyting is configured ok, after the rescan a new target should turn up. Repeat these steps on the other host.

Go Configuration=>Storage=>Add Storage and configure a new datastore on the SUMO.

Now you are able to do a storage vmoton (rightclick om vm, migrate, change datastore) if your license allows it. (If it doesn't you can temporarily set it back at a demo license key wich gives you full features, but you didn't hear that from me ;)
0
 

Author Comment

by:snyderkv
ID: 34932496
Ceesios,

Great! thanks that sounds easy enough. Just to clear up a couple things.

1) Click "Dynamic discovery", click "Add", Enter the ip of the SUMO, click ok, ok
Will this be the iSCSI IP of the SUMO or the ManagementIP?

2) Does my SUMO iSCSI IPs have to be on the same physical private network as the new old SAN?
0
 
LVL 1

Accepted Solution

by:
ceesios earned 2000 total points
ID: 34932513
I'm sorry, you must enter the iSCSI IP of the SUMO as this is the ip ESX wil use to communicate with your storage.

And yes, they have to be on the same physical network if you don't configure a additional kernel port on ESX. It's possible but not necessary. Just make sure you dont run into ip address conflicts! Double check that the ip of the sumo is different from the current storage and esx servers but in the same subnet.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 

Author Comment

by:snyderkv
ID: 34932642
Thanks a lot. Most helpfull.
0
 
LVL 1

Expert Comment

by:ceesios
ID: 34934509
no problem,

please mark my post as helpful if you succeed.
0
 

Author Comment

by:snyderkv
ID: 34986719
Yup that worked out like a charm.

Just incase anyone reads this, I had to input the IQN name of the ESX servers into the new SAN access list in order for the ESX servers to see the new storage (in addition to the above instructions). Not that it is a rule, but had to in my situation for some reason.

Also, the other servers like file servers exc, needed the iQN as well, otherwise I'd get Access Denied when connecting the storage on the server using the iSCSI Initiator (logon) tab. I've done this before the exact same way in other environments using the iSCSI IP and didn't have this issue.

Just an FYI.

Thanks Ceesios
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I show you step by step with screenshots to assist you - HOW TO: Deploy and Install the VMware vCenter Server Appliance 6.5 (VCSA 6.5), with some helpful tips along the way.
Giving access to ESXi shell console is always an issue for IT departments to other Teams, or Projects. We need to find a way so that teams can use ESXTOP for their POCs, or tests without giving them the access to ESXi host shell console with a root …
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…

916 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question