something else to think about, we've noticed that UCS maps traffic streams to different HIF's/NIF's without regard for utilization. So, a single HIF/NIF could be saturated and other's available or with lower utilization but they are not being used. what we've seen with our testing is that with UCS, the more vm's we've used for testing, the better it would distribute the traffic. the problem becomes when you overlay NSX and all of your traffic is encap/decap in the VTEP. the phys UCS components will not see your vm macs/ip's, only the vteps. when designing your solution with ucs, you will want to take this into account when determining your number of vteps. it's possible, with only a single vtep per blade, that your vtep traffic will all be hashed to the same HIF/NIF in UCS. also keep in mind that due to the lack of RSS support in the enic driver for the 1340/1380, you are only getting 6-7Gbps per HIF. i am now testing c series with the 1225 vics. they do not support vxlan offload, and i only get 4-5gbps per link with nsx, but i do not have to take into account any other c series being "pinned or hashed" to my links to the FI's.