We are using 4 physical NICs with VMware 5.0. We have one vswitch, with the switch ports configured in an MLT, with multiple vlans on the ports, using route based on ip hash. I am not a traffic expert. I'm being told that "best practice" is having a separate vswitch for management and another for vmotion traffic. The only reason I have found for this so far is one site mentioned that virtual machine traffic is "toxic" and shouldn't be mixed with "infrastructure traffic".
When using one vswitch I could see a problem if you vmotion many VMs that could saturate the bandwidth of all the ports of the MLT. Outside of that, what are the reasons for splitting it up?
At a high level, it seems like a better idea to have all the NICs teamed, so you don't have any single points of failure.
What are the downsides of doing this type of configuration?
Thanks
James
When using one vswitch I could see a problem if you vmotion many VMs that could saturate the bandwidth of all the ports of the MLT. Outside of that, what are the reasons for splitting it up?
At a high level, it seems like a better idea to have all the NICs teamed, so you don't have any single points of failure.
What are the downsides of doing this type of configuration?
Thanks
James