6.3.4 Packet Tracer – Troubleshoot EtherChannel (Instructions Answer)

6.3.4 Packet Tracer - Troubleshoot EtherChannel (Instructor Version)

Objectives

  • Part 1: Examine the Physical Layer and Correct Switch Port Mode Issues
  • Part 2: Identify and Correct Port Channel Assignment Issues
  • Part 3: Identify and Correct Port Channel Protocol Issues

Background

A junior technician recently configured four switches. Users are complaining that the network is running slowly, and they would like you to investigate.

Port Channel Table

Channel Group Ports Protocol
1 S1: G0/1, G0/2
S2: G0/1, G0/2
LACP active
2 S2: G0/1, G0/2
S4: G0/1, G0/2
LACP active
3 S1: F0/23, F0/24
S2: F0/23, F0/24
LACP active
4 S3: F0/23, F0/24
S4: F0/23, F0/24
LACP active
5 S1: F0/21, F0/22
S4: F0/21, F0/22
LACP active
6 S2: F0/21, F0/22
S3: F0/21, F0/22
LACP active

Device Table

Device Group Ports
S1 1 G0/1, G0/2
3 F0/23, F0/24
5 F0/21, F0/22
S2 2 G0/1, G0/2
3 F0/23, F0/24
6 F0/21, F0/22
S3 1 G0/1, G0/2
4 F0/23, F0/24
6 F0/21, F0/22
S4 2 G0/1, G0/2
4 F0/23, F0/24
5 F0/21, F0/22

Instructions

Part 1: Examine the Physical Layer and Correct Switch Port Mode Issues

Step 1: Look for access ports.

Examine the switches. When two or more redundant links connect the same switches, Spanning Tree protocol will only put one port in forwarding mode to prevent switching loops. You can see this in Packet Tracer. When physical ports are assigned to an EtherChannel port, they behave as one logical port. Each pair will either be operational or down.

Step 2: Verify ports are in trunk mode.

On S2, the port channel interfaces and physical interfaces that have been configured in the port channels are all configured as access ports. The physical interfaces should be configured as trunks. The port channel interfaces should also be configured as trunks.

S2#show running-config 
.
.
!
interface FastEthernet0/21
 switchport mode access
 channel-group 6 mode active
!
interface FastEthernet0/22
 switchport mode access
 channel-group 6 mode active
!
interface FastEthernet0/23
 switchport mode access
 channel-group 3 mode active
!
interface FastEthernet0/24
 switchport mode access
 channel-group 3 mode active
!
interface GigabitEthernet0/1
 switchport mode access
 channel-group 2 mode active
!
interface GigabitEthernet0/2
 switchport mode access
 channel-group 2 mode active

!
!
end

a. Verify that all physical ports in the topology are configured as trunks. Correct any ports that are in access mode.

S2(config)#interface range f0/21-24, g0/1-2
S2(config-if-range)#switchport mode trunk

b. Correct any EtherChannel ports that are not configured as trunks.

Instructor Note: Packet Tracer versions 7.2.1 and earlier do not grade the switchport mode trunk command on port-channel interfaces.

S1(config)#interface port-channel 1
S1(config-if)#switchport mode trunk
S2(config)#interface port-channel 2
S2(config-if)#switchport mode trunk
S2(config-if)#interface port-channel 3
S2(config-if)#switchport mode trunk
S2(config-if)#interface port-channel 6
S2(config-if)#switchport mode trunk

Part 2: Identify and Correct Port Channel Assignment Issues

Port channel interface assignment can be confusing. It is a possible that errors can occur when assigning physical ports to port channels. In this case, ports F0/21 and F0/22 on S4 have been assigned to port channel group 4. They should be reassigned to port channel group 5.

Step 1: Examine port channel assignments.

The Packet Tracer topology and the Port Channel and Device tables provide details about the physical ports and their EtherChannel assignments. Use the show etherchannel summary command to learn how the EtherChannel links are configured. Verify that the switches are configured as shown in the documentation.

S1#show etherchannel summary
Flags:  D - down        P - in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      f - failed to allocate aggregator
        u - unsuitable for bundling
        w - waiting to be aggregated
        d - default port


Number of channel-groups in use: 3
Number of aggregators:           3

Group  Port-channel  Protocol    Ports
------+-------------+-----------+----------------------------------------------

1      Po1(SD)           LACP   Gig0/1(I) Gig0/2(I) 
3      Po3(SU)           LACP   Fa0/23(P) Fa0/24(P) 
5      Po5(SU)           LACP   Fa0/21(P) Fa0/22(P)

S2#show etherchannel summary
Flags:  D - down        P - in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      f - failed to allocate aggregator
        u - unsuitable for bundling
        w - waiting to be aggregated
        d - default port


Number of channel-groups in use: 3
Number of aggregators:           3

Group  Port-channel  Protocol    Ports
------+-------------+-----------+----------------------------------------------

2      Po2(SU)           LACP   Gig0/1(P) Gig0/2(P) 
3      Po3(SU)           LACP   Fa0/23(P) Fa0/24(P) 
6      Po6(SD)           LACP   Fa0/21(I) Fa0/22(I)

S3#show etherchannel summary
Flags: D - down P - in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
u - unsuitable for bundling
w - waiting to be aggregated
d - default port

Number of channel-groups in use: 3
Number of aggregators: 3

Group Port-channel Protocol Ports
------+-------------+-----------+----------------------------------------------

1 Po1(SD) PAgP Gig0/1(I) Gig0/2(I)
4 Po4(SD) PAgP Fa0/23(I) Fa0/24(I)
6 Po6(SD) PAgP Fa0/21(I) Fa0/22(I) 

S4#show etherchannel summary
Flags: D - down P - in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
u - unsuitable for bundling
w - waiting to be aggregated
d - default port

Number of channel-groups in use: 3
Number of aggregators: 3

Group Port-channel Protocol Ports
------+-------------+-----------+----------------------------------------------

2 Po2(SU) LACP Gig0/1(P) Gig0/2(P)
4 Po4(SU) LACP Fa0/21(P) Fa0/22(P) Fa0/23(I) Fa0/24(I)
5 Po5(SD) -

Step 2: Correct port channel assignments.

Correct any switch ports that are not assigned to the correct EtherChannel port.

S4(config)#interface range f0/21-22
S4(config-if-range)#channel-group 5 mode active

Part 3: Identify and Correct Port Channel Protocol Issues

The Network Design Team has made it a requirement that all EtherChannel links actively negotiate LACP. The physical ports on switch S3 have been configured to unconditionally establish PAgP, not LACP, EtherChannels. This must be corrected on S3 in order that the EtherChannels can be established.

Step 1: Identify protocol issues.

In 2000, the IEEE released 802.3ad (LACP), which is an open standard version of EtherChannel. For compatibility reasons, the network design team chose to use LACP across the network. The design team has made it a requirement that all ports that participate in EtherChannel need to actively negotiate the link as LACP. Verify that the physical ports are configured as indicated in the topology and Port Channel Table.

S3#show etherchannel summary
Flags:  D - down        P - in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      f - failed to allocate aggregator
        u - unsuitable for bundling
        w - waiting to be aggregated
        d - default port


Number of channel-groups in use: 3
Number of aggregators:           3

Group  Port-channel  Protocol    Ports
------+-------------+-----------+----------------------------------------------

1      Po1(SD)           PAgP   Gig0/1(I) Gig0/2(I) 
4      Po4(SD)           PAgP   Fa0/23(I) Fa0/24(I) 
6      Po6(SD)           PAgP   Fa0/21(I) Fa0/22(I)
Step 2: Correct Protocol issues.

a. Correct any switch ports that are not negotiating using LACP.

S3(config)# interface range g0/1-2
S3(config-if-range)# no channel-group
S3(config-if-range)# channel-group 1 mode active
S3(config-if-range)# interface range f0/21-22
S3(config-if-range)# no channel-group
S3(config-if-range)# channel-group 6 mode active
S3(config-if-range)# interface range f0/23-24
S3(config-if-range)# no channel-group
S3(config-if-range)# channel-group 4 mode active

b. Reissue the show etherchannel summary command to verify that all EtherChannel links are now correctly configured.

S3#show etherchannel summary
Flags:  D - down        P - in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      f - failed to allocate aggregator
        u - unsuitable for bundling
        w - waiting to be aggregated
        d - default port


Number of channel-groups in use: 3
Number of aggregators:           3

Group  Port-channel  Protocol    Ports
------+-------------+-----------+----------------------------------------------

1      Po1(SU)           PAgP   Gig0/1(P) Gig0/2(P) 
4      Po4(SU)           PAgP   Fa0/23(P) Fa0/24(P) 
6      Po6(SU)           PAgP   Fa0/21(P) Fa0/22(P)

Device Configs - Final

SWITCH S1

! ==============================================================
!--- 6.3.4 Packet Tracer - Troubleshoot EtherChannel
!--- FIX SCRIPT FOR SWITCH S1
!--- Usage: from the console (or a Telnet/SSH session, if already reachable) on S1, enter privileged EXEC mode with "enable", then paste this whole file. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless.
!--- Confirmed error (Part 1): S1's logical Port-channel 1 interface (link to S3, per the Device Table - the Topology diagram and Device Table agree on this even though the Port Channel Table's own row for Group 1 mislabels the far end as S2) is left in access mode. That alone is why "show etherchannel summary" shows Po1(SD) with both members stuck as stand-alone (I) instead of bundled (P).
! ==============================================================

enable
configure terminal

! --------------------------------------------------------------
!--- Part 1, Step 2: Correct the Port Channel 1 logical interface to trunk mode
! --------------------------------------------------------------

!--- S1's physical G0/1/G0/2 members were already fine - only the Port-channel interface itself was left at the default access mode, which alone was enough to keep the bundle from coming up.
interface port-channel 1
 switchport mode trunk

end

! --------------------------------------------------------------
!--- Operational habit (not explicitly required by this lab): save to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config

! ==============================================================
!--- Verification:
!---   S1# show etherchannel summary -> Po1 changes from "Po1(SD) LACP Gig0/1(I) Gig0/2(I)" to "Po1(SU) LACP Gig0/1(P) Gig0/2(P)"
!---   S1# show interfaces trunk    -> Po1 now listed as trunking
! ==============================================================

SWITCH S2

! ==============================================================
!--- 6.3.4 Packet Tracer - Troubleshoot EtherChannel
!--- FIX SCRIPT FOR SWITCH S2
!--- Usage: from the console (or a Telnet/SSH session, if already reachable) on S2, enter privileged EXEC mode with "enable", then paste this whole file. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless.
!--- Confirmed error (Part 1): every physical port that belongs to an EtherChannel on S2 (F0/21-24, G0/1-2) is in access mode, and all three logical Port-channel interfaces (2, 3, 6) are too. Po2 and Po3 had already managed to bundle successfully as access-mode channels ("SU", members "(P)") - still wrong, since these links are meant to be trunks - while Po6 hadn't even come up ("SD", members "(I)").
! ==============================================================

enable
configure terminal

! --------------------------------------------------------------
!--- Part 1, Step 2.1: Trunk every physical port that belongs to an EtherChannel
! --------------------------------------------------------------

!--- Covers all three of S2's channels in one range: G0/1-2 (Group 2), F0/21-22 (Group 6), F0/23-24 (Group 3).
interface range FastEthernet0/21 - 24, GigabitEthernet0/1 - 2
 switchport mode trunk

! --------------------------------------------------------------
!--- Part 1, Step 2.2: Trunk the three logical Port-channel interfaces
! --------------------------------------------------------------

interface port-channel 2
 switchport mode trunk

interface port-channel 3
 switchport mode trunk

interface port-channel 6
 switchport mode trunk

end

! --------------------------------------------------------------
!--- Operational habit (not explicitly required by this lab): save to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config

! ==============================================================
!--- Verification:
!---   S2# show etherchannel summary -> Po2, Po3, Po6 all show SU with every member (P)
!---   S2# show interfaces trunk    -> Po2, Po3, Po6 all listed as trunking
! ==============================================================

SWITCH S3

! ==============================================================
!--- 6.3.4 Packet Tracer - Troubleshoot EtherChannel
!--- FIX SCRIPT FOR SWITCH S3
!--- Usage: from the console (or a Telnet/SSH session, if already reachable) on S3, enter privileged EXEC mode with "enable", then paste this whole file. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless.
!--- Confirmed error (Part 3): all three of S3's channel groups (1, 4, 6) are running PAgP instead of the network design team's required LACP - "show etherchannel summary" shows all of them as Po#(SD) with PAgP and members stand-alone (I), meaning none of them have actually bundled.
! ==============================================================

enable
configure terminal

! --------------------------------------------------------------
!--- Part 3, Step 2: Switch every channel group from PAgP to LACP active
! --------------------------------------------------------------

!--- A port already assigned to a channel-group can't just be handed a new mode/protocol directly - "no channel-group" removes it first, then "channel-group X mode active" re-adds it as LACP. Repeated for all three of S3's groups.
interface range GigabitEthernet0/1 - 2
 no channel-group
 channel-group 1 mode active

interface range FastEthernet0/21 - 22
 no channel-group
 channel-group 6 mode active

interface range FastEthernet0/23 - 24
 no channel-group
 channel-group 4 mode active

end

! --------------------------------------------------------------
!--- Operational habit (not explicitly required by this lab): save to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config

! ==============================================================
!--- Verification:
!---   S3# show etherchannel summary -> Po1, Po4, Po6 all show LACP instead of PAgP, with members (P) once the far end (S1, S4, S2) is also correctly configured
! ==============================================================

SWITCH S4

! ==============================================================
!--- 6.3.4 Packet Tracer - Troubleshoot EtherChannel
!--- FIX SCRIPT FOR SWITCH S4
!--- Usage: from the console (or a Telnet/SSH session, if already reachable) on S4, enter privileged EXEC mode with "enable", then paste this whole file. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless.
!--- Confirmed error (Part 2): F0/21 and F0/22 were assigned to channel-group 4 instead of 5 - "show etherchannel summary" shows Po4 with FOUR ports (Fa0/21(P) Fa0/22(P) Fa0/23(I) Fa0/24(I)) when Group 4 should only ever have F0/23-24, while Po5(SD) sits empty ("-") since its rightful members were misassigned elsewhere.
! ==============================================================

enable
configure terminal

! --------------------------------------------------------------
!--- Part 2, Step 2: Move F0/21-22 out of channel-group 4 and into channel-group 5
! --------------------------------------------------------------

!--- "no channel-group" first removes these ports from the WRONG group (4) they're currently in - the source lab's own instructions and answer script skip straight to "channel-group 5 mode active" without this step, but a port already bundled into one channel-group can't simply be reassigned to a different one without first being removed. This is the same "no channel-group" pattern the lab itself uses for S3's fix in Part 3 - see the discrepancy note in chat.
interface range FastEthernet0/21 - 22
 no channel-group
 channel-group 5 mode active

end

! --------------------------------------------------------------
!--- Operational habit (not explicitly required by this lab): save to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config

! ==============================================================
!--- Verification:
!---   S4# show etherchannel summary -> Po4 now shows only Fa0/23(P) Fa0/24(P); Po5 shows Fa0/21(P) Fa0/22(P) instead of sitting empty
! ==============================================================

Download Packet Tracer (.pka) file:

Subscribe
Notify of
guest

2 Corrections & Clarifications