Adapter teaming with Intel® Advanced Network Services (ANS) uses an intermediate driver to group multiple physical ports. Teaming can be used to add fault tolerance, load balancing, and link aggregation features to a group of ports.
Download ANS Teaming Software
Install ANS Teaming Software
Microsoft Windows Server 2012 NIC Teaming
Implementation Considerations (includes throughput and resource issues)
Download ANS Teaming Software
Drivers and software for Intel® Ethernet Adapters lists driver downloads for Intel® Ethernet Adapters that include Advanced Network Services (ANS) teaming software. A separate download for teaming software is not required or available.
Install ANS Teaming Software
Advanced Network Services (ANS) are installed by default along with Intel® PROSet for Windows* Device Manager. See the screen shot below.
When you run the installation from the CD included with your software or from downloaded software, the Setup Option gives you the choice to install ANS. Because ANS is checked by default, no special action is required during installation.
If you uncheck ANS during installation, then you need to modify the installation and select ANS as an install option.
If your adapter supports teaming, then a Teaming tab displays in Windows* Device Manager after installing the software. Use the New Team option and follow the wizard to create a team.
Teaming options are supported for Windows versions where the following Intel adapters receive full software support:
- Intel® Server Adapters
- Converged Network adapters
- Intel® Gigabit CT Desktop Adapters
Support for Intel® PROSet and Advanced Network Services (ANS) provides information on adapters with full support for Windows 7* and later.
When creating a team on a supported adapter, ports on non-supported adapters can display in the Intel® PROSet teaming wizard. Any port that displays in the Intel PROset teaming wizard can be included in a team including older Intel adapters and non-Intel adapters.
Intel® PRO/100 and PRO/1000 adapters that plug into PCI or PCI-X* slots do not support ANS teaming in any Windows versions later than Windows Vista* and Windows Server* 2008.
Some advanced features, including hardware offloading, are automatically disabled when non-Intel adapters are team members to assure a common feature set.
TOE (TCP Offload Engine) enabled devices cannot be added to a team and do not display in the list of available adapters.
Microsoft Windows Server* 2012 NIC Teaming
Windows Server 2012 adds support for NIC teaming, also known as Load Balancing and Failover (LBFO). Intel ANS teaming and VLANs are not compatible with Microsoft LBFO teams. Intel® PROSet blocks a member of an LBFO team from being added to an Intel ANS team or VLAN. Do not add a port that is part of an Intel ANS team or VLAN to an LBFO team. Adding a port can cause system instability.
If you use an ANS team member or VLAN in an LBFO team, do the following procedure to restore your configuration:
- Reboot the server.
- Remove LBFO team. Even though LBFO team creation failed, after a reboot the Server Manager reports that LBFO is Enabled. The LBFO interface is present in the NIC Teaming GUI.
- Remove the ANS teams and VLANS involved in the LBFO team and recreate them. This step is optional but strongly recommended. All bindings are restored when the LBFO team is removed.
||If you add an Intel AMT enabled port to an LBFO team, do not set the port to Standby in the LBFO team. If you set the port to Standby you can lose AMT functionality.|
Teaming features include Failover protection, increased bandwidth throughput aggregation, and balancing of traffic among team members. Teaming Modes are AFT, SFT, ALB, Receive Load Balancing (RLB), SLA, and IEEE 802.3ad Dynamic Link Aggregation.
Features available, using Intel Advanced Networking Software (ANS) include:
- Fault Tolerance
Uses one or more secondary adapters to take over for the primary adapter should the first adapter, its cabling, or the link partner fail. Designed to guarantee server availability to the network.
- Link Aggregation
Combines multiple adapters into a single channel to provide greater bandwidth. Bandwidth increase is only available when connecting to multiple destination addresses. ALB mode provides aggregation for transmission only while RLB, SLA, and IEEE 802.3ad dynamic link aggregation modes provide aggregation in both directions. Link aggregation modes require switch support, while ALB and RLB modes can be used with any switch.
- Load Balancing
The distribution of the transmission and reception load the among aggregated network adapters. An intelligent adaptive agent in the ANS driver repeatedly analyzes the traffic flow from the server and distributes the packets based on destination addresses. (In IEEE 802.3ad modes the switch provides load balancing on incoming packets.)
||Load Balancing in ALB mode can only occur on Layer 3 routed protocols (IP and NCP IPX). Load Balancing in RLB mode can only occur for TCP/IP. Non-routed protocols are transmitted only over the primary adapter. |
- Adapter Fault Tolerance (AFT)
Allows mixed models and mixed connection speeds as long as there is at least one Intel® PRO server adapter in the team. A 'failed' Primary adapter passes its MAC and Layer 3 address to the failover (secondary) adapter. All adapters in the team should be connected to the same hub or switch with Spanning Tree (STP) set to Off.
- Switch Fault Tolerance (SFT)
Uses two adapters connected to two switches to provide a fault tolerant network connection in the event that the first adapter, its cabling or the switch fails. Only two adapters can be assigned to an SFT team.
- Do not put clients on the SFT team link partner switches, because they do not pass traffic to the partner switch at fail.
- Spanning Tree (STP) must be running on the network to make sure that loops are eliminated.
- Turn off STP on the incoming ports of the switches directly connected to the adapters in the team, or configure ports for PortFast.
- Only 802.3ad DYNAMIC mode allows failover between teams.
Diagram of Switch Fault Tolerance (SFT) Team with Spanning Tree Protocol
Adaptive Load Balancing (ALB)
Offers increased network bandwidth by allowing transmission over 2-8 ports to multiple destination addresses, and incorporates Adapter Fault Tolerance. Only the primary adapter receives incoming traffic. Broadcasts/multicasts and non-routed protocols are only transmitted via the primary adapter in the team. The ANS software load balances transmissions, based on Destination Address, and can be used with any switch. Simultaneous transmission only occurs at multiple addresses. This mode can be connected to any switch.
- Receive Load Balancing (RLB)
- Offers increased network bandwidth by allowing reception over 2-8 ports from multiple addresses.
- Can only be used in conjunction with ALB.
- RLB is enabled by default when an ALB team is configured unless you are using Microsoft Hyper-V*.
- RLB mode is not compatible with Microsoft Hyper-V*. Use Virtual Machine Load Balancing mode if you want to balance both transmit and receive traffic.
- Only the adapters connected at the fastest speed are used to load balance incoming TCP/IP traffic. The primary adapter, regardless of speed, receives all other RX traffic.
- Can be used with any switch. Any failover increases network latency until ARPs are resent. Simultaneous reception only occurs from multiple clients.
- Virtual Machine Load Balancing (VMLB)
VMLB teaming mode was created specifically for use with Microsoft Hyper-V*. VMLB provides transmit and receive traffic load balancing across Virtual Machines bound to the team interface. The LMLB team also provides fault tolerance in the event of switch port, cable, or adapter failure. This teaming type works with any switch.
The driver analyzes the transmit and receive load on each member adapter, and balances the traffic across member ports. In a VMLB team, each Virtual Machine is associated with one team member port for its TX and RX traffic. For example: If you have three virtual machines and two member ports, and if VM1 has twice as much traffic as the combination of VM2 and VM3, then VM1 is assigned to team member port 1, and VM2 and VM3 share team member port 2.
If only one virtual NIC is bound to the team, or if Hyper-V is removed, then the VMLB team acts like an AFT team.
- VMLB does not load balance non-routed protocols such as NetBEUI and some IPX* traffic.
- VMLB supports from 2 to 8 ports per team.
- You can create a VMLB team with mixed speed adapters. The load is balanced according to the lowest common denominator of adapter capabilities, and the bandwidth of the channel.
This standard has been implemented in two ways:
- Static Link Aggregation (SLA):
- Equivalent to EtherChannel or Intel Link Aggregation
- Must be used with an 802.3ad, FEC/GEC/ or Intel Link Aggregation capable switch.
- Requires 802.3ad DYNAMIC capable switches.
- Active aggregators in software determine team membership between the switch and the ANS software (or between switches).
- There is a maximum of 2 aggregators per server and you must choose either maximum bandwidth or maximum adapters.
Both 802.3ad modes include adapter fault tolerance and load balancing capabilities. However in DYNAMIC mode load balancing is within only one team at a time.
IEEE 802.3ad Link Aggregation (LAG): what it is, and what it is not presents more informationHere is a chart of the features and modes available.
||Dynamic 802.3ad |
|Layer 3 Address Aggregation
|Layer 2 Address Aggregation
|Mixed Speed Adapters*
- You can mix different adapter types for any mode. But, you must run all the adapters in the team at the same speed when using Link Aggregation mode. Mixed Speed connections are possible in AFT, ALB, RLB, SFT, and 802.3ad modes.
- Multi-vendor teaming (MVT) is applicable to all modes in Microsoft Windows.
For AFT, SFT, ALB and RLB modes you can choose a Primary and Secondary Role for selected adapters.
The Secondary adapter becomes the Primary (if possible) at failure of the Primary, or its cable or link partner.
- The Primary adapter is the adapter that carries the most traffic.
- With AFT and SFT it is the only adapter used until that link fails.
- With ALB and non-routable protocols (anything other than IP or Novell IPX), it is the only adapter used. It is also the only adapter used for broadcast and multicast traffic.
- With RLB, all traffic other than IP traffic, is passed on the primary adapter, regardless of its speed.
- If the primary adapter is set by the user instead of the software, and is active at fail time, it allows failback to the chosen primary adapter.
||When a primary is removed from a team, its MAC address stays with the team until the server is rebooted. Do not add the primary back on that network until the server it was removed from is rebooted.|
Test Switch Configuration:
There is a utility in Intel PROset for Windows Device Manager, on the Advanced Settings Team page that allows the ANS software to query the switch partner for configuration settings. If the switch is configured differently than necessary for the team mode, a troubleshooting page displays listing possible corrective actions. When running this test, the team temporarily loses network connectivity. See Intel PROset for Windows Device Manager Help for limitations.
Linux Ethernet Bonding (also known as channel bonding or teaming) in Linux
Channel bonding documentation can be found in the Linux kernel source:
Advanced Network Services Software Whitepaper
IEEE 802.3ad Link Aggregation (LAG): what it is, and what it is not
Is Adapter Teaming supported on any system which carries iSCSI traffic?
IEEE 802.3AD Dynamic and Static Switch configuration for different team modes
Intel® PROSet for Device Manager tabs are not visible through terminal services
Intel® PROSet configuration tabs are missing
Teaming topic in the User Guide.
Windows Server 2012 NIC Teaming in Microsoft TechNet Library
1Advanced Networking Support (ANS) features are not available for Novell NetWare beginning with Intel network adapter software release 12.1 and later. Software version 12.0, ANSNWARE.EXE, is available for download and contains the last version of drivers that implement ANS in Novell NetWare.
This applies to: