EtherChannel Basics and Configuration on Cisco Devices
Published by THE NETWORK DNA | Network Engineering | Cisco CCNA / CCNP
What is EtherChannel?
EtherChannel is a powerful link aggregation technology used in Cisco network devices that allows multiple physical Ethernet links to be bundled together into a single logical link. This technology increases bandwidth, provides redundancy, and improves network performance — all while appearing as a single interface to the Spanning Tree Protocol (STP).
Whether you are preparing for your Cisco CCNA, CCNP, or working as a network engineer, understanding EtherChannel is a fundamental skill for building resilient and high-performance networks.
Key Benefit: EtherChannel can bundle up to 8 active physical links into one logical link, multiplying bandwidth up to 8x without STP blocking any of them.
Why Use EtherChannel? Key Benefits
| Feature | Benefit |
|---|---|
| Bandwidth Aggregation | Combines multiple links to increase total throughput |
| Redundancy and Failover | If one link fails, traffic is redistributed to remaining links |
| STP Compatibility | STP sees one logical link — no ports are blocked unnecessarily |
| Load Balancing | Traffic is distributed across all member links automatically |
| Cost Effective | Maximize existing infrastructure without buying faster hardware |
EtherChannel Protocols: LACP vs PAgP vs Static
Cisco supports three EtherChannel negotiation modes. Understanding the difference between LACP, PAgP, and Static (ON) is critical for both real-world deployments and Cisco certification exams.
1. LACP — Link Aggregation Control Protocol (IEEE 802.3ad)
LACP is an open IEEE standard protocol supported by multi-vendor devices. It dynamically negotiates the EtherChannel between two devices and is the recommended method in modern networks.
| Mode | Description | Forms EtherChannel? |
|---|---|---|
| active | Actively sends LACP packets | Yes (with active or passive) |
| passive | Waits for LACP packets | Yes (only with active) |
2. PAgP — Port Aggregation Protocol (Cisco Proprietary)
PAgP is a Cisco proprietary protocol. It only works between Cisco-to-Cisco devices and dynamically negotiates EtherChannel formation.
| Mode | Description | Forms EtherChannel? |
|---|---|---|
| desirable | Actively initiates PAgP negotiation | Yes (with desirable or auto) |
| auto | Passively waits for PAgP packets | Yes (only with desirable) |
3. Static EtherChannel (Mode: ON)
Using mode ON forces the interface into an EtherChannel without any negotiation. Both sides must be configured as ON. No LACP or PAgP packets are exchanged.
Warning: If one side is ON and the other is not, the EtherChannel will NOT form, and you may cause network loops.
Mode Compatibility Quick Reference
| Switch A Mode | Switch B Mode | Protocol | EtherChannel Formed? |
|---|---|---|---|
| active | active | LACP | Yes |
| active | passive | LACP | Yes |
| passive | passive | LACP | No |
| desirable | desirable | PAgP | Yes |
| desirable | auto | PAgP | Yes |
| auto | auto | PAgP | No |
| on | on | None (Static) | Yes |
EtherChannel Requirements and Rules
Before configuring EtherChannel on Cisco switches, the following conditions must match on all member ports:
- Same speed and duplex settings
- Same VLAN assignment (for access ports) or same allowed VLANs (for trunk ports)
- Same switchport mode (all access or all trunk)
- Same native VLAN on trunk ports
- Same STP settings per port
- Up to 8 active ports per EtherChannel (16 can be configured with LACP standby)
- All ports must be on the same switch or switch stack
Important: Mismatched configuration on any parameter will prevent the EtherChannel from forming and may cause interfaces to suspend or error-disable.
Step-by-Step EtherChannel Configuration on Cisco Switches
Below are the most common EtherChannel configuration scenarios you will encounter in production networks and Cisco certification labs.
Scenario 1: LACP EtherChannel (Recommended)
Configure EtherChannel between SW1 and SW2 using LACP with interfaces Gi0/1 and Gi0/2 bundled into Port-Channel 1.
SW1 Configuration:
SW1# configure terminal
SW1(config)# interface range GigabitEthernet0/1 - 2
SW1(config-if-range)# switchport mode trunk
SW1(config-if-range)# switchport trunk encapsulation dot1q
SW1(config-if-range)# channel-protocol lacp
SW1(config-if-range)# channel-group 1 mode active
SW1(config-if-range)# no shutdown
SW1(config-if-range)# exit
SW1(config)# interface Port-channel 1
SW1(config-if)# switchport mode trunk
SW1(config-if)# switchport trunk encapsulation dot1q
SW1(config-if)# end
SW2 Configuration:
SW2# configure terminal
SW2(config)# interface range GigabitEthernet0/1 - 2
SW2(config-if-range)# switchport mode trunk
SW2(config-if-range)# switchport trunk encapsulation dot1q
SW2(config-if-range)# channel-protocol lacp
SW2(config-if-range)# channel-group 1 mode passive
SW2(config-if-range)# no shutdown
SW2(config-if-range)# exit
SW2(config)# interface Port-channel 1
SW2(config-if)# switchport mode trunk
SW2(config-if)# switchport trunk encapsulation dot1q
SW2(config-if)# end
Scenario 2: PAgP EtherChannel (Cisco-to-Cisco)
Configure EtherChannel using PAgP with Gi0/3 and Gi0/4 bundled into Port-Channel 2 in access mode for VLAN 10.
SW1 Configuration:
SW1# configure terminal
SW1(config)# interface range GigabitEthernet0/3 - 4
SW1(config-if-range)# switchport mode access
SW1(config-if-range)# switchport access vlan 10
SW1(config-if-range)# channel-protocol pagp
SW1(config-if-range)# channel-group 2 mode desirable
SW1(config-if-range)# no shutdown
SW1(config-if-range)# end
SW2 Configuration:
SW2# configure terminal
SW2(config)# interface range GigabitEthernet0/3 - 4
SW2(config-if-range)# switchport mode access
SW2(config-if-range)# switchport access vlan 10
SW2(config-if-range)# channel-protocol pagp
SW2(config-if-range)# channel-group 2 mode auto
SW2(config-if-range)# no shutdown
SW2(config-if-range)# end
Scenario 3: Static EtherChannel (Mode ON)
Configure a static EtherChannel using mode ON with no negotiation protocol required.
SW1(config)# interface range GigabitEthernet0/5 - 6
SW1(config-if-range)# switchport mode trunk
SW1(config-if-range)# channel-group 3 mode on
SW1(config-if-range)# no shutdown
SW1(config-if-range)# end
! Repeat identical config on SW2 with mode on
EtherChannel Load Balancing Configuration
Cisco switches use a load balancing algorithm to distribute traffic across EtherChannel member links. You can configure it globally using the command below:
Switch(config)# port-channel load-balance ?
dst-ip Destination IP address
dst-mac Destination MAC address
src-dst-ip Source XOR Destination IP
src-dst-mac Source XOR Destination MAC
src-ip Source IP address
src-mac Source MAC address
! Example: Use source-destination IP for best distribution
Switch(config)# port-channel load-balance src-dst-ip
| Load Balance Method | Best Used When |
|---|---|
| src-mac | Many different source devices (default on some platforms) |
| dst-mac | Traffic to many different destinations |
| src-dst-ip | Best overall distribution for routed networks |
| src-dst-mac | Best for Layer 2 switched environments |
Verifying EtherChannel — Show Commands
After configuration, always verify the EtherChannel status using these essential Cisco show commands:
1. show etherchannel summary
SW1# show etherchannel summary
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use N - not in use, no aggregation
Number of channel-groups in use: 1
Number of aggregators: 1
Group Port-channel Protocol Ports
------+-------------+-----------+---------------------------
1 Po1(SU) LACP Gi0/1(P) Gi0/2(P)
Tip: Look for SU on the Port-channel (S=Layer2, U=in use) and P on member ports (P=Bundled). This confirms EtherChannel is active!
2. show etherchannel detail
SW1# show etherchannel detail
! Shows detailed info about each channel-group,
! including member interfaces, protocol, flags, and port states
3. show interfaces port-channel 1
SW1# show interfaces port-channel 1
Port-channel1 is up, line protocol is up (connected)
Hardware is EtherChannel, address is 0c27.24b4.0101
MTU 1500 bytes, BW 2000000 Kbit/sec, DLY 10 usec
Members in this channel: Gi0/1 Gi0/2
4. show etherchannel port-channel
SW1# show etherchannel port-channel
! Shows port-channel status, load-balance method,
! protocol used, and all member port details
5. show lacp neighbor (LACP specific)
SW1# show lacp neighbor
! Shows LACP neighbor device information including
! system ID, port priority, and port state
EtherChannel Troubleshooting Guide
When EtherChannel fails to form or ports go into a suspended state, use this systematic troubleshooting approach:
| Problem | Likely Cause | Fix |
|---|---|---|
| Port shows as (I) stand-alone | Incompatible modes or no partner | Match modes — use active/passive or desirable/auto |
| Port shows as (s) suspended | Config mismatch on duplex, VLAN, or speed | Ensure all parameters match on all member ports |
| EtherChannel not forming at all | Wrong protocol or mismatched channel-group | Use same channel-group number and protocol on both switches |
| Spanning Tree problems after config | One side ON, other side using LACP or PAgP | Never mix ON with dynamic modes |
| Low bandwidth even with EtherChannel | Poor load balancing method configured | Change to src-dst-ip for better distribution |
Pro Tip: Always configure the EtherChannel settings on the Port-channel interface itself as well as on the member interfaces. Changes to physical interfaces will sync to the Port-channel automatically.
Layer 3 EtherChannel Configuration (Routed Port)
EtherChannel can also operate at Layer 3 as a routed port, typically used between multilayer switches and routers. This is common in campus network core and distribution layer designs.
! Configure Layer 3 EtherChannel on a Multilayer Switch
SW1(config)# interface range GigabitEthernet0/1 - 2
SW1(config-if-range)# no switchport
SW1(config-if-range)# channel-group 1 mode active
SW1(config-if-range)# no shutdown
SW1(config-if-range)# exit
SW1(config)# interface port-channel 1
SW1(config-if)# no switchport
SW1(config-if)# ip address 192.168.1.1 255.255.255.0
SW1(config-if)# no shutdown
SW1(config-if)# end
EtherChannel vs Traditional Redundant Links
| Criteria | EtherChannel | Traditional STP Redundancy |
|---|---|---|
| Bandwidth Usage | All links active | Redundant links blocked |
| Failover Time | Milliseconds | 30 to 50 seconds (classic STP) |
| STP Complexity | One logical link, simpler STP | Complex STP topology |
| Scalability | Up to 8 active links | One active link only |
| Load Balancing | Built-in | None |
EtherChannel Best Practices
- Always use LACP (active/active or active/passive) in modern networks for best interoperability
- Avoid mode ON unless specifically required — it provides no error detection
- Configure all member interfaces identically before assigning them to a channel-group
- Use src-dst-ip load balancing for the best traffic distribution in routed networks
- Always configure the Port-channel interface with trunk or access settings, not just member ports
- Document your EtherChannel groups with interface descriptions
- Monitor EtherChannel health with show etherchannel summary regularly
- Consider using LACP fast timers for quicker failure detection on critical links
Frequently Asked Questions — EtherChannel
Q: How many links can I bundle in an EtherChannel?
A: Cisco supports up to 8 active links per EtherChannel. With LACP, you can configure up to 16 links — 8 active and 8 in hot-standby mode.
Q: Does EtherChannel require the same speed on all links?
A: Yes. All member interfaces must operate at the same speed and duplex settings. Mismatched speeds will prevent the EtherChannel from forming.
Q: Can EtherChannel work across different switches?
A: Traditional EtherChannel works between two switches. Technologies like Multi-chassis EtherChannel (MEC) with VSS or vPC (on Nexus) allow EtherChannel across physically separate chassis.
Q: What is the difference between LACP and PAgP?
A: LACP (IEEE 802.3ad) is an open standard that works with any vendor. PAgP is Cisco proprietary and only works between Cisco devices. LACP is preferred in modern networks.
Q: Does EtherChannel increase bandwidth to exactly 2x or 4x?
A: EtherChannel increases aggregate bandwidth, but a single traffic flow (same source-destination pair) is typically limited to one physical link due to the hashing algorithm. Overall throughput increases for multiple concurrent flows.
Summary — EtherChannel Quick Reference
EtherChannel Cheat Sheet
- LACP Modes: active + active = Yes | active + passive = Yes | passive + passive = No
- PAgP Modes: desirable + desirable = Yes | desirable + auto = Yes | auto + auto = No
- Static Mode: on + on = Yes | on + active or passive = No
- Max Active Links: 8 active (LACP supports 8 standby = 16 total configured)
- Key Command: channel-group [number] mode [active | passive | desirable | auto | on]
- Verify: show etherchannel summary
- Load Balance: port-channel load-balance src-dst-ip
- STP View: Entire EtherChannel appears as 1 logical link to STP
Conclusion
EtherChannel is one of the most valuable technologies in Cisco network design. It provides bandwidth aggregation, fast failover, and simplified STP topology — all from existing hardware. Whether you are configuring it in a CCNA lab, a CCNP enterprise network, or a production data center, mastering EtherChannel is essential.
Remember to use LACP for maximum flexibility, ensure all member interfaces have identical configurations, and always verify with show etherchannel summary after deployment.
Found this article helpful?
Share it with your networking community and leave a comment below with your EtherChannel questions or experiences!
Tags and Keywords: EtherChannel, Cisco EtherChannel, LACP Configuration, PAgP Configuration, Link Aggregation Cisco, Port-Channel Cisco, EtherChannel CCNA, EtherChannel CCNP, Cisco Switch Configuration, Network Redundancy, Bandwidth Aggregation, 802.3ad LACP, Cisco Networking, Switch Trunk EtherChannel, EtherChannel Troubleshooting, show etherchannel summary, Cisco IOS Commands, Layer 2 EtherChannel, Layer 3 EtherChannel, EtherChannel Load Balancing
