vmtrekker
Contributor
Contributor

Cannot migrate through the required network. Someone Please help.. ?

Jump to solution

I have set up 3 ESXi hosts connected via 2 parallel networks. One is a slower network (100 base) on 192.168.12.0/24 and the other is a gigabit speed network on 10.1.1.0/24. Each host is having two physical NICs for each of the network.

Host #1 Config is as follows: (Also see attached pic)

vSwitch0 (connected to vmNic0 ) has -->

- VM Network (Virtual Machine Port group)

- Management Network (VMKernel Port)

vSwitch1 (connected to vmNic1 ) has -->

- SAN Network (Virtual Machine Port group)

- VMKernel-Special (VMKernel Port)

NOTE: Host # 2 has also a similar setup with a different set of IPs.

My problem is that when i try to cold migrate a VM from one host to another (in left pane if you see, its from 192.168.12.30 to 192.168.12.32), it always does migration through the slower network (vSwitch 0). I want it to do cold migration through the faster gigabit network configured on vSwitch 1.

I havent even tried making clusters or doing vmotion because I cannot manage to properly configure the networks I want to be used. so can you please help me with this? I want to ensure that when I do migration (cold migration to begin with) It should happen through the network of my choice, which, in this case is the gigabit network. Many Thanks.

vmTrekker

0 Kudos
1 Solution

Accepted Solutions
Texiwill
Leadership
Leadership

Hello,

Cold Migration traffic flows over the first Management Appliance the system finds. In your case it finds two with the slower network being the first it finds. There is no way to route based on activity, so you either place the entire managemernt network on vSwitch1 or you live with the slower speeds. Personally I am not sure I would ever have my VM Network on the same link as my Management Appliance/Network as they are usually two different trust zones, etc.


Best regards,
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, 2010

Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security'[/url]

Also available 'VMWare ESX Server in the Enterprise'[/url]

Blogging: The Virtualization Practice[/url]|Blue Gears[/url]|TechTarget[/url]|Network World[/url]

Podcast: Virtualization Security Round Table Podcast[/url]|Twitter: Texiwll[/url]

--
Edward L. Haletky
vExpert XIII: 2009-2021,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill

View solution in original post

0 Kudos
4 Replies
Rumple
Virtuoso
Virtuoso

you need to make sure that vmkernel-special port group is configured as the vmotion network as cold migration still goes over the interface marked as being used for vmotion.

You will want to make sure your default vmkernel is not used for vmotion.

0 Kudos
athlon_crazy
Virtuoso
Virtuoso

As mentioned by Rumple, you can do this by going to vmk0 property and "untick" option for vMotion.






vcbMC-1.0.6 Beta

vcbMC-1.0.7 Lite

http://www.no-x.org

http://www.no-x.org
0 Kudos
vmtrekker
Contributor
Contributor

Hi Rumple,

Thanks for the answer. But I have already tried earlier what you suggested. To be precise, The vmkernel port on vswitch0 has vmotion turned off whereas the vmkernel port on vswitch1 has vmotion turned on (i.e. ticked). This is true for both the Host #1 http://192.168.12.30 and Host #2 http://192.168.12.32. But when I try doing cold migration EVEN after these settings, it only happens through the 192.168.12.0/24 network which is 100mbps network only! Are you sure whether "cold migration" is a part of vmotion and thus relevant to its settings?

There's also one more tick mark "Management Traffic" which is selected on both vswitch0 and vswitch1.

As another scenario, I redefined Management network on ESXi hosts directly to be 10.1.1.30 and 10.1.1.32 and removed vmkernel port that was connected to vswitch0 while keeping the vmkernel port connected to vswitch1 . This was done on both hosts. My vCenter server is setup as a VM on Host #3 http://192.168.12.31. What I did now is to connect vCenter server to both the networks i.e. 100mbps and 1000mbps. Since the vSphere client is on 100mbps network, I can now connect only to vCenter Server which in turn communicates with the Hosts on 1000mbps network. With these settings, when I tried cold migration again, it went well through the faster network, BUT, now, from my vSphere client, while I am connected to vCenter server, and through it to one of the VMs, When I try to open the console, it says "cannot connect to 10.1.1.x". This is obvious since my vsphere client is on the 100mbps network and cannot see 1gbps network directly. (It seems that when we try to open the console on vsphere client, it doesnt go through vCenter server rather tries to establish a direct connection to host on 10.1.1.x network from a desktop which is on 192.168.12.x network.

Hope you understood the whole situation. Can anyone help please?

vmTrekker

0 Kudos
Texiwill
Leadership
Leadership

Hello,

Cold Migration traffic flows over the first Management Appliance the system finds. In your case it finds two with the slower network being the first it finds. There is no way to route based on activity, so you either place the entire managemernt network on vSwitch1 or you live with the slower speeds. Personally I am not sure I would ever have my VM Network on the same link as my Management Appliance/Network as they are usually two different trust zones, etc.


Best regards,
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, 2010

Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security'[/url]

Also available 'VMWare ESX Server in the Enterprise'[/url]

Blogging: The Virtualization Practice[/url]|Blue Gears[/url]|TechTarget[/url]|Network World[/url]

Podcast: Virtualization Security Round Table Podcast[/url]|Twitter: Texiwll[/url]

--
Edward L. Haletky
vExpert XIII: 2009-2021,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill

View solution in original post

0 Kudos