Cisco Packet Tracer Lab Guide for EtherChannel

EtherChannel is a technology used to combine multiple physical Ethernet links into a single logical link to increase bandwidth and provide redundancy. It’s commonly used in switches to prevent link failures from disrupting network traffic and to provide load balancing.

This lab guide will help us set up and configure EtherChannel using Cisco Packet Tracer for CCNA 200–301 preparation.

Lab Objectives

1. Configure EtherChannel between two switches (using LACP and PAgP).
2. Verify EtherChannel status.
3. Understand and configure different EtherChannel modes.
4. Troubleshoot EtherChannel misconfigurations.

Lab Setup

We will use two switches (Switch1 and Switch2) connected by multiple Ethernet links to create an EtherChannel between them.

Photo by Brian Botos on Unsplash

Network Topology

— Devices: 2 Switches (Cisco 2960 or 3560)

Connections:

— Two GigabitEthernet ports on each switch (Switch1: G0/1, G0/2; Switch2: G0/1, G0/2)

You should have the following ports connected:

— Switch1: G0/1 and G0/2

— Switch2: G0/1 and G0/2

Lab Steps

Step 1: Basic Configuration

Before configuring EtherChannel, ensure the switches are properly set up with basic configurations (hostname, IP addresses, and enable passwords).

Configure Switch1:

Switch1> enable 
Switch1# config terminal 
Switch1(config)# hostname Switch1 
Switch1(config)# interface range gigabitEthernet 0/1 - 2 
Switch1(config-if-range)# no shutdown 
Switch1(config-if-range)# exit 
Switch1(config)# exit

Configure Switch2:

Switch2> enable 
Switch2# config terminal 
Switch2(config)# hostname Switch2 
Switch2(config)# interface range gigabitEthernet 0/1 - 2 
Switch2(config-if-range)# no shutdown 
Switch2(config-if-range)# exit 
Switch2(config)# exit

Step 2: Configure EtherChannel Using LACP (Link Aggregation Control Protocol)

Link Aggregation Control Protocol (LACP) is one of the most common protocols for EtherChannel. The EtherChannel ports are dynamically negotiated using LACP.

1. On Switch1:

Switch1(config)# interface range gigabitEthernet 0/1 - 2 
Switch1(config-if-range)# channel-group 1 mode active 
Switch1(config-if-range)# exit

Explanation:

The channel-group 1 command adds interfaces G0/1 and G0/2 to EtherChannel group 1.

mode active configures LACP to actively negotiate with the peer.

On Switch2:

Switch2(config)# interface range gigabitEthernet 0/1 - 2 
Switch2(config-if-range)# channel-group 1 mode passive
Switch2(config-if-range)# exit

Explanation:

channel-group 1 is used to add G0/1 and G0/2 to EtherChannel group 1 on Switch2.

The mode passiveconfigures LACP negotiation for passive mode.

N/B — Active-Active: This configuration is not valid because both sides cannot be set to active mode. LACP requires one side to be in active mode (initiating negotiations) and the other side to be in passive mode (responding to negotiations). Both sides in active mode will try to initiate the negotiation, causing a conflict.

— Active-Passive: This is the correct configuration for LACP. One switch should be configured in active mode, and the other should be in passive mode. In this setup:

— The active side will initiate the EtherChannel negotiation.

— The passive side will respond to the negotiation and only accept the connection if the active side sends a negotiation request.

Step 3: Configure EtherChannel Using PAgP (Port Aggregation Protocol)

Alternatively, you can use PAgP (Port Aggregation Protocol) for EtherChannel negotiation. PAgP is a Cisco proprietary protocol, unlike LACP, which is an open standard.

On Switch1 (Using PAgP):

Switch1(config)# interface range gigabitEthernet 0/1 - 2 
Switch1(config-if-range)# channel-group 1 mode desirable 
Switch1(config-if-range)# exit

Explanation:

channel-group 1 adds interfaces G0/1 and G0/2 to EtherChannel group 1.

mode desirable actively negotiates the EtherChannel using PAgP.

On Switch2 (Using PAgP):

Switch2(config)# interface range gigabitEthernet 0/1 - 2 
Switch2(config-if-range)# channel-group 1 mode auto
Switch2(config-if-range)# exit

Explanation:

• The mode desirable also sets up PAgP negotiation with the peer.

Step 4: Verify EtherChannel Configuration

After configuring EtherChannel, you can verify the status using the following commands:

Verify EtherChannel status on both switches:

Switch1# show etherchannel summary

1. This command will show the EtherChannel group, protocol (LACP or PAgP), and the interfaces involved.

Example output:

Verify the status of each port:

Switch1# show interfaces gigabitEthernet 0/1 etherchannel

Check if the EtherChannel is up and operational:

Switch1# show running-config

Step 5: Configure Load Balancing (Optional)

By default, EtherChannel uses the MAC address of the source or destination for load balancing. You can change the load balancing method using the following command:

Set load balancing method to IP address:

Switch1(config)# port-channel load-balance src-ip

Set load balancing method to Layer 4 (Transport Layer):

Switch1(config)# port-channel load-balance dst-ip

Step 6: Troubleshooting EtherChannel Configuration

If EtherChannel is not working as expected, use the following steps to troubleshoot:

Check EtherChannel status:

Switch1# show etherchannel summary

Check for errors in interface configuration:

Switch1# show run interface gi0/1 Switch1# show run interface gi0/2

Verify negotiation (LACP or PAgP) status:

Switch1# show lacp neighbor

Check for mismatched configurations: Ensure both switches are using the same EtherChannel protocol and mode. If using LACP, both switches must be in the same mode (active or passive).

Step 7: Save the Configuration

After verifying and ensuring the EtherChannel is working as expected, save your configuration.

Save configuration on Switch1:

Switch1# write memory

Save configuration on Switch2:

Switch2# write memory

Conclusion

We have successfully configured EtherChannel between two switches using both LACP and PAgP. This lab demonstrates how to set up and verify EtherChannel for redundancy and load balancing in a Cisco network. EtherChannel provides a vital method for improving network performance and fault tolerance, which is important for CCNA exam objectives.