NIC Teaming was a highlight we gotten through autonomous equipment merchants such as Broadcom. A isolated piece of program was introduced and you went through a GUI to group your interfacing. Some of the time it was simple to do, now and then it wasn't. Windows Server 2012 presently has NIC Joining built-in. NIC Teaming is the act of holding arrange connectors to make one coherent arrange connector. It gives valuable highlights such as stack adjusting over person joins and failover.

We can do this in two configurations:

- Connecting all network adapters to the same switch.

- Connecting network adapters to different switches.

Within switch-dependent mode, We have two choices for teaming:

- Generic -- 802.3ad

- Dynamic -- 802.1ax -- LACP

Network Availability

One of the reasons you'd utilize NIC Teaming is to supply organize accessibility to your server. This diminishes blackouts and anticipates disappointments such as NIC disappointments, switch disappointments or something as basic as somebody incidentally detaching the organize cable. In case one of the arrange interfacing goes down, all activity will failover to any remaining interfacing on the group. You'll have less amassed transfer speed but your server is still accessible.

Network Performance

Another reason for NIC Teaming is to supply more execution. With many workloads being virtualized you've got more thickness. Total the transmission capacity of all accessible arrange interfacing with NIC Teaming .

Algorithm

Activity is dispersed on outbound activity among accessible joins. There are two alternatives accessible.

Hyper-V switch port

The MAC address of the virtual machine provides the basis for dividing traffic.

Hashing

A hash is made based on the components of each bundle. It is at that point relegated to an accessible arrange connector. Bundles from the same TCP stream are set on the same organize adapter.

Inputs for the hashing function are:

- MAC addresses

- IP addresses

- TCP Ports

Configuration

- In Server Manager click on Local Server and then Disabled next to NIC Teaming

- In the NIC Teaming window,in the bottom left tile under Teams, click on TASKS and then click on New Team

- A new Window appears. In the Team name text box type in a name for this team and then select the adapters to be part of the team. Click on Additional properties and you can make modifications such as the Teaming mode, load balancing mode, Standby adapter, and Primary team interface.

- Team will now be created. I got a few warnings and errors before the team is finally up and running.

- In the Adapters and Interfaces Tile you have the ability to change the team and/or move interfaces into a new or existing team by clicking on TASKS.

- Clicking on Properties for the Team brings up the properties window.

- NIC Teaming is now enabled in Server Manager
https://mobileinfoworld.com/configure-nic-teaming-on-windows-server-2012-r2/