15 hands-on EtherChannel scenarios you build in your own Cisco Modeling Labs instance and grade against the answer key. EtherChannel configuration and troubleshooting practice for CCNA and CCNP.
Included with a subscription
Bring together core campus redundancy skills in one focused day: elect a deterministic STP root on the intended distribution switch, form a working LACP EtherChannel between distribution and access, harden edge with PortFast/BPDU Guard, and stand up an HSRP virtual gateway that the VLAN 10 users actually use. The starter is intentionally mis-tuned across layers so you must build or repair it end-to-end.
Troubleshoot and fix an LACP EtherChannel between campus switches so both physical members bundle and the trunk reliably carries VLAN 10. Two independent faults are seeded: an intra-bundle trunk mismatch on one switch and an administratively down member on the other. Learners diagnose with show commands, align trunk attributes, and verify end-to-end host reachability.
Daily CCNA campus-redundancy lab focused on EtherChannel scale-out and hashing. Two distribution switches are joined by three parallel trunk links. Two links are already bundled with LACP into a trunking port-channel; the third is a plain trunk currently STP-blocked and wasting capacity. Add the spare link to the existing bundle on both sides and change the global hashing method so multiple flows can actually use multiple member links. End-to-end switching must continue to work for the users VLAN.
Hands-on CCNA EtherChannel repair lab. Two uplinks between a distribution and an access switch are intended to form a single port-channel trunk carrying VLAN 10. The starter ships with a real mode mismatch across the bundle and an allow-list error, so the Port-channel stays down and hosts cannot talk. Learners diagnose the symptom and standardize on one protocol family (PAgP, LACP, or Static) and correct trunking so VLAN 10 forwards end-to-end.
Bundle two parallel switch uplinks into a single Port-Channel using LACP so that Spanning Tree no longer blocks one link. You will convert two existing 802.1Q trunks into one logical trunk, verify both member links are active in the Port-Channel, and confirm end-to-end host reachability.
Build a two-link LACP EtherChannel between two layer-2 switches as an access port for VLAN 60, then tune the global load-balancing algorithm to src-dst-ip so traffic distributes more evenly. Verify Po6 status, the hashing method, and end-to-end host reachability.
Build a two-link LACP EtherChannel between SW1 and SW2 using an active/passive pairing. The logical Port-channel2 carries VLAN 20 as an access link so two hosts on opposite switches can communicate. Verify with show etherchannel summary, show lacp neighbor, and host-to-host pings.
Build a two-link LACP EtherChannel between SW1 and SW2 and convert the Port-channel into an 802.1Q trunk that explicitly carries VLANs 40 and 41. Validate end-to-end host reachability across VLAN 40 and confirm the trunk’s allowed VLAN list and switchport mode on the logical port-channel. Emphasis: deterministic EtherChannel configuration on member interfaces, correct trunking on the Port-channel, and verification with IOS show commands.
Build a Layer-3 EtherChannel between two IOS XE routers using LACP active/active. Two parallel router links are bundled into Port-channel5, which carries a /30 transit. R2 hosts a loopback; R1 installs a static route to reach it. Validate that the Port-channel holds the IP (members do not), that the bundle is up and uses both links, and that pings across the /30 and to the loopback succeed. Emphasis: deterministic EtherChannel configuration and Layer-3 port-channel practices.
Build a routed LACP EtherChannel (Port-channel 8) between two iol-xe routers and route real inter-LAN traffic using static routes. Two parallel physical links (Ethernet0/0 and Ethernet0/1) on each router are bundled into a single Layer-3 Port-channel with a /30 transit. Each router serves a local /24 LAN with an alpine host. Validate that Po8 is up/up, static routes are present, and end-to-end host pings succeed across the aggregated uplink.
Build an LACP Layer-2 EtherChannel between SW1 and SW2 so Rapid-PVST+ treats two parallel links as one logical Port-channel 7. Without EtherChannel, STP will block one of the two access links. With LACP active on both members and Port-channel 7 as an access port in VLAN 70, STP shows a single forwarding interface (Po7) and both physical links forward as one logical channel. Two hosts in VLAN 70 verify end-to-end connectivity.
Beginner CCNA lab that builds a static Layer-2 EtherChannel (mode on) between two ioll2-xe switches using two parallel links as members of Port-channel1. The Port-channel is configured as an access port in VLAN 10 so that two hosts, one on each switch, can communicate without spanning-tree blocking a parallel path. Learners deploy and verify the bundle, then validate end-to-end host connectivity.
Free with an account
Advanced CCNP troubleshooting lab: a pair of Layer-2 switches are connected by a two-link EtherChannel intended to carry VLAN 90 between access hosts. The starter configuration ships broken on purpose: the inter-switch bundle won’t form due to incompatible aggregation modes, and a trunk allow-list drift on one side prunes VLAN 90. Diagnose with IOS show commands, correct the EtherChannel mode so LACP forms the Port-channel, and restore trunk policy so same-VLAN hosts can communicate.
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.
Build a Layer-2 PAgP EtherChannel between two ioll2-xe switches (SW1 and SW2) using a desirable/auto pairing on two parallel links. Bundle Ethernet0/0 and Ethernet0/1 into Port-channel 3, make the port-channel a VLAN 30 access interface on both switches, and verify with show etherchannel summary, show pagp neighbor, show pagp counters, and end-to-end host pings in VLAN 30.
EtherChannel bundles several physical links between the same two devices into one logical interface. That buys aggregate bandwidth, but the bigger reason to use it is spanning tree: STP sees the bundle as a single logical port with one path cost, so it never blocks the redundant members the way it would block a second discrete cable. Both links forward, and losing one is a sub-second event instead of a reconvergence. Almost everything that goes wrong with EtherChannel is a negotiation or consistency problem, two passive ends that both wait for the other, a static end facing an LACP end, or one member whose speed, duplex, or allowed VLAN list disagrees with its bundle-mates. Those are diagnosed by reading the flags in show etherchannel summary, which is a skill you build by making bundles fail on purpose.
These labs have you build channels on real Cisco IOS in Cisco Modeling Labs. You will select members with interface range, negotiate with channel-group 1 mode active or passive for LACP, desirable or auto for PAgP, and on for a static bundle, then put every switchport setting on interface port-channel 1 rather than the physical members. Layer 3 labs convert the members with no switchport and place the IP address on the Port-channel itself. You will also set the hash with port-channel load-balance src-dst-ip. Verify with show etherchannel summary, reading Po1 as (SU) for a Layer 2 bundle or (RU) for a routed one and each member as (P) for bundled, (s) for suspended, or (D) for down, then confirm the partner with show lacp neighbor and the VLANs with show interfaces trunk. Fault labs include two passive ends, an on-to-active mismatch, a member with a mismatched allowed VLAN list, and an IP address left on a physical port. Grading checks your configuration requirement by requirement against the answer key.
LACP, using modes active and passive, is the IEEE 802.1AX standard and works between vendors, so it is the default choice; at least one end must be active or the bundle never forms. PAgP, using desirable and auto, is Cisco-proprietary but functionally equivalent. Mode on does no negotiation at all, so it cannot detect miscabling or a mismatched far end. Use it only when the peer genuinely cannot negotiate, and then on both ends.
No. The switch hashes each conversation onto one member link and keeps it there so frames do not arrive out of order, which means one TCP session is capped at a single link speed. You see the aggregate only when many flows spread across the members. The labs have you change the hash with port-channel load-balance and observe which member a given source and destination pair selects.
Yes. Each lab is a package for your own Cisco Modeling Labs instance built on free-tier images, so you can run two, three, or four virtual links between a pair of virtual switches and get the same show etherchannel summary flags and LACP partner output a physical pair produces.
Study the theory behind these labs — the concept explainer and step-by-step guides.
Looking for something else? Browse the full lab archive, narrow it to self-standing labs, or see today's daily lab.