Instruction Manual
16
NOTES:
• Be sure to use the latest available drivers.
• Hot Plug operations for an adapter that is part of a team are only available in
Windows Server.
• For SLA teams, all team members must be connected to the same switch. For
AFT, ALB, and RLB teams, all team members must belong to the same subnet. The
members of an SFT team must be connected to a different switch.
• Teaming only one adapter port is possible, but provides no benefit.
• NDIS 6.2 introduced new RSS data structures and interfaces. Because of this, you
cannot enable RSS on teams that contain a mix of adapters that support NDIS 6.2
RSS and adapters that do not.
• If a team is bound to a Hyper-V virtual NIC, you cannot change the Primary or
Secondary adapter.
• Intel adapters that do not support Intel PROSet may still be included in a team.
However, they are restricted in the same way non-Intel adapters are. See
Multi-
Vendor Teaming
below for more information.
• To assure a common feature set, some advanced features, including hardware
offloading, are automatically disabled when an adapter that does not support Intel
PROSet is added to a team.
• Hot Plug operations in a Multi-Vendor Team may cause system instability. We
recommended that you restart the system or reload the team after performing Hot
Plug operations with a Multi-Vendor Team.
• Spanning tree protocol (STP) should be disabled on switch ports connected to
teamed adapters in order to prevent data loss when the primary adapter is returned
to service (failback). Alternatively, an activation delay may be configured on the
adapters to prevent data loss when spanning tree is used. Set the Activation Delay
on the advanced tab of team properties.
• ANS teaming of Virtual Function devices inside a Windows 2008 R2 guest running
on an open source hypervisor is supported.
• Fiber Channel over Ethernet/Data Center Bridging will be automatically disabled
when an adapter is added to a team with non-FCoE/DCB capable adapters.
