Users Guide
2–Configuring Teaming in Windows Server
Load Balancing and Fault Tolerance
11 BC0054508-00 M
Generic Trunking (FEC/GEC)/802.3ad-Draft Static
The Generic Trunking (FEC/GEC)/802.3ad-Draft Static type of team is very similar 
to the Link Aggregation (802.3ad) type of team in that all adapters in the team are 
configured to receive packets for the same MAC address. The Generic Trunking 
(FEC/GEC)/802.3ad-Draft Static) type of team, however, does not provide LACP 
or marker protocol support. This team type supports a variety of environments in 
which the adapter link partners are statically configured to support a proprietary 
trunking mechanism. For instance, this type of team could be used to support 
Lucent
®
 OpenTrunk™ or Cisco
®
 Fast EtherChannel (FEC). Basically, the Generic 
Trunking team type is a light version of the Link Aggregation (802.3ad) team type. 
This approach is much simpler because it does contain a formalized link 
aggregation control protocol (LACP). As with the other types of teams, the 
creation of teams and the allocation of physical adapters to various teams is done 
statically through user configuration software. 
The Generic Trunking (FEC/GEC/802.3ad-Draft Static) type of team supports load 
balancing and failover for both outbound and inbound traffic.
SLB (Auto-Fallback Disable)
The SLB (Auto-Fallback Disable) type of team is identical to the Smart Load 
Balancing and Failover type of team, with the following exception: When the 
standby member is active, if a primary member comes back on line, the team 
continues using the standby member, rather than switching back to the primary 
member.
All primary interfaces in a team participate in load-balancing operations by 
sending and receiving a portion of the total traffic. Standby interfaces take over in 
the event that all primary interfaces have lost their links.
Failover teaming provides redundant adapter operation (fault tolerance) in the 
event that a network connection fails. If the primary adapter in a team is 
disconnected because of failure of the adapter, cable, or switch port, the 
secondary team member becomes active, redirecting both inbound and outbound 
traffic originally assigned to the primary adapter. Sessions are maintained, 
causing no impact to the user.
NOTE
Generic Trunking (FEC/GEC/802.3ad Draft Static) team type is not 
supported for ports with NPAR mode or FCoE-Offload or iSCSI-Offload 
enabled.










