09-11-2015 11:33 AM - edited 03-01-2019 12:22 PM
When we enable VMQ in the service profile on a Hyper-V host. Do we also need to configure the VMQ to CPU assignment VIA powershell as described in the following? http://blogs.technet.com/b/networking/archive/2013/09/24/vmq-deep-dive-2-of-3.aspx
Does USC handle it?
Thanks
09-12-2015 06:07 AM
Hello,
The quick answer is no. The long answer is VMQ takes the MAC address of the host’s vNIC and each VM’s vmNIC and assigns it to a queue on the NIC. The NIC also has a default queue which latches all the traffic that does not match a MAC filter on the NIC. (Basically, if a vnic doesn't have vmq enabled, it falls under the default queue).
What we are really achieving here is a queue per vnic versus one queue for all vnics. Assigning cores to a VMQ just dictates which cores will be responsible for which queue.
Hope this helps,
Justin
09-14-2015 08:54 AM
Thank you Justin for the clarification, however the commands that are referenced in the blog are used to "pin" certain NIC's and its VMQ workloads to certain processors.
Does Cisco UCS handle this dynamically? If yes, where can I read more about this?
Thanks
09-14-2015 10:23 AM
Hello,
Just for clarification VMQ is a Microsoft technology, Cisco supports it on their hardware. Without pinning the processors the traffic would be handled by the next core available in the CPU scheduler.
Thanks,
Justin
09-15-2015 05:08 PM
After a lot of research, here is what I found!
With 2012r2 and Dynamic VMQ, the os should handle most workloads. Only after careful analysis should you need to tweak the VMQ / Core assignments.
Thanks
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide