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?
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?
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Ensure that you have a VMKernel Interface on the same network and subnet, and then select that as your vMotion interface.
ASKER
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 %.
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 %.
what is the error?
What build of ESXi 5.1 are you using? Are you changing the IP via GUI or commad-line?
ASKER
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.
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.
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
ASKER
The error just states losing connectivity to host and reverts changes.
Here are the vswitch settings.
rack-host-vswitch.JPG
blade-vswitch.JPG
Here are the vswitch settings.
rack-host-vswitch.JPG
blade-vswitch.JPG
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...
ASKER
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.
My only other option at this point is to change the management IP of the rack server and see if that helps.
Let me know how you make out... Good Luck
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Very interesting and good to know..
ASKER
This was the solution to my problem.