Vmotion Network Traffic

[gavinmansell]

We currently have virtual switches that have all ports on the switch (VM, Service Console and VMkernel) connected to the same physical NICs - the traffic is not seperated to individual subnets. I have read that creating a seperate physical network for VMotion traffic is the best practice. Is this an easy configuration change within the VI client? What would be the best way to go about making this change?

[AndreTheGiant]

I have read that creating a separate physical network for VMotion traffic is the best practice.

Maybe.

But also have at least 2 physical NIC for each vSwitch... so you can have not enough NIC

A good tradeoff is use a vSwitch for SC and VMotion.

Is this an easy configuration change within the VI client? What would be the best way to go about making this change?

For each ESX you create a new vSwitch, create a new VMotion port, and then delete the old one.

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

[gavinmansell]

Hi Andre,

We have 3 physical nics per vSwitch, it's just that the traffic is not segmented at the moment. We also have a VMkernel port on each vswitch on the ESX host is this Overkill? I will look at creating a new vswitch for the VMkernel for the Vmotion traffic.

Thanks

[AndreTheGiant]

You're welcome.

See also: http://www.networkworld.com/community/node/35640.

Andre