##  [Link Aggregation](/link-aggregation-0) 

 Definition

Combining two or more physical or logical data links between network devices into a single logical interface that presents aggregated capacity, distributes frames according to a selectable balancing policy, and provides link-level redundancy while preserving end-to-end addressing and forwarding semantics.

 

 

 

 

 

 





## Principle

Principle

Treat the aggregated member links as a single logical data-path: total usable capacity and fault tolerance scale with active members, but per-flow throughput and frame ordering depend on the chosen distribution (hashing) policy and on which member carries each frame.

 

 

 

 

 





## Demonstration

Demonstration

Illustrative scenario → Recognition → Action → Consequence: Two switches connect with two 1 Gbps ports and configure a single aggregated interface. The administrator recognizes the goal (increase capacity and resilience), enables aggregation with a flow-hash policy, and transmits traffic. Result: aggregate capacity approaches 2 Gbps for multiple concurrent flows and one port failure leaves the logical interface up at reduced capacity; a single large TCP flow may remain limited to 1 Gbps because hashing pins that flow to one member.

 

 

 

 

## Misapplication

Misapplication

Mistaken interpretation: assuming every individual flow is split across member links to multiply a single flow's throughput. Why plausible: 'aggregate' suggests summation. Semantic error: conflating aggregate capacity across flows with per-flow channel bonding. Correct interpretation: per-flow forwarding is subject to the hashing/balancing rule; a single flow often does not exceed one member's capacity.

 

 

 

 

 





## Consequence

Consequence

When correctly applied, link aggregation increases aggregate throughput for multiple flows and delivers transparent link redundancy; when misconfigured or misunderstood it can leave single flows bottlenecked, cause asymmetric paths, or—if members are on different devices without multi-chassis support—create forwarding loops or blackholes.

 

 

 

 

## Reversal

Reversal

Aggregation requires that member links share forwarding context and compatible capabilities. Where member links terminate on different independent devices without coordinated aggregation support, the logical single-interface semantics break and the principle of capacity aggregation and transparent redundancy does not hold.

 

 

 

 

 





## Boundary

Boundary

Clearly within: multiple parallel Ethernet (or similar) links between the same pair of devices combined into one logical link. Boundary case: links terminating on separate chassis with special multi-chassis support (requires additional coordination). Clearly outside: routing-based multipath (e.g., per-packet routing across distinct IP paths) or transport-layer multipath mechanisms that operate above link layer.

 

 

 

 

 





## Semantic Tension

Semantic Tension

Throughput aggregation ↔ Per-flow consistency: maximizing summed capacity conflicts with preserving per-flow ordering and predictable per-flow throughput. Aggregation design balances total capacity against predictable single-flow performance.

 

 

 

 

 





## Synthesis

Synthesis

Link aggregation is a link-layer multiplexing that merges physical resources for aggregate capacity and redundancy while retaining single-interface semantics; understanding its limits requires distinguishing aggregate capacity from per-flow behavior and ensuring compatible termination and configuration.