# Choose Adapter Teaming Options (Server Adapter Only)

The PRO/100 Server adapter teaming features include fault tolerance, load balancing, and increased throughput options when running Windows* NT 4.0 and Windows 2000*, NetWare* 4.1x and above, Linux, and UnixWare 7.x.*

- Adapter Fault Tolerance (AFT) -- provides automatic redundancy for your adapter. If the primary adapter fails, the secondary takes over. Adapter Fault Tolerance supports two to eight adapters per team. This feature works with any hub or switch.
- Adaptive Load Balancing (ALB) -- allows balancing the transmission data flow among two to eight adapters. Also includes adapter fault tolerance. This feature works with any switch.
- Intel Link Aggregation or Cisco Fast EtherChannel* (FEC) -- creates a team of two to eight adapters to increase transmission and reception throughput. Also includes adapter fault tolerance and load balancing. Requires a switch with Link Aggregation or FEC capability.
- 802.3ad -- IEEE 802.3ad is a performance technology standard similar to the Fast EtherChannel* (FEC) standard with the addition of dynamic team aggregation. Requires an 802.3ad switch, configured to match static or dynamic capabilities.

For an overview of Teaming Options, see "Solving Server Bottlenecks with Intel Server Adapters." This document covers teaming and load balancing options. You can view this document with the Adobe Acrobat* Viewer.

| IMPORTANT: For optimal performance, you must disable the Spanning Tree Protocol (STP) when using teaming.

| IMPORTANT: When you use PROSet II to create a team in Windows 2000, a virtual adapter instance is displayed in both the Device Manager and Network and Dial-up Connections. Each virtual adapter instance is listed as "Intel(R) Advanced Network Services Virtual Adapter." Do not attempt to modify (except to change protocol configuration), disable or remove these virtual adapter instances using Device Manager or Network and Dial-up Connections. Instead, you must only use PROSet II. Doing otherwise may result in system anomalies, including bluescreens.

## Adapter Fault Tolerance Overview

Adapter Fault Tolerance (AFT) provides the safety of an additional backup link between the server and switch. In the case of switch port, cable, or adapter failure, you can maintain uninterrupted network performance.

Adapter Fault Tolerance is implemented with a primary adapter and one or more backup, or secondary adapters. During normal operation, the backup adapters are disabled. If the link to the primary adapter fails, the link to the secondary adapter automatically takes over.

To use Adapter Fault Tolerance, you must have at least one PRO/100 or one PRO/1000 adapter in your team with all adapters linked to the same switch.

## Adaptive Load Balancing Overview

Adaptive Load Balancing (ALB) uses software to balance the transmission load of your server among a team of two to eight Intel adapters (must include at least one server adapter) connected to the same switch. The software analyzes transmit loading on each adapter and balances the rate across the adapters based on destination address. Received data is not load-balanced. Adapter teams configured for ALB also provide the benefits of AFT.

| NOTE: ALB does not balance non-routed protocols such as NetBEUI and some IPX* traffic. For a list of specific IPX environments that are supported, see Teaming Options Supported by OS and Protocol.

## Fast EtherChannel (FEC)/Intel Link Aggregation Overview

Fast EtherChannel (FEC) is a performance technology developed by Cisco to increase throughput between switches. Intel has implemented FEC on server adapters that works with either FEC capable switches or Intel Link Aggregation capable switches to increase your server's throughput to multiple addresses. Unlike ALB, FEC can be configured to increase both transmission and reception channels between your server and switch.

The transmission speed will never exceed the adapter base speed to any single address (per specification). Teams may be from 2 to 8 adapters but must match the capability of the switch. Adapter teams configured for FEC also provide the benefits of fault tolerance and load balancing.

| NOTE: To replace an existing FEC-teamed adapter in a hot plug slot, first unplug the adapter cable. When the adapter is replaced, reconnect the cable..

## 802.3ad Overview

802.3ad is an adopted IEEE standard that has two modes: static or dynamic link aggregation. In static mode, it is similar to Fast EtherChannel* (FEC). In dynamic mode, the adapter software probes the switch and vice versa to determine the team aggregations. Teams can consist of two to eight adapters and you can have a maximum of two IEEE 802.3ad teams per server. You must use 802.3ad switches (aggregation can go across switches). Adapter teams configured for IEEE 802.3ad also provide the benefits of fault tolerance and load balancing. Under 802.3ad, all protocols can be load balanced.

In Dynamic mode, you can add and remove adapters from the link without losing the connection. Dynamic mode supports multiple aggregators and they are formed either by different speeds on the same switch (teams based on speed) or by using multiple switches (provides some redundancy between switches). Only one team will be active at a time and because switch implementations may vary, the Intel ANS (teaming) software allows you to select either maximum bandwidth or maximum adapters.

| NOTE: Once you choose an aggregator, it remains in force until all adapters in that aggregator lose link.

## Setting Up Teaming in Windows

| NOTE: Adapter Teaming options for NT 4.0 require Service Pack 5 or later.

1. Start Intel PROSet II as described in Using PROSet II. If PROSet II is not installed see Running the Component Installer page.
2. Choose a server adapter in the left panel and right-click the mouse to start Teaming Wizard.
3. Complete the Teaming Wizard to add adapters to each team.
4. See the PROSet II online help for additional information.
5. To finish, you must close PROSet II when the wizard is done.

### Removing a Team

1. In the Network Component Tree in PROSet II, right click on a Team Listing.
2. In the menu that appears, click Remove.
3. A confirmation message appears. Click Yes.

| NOTE: If you have created VLANs or Priority Packet Filters for the team, these will be removed along with the team. If you created VLANs or Priority Packet Filters for an adapter before it was teamed, these will be retained when the team is removed.

## Setting Up Teaming in Novell NetWare 4.1x and Above

Copy iANS.LAN and CE100B.LAN files into the system directory (SYS:SYSTEM) of your server. See instructions in Teaming Tips and specific examples in the Examples text file.

### Removing a Team

To remove a team in AFT/ALB/FEC/802.3ad mode, unload iANS.LAN by typing "UNLOAD IANS" at the console. Remember to comment out any lines you added to autoexec.ncf or a batch file if you do not want them to reload when you restart the server .

## Setting Up Teaming in UnixWare 7.x

Configuration information for PRO/100 adapter teaming features under UnixWare 7.x may be found on the Installing the eeE DDI8 Driver for UnixWare* 7 page.

## Setting up Teaming in Linux

See instructions in the Linux ANS readme file.

## Teaming Options Supported by OS and Protocol

### Supported Protocols
Teaming Option | Windows NT 4.0, Windows 2000 | NetWare | UnixWare 7.1.x
--- | --- | --- | ---
AFT | IP, NetBEUI, IPX (NCP), IPX (NetBIOS) | IP, IPX (NCP), AppleTalk* | IP, IPX
ALB | IP, IPX (NCP) | IP, IPX (NCP) | IP, IPX (NCP)
FEC | IP, NetBEUI, IPX (NCP), IPX (NetBIOS) | IP, IPX (NCP) | IP, IPX (NCP)

| NOTE: Note that only IPX packets type NCP (NetWare Core Protocol) are load balanced. If a particular protocol is not listed above, it means that protocol's traffic is routed through the primary adapter of the team.

* See Legal Notices