EtherChannel Essentials
EtherChannel – Basics
Purpose: Aggregates multiple physical links into a single logical link for better bandwidth and redundancy.
Modes:
PAgP (Cisco proprietary):
auto,desirablemodes.LACP (IEEE standard):
active,passivemodes.
Port-Channel Membership: Physical interfaces need to be configured identically.
Load Balancing: Distributes traffic across multiple links based on source/destination IP/ MAC or layer 3/4 information.
LACP vs PAgP – Comparison
| Feature | PAgP | LACP |
| Standard | Cisco proprietary | IEEE 802.3ad (open standard) |
| Modes | auto / desirable | active / passive |
| Support | Cisco-only devices | Multi-vendor, interoperable |
| Max Links | 8 active links (no standby) | 8 active + 8 standby |
| Preferred | Cisco-only legacy environments | Preferred for modern multi-vendor setups |
LACP Negotiation
Active Mode: Initiates negotiation to form an aggregation.
Passive Mode: Waits for negotiation from active mode.
Packet Flow: LACPDU frames exchanged to agree on aggregation.
Port-Channel Configuration Best Practices
Consistency: Configure physical interfaces identically (speed, duplex, encapsulation).
Error Handling: Ensure matching configurations on both ends.
LACP: Preferred over PAgP due to its standards-based nature.
Load Balancing: Implement source-based for better bandwidth utilization.
Link Aggregation Control Protocol (LACP)
Modes:
Active: Actively attempts to form a link aggregation.
Passive: Waits for the active mode to initiate.
Failover Handling: Detects and reconfigures after link failure.
Negotiation Process: Initiator (active) and responder (passive) exchange LACPDU to form the link aggregation.
LACPDU Packet Flow – Negotiation Sequence
Scenario: Switch A (active) ↔ Switch B (passive)
Switch A (Active):
Sends out LACPDU every second to initiate link aggregation.Switch B (Passive):
Receives LACPDU, responds back with its own LACPDU agreeing to form an EtherChannel.Exchange Info Includes:
System Priority
System ID (MAC address)
Port Priority
Port Number
Aggregation Key (common across member ports)
Actor/Partner State (active/passive, collecting/distributing)
Link Establishment:
Once both sides agree and configs match, they form a LAG (Link Aggregation Group) and move traffic.
⚖️ Load Balancing in EtherChannel – Use Cases
Cisco switches use various hashing algorithms for distributing traffic:
| Load-Balancing Method | When to Use |
| src-mac | Useful when most traffic is from many sources (e.g., clients to server). |
| dst-mac | Good when traffic is toward multiple destinations (e.g., servers or printers). |
| src-dst-mac | Balances on the combination of source and destination MACs – more uniform hashing. |
| src-ip | Ideal in routed networks with many client subnets. |
| dst-ip | If targeting multiple IP destinations, such as web farms. |
| src-dst-ip | Best in complex routed environments, for more uniform distribution. |
| layer4 (TCP/UDP ports) | Use when you want per-session flow distribution (e.g., data center east-west traffic). |
Key Takeaways:
VTP: Use transparent mode for most environments. Server mode if VLAN sync is needed across switches.
EtherChannel: Preferred for load balancing, fault tolerance, and increased bandwidth.
LACP: Best for multi-vendor environments, resilience, and standards compliance.