This is dependent on the load balancing method used. I suspect all of this traffic is coming from one virtual machine.
search for load balancing
Social Media Specialist
Thanks Brian, so basically according to that article it's doing what it's supposed to be doing, and there isn't enough bandwidth being used to warrant it to spread to the other NICs? Also Rick, although there is an outside possibility that the majority of the network is coming from 1 VM, I highly doubt it as we have a Citrix box with 20+ users, email system, and a database on that host.
Maybe now I have the proof to start breaking up the pNICs that I needed
I'm betting its more like that the loads are actually spread over the 4 nics, but that the total loads are so insignificant on 3 of them that you are only noticing the higher number on vmnic0. Its possible that there could be a single (as Rick suggested) or multiple "higher traffic" VMs all utilizing vmnic0. vmnic0 receives are peaked at 1.33 MBps, so the load is still light.
This is also the part where I could preach about having baselines for your virtual machines, but I will spare you today!
You have selected "route based on originating virtual port id" as the load balancing method to be implied which means it will send the packets in order of, from which nics they came. In short it won't try to scatter the load across the nics and rather follow the external method used.
The best way you can achieve the required is to configure "ether-channelling" or port aggregation at the physical switch for all the ports. At the same time you have to select "route based on ip hash" at vSwitch load balancing method for ESX. This works best !
(Preparing for VCP 4)
just remember than any one tcp conversation will always use only 1 pnic, no matter how many pnics you have teamed. If most of your traffic is from one vm to another vm, and you have a 4 pnic team, you will only get 1gb, not 4gb (assumming that your pnics are 1gb).