Troubleshooting EtherChannel Issues

Scenario:

A network administrator configures EtherChannel between two Cisco switches using LACP, but the link is not forming, and some VLANs are not passing traffic.

Network Setup:


Step 1: Verify EtherChannel Status

Check the current EtherChannel summary on SW1

SW1# show etherchannel summary

Output:

Group  Port-channel  Protocol  Ports
------ ------------ -------- ------------------------
1 Po1(SD) LACP Gi0/1(P) Gi0/2(D)

๐Ÿšจ Problem Detected:


Step 2: Check Interface Configurations

Check Gi0/1 and Gi0/2 settings

SW1# show running-config interface Gi0/1
SW1# show running-config interface Gi0/2

Output (SW1):

interface GigabitEthernet0/1
switchport mode trunk
switchport trunk allowed vlan 10,20,30
channel-group 1 mode passive # LACP mode
!
interface GigabitEthernet0/2
switchport mode trunk
switchport trunk allowed vlan 10,20,30
channel-group 1 mode passive # LACP mode

Check the same on SW2

bashCopyEditSW2# show running-config interface Gi0/1
SW2# show running-config interface Gi0/2

Output (SW2):

interface GigabitEthernet0/1
switchport mode trunk
switchport trunk allowed vlan 10,20,30
channel-group 1 mode passive # LACP mode
!
interface GigabitEthernet0/2
switchport mode trunk
switchport trunk allowed vlan 10,20,30
channel-group 1 mode passive # LACP mode

๐Ÿšจ Problem Detected:

โœ… Fix: Change SW1 to “active”

SW1(config)# interface range Gi0/1 - 2
SW1(config-if-range)# channel-group 1 mode active
SW1(config-if-range)# exit

๐Ÿ‘‰ Expected Result: LACP will now negotiate the EtherChannel.


Step 3: Verify if the EtherChannel is Now Up

SW1# show etherchannel summary

Output (Expected):

cssCopyEditGroup  Port-channel  Protocol  Ports
------  ------------  --------  ------------------------
1      Po1(SU)       LACP      Gi0/1(P) Gi0/2(P)

โœ… “SU” (Layer 2, Up) means EtherChannel is working!
โœ… “P” (Port is active in EtherChannel) shows both interfaces are bundled.


Step 4: Verify VLANs on the Trunk

If VLAN traffic is still not passing, check allowed VLANs on the trunk:

SW1# show interfaces trunk

Output:

Port      Mode         Encapsulation  Status        Allowed VLANs
Po1 on 802.1q trunking 1,10,20,30

๐Ÿšจ Problem Detected:

โœ… Fix: Explicitly allow VLANs

SW1(config)# interface Port-channel 1
SW1(config-if)# switchport trunk allowed vlan 10,20,30
SW1(config-if)# exit

๐Ÿ‘‰ Now, only the necessary VLANs are allowed.


Step 5: Final Verification

Check VLANs Allowed on Trunk

SW1# show interfaces trunk

โœ… Expected Output:

Port      Mode         Encapsulation  Status        Allowed VLANs
Po1 on 802.1q trunking 10,20,30

Check Spanning Tree

# show spanning-tree active

โœ… Ensure Port-Channel 1 is forwarding traffic.


Summary of Troubleshooting Steps

IssueCauseSolution
EtherChannel is down (SD)Both sides set to passive in LACPChange one side to active.
One port is down (D)Speed/duplex mismatchSet speed/duplex manually.
VLAN traffic not passingVLANs not allowed on the trunkUse switchport trunk allowed vlan X.
STP blocking the EtherChannelSpanning Tree treating Port-Channel as a loopCheck show spanning-tree and adjust priority.

Best Practices for EtherChannel Configuration

โœ… Use LACP instead of PAgP (open standard, more stable).
โœ… Manually set trunk mode on Port-Channel interfaces (switchport mode trunk).
โœ… Ensure the same speed, duplex, and VLAN settings on both sides.
โœ… Check for STP blocking with show spanning-tree.
โœ… Use show etherchannel summary to monitor link status.


Conclusion

In this real-world case, the EtherChannel was down due to LACP passive mode on both switches. Changing one side to active resolved the issue. Additionally, VLAN traffic issues were fixed by explicitly allowing the required VLANs.

renjithbs Avatar

Posted by

Leave a comment