I'm actually looking into this and I just today updated the NIC drivers on our 2008 R2 Hyper-V Cluster nodes. Even though we're running R610s, I checked the Broadcom drivers for the R710 and the driver has the same time/date stamp as the one I used today.
I compared the physical NIC parameters of the updated NIC driver to the other node that was running the stock OS MS Broadcom Driver. The updated node had a VMQ option that was enabled by default.
That said, I believe that your NIC supports this as well. As part of our upgrades, I'm updating all the Dell drivers/firmware on both nodes. We're running R2 SP1 on both nodes which supports TCP Offloading/VMQ.
When these servers were built, TCP Offloading was disabled because that was the recommendation pre-VMQ.
woochman
279 Posts
1
September 23rd, 2011 20:00
Hi Goodshots,
I'm actually looking into this and I just today updated the NIC drivers on our 2008 R2 Hyper-V Cluster nodes. Even though we're running R610s, I checked the Broadcom drivers for the R710 and the driver has the same time/date stamp as the one I used today.
I compared the physical NIC parameters of the updated NIC driver to the other node that was running the stock OS MS Broadcom Driver. The updated node had a VMQ option that was enabled by default.
That said, I believe that your NIC supports this as well. As part of our upgrades, I'm updating all the Dell drivers/firmware on both nodes. We're running R2 SP1 on both nodes which supports TCP Offloading/VMQ.
When these servers were built, TCP Offloading was disabled because that was the recommendation pre-VMQ.