Outbound Traffic Distribution Across Trunked Links - ProCurve 2626 Management And Configuration Manual

Switch 2600 series switch 2600-pwr series switch 2800 series switch 4100 series switch 6108
Hide thumbs Also See for 2626:
Table of Contents

Advertisement

Port Trunking
Port Status and Configuration
12-26
Interface Option
Menu Interface
CLI:
show trunk
show interfaces
show lacp
show spanning-tree
show igmp
show config

Outbound Traffic Distribution Across Trunked Links

Both trunk group options (LACP and Trunk) use source-destination address
pairs (SA/DA) for distributing outbound traffic over trunked links.
SA/DA (source address/destination address) causes the switch to distribute
outbound traffic to the links within the trunk group on the basis of source/
destination address pairs. That is, the switch sends traffic from the same
source address to the same destination address through the same trunked link,
and sends traffic from the same source address to a different destination
address through a different link, depending on the rotation of path assign­
ments among the links in the trunk. Likewise, the switch distributes traffic for
the same destination address but from different source addresses through
different links. Because the amount of traffic coming from or going to various
nodes in a network can vary widely, it is possible for one link in a trunk group
to be fully utilized while others in the same trunk have unused bandwidth
capacity even though the address assignments are evenly distributed across
the links in a trunk. In actual networking environments, this is rarely a
problem. However, if it becomes a problem, you can use the ProCurve Man­
ager Plus network management software to quickly and easily identify the
sources of heavy traffic (top talkers) and make adjustments to improve
performance.
Broadcasts, multicasts, and floods from different source addresses are dis­
tributed evenly across the links. As links are added or deleted, the switch
redistributes traffic across the trunk group. For example, in figure 12-12
showing a three-port trunk, traffic could be assigned as shown in table 12-6.
Dynamic LACP
Static LACP
Trunk Group
Trunk Group
No
Yes
No
Yes
No
Yes
Yes
Yes
No
Yes
No
Yes
No
Yes
Static Non-Protocol
Trunk Group
Yes
Yes
Yes
No
Yes
Yes
Yes

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents