AdvancedPublished 2026-07-02
EtherChannel Troubleshooting Capstone (L2 LACP)
Bundle lab
Advanced EtherChannel capstone, run as a fault hunt. The uplink bundle between two access switches is not passing traffic and the hosts either side cannot reach each other. Some members are up, the bundle is not, and nothing was recorded. You get symptoms and the required end state — no fault list. Both ends of a bundle have to agree about several things at once, and only one end was touched during the change — so comparing them is the exercise.
Learning objectives
- Diagnose an EtherChannel that will not form, from operational state alone
- Compare both ends of a bundle rather than assuming the local switch owns the fault
- Recognise a negotiation-mode mismatch (static on against LACP) as distinct from a member that is simply down
- Know that member ports and the port-channel must agree about switchport mode and VLAN
- Restore the bundle without resorting to configuring every port statically
Troubleshooting focus
- If a Port-channel remains down or members show suspended/individual, compare the channel-group number per member on the SAME device to ensure they join the same aggregator.
- Confirm both ends are using compatible EtherChannel modes: on/on (static), active/active or active/passive (LACP), desirable/desirable or desirable/auto (PAgP).
- Validate that each member’s switchport parameters are identical on its local device (mode access or trunk, VLAN or allowed list, speed/duplex) so the bundle can form.
- Check that the logical Port-channel interface has the intended Layer-2 settings and that the members inherit the same parameters.
- Use show etherchannel summary and show etherchannel 100 detail to correlate state flags, partner information, and reasons a member is not bundled.
Topology
Subscribe to preview this lab's topology.
See plansGrade your work
How this lab is graded
- Build it your way. Where a lab lets you choose a value — a VLAN name, an interface description — grading checks that you configured it, not which name you picked. Names that another line has to reference, like an ACL applied with
access-class, are stated in the guide and do have to match. - Addresses, modes and protocol keywords are exact. An IP address, a subnet mask,
switchport mode trunk, an encapsulation — these carry the meaning of the lab, so they are graded as written in the guide. - Grading reads your saved configuration. Export the lab from CML after you have configured it, and make sure anything you set is in the running-config — a change that only exists in a terminal session never reaches the grader.
- You can submit as many times as you like. Your best score stands, and each attempt tells you which checks passed so you can work the gaps.
- Scored something you believe is correct? Use Report an issue on this page — that is exactly how the grading fixes in the changelog got found.
Create a free account to submit your lab for grading.
Create a free accountFound a problem with this lab?
Please sign in to report a problem — tying it to your attempts lets us reproduce and fix it faster.