Windows Server 2008 R2 supported NIC teams, but Windows Server 2008 R2 depended on the NIC manufacturers to develop the teaming software. In Windows Server 2012 the NIC teaming capability is now native to the Operating System.
There are three great things that stand out to me about NIC teaming.
- You can team NICs for normal network traffic or for your virtual environment.
- You can now team NICs from different manufacturers.
- You can team up to 32 NICs into a single team.
Below, I will walk through the User Interface and options available.
We have a good NIC teaming overview here, but I wanted to hit a few of the high points of NIC teaming in Windows Server 2012. You need at least two NICs to create a team and you can team as many as 32 NICs into one team. Setting up a NIC team is very easy and I really like that the setup process respects the names you put on your NICs.
Below, are the additional details that can be configured for your NIC team. This allows you to be very specific about how the team is load balanced and connected to your network.
You can configure your team for either Static Teaming, Switch Independent, or LACP (Link Aggregation Control Protocol).
Static Teaming requires configuration on the switch and the computer to identify which links form the team. Because this is a statically configured solution. This is a switch dependent mode of NIC teaming.
Switch Independent mode allows you to distribute the NICs in your team across numerous Network Switches in your environment.
LACP provides the Link Aggregation and allows for the expansion and reduction of the NIC team. This is a switch independent mode of NIC teaming.
Load Balancing Mode:
Load balancing mode: your choices are either Address Hash, or Hyper-V Port. Address Hash is how you configure your team to load balance network traffic between the NICs in the team. Hyper-V Port load balancing will load balance your traffic by VM. With Hyper-V Port, the good news is that each VM will transact on a separate NIC, but the down side is that each VM will only transact over a single NIC. If you have multiple virtual NICs in your VM and they are teamed, the Hyper-V Port may be the best choice. For most configurations, I expect that the Address Hash will be your best choice to allow your VM to still access the network in case the NIC the VM is utilizing fails. Remember that with Hyper-V Port the failure of the NIC the VM is utilizing disrupts communication between the VM and the network. Address Hash won’t have this problem.
This allows you to define a Standby Adapter for the team. Take note that you can only define one Standby Adapter, but you can ensure that your teamed bandwidth is available even if a NIC in your team fails.
|Take a look at the current Network Connections. Team 1 is the teamed NIC. I hope you have also noticed that the teamed NICs are from different manufacturers!
You are able to now team NICs from different manufacturers.
Until next time,