• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 870
  • Last Modified:

VMWare migrate VMs to new SAN

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
snyderkv
Asked:
snyderkv
  • 3
  • 3
1 Solution
 
ceesiosCommented:
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
 
snyderkvAuthor Commented:
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
 
ceesiosCommented:
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
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
snyderkvAuthor Commented:
Thanks a lot. Most helpfull.
0
 
ceesiosCommented:
no problem,

please mark my post as helpful if you succeed.
0
 
snyderkvAuthor Commented:
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

Become an Android App Developer

Ready to kick start your career in 2018? Learn how to build an Android app in January’s Course of the Month and open the door to new opportunities.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now