{"id":14032,"date":"2013-01-10T13:43:00","date_gmt":"2013-01-10T13:43:00","guid":{"rendered":"https:\/\/aidanfinn.com\/?p=14032"},"modified":"2014-08-07T13:27:45","modified_gmt":"2014-08-07T13:27:45","slug":"windows-server-2012-nic-teaming-part-4-load-distribution","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=14032","title":{"rendered":"Windows Server 2012 NIC Teaming Part 4 \u2013 Load Distribution"},"content":{"rendered":"<p><a href=\"https:\/\/aidanfinn.com\/?p=13984\">Windows Server 2012 NIC Teaming Part 1 \u2013 Back To Basics<\/a><\/p>\n<p><a href=\"https:\/\/aidanfinn.com\/?p=13997\">Windows Server 2012 NIC Teaming Part 2 \u2013 What\u2019s What?<\/a><\/p>\n<p><a href=\"https:\/\/aidanfinn.com\/?p=14004\"><span style=\"font-weight: normal;\">Windows Server 2012 NIC Teaming Part 3 \u2013 Switch Connection Modes<\/span><\/a><\/p>\n<p>With a team formed you have the failover part of LBFO figured out.\u00a0 But what about the load balancing piece of LBFO?\u00a0 That&#8217;s what this post is going to discuss.<\/p>\n<p>First, think about some concepts:<\/p>\n<ul>\n<li>A packet sent into the NIC team should not be fragmented and sent across multiple NICs.\u00a0 We like BIG packets because they fill bandwidth and reduce the time to get data from A to B.<\/li>\n<li>Sometimes we need to make the path of traffic predictable \u2026 very predictable.\u00a0 And sometimes we don\u2019t \u2026 but there still needs to be some organisation.<\/li>\n<\/ul>\n<p>There are 2 traffic or load distribution algorithms in WS2012 NIC teaming (actually it\u2019s more if you dig into it).\u00a0 The one you choose when creating\/configuring a team depends on the traffic and the purpose of the team.<\/p>\n<p><strong><span style=\"text-decoration: underline;\">Hyper-V Switch Port<\/span><\/strong><\/p>\n<p>Generally speaking, this is the load distribution that you should use when creating a NIC team that will be used to connect a Hyper-V external virtual switch to the LAN, as below.<\/p>\n<p><a href=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2013\/01\/image17.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin-left: auto; display: block; padding-right: 0px; margin-right: auto; border: 0px;\" title=\"image\" alt=\"image\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2013\/01\/image_thumb16.png\" width=\"304\" height=\"334\" border=\"0\" \/><\/a><\/p>\n<p>However, you <em>do not<\/em> have to choose this type of load distribution for this architecture, but it is my rule of thumb.\u00a0 Let\u2019s get into specifics.<\/p>\n<p>Hyper-V Switch Port will route traffic from a virtual NIC (either in a VM or in the management OS) to a single physical NIC in the team (a team member).\u00a0 Let\u2019s illustrate that.\u00a0 In the below diagram, the NIC team is associating the traffic from the vNIC in VM01 with the team member called pNIC1.\u00a0 The traffic from the vNIC in VM02 is being sent to pNIC2.\u00a0 Two things to note:<\/p>\n<ul>\n<li>The traffic path is predictable (unless a team member fails).\u00a0 Incoming traffic to the virtual NICs is also going to flow through their associated physical NICs<\/li>\n<li>This is not a per-VM association.\u00a0 It is a per-virtual NIC association.\u00a0 If we add a second virtual NIC to VM01 then the traffic for that virtual NIC could be associated with any team member by the NIC team.<\/li>\n<\/ul>\n<p><a href=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2013\/01\/image18.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin-left: auto; display: block; padding-right: 0px; margin-right: auto; border: 0px;\" title=\"image\" alt=\"image\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2013\/01\/image_thumb17.png\" width=\"304\" height=\"318\" border=\"0\" \/><\/a><\/p>\n<p>This is one of the things that can confuse people.\u00a0 They see a team of 2 NICs, maybe giving them a \u201c2 Gbps\u201d or \u201c20 Gbps\u201d pipe.\u00a0 True, there is a total aggregation of bandwidth, but access to that bandwidth is given on per-team member basis.\u00a0 That means the virtual NIC in VM02 cannot exceed 1 Gbps or 10 Gbps, depending on the speeds of the team members (physical NICs in the team).<\/p>\n<p>Hyper-V Switch Port is appropriate if the team is being used for an external virtual switch (like the above examples) and:<\/p>\n<ul>\n<li>You have more virtual NICs than you have physical NICs.\u00a0 Maybe you have 2 physical NICs and 20 virtual machines.\u00a0 Maybe you have 2 physical NICs and you are creating a converged fabric design with 4 virtual NICs in the management OS and several virtual machines.<\/li>\n<li>You plan on using the Dynamic Virtual Machine Queue (DVMQ) hardware offload then you should use Hyper-V Switch Port traffic distribution.\u00a0 DVMQ uses an RSS queue device in a team member to accelerate inbound traffic to a virtual NIC.\u00a0 The RSS queue must be associated with the virtual NIC and that means the path of inbound traffic must come through the same team member every time\u2026 and Hyper-V Switch Port happens to do this via the association process.<\/li>\n<\/ul>\n<p>As I said, there are times, when you might not use Hyper-V Switch Port.\u00a0 Maybe you have some massive host, and you\u2019re going to have just 2 massive VMs on it.\u00a0 You could use one of the alternative load distribution algorithms then.\u00a0 But that\u2019s a very rare scenario.\u00a0 I like to keep it simple for people: use Hyper-V <span style=\"text-decoration: underline;\">Switch<\/span> Port if you are creating the NIC team for a Hyper-V external virtual <span style=\"text-decoration: underline;\">switch<\/span> \u2026 unless you understand what\u2019s going on under the hood and have one of those rare situations to vary.<\/p>\n<p><strong><span style=\"text-decoration: underline;\">Address Hashing<\/span><\/strong><\/p>\n<p>This method of traffic distribution in the NIC team does not associate virtual NICs with team members.\u00a0 Instead, each packet that is sent down to the NIC team by the host\/server is inspected.\u00a0 The destination details of the packet (which can include MAC address, IP address, and port numbers) are inspected by the team to determine which team member to send the packet to.<\/p>\n<p>You can see an example of this in the below diagram.\u00a0 VM01 is sending 2 packets, one to address A and the other to address B.\u00a0 The NIC team receives the packets, performs a hashing algorithm (hence the name Address Hashing) on the destination details, and uses the results to determine the team member (physical NIC) that will send each packet.\u00a0 In this case, the packet being send to A goes via pNIC1 and the packet being sent to B is going via pNIC2.<\/p>\n<p><a href=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2013\/01\/image19.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin-left: auto; display: block; padding-right: 0px; margin-right: auto; border: 0px;\" title=\"image\" alt=\"image\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2013\/01\/image_thumb18.png\" width=\"304\" height=\"265\" border=\"0\" \/><\/a><\/p>\n<p>In theory, this means that a virtual NIC <em>can<\/em> take advantage of all the available bandwidth in the NIC team, e.g. the full 2 Gbps or 20 Gbps.\u00a0 But this is completely dependent on the results of the hashing algorithm.\u00a0\u00a0 Using the above example, if all data is going to address A, then all packets will travel through pNIC1.<\/p>\n<p>And that brings us to a most common question about NIC teams and bandwidth.\u00a0 Say I have a host (or any server) that uses a nice big fat 20 GbE NIC team for Live Migration (or any traffic of a specific protocol).\u00a0 I want to test Live Migration and the NIC team.\u00a0 I pause the host, open up PerfMon and expect to see Live Migration using up all 20 Gbps of my NIC team.\u00a0 What is going on here, under the hood?<\/p>\n<ul>\n<li>Host1 is sending data to the single IP address of Host2 on the Live Migration network.<\/li>\n<li>Live Migration is sending packets down to the NIC team.\u00a0 The NIC team inspects each packet, and every one of them has the same destination details: the same MAC address, the same IP address, and same TCP port on Host2.<\/li>\n<li>The destination details are hashed and result in <em>all<\/em> of the packets being sent via a single team member, pNIC1 in this case (see the below figure).<\/li>\n<li>This limits Live Migration to the bandwidth of a single team member in the team.<\/li>\n<\/ul>\n<p><a href=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2013\/01\/image20.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin-left: auto; display: block; padding-right: 0px; margin-right: auto; border: 0px;\" title=\"image\" alt=\"image\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2013\/01\/image_thumb19.png\" width=\"504\" height=\"231\" border=\"0\" \/><\/a><\/p>\n<p>That doesn\u2019t mean Live Migration (or any other protocol \u2013 I just picked Live Migration because that\u2019s the one Hyper-V engineers are likely to test with first) is limited to just a single team member.\u00a0 Maybe I have a 3rd host, Host3, and pausing Host1 will cause VMs to Live Migrate to both Host2 and Host3.\u00a0 The resulting hashing of destination addresses <em>might<\/em> cause the NIC team to use both team members in Host1 and give me a much better chance at fully using my lovely 20 GbE NIC team (other factors impact bandwidth utilization by Live Migration).<\/p>\n<p><a href=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2013\/01\/image21.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; float: none; padding-top: 0px; padding-left: 0px; margin-left: auto; display: block; padding-right: 0px; margin-right: auto; border: 0px;\" title=\"image\" alt=\"image\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2013\/01\/image_thumb20.png\" width=\"604\" height=\"184\" border=\"0\" \/><\/a><\/p>\n<p>A misconception of Address Hashing is that packet1 to addressA will go via teamMember1, and pack2 to the same address (addressA) will go via teamMember2.\u00a0 I have shown that this is not the case.\u00a0 However, in most situations, traffic is going to all sorts of addresses and ports, and over the long term you should see different streams of traffic balancing across all of the team members in the NIC team \u2026 unless you have a 2 node Hyper-V cluster and are focusing on comms between the two hosts.\u00a0 In that case, you\u2019ll see 50% utilization of a 2-team-member NIC team \u2013 and you\u2019ll be getting the FO part of LBFO until you add a third host.<\/p>\n<p>If you configure a team in the GUI, you are only going to see Hyper-V Switch Port or Address Hash as the Load Balancing Mode options.\u00a0 Using <a href=\"http:\/\/technet.microsoft.com\/en-us\/library\/jj130847.aspx\" target=\"_blank\">PowerShell<\/a>, however, and you can be very precise about the type of Address Hashing that you want to do. \u00a0Note that the GUI &#8220;Address Hashing&#8221; option will use these in order of preference depending on the packets:<\/p>\n<ol>\n<li><strong>TransportPorts (4-Tuple Hash)<\/strong>: Uses the source and destination UDP\/TCP ports and the IP addresses to create a hash and then assigns the packets that have the matching hash value to one of the available interfaces.<\/li>\n<li><strong>IPAddresses (2-Tuple Hash)<\/strong>: Uses the source and destination IP addresses to create a hash and then assigns the packets that have the matching hash value to one of the available interfaces. Used when the traffic is not UDP- or TCP-based, or that detail is hidden (such as with IPsec)<\/li>\n<li><strong>MacAddresses<\/strong>: Uses the source and destination MAC addresses to create a hash and then assigns the packets that have the matching hash value to one of the available interfaces. \u00a0Used when the traffic is not IP-based.<\/li>\n<\/ol>\n<p>My rule of thumb for Address Hashing is that I\u2019ll use it for NIC teams that are nothing to do with a Hyper-V virtual switch, such as a NIC team in a non-host server, or a NIC team in a host that is nothing to do with a virtual switch.\u00a0 However, <em>if <\/em>I am using the NIC team for an external virtual switch, and I have fewer virtual NICs connecting to the virtual switch than I have team members, then I <em>might<\/em> use Address Hashing instead of Hyper-V Switch Port.<\/p>\n<p>EDIT:<\/p>\n<p>WS2012 R2 added a new load distribution mode called Dynamic. It is enabled by default and should be used. It is a blend of Address Hashing for outbound traffic and Hyper-V Port for inbound traffic. Microsoft urges you to use this default load balancing method on WS2012 R2.<\/p>\n<p>END EDIT<\/p>\n<p>This information has been brought to you by <a href=\"http:\/\/www.amazon.com\/Windows-Server-Hyper-V-Installation-Configuration\/dp\/1118486498%3FSubscriptionId%3DAKIAIJ5WNI7ZSH7W4OXA%26tag%3Dafm0c-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D1118486498\">Windows Server 2012 Hyper-V Installation and Configuration Guide<\/a> (available on pre-order on Amazon) where you\u2019ll find lots of PowerShell like in this script:<\/p>\n<p><a href=\"http:\/\/www.amazon.com\/Windows-Server-Hyper-V-Installation-Configuration\/dp\/1118486498%3FSubscriptionId%3DAKIAIJ5WNI7ZSH7W4OXA%26tag%3Dafm0c-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D1118486498\" target=\"_blank\"><img loading=\"lazy\" decoding=\"async\" style=\"float: none; margin-left: auto; display: block; margin-right: auto;\" title=\"image\" alt=\"image\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/09\/image_thumb19.png\" width=\"196\" height=\"244\" border=\"0\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p><a href=\"https:\/\/aidanfinn.com\/?p=14039\">Windows Server 2012 NIC Teaming Part 5 \u2013 Configuration Matrix<\/a><\/p>\n<p>Technorati Tags: <a href=\"http:\/\/technorati.com\/tags\/Windows+Server+2012\">Windows Server 2012<\/a>,<a href=\"http:\/\/technorati.com\/tags\/Hyper-V\">Hyper-V<\/a>,<a href=\"http:\/\/technorati.com\/tags\/Networking\">Networking<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Windows Server 2012 NIC Teaming Part 1 \u2013 Back To Basics Windows Server 2012 NIC Teaming Part 2 \u2013 What\u2019s What? Windows Server 2012 NIC Teaming Part 3 \u2013 Switch Connection Modes With a team formed you have the failover part of LBFO figured out.\u00a0 But what about the load balancing piece of LBFO?\u00a0 That&#8217;s &hellip; <a href=\"https:\/\/aidanfinn.com\/?p=14032\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Windows Server 2012 NIC Teaming Part 4 \u2013 Load Distribution&#8221;<\/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-14032","post","type-post","status-publish","format-standard","hentry","category-hyper-v","tag-hyper-v","tag-networking","tag-windows-server-2012"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 4.9.8 - aioseo.com -->\n\t<meta name=\"description\" content=\"Windows Server 2012 NIC Teaming Part 1 \u2013 Back To Basics Windows Server 2012 NIC Teaming Part 2 \u2013 What\u2019s What? Windows Server 2012 NIC Teaming Part 3 \u2013 Switch Connection Modes With a team formed you have the failover part of LBFO figured out. But what about the load balancing piece of LBFO? That&#039;s\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"AFinn\"\/>\n\t<meta name=\"google-site-verification\" content=\"TDKjbi2McB2eLIfL6KwPB3aQqv5E-mbcb2QYIcovGaI\" \/>\n\t<link rel=\"canonical\" href=\"https:\/\/aidanfinn.com\/?p=14032\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 4.9.8\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_GB\" \/>\n\t\t<meta property=\"og:site_name\" content=\"Aidan Finn, IT Pro - A blog covering Azure, Hyper-V, Windows Server, desktop, systems management, deployment, and so on ...\" \/>\n\t\t<meta property=\"og:type\" content=\"activity\" \/>\n\t\t<meta property=\"og:title\" content=\"Windows Server 2012 NIC Teaming Part 4 \u2013 Load Distribution | Aidan Finn, IT Pro\" \/>\n\t\t<meta property=\"og:description\" content=\"Windows Server 2012 NIC Teaming Part 1 \u2013 Back To Basics Windows Server 2012 NIC Teaming Part 2 \u2013 What\u2019s What? Windows Server 2012 NIC Teaming Part 3 \u2013 Switch Connection Modes With a team formed you have the failover part of LBFO figured out. But what about the load balancing piece of LBFO? That&#039;s\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/aidanfinn.com\/?p=14032\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary\" \/>\n\t\t<meta name=\"twitter:site\" content=\"@joe_elway\" \/>\n\t\t<meta name=\"twitter:title\" content=\"Windows Server 2012 NIC Teaming Part 4 \u2013 Load Distribution | Aidan Finn, IT Pro\" \/>\n\t\t<meta name=\"twitter:description\" content=\"Windows Server 2012 NIC Teaming Part 1 \u2013 Back To Basics Windows Server 2012 NIC Teaming Part 2 \u2013 What\u2019s What? Windows Server 2012 NIC Teaming Part 3 \u2013 Switch Connection Modes With a team formed you have the failover part of LBFO figured out. But what about the load balancing piece of LBFO? That&#039;s\" \/>\n\t\t<meta name=\"twitter:creator\" content=\"@joe_elway\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?p=14032#article\",\"name\":\"Windows Server 2012 NIC Teaming Part 4 \\u2013 Load Distribution | Aidan Finn, IT Pro\",\"headline\":\"Windows Server 2012 NIC Teaming Part 4 \\u2013 Load Distribution\",\"author\":{\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?author=1#author\"},\"publisher\":{\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/#person\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/aidanfinn.com\\\/wp-content\\\/uploads\\\/2013\\\/01\\\/image_thumb16.png\",\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?p=14032\\\/#articleImage\",\"width\":304,\"height\":334},\"datePublished\":\"2013-01-10T13:43:00+00:00\",\"dateModified\":\"2014-08-07T13:27:45+01:00\",\"inLanguage\":\"en-GB\",\"commentCount\":20,\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?p=14032#webpage\"},\"isPartOf\":{\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?p=14032#webpage\"},\"articleSection\":\"Hyper-V, Hyper-V, Networking, Windows Server 2012\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?p=14032#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/aidanfinn.com#listItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/aidanfinn.com\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?cat=20#listItem\",\"name\":\"Hyper-V\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?cat=20#listItem\",\"position\":2,\"name\":\"Hyper-V\",\"item\":\"https:\\\/\\\/aidanfinn.com\\\/?cat=20\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?p=14032#listItem\",\"name\":\"Windows Server 2012 NIC Teaming Part 4 \\u2013 Load Distribution\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/aidanfinn.com#listItem\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?p=14032#listItem\",\"position\":3,\"name\":\"Windows Server 2012 NIC Teaming Part 4 \\u2013 Load Distribution\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?cat=20#listItem\",\"name\":\"Hyper-V\"}}]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/#person\",\"name\":\"AFinn\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?p=14032#personImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/65fde4aa9f2ab1cf1514ae320a37ec682d9398ce5791d3c2dd1e8670a71ceea0?s=96&d=mm&r=g\",\"width\":96,\"height\":96,\"caption\":\"AFinn\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?author=1#author\",\"url\":\"https:\\\/\\\/aidanfinn.com\\\/?author=1\",\"name\":\"AFinn\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?p=14032#authorImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/65fde4aa9f2ab1cf1514ae320a37ec682d9398ce5791d3c2dd1e8670a71ceea0?s=96&d=mm&r=g\",\"width\":96,\"height\":96,\"caption\":\"AFinn\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?p=14032#webpage\",\"url\":\"https:\\\/\\\/aidanfinn.com\\\/?p=14032\",\"name\":\"Windows Server 2012 NIC Teaming Part 4 \\u2013 Load Distribution | Aidan Finn, IT Pro\",\"description\":\"Windows Server 2012 NIC Teaming Part 1 \\u2013 Back To Basics Windows Server 2012 NIC Teaming Part 2 \\u2013 What\\u2019s What? Windows Server 2012 NIC Teaming Part 3 \\u2013 Switch Connection Modes With a team formed you have the failover part of LBFO figured out. But what about the load balancing piece of LBFO? That's\",\"inLanguage\":\"en-GB\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?p=14032#breadcrumblist\"},\"author\":{\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?author=1#author\"},\"creator\":{\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/?author=1#author\"},\"datePublished\":\"2013-01-10T13:43:00+00:00\",\"dateModified\":\"2014-08-07T13:27:45+01:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/#website\",\"url\":\"https:\\\/\\\/aidanfinn.com\\\/\",\"name\":\"Aidan Finn, IT Pro\",\"description\":\"A blog covering Azure, Hyper-V, Windows Server, desktop, systems management, deployment, and so on ...\",\"inLanguage\":\"en-GB\",\"publisher\":{\"@id\":\"https:\\\/\\\/aidanfinn.com\\\/#person\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"Windows Server 2012 NIC Teaming Part 4 \u2013 Load Distribution | Aidan Finn, IT Pro","description":"Windows Server 2012 NIC Teaming Part 1 \u2013 Back To Basics Windows Server 2012 NIC Teaming Part 2 \u2013 What\u2019s What? Windows Server 2012 NIC Teaming Part 3 \u2013 Switch Connection Modes With a team formed you have the failover part of LBFO figured out. But what about the load balancing piece of LBFO? That's","canonical_url":"https:\/\/aidanfinn.com\/?p=14032","robots":"max-image-preview:large","keywords":"","webmasterTools":{"google-site-verification":"TDKjbi2McB2eLIfL6KwPB3aQqv5E-mbcb2QYIcovGaI","miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/aidanfinn.com\/?p=14032#article","name":"Windows Server 2012 NIC Teaming Part 4 \u2013 Load Distribution | Aidan Finn, IT Pro","headline":"Windows Server 2012 NIC Teaming Part 4 \u2013 Load Distribution","author":{"@id":"https:\/\/aidanfinn.com\/?author=1#author"},"publisher":{"@id":"https:\/\/aidanfinn.com\/#person"},"image":{"@type":"ImageObject","url":"https:\/\/aidanfinn.com\/wp-content\/uploads\/2013\/01\/image_thumb16.png","@id":"https:\/\/aidanfinn.com\/?p=14032\/#articleImage","width":304,"height":334},"datePublished":"2013-01-10T13:43:00+00:00","dateModified":"2014-08-07T13:27:45+01:00","inLanguage":"en-GB","commentCount":20,"mainEntityOfPage":{"@id":"https:\/\/aidanfinn.com\/?p=14032#webpage"},"isPartOf":{"@id":"https:\/\/aidanfinn.com\/?p=14032#webpage"},"articleSection":"Hyper-V, Hyper-V, Networking, Windows Server 2012"},{"@type":"BreadcrumbList","@id":"https:\/\/aidanfinn.com\/?p=14032#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/aidanfinn.com#listItem","position":1,"name":"Home","item":"https:\/\/aidanfinn.com","nextItem":{"@type":"ListItem","@id":"https:\/\/aidanfinn.com\/?cat=20#listItem","name":"Hyper-V"}},{"@type":"ListItem","@id":"https:\/\/aidanfinn.com\/?cat=20#listItem","position":2,"name":"Hyper-V","item":"https:\/\/aidanfinn.com\/?cat=20","nextItem":{"@type":"ListItem","@id":"https:\/\/aidanfinn.com\/?p=14032#listItem","name":"Windows Server 2012 NIC Teaming Part 4 \u2013 Load Distribution"},"previousItem":{"@type":"ListItem","@id":"https:\/\/aidanfinn.com#listItem","name":"Home"}},{"@type":"ListItem","@id":"https:\/\/aidanfinn.com\/?p=14032#listItem","position":3,"name":"Windows Server 2012 NIC Teaming Part 4 \u2013 Load Distribution","previousItem":{"@type":"ListItem","@id":"https:\/\/aidanfinn.com\/?cat=20#listItem","name":"Hyper-V"}}]},{"@type":"Person","@id":"https:\/\/aidanfinn.com\/#person","name":"AFinn","image":{"@type":"ImageObject","@id":"https:\/\/aidanfinn.com\/?p=14032#personImage","url":"https:\/\/secure.gravatar.com\/avatar\/65fde4aa9f2ab1cf1514ae320a37ec682d9398ce5791d3c2dd1e8670a71ceea0?s=96&d=mm&r=g","width":96,"height":96,"caption":"AFinn"}},{"@type":"Person","@id":"https:\/\/aidanfinn.com\/?author=1#author","url":"https:\/\/aidanfinn.com\/?author=1","name":"AFinn","image":{"@type":"ImageObject","@id":"https:\/\/aidanfinn.com\/?p=14032#authorImage","url":"https:\/\/secure.gravatar.com\/avatar\/65fde4aa9f2ab1cf1514ae320a37ec682d9398ce5791d3c2dd1e8670a71ceea0?s=96&d=mm&r=g","width":96,"height":96,"caption":"AFinn"}},{"@type":"WebPage","@id":"https:\/\/aidanfinn.com\/?p=14032#webpage","url":"https:\/\/aidanfinn.com\/?p=14032","name":"Windows Server 2012 NIC Teaming Part 4 \u2013 Load Distribution | Aidan Finn, IT Pro","description":"Windows Server 2012 NIC Teaming Part 1 \u2013 Back To Basics Windows Server 2012 NIC Teaming Part 2 \u2013 What\u2019s What? Windows Server 2012 NIC Teaming Part 3 \u2013 Switch Connection Modes With a team formed you have the failover part of LBFO figured out. But what about the load balancing piece of LBFO? That's","inLanguage":"en-GB","isPartOf":{"@id":"https:\/\/aidanfinn.com\/#website"},"breadcrumb":{"@id":"https:\/\/aidanfinn.com\/?p=14032#breadcrumblist"},"author":{"@id":"https:\/\/aidanfinn.com\/?author=1#author"},"creator":{"@id":"https:\/\/aidanfinn.com\/?author=1#author"},"datePublished":"2013-01-10T13:43:00+00:00","dateModified":"2014-08-07T13:27:45+01:00"},{"@type":"WebSite","@id":"https:\/\/aidanfinn.com\/#website","url":"https:\/\/aidanfinn.com\/","name":"Aidan Finn, IT Pro","description":"A blog covering Azure, Hyper-V, Windows Server, desktop, systems management, deployment, and so on ...","inLanguage":"en-GB","publisher":{"@id":"https:\/\/aidanfinn.com\/#person"}}]},"og:locale":"en_GB","og:site_name":"Aidan Finn, IT Pro - A blog covering Azure, Hyper-V, Windows Server, desktop, systems management, deployment, and so on ...","og:type":"activity","og:title":"Windows Server 2012 NIC Teaming Part 4 \u2013 Load Distribution | Aidan Finn, IT Pro","og:description":"Windows Server 2012 NIC Teaming Part 1 \u2013 Back To Basics Windows Server 2012 NIC Teaming Part 2 \u2013 What\u2019s What? Windows Server 2012 NIC Teaming Part 3 \u2013 Switch Connection Modes With a team formed you have the failover part of LBFO figured out. But what about the load balancing piece of LBFO? That's","og:url":"https:\/\/aidanfinn.com\/?p=14032","twitter:card":"summary","twitter:site":"@joe_elway","twitter:title":"Windows Server 2012 NIC Teaming Part 4 \u2013 Load Distribution | Aidan Finn, IT Pro","twitter:description":"Windows Server 2012 NIC Teaming Part 1 \u2013 Back To Basics Windows Server 2012 NIC Teaming Part 2 \u2013 What\u2019s What? Windows Server 2012 NIC Teaming Part 3 \u2013 Switch Connection Modes With a team formed you have the failover part of LBFO figured out. But what about the load balancing piece of LBFO? That's","twitter:creator":"@joe_elway"},"aioseo_meta_data":{"post_id":"14032","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":"","og_description":"","og_object_type":"activity","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":"","twitter_use_og":false,"twitter_card":"summary","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"breadcrumb_settings":null,"limit_modified_date":false,"ai":null,"created":"2020-12-21 03:53:20","updated":"2025-06-04 15:37:51","seo_analyzer_scan_date":null},"aioseo_breadcrumb":"<div class=\"aioseo-breadcrumbs\"><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/aidanfinn.com\" title=\"Home\">Home<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/aidanfinn.com\/?cat=20\" title=\"Hyper-V\">Hyper-V<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\tWindows Server 2012 NIC Teaming Part 4 \u2013 Load Distribution\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/aidanfinn.com"},{"label":"Hyper-V","link":"https:\/\/aidanfinn.com\/?cat=20"},{"label":"Windows Server 2012 NIC Teaming Part 4 \u2013 Load Distribution","link":"https:\/\/aidanfinn.com\/?p=14032"}],"jetpack_featured_media_url":"","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/14032","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=14032"}],"version-history":[{"count":2,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/14032\/revisions"}],"predecessor-version":[{"id":16915,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/14032\/revisions\/16915"}],"wp:attachment":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=14032"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=14032"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=14032"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}