Cisco Systems 5709 用户手册
User Guide
NetXtreme II
January 2010
Bro a d c o m Co rp o r a ti o n
Document
ENGSRVT52-CDUM100-R
Teaming Mechanisms
Page 33
Dynamic Trunking (IEEE 802.3ad Link Aggregation)
This mode supports link aggregation through static and dynamic configuration via 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 BASP 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 BASP
manages the outbound traffic. Both the BASP 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.
(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 BASP 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 BASP
manages the outbound traffic. Both the BASP 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.
Network Communications
The following are the key attributes of Dynamic Trunking:
•
Failover mechanism – Link loss detection
•
Load Balancing Algorithm – Outbound traffic is balanced through a Broadcom proprietary mechanism based on L4
flows. Inbound traffic is balanced according to a switch specific mechanism.
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 Broadcom Ethernet adapter as a team member)
Applications
Dynamic trunking works with switches that support IEEE 802.3ad Link Aggregation dynamic mode using LACP. Inbound
load balancing is switch dependent. In general, the switch traffic is load balanced based on L2 addresses. In this case, all
network protocols such as IP, IPX, and NetBEUI are load balanced. Therefore, this is the recommended teaming mode when
the switch supports LACP, except when switch fault tolerance is required. SLB is the only teaming mode that supports switch
fault tolerance.
load balancing is switch dependent. In general, the switch traffic is load balanced based on L2 addresses. In this case, all
network protocols such as IP, IPX, and NetBEUI are load balanced. Therefore, this is the recommended teaming mode when
the switch supports LACP, except when switch fault tolerance is required. SLB is the only teaming mode that supports switch
fault tolerance.
Configuration Recommendations
Dynamic trunking supports connecting the teamed ports to switches as long as they are on the same broadcast domain and
supports IEEE 802.3ad LACP trunking. It does not support connecting to a router or Layer 3 switches since the ports must
be on the same subnet.
supports IEEE 802.3ad LACP trunking. It does not support connecting to a router or Layer 3 switches since the ports must
be on the same subnet.
LiveLink™
LiveLink™ is a feature of BASP that is available for the Smart Load Balancing (SLB) and SLB (Auto-Fallback Disable) type
of teaming. The purpose of LiveLink is to detect link loss beyond the switch and to route traffic only through team members
that have a live link. This function is accomplished though the teaming software. The teaming software periodically probes
(issues a link packet from each team member) one or more specified target network device(s). The probe target(s) responds
when it receives the link packet. If a team member does not detect the response within a specified amount of time, this
indicates that the link has been lost, and the teaming software discontinues passing traffic through that team member. Later,
if that team member begins to detect a response from a probe target, this indicates that the link has been restored, and the
teaming software automatically resumes passing traffic through that team member. LiveLink works only with TCP/IP.
of teaming. The purpose of LiveLink is to detect link loss beyond the switch and to route traffic only through team members
that have a live link. This function is accomplished though the teaming software. The teaming software periodically probes
(issues a link packet from each team member) one or more specified target network device(s). The probe target(s) responds
when it receives the link packet. If a team member does not detect the response within a specified amount of time, this
indicates that the link has been lost, and the teaming software discontinues passing traffic through that team member. Later,
if that team member begins to detect a response from a probe target, this indicates that the link has been restored, and the
teaming software automatically resumes passing traffic through that team member. LiveLink works only with TCP/IP.
LiveLink™ functionality is supported in both 32-bit and 64-bit Windows operating systems. For similar functionality in Linux
operating systems, see the Channel Bonding information in your Red Hat documentation.
operating systems, see the Channel Bonding information in your Red Hat documentation.