Network link aggregation, also known as trunk, is a feature built into Windows Server 2019. This allows the maximum throughput of several network cards to be cumulated, so as not to cap at 1Gbits or 10GbE as the maximum offer for each NIC but to do 2 x 1Gbits, 3 x, 4 x or more. A real increase in the network performance of a server, essential in high availability SGBD fileserver, etc.
Not active by default after installing the operating system, Microsoft offers to configure it in a few clicks. This tutorial explains how to configure the NIC Teaming, the combination of network cards, to increase the network speed of a physical or virtual server tenfold with Windows Server 2019 . The procedure for activating the NIC Teaming also exists on Windows Server 2012 / R2 and 2016.
Configuring a network card association under Windows Server 2019
1. Open the Server Manager and go to Configure this local server .
2. The ” line “. Association of network cards » (NIC Teaming) is logically in status “Teaming Off Off ” (default). Click on it . Just below, are listed all the network cards of the server (physical or VM ).
3. The “Network Card Association” window opens with three parts. In the block Teams at the bottom left, click on Tasks and” New team ” (New Team in English).
4. Give a name to this Teaming and select member cards of this group.
5. The ” menu “. Additional properties ” offers various options, including the following default settings:
- Team mode (Teaming mode): if the lag (latency) is static on the switch (IEEE 802.3ad), select”. Static association “if the lag is configured dynamically (IEEE 802.1ax), select”. LACP “; the option” Independent of the switch “must allow to free itself from any configuration of the switch (default).
- Load balancing mode (Load balaing mode):” Address hashing “uses the addresses MAC the addresses IP and ports TCP ; « Port Hyper-V “is to be selected to dedicate the trunk to the Microsoft hypervisor;” Dynamics “for automatic.
- Network card pending (Standby adapt): choose “Standby None None “to use all network cards in the NIC Teaming; otherwise choose the one that will be waiting.
- Main team interface (Primary team interface) : possibility to assign the trunk to a VLAN specific.
6. Validate by OK and wait because the warning “Failed” can be displayed and switch to the status “Failed” by itself OK “after a few moments.
7. The group of network cards is now seen as a single connection, additional to the physical cards.
The icon is different for this NIC Teaming and you always have a view on the connection status of each card.
All that remains is to test network transfers to verify that the throughput is doubled, tripled, quadrupled. Of course, you must have a source that has a network connection greater than 1Gbits, a 10GbE link or several shared Gigabit sources.
This way of doing things, with the graphical interface, is a little easier than in PowerShell .
Important note on the NIC Teaming
It may take the Teaming a few moments to start, we notice this problem when after a restart of Windows Server, an error message indicates that it does not find the domain. The first idea is to connect as a Local Administrator but the solution is to switch the service to “Delayed Start”. Thus, after a system reboot, you wait less than a minute and the connection to the domain will be operational with the association of network cards.