Domain 2Network AccessCORE

EtherChannel and Link Aggregation

Configuring and verifying EtherChannel for link aggregation using LACP and PAgP, including load balancing and troubleshooting.

Domain: Domain 2: Network Access•Updated: 2026-08-26
#EtherChannel#LACP#PAgP#Load Balancing#Link Aggregation

EtherChannel (Port Channel / LAG)

Overview & Purpose

  • Concept: EtherChannel groups multiple physical interfaces into a single logical interface, allowing them to behave as one. Also known as a Port Channel or LAG (Link Aggregation Group).
  • Problem Solved: Without EtherChannel, Spanning Tree Protocol (STP) will block redundant links between switches to prevent Layer 2 loops, wasting bandwidth. EtherChannel bundles these links, so STP treats the entire bundle as a single logical link. This provides both increased bandwidth and redundancy without causing broadcast storms.
  • Capacity: Up to 8 physical interfaces can be active in a single EtherChannel. (LACP supports up to 16, with 8 active and 8 in standby).
graph TD
    subgraph Without EtherChannel
        SW1_A[ASW1] -- Link 1 (Forwarding) --> SW2_A[DSW1]
        SW1_A -- Link 2 (Blocked by STP) --> SW2_A
        SW1_A -- Link 3 (Blocked by STP) --> SW2_A
    end
    subgraph With EtherChannel
        SW1_B[ASW1] == "Port-Channel 1 (4x Bandwidth, Forwarding)" ==> SW2_B[DSW1]
    end

Load Balancing

  • Concept: Traffic is load-balanced across the physical member interfaces based on flows (a communication session between two nodes), not per-packet. This prevents frames from arriving out of order, which can disrupt applications.
  • Details: The switch uses a hash algorithm to determine which physical interface a flow will use. All frames in the same flow use the same physical interface.
  • Hash Inputs (varies by switch model):
    • Source MAC address
    • Destination MAC address
    • Source AND Destination MAC addresses
    • Source IP address
    • Destination IP address
    • Source AND Destination IP addresses
    • Layer 4 TCP/UDP port numbers (on supported models)
  • Things to note: Non-IP traffic defaults to using Source and Destination MAC addresses for the hash calculation, as no IP addresses are present.
Switch# show etherchannel load-balance
Switch(config)# port-channel load-balance src-dst-mac

Things to note: Cisco uses inconsistent keywords here. You view the setting with show etherchannel load-balance, but you configure it with port-channel load-balance.

Configuration Methods

There are three methods to configure EtherChannel. The configuration is applied to the physical member interfaces using the interface range command to ensure consistency.

Protocol Standard Modes Behavior
PAgP (Port Aggregation Protocol) Cisco Proprietary desirable, auto desirable actively negotiates. auto only responds to desirable.
LACP (Link Aggregation Control Protocol) IEEE 802.3ad (Industry Standard) active, passive active actively negotiates. passive only responds to active.
Static (Manual) None on Forces the channel without negotiation.

Valid Mode Combinations

  • on ↔ on (Static)
  • desirable ↔ desirable or auto (PAgP)
  • active ↔ active or passive (LACP)
  • Invalid: auto ↔ auto, passive ↔ passive, or mixing protocols (e.g., desirable ↔ active).
! PAgP Configuration Example
Switch(config)# interface range gigabitethernet 0/1 - 4
Switch(config-if-range)# channel-group 1 mode desirable

! LACP Configuration Example (Preferred for CCNA)
Switch(config)# interface range gigabitethernet 0/1 - 4
Switch(config-if-range)# channel-group 1 mode active

! Static Configuration Example
Switch(config)# interface range gigabitethernet 0/1 - 4
Switch(config-if-range)# channel-group 1 mode on

Things to note: The channel-group number (e.g., 1) is locally significant. It identifies the virtual interface on the local switch. It does not need to match the channel-group number on the neighboring switch (e.g., Group 1 on SW1 can connect to Group 2 on SW2).

Configuration Rules & Requirements

  • Concept: All physical member interfaces in an EtherChannel must have identical configurations.
  • Details: Mismatched parameters will cause the specific interface to be suspended (excluded from the bundle). Matching requirements include:
    • Speed and Duplex settings
    • Switchport mode (Access or Trunk)
    • Allowed VLANs (if trunking)
    • Native VLAN (if trunking)
    • STP settings

Verification Commands

Switch# show etherchannel summary
Switch# show etherchannel port-channel
Switch# show interfaces trunk

show etherchannel summary Flags

Flag Meaning Context
S Layer 2 EtherChannel (Switchport) Next to Port-Channel interface
R Layer 3 EtherChannel (Routed port) Next to Port-Channel interface
U In Use (Active and operational) Next to Port-Channel interface
P Bundled in Port-Channel Next to physical member interfaces (Desired state)
D Down Interface or Port-Channel is administratively down
s Suspended Interface excluded due to configuration mismatch

Things to note: show etherchannel port-channel provides detailed info, including the negotiated channel-group mode (e.g., active, desirable), which is not shown in the summary output. STP commands (like show spanning-tree) will only display the Port-Channel interface, not the individual physical links.

Layer 3 EtherChannel

  • Concept: Used in modern network designs (e.g., between distribution and core switches) to eliminate STP entirely by using routed ports instead of switchports.
  • Details: Physical interfaces are converted to Layer 3 before being added to the channel group. The IP address is assigned to the logical port-channel interface, not the physical interfaces.
Switch(config)# interface range gigabitethernet 0/1 - 4
Switch(config-if-range)# no switchport
Switch(config-if-range)# channel-group 1 mode active
Switch(config-if-range)# exit

Switch(config)# interface port-channel 1
Switch(config-if)# no switchport
Switch(config-if)# ip address 10.0.0.1 255.255.255.252

Things to note: When you apply no switchport to the member interfaces and add them to the channel group, the resulting port-channel interface automatically inherits the no switchport state.

Troubleshooting & Exam Insights

  • Protocol Mismatch: If you manually set the negotiation protocol using channel-protocol, the channel-group mode must match that protocol.
    • Example: If channel-protocol lacp is configured, channel-group 1 mode on will be rejected. You must use mode active or mode passive.
  • Boson ExSim Scenario: Creating the interface port-channel 1 manually before using channel-group is valid but unnecessary; the channel-group command auto-creates it. However, if channel-protocol is explicitly set, incompatible mode commands will fail.

Command Summary

! View current load-balancing method
Switch# show etherchannel load-balance

! Configure load-balancing method (e.g., src-dst-mac, src-dst-ip)
Switch(config)# port-channel load-balance src-dst-mac

! Configure physical interfaces for EtherChannel (PAgP, LACP, or Static)
Switch(config)# interface range gigabitethernet 0/1 - 4
Switch(config-if-range)# channel-group 1 mode {desirable | auto | active | passive | on}

! (Optional) Manually set the negotiation protocol
Switch(config-if-range)# channel-protocol {lacp | pagp}

! Configure Layer 3 EtherChannel
Switch(config-if-range)# no switchport
Switch(config)# interface port-channel 1
Switch(config-if)# no switchport
Switch(config-if)# ip address <ip> <mask>

! Verify EtherChannel status and flags
Switch# show etherchannel summary

! Verify detailed Port-Channel info (including mode)
Switch# show etherchannel port-channel