4.3.7Selecting a Team Type
The following flow chart provides the decision flow when planning for Layer 2 teaming. The primary rationale for teaming is the need for additional network bandwidth and fault tolerance. Teaming offers link aggregation and fault tolerance to meet both of these requirements. Preference teaming should be selected in the following order: IEEE 802.3ad as the first choice, Generic Trunking as the second choice, and SLB teaming as the third choice when using unmanaged switches or switches that do not support the first two options. if switch fault tolerance is a requirement, however, then SLB is the only choice (refer to "• Process for Selecting a Team Type" (Jpg.129)).
• Process for Selecting a Team Type
| Do you need additional | No |
| network bandwidth or fault |
|
|
| |
| tolerance? |
|
| Yes |
|
Yes | Do you need switch |
|
| fault tolerance? |
|
No
Are you using a | Yes | |
switch that supports IEEE | ||
| ||
802.3ad LACP? |
| |
No |
| |
| ||
Are you using a |
| |
Yes | ||
switch that supports Static |
| |
| ||
Trunking (FEC/GEC?) |
| |
|
|
No Teaming
Set up a Dynamic Trunking Team
Set up a Generic Trunking Team
No
Set up an SLB
Team
E