Solved

VMWare migrate VMs to new SAN

Posted on 2011-02-19
6
859 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 500 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
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 

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

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
delete phantom  datastores 5 52
Esxi time zone 5 55
HP VSA on ESXi Best Practice 3 40
vmware 5.5 1 33
If we need to check who deleted a Virtual Machine from our vCenter. Looking this task in logs can be painful and spend lot of time, so the best way to check this is in the vCenter DB. Just connect to vCenter DB(default DB should be VCDB and using…
Last article we focus in how to VMware: How to create and use VMs TAGs – Part 1 so before follow this article and perform the next tasks, you should read the first article how to create the TAG before using them in Veeam Backup Jobs.
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…

919 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

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now