SLB works only with SLB-enabled switches, such as the Catalyst 6000 series. The SLB software continuously analyzes loading on each adapter and balances network traffic across the adapters as needed. Adapter teams configured for SLB also provide the benefits of NFT.

To use SLB, you must have at least two HP Fast Ethernet or Gigabit adapters installed in your server and linked to the same SLB-enabled switch. For SLB, you can only team 100 Mbps adapters together (no 10 Mbps or Gigabit), with the exception of the NC71xx and NC77xx server adapters, which are Gigabit and can run at 10/100 Mbps.

•Transmit Load Balancing with Fault Tolerance (TLB). TLB creates a team of adapters to increase a server's throughput. If you configure TLB, NFT is automatically configured. TLB works with any industry-standard 10BASE-T, 100BASE-TX, or Gigabit switch. All transmit IP frames are load balanced among all team members based on a Load Balancing algorithm in the teaming device driver. The Current Primary adapter transmits all non-IP frames, and receives all frames for the team. If a failover event occurs, one of the non-Primary adapters assumes the role of Current Primary adapter, and transmit IP packets are load balanced among all remaining team members. If a failure occurs in any of the non-Primary adapters, the packets are load balanced among all remaining team members.

To use TLB, you must have at least two NCxxxx adapters (ports) capable of the same speed and linked to the same Layer 2 (Broadcast) switch installed in your server. They cannot be connected to the same switch and/or be members of different VLANs. With TLB, as you add adapters to your server, you can group them in teams to provide a single virtual adapter with increased transmission bandwidth. For example, a TLB team containing four HP Fast Ethernet adapters configured for full- duplex operation would provide an aggregate maximum transmit rate of 400 Mbps and a 100 Mbps receive rate resulting in a total bandwidth of 500 Mbps.

TLB load balances IP traffic under Windows NT® and IP and IPX traffic under NetWare.

•Transmit Load Balancing with Fault Tolerance and Preference Order. All transmitted IP packets are load balanced among all team members based on a Load Balancing algorithm in the teaming device driver. The Current Primary adapter transmits all non-IP packets, and receives all frames for the team. If a failover event occurs, one of the non-Primary adapters assumes the role of Current Primary adapter, and transmitted IP packets are load balanced among all remaining team members. If a failure occurs in any of the non-Primary adapters, the packets are load balanced among all remaining team members. The user sets the priority of the adapters relative to each other within the team. The priority of the adapters is an additional consideration when determining the Primary adapter.

•Network Fault Tolerance Only (NFT). NFT provides the safety of an additional backup link between the server and hub/switch. NFT is implemented with a Primary adapter and a Secondary (backup) adapter(s). During normal operations, if the Primary adapter fails, the link to the Secondary adapter automatically takes over.

o NFT can occur between two TOE-enabled adapters

•Network Fault Tolerance only with Preference Order. NFT provides the safety of an additional backup link between the server and hub/switch. NFT is implemented with a Primary adapter and a Secondary (backup) adapter(s). During normal operations, if the Primary adapter fails, the link to the Secondary adapter automatically takes over. The user sets the priority of the adapters relative to each other within the team. The priority of the adapters is an additional consideration when determining the Primary adapter.

Currently, NFT is supported in Windows® 2000, Windows Server 2003, and Windows Server 2003 x64, Windows NT® 4.0, NetWare 6.x, and UnixWare 7.x.

Transmit Balancing Method

Team properties 128