Ranjna Aggarwal wrote: Thanks rickardnobel, Tell me one more thing Generally multiple vSwitches are used in Production Environments or only as few as possible. I tend t...
See more...
Ranjna Aggarwal wrote: Thanks rickardnobel, Tell me one more thing Generally multiple vSwitches are used in Production Environments or only as few as possible. I tend to do very similar to what a.p. described above. A customer I am helping at the moment with a new environment will have something like: vSwitch0 - for Management and vMotion, using active/standby - two vmks and two vmnics, different VLAN and IP range vSwitch1 - for iSCSI - two vmk and two vmnics, using active/unused vSwitch2 - for production VM networking - several portgroups with different VLANs, two/maybe four vmnics - not decided and possible: vSwitch3 - for test VMs, where the wish is to totally physically separation and no risk for the test VM traffic to disturb the production VMs. So more than 4-5 vSwitches is most often not necessary, but possible. As for the memory overhead it seems like minimal, so it is just a combination of the amount of physical vmnic ports and keeping the virtual networking setup both flexible, secure and simple.