I do know how to configure LACP teaming, so I always prefer to use"switch-assisted" (opposite to "switch independent") NIC redundancy for servers.
To learn how to do NIC teaming using LACP (802.3ad) protocol in Windows Server 2012 with H3C switches press the link.
Prior to Windows Server 2012 we all had to rely on 3rd party software like HP Network Configuration Utility to provide NIC teaming or bonding. And chances are you experienced various problems and limitations of these kind of utilities in general and HP Network Configuration Utility in particular.
I mention HP Network Configuration Utility just as an example and due to majority of servers I have here are built by HP.
Now in Windows 2012 NIC teaming is performed using native functionality. You can use Powershell 3.0 or lbfoadmin utility to do the job.
New-NetLbfoTeam lacpteam "Ethernet","Ethernet 2"–TeamingMode Lacp
However if you forget to configure switch ports to support the aforementioned server side configuration, you get an error like this (you can see lbfoadmin interface in the background with Powershell interface on top):
The switch part (as before I hope this code will work for any Comware-based switch) can look like this:
![]()
So my take is that MS did a great job providing in-house NIC teaming solution. And what do you think?
interface Bridge-Aggregation1
description win2012testteam
port access vlan 10
link-aggregation mode dynamic
#
return
interface GigabitEthernet1/0/1
port link-mode bridge
description win2012nic1
port access vlan 10
port link-aggregation group 1
#
interface GigabitEthernet2/0/1
port link-mode bridge
description win2012nic2
port access vlan 10
port link-aggregation group 1
#
return
It is wise to connect server's NICs to different slots, that is why I use gi1/0/1 and gi2/0/1 ports. And you must use link-aggregation mode dynamic to enable LACP functionality.
Now you have working configuration. To check if your team is ok use Get-NetLbfoTeam comandlet:
So my take is that MS did a great job providing in-house NIC teaming solution. And what do you think?