best practice v-switch

[enkidoe]

guys,

i need some help with the v-sciwtch part. When reading about the v-scwitch, i still cant figure out a best practice.

Should i use more than 1 v-switch when i got more than 1 vm with the same functionality(lets say, 2 exchange servers on the same v-switch) ? or should i use v-switches to split vm's with different functionality?

many thanks for the reply.

[rickardnobel]

enkidoe wrote:

Should i use more than 1 v-switch when i got more than 1 vm with the same functionality(lets say, 2 exchange servers on the same v-switch) ?

You can think of a vSwitch like a physical switch in most way. If you put several physical servers on the same physical switch they will be able to communicate with each other extremely fast, but they will share a common uplink to the rest of the network. This is just the same with the vSwitch, where the VMNIC is the uplink to the rest of the network.

Depending on the traffic load and needs of your VMs it might make sense to divide them on several vSwitches, but most likely it will not be needed and be better to instead add more VMNICs (physical adapter ports) to the vSwitch for more uplinks and failover capacity.

[john23]

vswitch usage depend on many stuffs ..I found this blog is very useful.

http://kensvirtualreality.wordpress.com/2009/04/10/the-great-vswitch-debate-part-4/

[AndreTheGiant · Accepted solution]

See also: http://www.vmware.com/files/pdf/virtual_networking_concepts.pdf

Thread has been moved in vNetwork area.