Users Guide

11–Marvell Teaming Services
Executive Summary
158 BC0054508-00 M
Selecting 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:
 First choice: Link Aggregation
 Second choice: Generic Trunking
 Third choice: SLB, when using unmanaged switches or switches that do not
support the first two choices. If switch fault tolerance is a requirement, either
SLB or in-OS switch independent NIC teaming is the only choice.
Load balancing by IP
address
No Yes Yes Yes
Load balancing by
MAC address
No Yes (used for
no-IP/IPX)
Yes Yes
a
SLB with one primary and one standby member.
b
Requires at least one Marvell adapter in the team.
Table 11-4. Comparison of Team Types (Continued)
Type of Team
Fault
Tolerance
Load
Balancing
Switch-Dependent
Static Trunking
Switch-Independent
Dynamic Link
Aggregation
(IEEE 802.3ad)
Function
SLB with
Standby
a
SLB Generic Trunking Link Aggregation