Users Guide

12–Marvell Teaming Services
Teaming Mechanisms
Doc No. BC0054508-00 Rev. R
January 21, 2021 Page 164 Copyright © 2021 Marvell
Network Communications
The following are the key attributes of Generic Static Trunking:
 Failover mechanism—Link loss detection
 Load Balancing Algorithm—Outbound traffic is balanced through Marvell
proprietary mechanism-based Layer 4 flows. Inbound traffic is balanced
according to a switch specific mechanism.
 Outbound Load Balancing using MAC Address—No
 Outbound Load Balancing using IP Address—Yes
 Multivendor teaming—Supported (Must include at least one Marvell
Ethernet adapter as a team member)
Applications
Generic trunking works with switches that support Cisco Fast EtherChannel,
Cisco Gigabit EtherChannel, Extreme Networks Load Sharing and Bay Networks
or IEEE 802.3ad Link Aggregation static mode. Because load balancing is
implemented on Layer 2 addresses, all higher protocols such as IP, IPX, and
NetBEUI are supported. Therefore, this is the recommended teaming mode when
the switch supports generic trunking modes over SLB.
Configuration Recommendations
Static trunking supports connecting the teamed ports to switches if they are on the
same broadcast domain and support generic trunking. It does not support
connecting to a router or Layer 3 switches because the ports must be on the same
subnet.
Dynamic Trunking (IEEE 802.3ad Link Aggregation)
This mode supports link aggregation through static and dynamic configuration
through the link aggregation control protocol (LACP). With this mode, all adapters
in the team are configured to receive packets for the same MAC address. The
MAC address of the first adapter in the team is used and cannot be substituted for
a different MAC address. The QLASP driver determines the load-balancing
scheme for outbound packets, using Layer 4 protocols previously discussed,
whereas the team’s link partner determines the load-balancing scheme for
inbound packets. Because the load balancing is implemented on Layer 2, all
higher protocols such as IP, IPX, and NetBEUI are supported. The attached switch
must support the 802.3ad Link Aggregation standard for this mode of operation.
The switch manages the inbound traffic to the adapter while the QLASP manages
the outbound traffic. Both the QLASP and the switch continually monitor their
ports for link loss. In the event of link loss on any port, traffic is automatically
diverted to other ports in the team.