← Module 02 · Layer 2: Data Link

EtherChannel / Link Aggregation

Instead of one cable and a blocked backup, bundle several cables into one link that spanning tree treats as if it were only ever one.

The problem: STP has to block your extra bandwidth

Cable two switches together with two separate physical links and spanning tree sees exactly what the last two topics described: a loop. It picks one link to forward on and blocks the other outright, sitting idle unless the first one fails. You paid for double the bandwidth and STP (Spanning Tree Protocol) is only letting you use half of it.

EtherChannel (the generic term is link aggregation) solves this by bundling multiple physical links into a single logical link before STP ever sees them. Picture a toll plaza widened from one lane to four: instead of building a whole second redundant highway that traffic control has to keep closed, you widen the one road everyone already agrees is open.

SW1 SW2 One logical link: spanning tree sees this, not four separate ones A hash (source/destination MAC, IP, or port) decides which member link each flow rides on
Four physical links act as one EtherChannel. Lose one member and the bundle keeps running on the rest, no STP recalculation needed.

A single flow (say, one file transfer) still rides entirely on one member link. EtherChannel doesn't slice individual frames across cables. What it does is hash each flow, based on some combination of source/destination MAC (Media Access Control) address, IP (Internet Protocol) address, or port number depending on configuration, to consistently pick which member link that flow rides on. Different flows land on different links, and in aggregate, traffic spreads across the whole bundle.

PAgP vs. LACP

Two link members won't bundle themselves just because they're plugged in with matching config. A control protocol negotiates the bundle and continuously verifies every member is still healthy and consistently configured.

THE FAILURE MODE TO WATCH FOR

Member links need matching speed, duplex, and VLAN (Virtual Local Area Network) / trunk configuration. Mismatch one of them and instead of a clean error, the bundle can silently fail to form or drop into an inconsistent state (some links up, some in a non-bundled err state), which looks like a partial outage rather than an obvious misconfiguration.