There are 4 possible basic configurations of a NIC team, depending on your physical switches and how you want to distribute or load balance traffic across the team members of the NIC team. In this post, I want to focus on the switch connection modes.
This configuration of the switch connection mode is determined in one of two ways:
- You decide how you want traffic to flow, that determines your switch architecture, and you design the team appropriately.
- You already have a physical switch architecture, and you have to configure the team appropriately.
There are two switch connection modes in a WS2012 NIC team. My tip: focus on the use of independent and dependent when trying to remember which is which.
This type of NIC team has no dependency on functionality in the connected physical switch(es) to make the NIC team work. It is appropriate to use this type of NIC team in two scenarios:
1) A single dumb switch, like the sort you might get in a store for a lab
The switch does switching and that’s it. There’s no management port or console, and no settings you can configure. The team works independently of any non-existing functionality in the switch.
Alternatively, the team members are plugged into multiple independent switches. In this case, the switches might or might not have some clever management. The key piece here is that each access switch is functioning completely independent of the other – there is no switch stacking going on.
A nice feature of switch independent teams is that you can configure a hot-standby team member in the NIC team. This is only possible in a switch independent team.
The name says it all; the NIC team relies on some functionality in the switch(es) that the NIC team members are connected to. This could be a single managed switch. It could also be a single logical switch, such as a switch stack.
There are two ways to set up a switch dependent NIC team. Both options require you to configure the switch(es) in some way (consult your network documentation):
- Static teaming
Static teaming is when the switch ports are configured to be in the same team. Using the above example, the switch ports for pNIC1 and pNIC2 would have to be configured to be in the same team. This is pretty inflexible: try reconfiguring the team or moving the cables to different switch ports and you’ll break the team without doing some switch reconfiguration to match the changes.
Link Aggregation Control Protocol (LACP) is similar to static teaming because it requires switch configuration. However, once the switch is enabled for LACP, the team dynamically configures the switch whenever it comes online or is reconfigured. This means that you do not need to constantly log calls for the network admins when you are doing physical server operations.
That’s enough for today. Next up will be load distribution.
This information has been brought to you by Windows Server 2012 Hyper-V Installation and Configuration Guide (available on pre-order on Amazon) where you’ll find lots of PowerShell like in this script:
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.