There are 3 ways that you can create QoS rules, and each type depends on the type of traffic you are dealing with and changes where the rule is applied, and what it applies to:<\/p>\n
1) The Virtual Switch<\/u><\/strong><\/p>\n This is the simplest of the options in my opinion. You can create rules to be applied by a QoS enabled virtual switch. This should be used when the traffic you are dealing with is passing through a virtual switch (highlighted with red \u201c1\u201d above). Each rule is applied to a virtual NIC, either in a virtual machine or the Management OS. You can define a default bucket rule; this pool rule is used for any virtual NIC that does not have an explicit rule and the b\/w is shared in the pool. All of my previous PoSH examples on my blog have focused on this approach.<\/p>\n 2) OS Packet Scheduler<\/u><\/strong><\/p>\n Maybe you have physical NICs that will be shared between roles (e.g. SMB 3.0, cluster communications, and Live Migration). These NICs have nothing to do with virtual NICs. In this case you create per-protocol rules, not virtual NIC rules. The rules are applied to network traffic as they pass through the networking stack by the OS Packet Scheduler.<\/p>\n Note that you can also use this approach in the guest OS of a VM.<\/p>\n 3) Datacenter Bridging (DCB)<\/u><\/strong><\/p>\n DCB is a function of hardware, allowing you to classify and apply QoS to networking protocols using hardware instead of software. Some protocols are invisible to Windows, such as Remote Direct Memory Access (RDMA) which is used for SMB Direct. You must use DCB to apply QoS for RDMA. Actually, using DCB offers the best performance. Two notes:<\/p>\n It\u2019s one thing to apply QoS on a per NIC or server level, but the network admins might want to control traffic on the LAN. You can classify and tag traffic so that QoS rules on the switches\/routers can also apply QoS rules. The classification can ID protocols, ports, destination IP addresses, and so on, classify the traffic, and that classification can be used by network admins, e.g. stop the total sum of backup traffic from screwing up the host networking.<\/p>\n —<\/p>\n QoS, combined with NIC teaming, virtual NICs, VLANs, RSS, DVMQ, etc, all make converged fabrics possible. There\u2019s no one right design, but there are wrong ones, e.g. trying to use RSS and DVMQ on the same physical NICs.<\/p>\n Microsoft has published some common configurations<\/a> on TechNet, along with a bunch of PowerShell. Here are some thoughts:<\/p>\n 2 NICs without NIC Teaming<\/u><\/strong><\/p>\n I\u2019d expect this to be an uncommon configuration, but could see it being used in very large hosting with 1+1 host fault tolerance. In this example you can see:<\/p>\n 2 NICs with NIC Teaming<\/u><\/strong><\/p>\n This will be a very common configuration, useful for clusters using SAS or Fibre Channel storage. My previous blogging has focused on this example. In this example you can see:<\/p>\n A twist on this example is to add 2 physical NICs for non-converged iSCSI so that you can have dedicated iSCSI switches (for manufacturer support).<\/p>\n 4 NICs in two NIC teams<\/u><\/strong><\/p>\n This example is basically the 2 NICs without NIC Teaming example with NIC teaming. I can see this one being used where SMB 3.0 storage is required but there is no<\/u><\/em><\/strong> RDMA\/SMB Direct being used. NIC teaming can\u2019t see RDMA! <\/p>\n The two physical NICs on the left are dedicated to the Management OS. The QoS rules classify and tag protocols and apply QoS either:<\/p>\n The NIC team and virtual switch are dedicated to virtual machines.<\/p>\n 4 NICs with a standard NIC team and two RDMA NICs<\/u><\/strong><\/p>\n This is a variation on the last example. Two RDMA NICs are being used for SMB Direct. NIC teaming must be dispensed with in the Management OS. Now DCB must be used. Rules are created to classify and tag protocols, and DCB is used to apply QoS. PFC will be enabled for RDMA if using RoCE NICs.<\/p>\n Some notes:<\/p>\n Alternate configuration of 4 NICs with a standard NIC team and two RDMA NICs<\/u><\/strong><\/p>\n This example uses the flexibility of virtual NIC for the Management OS, while dedicating 100% of bandwidth of the RDMA NICs for SMB 3.0. See the previous example notes for the 2 SMB 3.0 NICs (IP addresses, QoS, PFC, and MPIO).<\/p>\n You\u2019ll use QoS on a per virtual NIC basis that is applied by the virtual switch for the Management OS vNICs (Management, Live Migration, Clustering).<\/p>\n —<\/p>\n Microsoft also published some best practices for QoS<\/a>.<\/p>\n Some notes:<\/p>\n If you have reached here without reading the referenced Microsoft pages then, then don\u2019t be an idiot: go back and read them. I\u2019ve only covered\/explained a tiny fraction of the shared information.<\/p>\n The Quality of Service (QoS) feature has been improved in Windows Server 2012 and this becomes a major ingredient in converged fabrics. QoS rules can be used to: Guarantee a minimal and burstable (if there\u2019s free capacity) amount of bandwidth (flexible) Limit bandwidth (inflexible) There are 3 ways that you can create QoS rules, and … Continue reading “Microsoft Publishes WS2012 QoS Guidance”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[20],"tags":[181,80,118],"class_list":["post-13891","post","type-post","status-publish","format-standard","hentry","category-hyper-v","tag-hyper-v","tag-networking","tag-windows-server-2012"],"aioseo_notices":[],"jetpack_featured_media_url":"","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/13891","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=13891"}],"version-history":[{"count":0,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/13891\/revisions"}],"wp:attachment":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=13891"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=13891"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=13891"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"image\"](\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/12\/image2.png\" "\\"image\\"")
<\/a><\/p>\n\n
\n
\n
\n
\n
\n