Does "Cold Migration" use vMotion enabled Network?

[vmtrekker]

I have three ESXi hosts installed and they are networked with 2 different networks. One is the regular 100mbps network which I am using as management network, which is also used to connect my vsphere client to connect to the hosts individually or to the vCenter Server (which is running as VM on one of the hosts).

My other network is 1Gbps network which I am trying to desginate for vMotion traffic only. I have enabled vMotion (tick marked) on the vmKernel port which is connected to gigabit speed network whereas I have disabled the vMotion on the slower network.

Yet, to my surprise, when I am doing "COLD MIGRATION" (emphasis is on cold migration, not hot vMotion), it still uses the slower network while the faster network remains idle.

This seems to show that the network path taken by Cold Migration is irrelevant to the one taken by vMotion enabled vmKernel port. How can I ensure that the cold migration and all other "Heavy" activity happens ONLY through the faster network.

I only want to use the slower network which is on my local LAN for connecting vsphere Client (on my laptop) to vCenter Server or to the hosts directly if needed. Can someone please help? I'll really appreciate as I'm stuck now. Thanks.

[AntonVZhbankov · Accepted solution]

Cold migration works through Service Console / Management VMkernel, and does not use VMotion VMkernel.

---

MCSA, MCTS Hyper-V, VCP 3/4, VMware vExpert

http://blog.vadmin.ru

[vmtrekker]

Many Thanks Anton.

Now that its clear that Cold Migration uses the Management enabled network and not the vMotion enabled network, How can I direct the Cold Migration activity to use the faster network?

If I disable the "Management Traffic" on slower network's settings, then I lose the connection between my vSphere client (which is on slower network) and the vCenter server. On the other hand, if vmKernel on both the slow and fast network have their "Management Traffic" enabled, then Cold migration always happens through the slower network!

Is there a way to specifically configure Cold migration traffic to go through the faster network while you can still use the slower network for management and connectivity to vsphere client? Thanks.

vmTrekker

[AntonVZhbankov]

No way. Use high-speed NICs even for management.

---

MCSA, MCTS Hyper-V, VCP 3/4, VMware vExpert

http://blog.vadmin.ru

[jkumhar75]

You can use the high speed NIC or if you are using a high speed NIC, then connect it to the same physical switch of 1Gbps.

Jay

VCP 310,VCP 410,MCSE

Consider awarding points for "helpful" and/or "correct" answers.

[Phokay]

You could configure another service console port groups and uplink to physical nics used by the vmotion network and see if cold migration uses it.

[529122530]

Cold Migration only need a share network and keep the port 443 is OK,not use VMkernel