Joining two separate environments with different vMotion networks

I am upgrading my ESXi 5.1 cluster from rack servers to blades.
My rack servers are on the following subnet:

192.168.9.0/24

The blade servers (Cisco UCS) is on the following subnet:

172.20.0.0/16

My issue is that I am attempting to host vMotion VM's to the new cluster and it cannot find/see the network and fails at 14%. vMotion IP's are on the same respective subnets as the hosts.

I read this article from VMWare but it didn't help me.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2052092

I attempt to change the vMotion IP's on the blades to match the same subnet and vCenter rejects the change and reverts back to original IP.

How can I best approach this and successfully move these VM's?
LVL 17
James HIT DirectorAsked:
Who is Participating?
 
James HConnect With a Mentor IT DirectorAuthor Commented:
I was able to get this working. For some reason the vMotion NIC's on the UCS were not pinned correctly and thus no traffic was passing through. Once I fixed the mess the original installer made I was able to get this working.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Ensure that you have a VMKernel Interface on the same network and subnet, and then select that as your vMotion interface.
0
 
James HIT DirectorAuthor Commented:
That's my problem. I try to add/change a VMk interface on the blades and it will error out and roll back changes. Storage is visible to all servers and there is new storage for blade servers, not an issue as Storage vMotion works flawlessly.

The only interfaces I can change the VMk on are the rack servers. I did attempt the change the vMotion IP's to match the blades but it still failed at 14 %.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
what is the error?
0
 
compdigit44Commented:
What build of ESXi 5.1 are you using? Are you changing the IP via GUI or commad-line?
0
 
James HIT DirectorAuthor Commented:
I am changing the IP via the GUI.
I verified that all addresses are reachable on the network side and ensured they are on the correct VLAN. It's looks to me like the vMotion wants to take place over the management network even though that is not selected as vMotion.
0
 
compdigit44Commented:
As hanccocka mention previously, can you please upload the error you receive when changing the IP. Also, please upload any error in the vcenter log files and image of your vswitch / vds layout
0
 
James HIT DirectorAuthor Commented:
The error just states losing connectivity to host and reverts changes.
Here are the vswitch settings.
rack-host-vswitch.JPG
blade-vswitch.JPG
0
 
compdigit44Commented:
Hum...have you talked to your networking departement to see if they would be able to allow the  port nic's 4 & 5 on the blade at plugged into access to the same vLAN your racks server is plugged into...
0
 
James HIT DirectorAuthor Commented:
Remember, the UCS NIC's are all virtual, so I did the reverse. I changed the VLAN's and IP's on the rack servers, verified the addresses are visible and it still fails at 14%.
My only other option at this point is to change the management IP of the rack server and see if that helps.
0
 
compdigit44Commented:
Let me know how you make out... Good Luck
0
 
compdigit44Commented:
Very interesting and good to know..
0
 
James HIT DirectorAuthor Commented:
This was the solution to my problem.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.