In the world of network engineering, redundancy and bandwidth are the two pillars of a stable infrastructure. EtherChannel (or Link Aggregation) is the technology that allows us to bundle multiple physical links into a single logical "pipe."
To manage these bundles, we use two primary negotiation protocols: PAgP and LACP. While they achieve similar results, choosing the wrong one can lead to failed links or vendor lock-in.
1. PAgP: The Cisco Original
Port Aggregation Protocol (PAgP) is a Cisco-proprietary protocol developed in the early 1990s. It was the standard for years before an open alternative existed.
- Vendor Support: Only works on Cisco switches (or a few licensed third-party vendors).
- Key Feature: It integrates deeply with Cisco's Spanning Tree Protocol (STP) to handle topology changes more efficiently.
- Maximum Links: Supports up to 8 active links in a bundle.
PAgP Negotiation Modes
| Mode | Action |
|---|---|
| Desirable | Actively asks the neighbor to form a bundle. |
| Auto | Passively waits for the neighbor to initiate the request. |
2. LACP: The Industry Standard
Link Aggregation Control Protocol (LACP) is defined by IEEE 802.3ad (now 802.1AX). It is the universal language of link aggregation used in modern data centers.
- Vendor Support: Open standard supported by almost every manufacturer, including Cisco, Juniper, and HP.
- Key Feature: Supports Cross-Stack EtherChannel, allowing you to terminate links on different physical switches within a stack for extreme redundancy.
- Maximum Links: Supports 16 links—8 active and 8 in "hot-standby" mode.
LACP Negotiation Modes
| Mode | Action |
|---|---|
| Active | Actively sends LACPDUs to negotiate a bundle. |
| Passive | Only responds to LACP requests; never initiates. |
3. Which Should You Choose?
| Feature | PAgP | LACP |
|---|---|---|
| Standard | Cisco Proprietary | IEEE 802.3ad (Open) |
| Compatibility | Cisco Only | Multi-vendor |
| Stacking | No Cross-Stack | Supports Cross-Stack |
| Modern Usage | Legacy/Specialized | Industry Default |
Use LACP for 99% of modern deployments. Its cross-vendor support and ability to form bundles across a switch stack make it more flexible and future-proof.
Use PAgP only if you are working in an older, purely Cisco-based environment where specific legacy features or stability with older Catalyst switches are required.
Troubleshooting Tip: The "Passive-Passive" Trap
A common mistake in both protocols is setting both ends to passive (Auto/Auto or Passive/Passive). In this state, both switches are waiting for a "hello" that never comes, and the EtherChannel will never form.
Rule of thumb: At least one side must be set to Active (LACP) or Desirable (PAgP).