{"id":3749,"date":"2015-06-01T08:59:59","date_gmt":"2015-06-01T13:59:59","guid":{"rendered":"http:\/\/www.poweradmin.com\/blog\/?p=3749"},"modified":"2015-05-29T10:37:37","modified_gmt":"2015-05-29T15:37:37","slug":"configuring-nic-teaming","status":"publish","type":"post","link":"https:\/\/www.poweradmin.com\/blog\/configuring-nic-teaming\/","title":{"rendered":"Configuring NIC Teaming"},"content":{"rendered":"

In this article we will learn about a new feature that was introduced in Windows Server 2012<\/a>, NIC teaming. This technology allows a server to group multiple network interfaces (NIC) into a so called team. To achieve similar results with older Windows Server Editions, you would had to buy a dedicated third party equipment that has these capabilities.<\/span><\/p>\n

With NIC teaming you ensure that servers still have connectivity if one network adapter fails and you can aggregate network traffic over multiple devices. These technologies were more common at network devices such as switches, but they can now be configured server-side.<\/span><\/p>\n

You can group 2 or more network adapters into a team by using either Server Manager<\/i> or Powershell<\/i>. Note that Windows Server 2012 allows grouping of up to 32 network cards. Network interfaces that are grouped into a team can work in three modes:<\/span><\/p>\n

LACP:<\/b>It\u2019s a protocol supported by most enterprise switches. The LACP (Link Aggregation Control Protocol) automatically detects links between servers and switches, but you\u2019ll have to enable LACP on the switch prior to creating the team.<\/span><\/p>\n

Static Teaming:<\/b> requires that you configure the switch and the servers manually to enable the links that will form the team.<\/span><\/p>\n

Switch Independent: <\/b>allows network interfaces that are part of a team to connect to different switches<\/span><\/p>\n

I will show you how to enable NIC teaming by using both methods. Note that I\u2019m using a Windows Server 2012 VM hosted in my VirtualBox testing environment.<\/span><\/p>\n

Open Server Manger<\/i> console, navigate to the All Servers<\/i> section, right click<\/i> on your machine and select Configure NIC Teaming<\/i>:<\/span><\/p>\n

\"Configure<\/a><\/p>\n

From the bottom right section of the panel select two or more NICs, right click<\/i> them and click on Add to New Team<\/i>:<\/span><\/p>\n

\"NIC<\/p>\n

Set a name for your team and make sure that the desired interfaces are selected. By clicking on the additional properties<\/i> menu you can set the following settings:<\/span><\/p>\n

\"NIC<\/p>\n

Teaming mode: <\/b>the ones we\u2019ve discussed in the beginning of the article<\/span><\/p>\n

Load balancing mode: <\/b><\/span><\/p>\n

\u00b7 Address Hash<\/b> \u2013 load balances all outbound traffic using all NICs but receives inbound traffic on only one network card. Basically, each packet is inspected and based on the address field, a hash will be created. The packet is then assigned to a particular adapter based on the given hash.<\/span><\/p>\n

\u00b7 Hyper-V<\/a> port<\/b> \u2013 works best when your physical server is a Hyper-V node that hosts multiple VMs. This load balancing mode should be used in most scenarios. Outbound and inbound traffic for each VM will be handled by a specific NIC since VMs connect to a Hyper-V virtual switch.<\/span><\/p>\n

\u00b7 Dynamic<\/b> \u2013 takes advantages of features from both of the above components. Inbound traffic will be distributed using Hyper-V mode while outbound traffic will be handled using the hash of the port and address fields\/<\/span><\/p>\n

Standby adapter<\/b>: by selecting a secondary adapter, you ensure that network traffic is not disrupted if one of your network devices fails<\/span><\/p>\n

Primary team interface:<\/b> from this section you can configure the VLAN membership of your network team. You can either set the default option which will let the primary interface handle all traffic that is not destined for other VLANS or set a specific VLAN:<\/span><\/p>\n

\"VLAN<\/p>\n

Using Powershell<\/i>, we can configure NIC teaming by using cmdlets that are part of the NetLbfo<\/i> module. To view available cmdlets, use the following command: Get-Command \u2013Module NetLbfo<\/i>:<\/span><\/p>\n

\"Powershell<\/p>\n

First, let\u2019s get the network card names by typing the following command:<\/span><\/p>\n

netsh interface ipv4 show interfaces<\/i><\/span><\/p>\n

Once we\u2019ve obtained the names we\u2019ll have to create the team by typing the following command:<\/span><\/p>\n

New-NetLbfoTeam -Name Myteam -TeamMembers Ethernet,Ethernet 2 -TeamingMode Lacp -LoadBalancingAlgorithm HyperVPort<\/i><\/span><\/p>\n

Name<\/i> \u2013 new team\u2019s name<\/span><\/p>\n

TeamMembers<\/i> \u2013 the names of the NICs<\/a> that will be part of the team<\/span><\/p>\n

TeamingMode<\/i> and LoadBalancingAlgorithm \u2013 <\/i>parameters are the ones we\u2019ve discussed previously.<\/span><\/p>\n

\"NIC<\/p>\n

With the Get-NetLbfoTeam<\/i> you can view the teams configured on the server and you can edit one by using the Set-NetLbfoTeam<\/i> command. To remove the newly configured team, type in the following command: Remove-NetLbfoTeam Myteam<\/i><\/span><\/p>\n

\"Editing<\/p>\n

NIC teaming is a great technology that you can use to ensure business continuity by proving a redundant way your servers manage network traffic. Teams can be configured easily by using either Server Manager<\/i> or Powershell<\/i> and can really help you in consolidating the network infrastructure. The only thing you\u2019ll need to ensure is that switches are configured accordingly to be able to communicate with your servers. Please share your thoughts on this topic and don\u2019t hesitate to post any questions in our dedicated section.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

In this article we will learn about a new feature that was introduced in Windows Server 2012, NIC teaming. This technology allows a server to group multiple network interfaces (NIC) into a so called team. To achieve similar results with older Windows Server Editions, you would had to buy a dedicated third party equipment that […]<\/p>\n","protected":false},"author":4,"featured_media":3775,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,5,9,8],"tags":[],"class_list":["post-3749","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-general-it","category-how-to","category-technical","category-windows"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/3749","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/comments?post=3749"}],"version-history":[{"count":5,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/3749\/revisions"}],"predecessor-version":[{"id":3774,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/posts\/3749\/revisions\/3774"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/media\/3775"}],"wp:attachment":[{"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/media?parent=3749"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/categories?post=3749"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.poweradmin.com\/blog\/wp-json\/wp\/v2\/tags?post=3749"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}