LAB: STP and EtherChannel
Redundancy without tears. This lab wires three switches into a triangle so that Spanning Tree has a real loop to break, lets you watch the root election happen, then bundles two links into an EtherChannel so STP no longer has to sacrifice a link at all. The whole lab is two ideas made visible: STP blocks the loop and EtherChannel removes the loop.
- Build a redundant triangle topology with three switches.
- Observe the root bridge election and identify the root.
- Identify the blocked port STP chose to break the loop.
- Bundle two links into an EtherChannel with LACP and watch the blocked port disappear.
- Verify with show spanning-tree, show etherchannel summary, and pings.
- Explain why the EtherChannel member links both forward.
Overview and goal
A triangle of switches is the smallest possible L2 loop: three secrets forming a ring. STP must elect one of the three as root, give the other two a root port each, and block one remaining port so the ring becomes a tree. Then the lab changes the game: two of the links get bundled into a port-channel, the loop disappears by construction, and STP happily forwards on both members.
Topology
Cabling: SW1 Gi0/1 ↔ SW2 Gi0/1; SW1 Gi0/2 ↔ SW3 Gi0/1; SW2 Gi0/3 and Gi0/4 ↔ SW3 Gi0/3 and Gi0/4 (mirrored). Optionally hang PC-A off SW1 Gi0/24 to have a ping source.
Step 1 — Build the triangle
Place three switches and give each a hostname. No VLAN work is needed — everything can run in the default VLAN 1, which keeps this lab purely about STP and EtherChannel. If you attached a PC, give it any address in 192.168.1.0/24 (e.g. 192.168.1.10/24, gateway not needed for local pings).
Switch# configure terminal Switch(config)# hostname SW1 SW1(config)# exit ... repeat hostname for SW2 and SW3 ...
Step 2 — Watch the root election
With all links up, STP converges within tens of seconds. On a default LAN, all three switches have priority 32768, so the election falls to the base MAC address: the switch with the lowest base MAC becomes root. Identify the winner on any switch:
SW1# show spanning-tree VLAN0001 Spanning tree enabled protocol ieee Root ID Priority 32768 Address aaaa.aaaa.aaaa This bridge is the root Bridge ID Priority 32768 Address aaaa.aaaa.aaaa Interface Role Sts Cost Prio.Nbr Type Gi0/1 Desg FWD 4 128.1 P2p Gi0/2 Desg FWD 4 128.2 P2p
Read the header carefully: This bridge is the root means this switch is the
root. If the line is absent (or says another address), this switch is not root. The two ports on the
root are both Desg FWD — the root owns every one of its segments.
spanning-tree vlan 1 priority 0. The random election is exactly why the design rule
exists.
Step 3 — Find the blocked port
Check the two non-root switches. Each should show exactly one Root port (toward SW1) and, on SW2 or SW3, the port on the bottom link should be blocked:
SW2# show spanning-tree VLAN0001 Root ID Priority 32768 Address aaaa.aaaa.aaaa Bridge ID Priority 32768 Address bbbb.bbbb.bbbb Interface Role Sts Cost Prio.Nbr Type Gi0/1 Root FWD 4 128.1 P2p Gi0/3 Altn BLK 4 128.3 P2p Gi0/4 Altn BLK 4 128.4 P2p
If SW2 is the one with the worse path, both of its bottom ports show Altn BLK —
alternate/blocked — because SW2 is not the designated switch for that segment. The twin blocked
ports are the point: there are two physical paths between SW2 and SW3, and STP currently sacrifices
one (both) to stop the loop. After Step 5, that frustration disappears.
Step 4 — Confirm connectivity across the loop
Even with a blocked port, the network works — a blocked STP port is a hot standby, not a broken link. Ping from PC-A to SW2’s management address or simply check that PC-A can ping a host on the SW2 side. Then pull SW1’s Gi0/1 while a continuous ping runs (or just observe), and note the outage: classic STP takes roughly 30–50 seconds (max age + forward delays) to move a blocked port into forwarding. That is the convergence lesson, live.
Step 5 — Bundle two links with LACP
Restore any link you pulled, then make the two SW2–SW3 links a single port-channel with LACP mode active on both ends. Configure identical physical properties first, then group:
SW2(config)# interface range gigabitEthernet 0/3-4 SW2(config-if-range)# switchport mode trunk SW2(config-if-range)# channel-group 1 mode active SW2(config-if-range)# exit SW2(config)# interface port-channel 1 SW2(config-if)# switchport mode trunk SW2(config-if)# exit SW3(config)# interface range gigabitEthernet 0/3-4 SW3(config-if-range)# switchport mode trunk SW3(config-if-range)# channel-group 1 mode active SW3(config-if-range)# exit SW3(config)# interface port-channel 1 SW3(config-if)# switchport mode trunk SW3(config-if)# end
Both ends active means LACP negotiates happily (active+active). Had one side used
mode on and the other mode active, they would never agree — a good
thing LACP exists for.
Step 6 — Watch STP un-block the channel
Now that SW2 and SW3 are joined by a single logical link, the loop is gone. STP’s view has three switches in a simple Y — nothing to block. Verify on both switches:
SW2# show spanning-tree Interface Role Sts Cost Prio.Nbr Type Po1 Desg FWD 4 128.1 P2p Gi0/1 Root FWD 4 128.1 P2p
The two physical members now appear as one logical interface, Po1, in the
Designated / Forwarding state. No port is blocked because no port is a loop. Both member
cables carry traffic — a state that was impossible in Step 3.
show spanning-tree (Po1 FWD) and show etherchannel summary (P flags) is
the evidence an answer question quotes.
Step 7 — Final verification
SW2# show etherchannel summary Group Port-channel Protocol Ports ------+-------------+-----------+----------------------------------------------- 1 Po1(SU) LACP Gi0/3(P) Gi0/4(P) SW2# show port-channel 1 Channel group: 1 Channel members: 2 GigabitEthernet0/3 GigabitEthernet0/4 Load-balance method: src-dst mac SW2# ping 192.168.1.10 !!! ! host reachable through the channel
The two P flags in show etherchannel summary are the definitive proof both links are
bundled. A member that appears with I (stand-alone) instead of P means a consistency
problem — check the troubleshooting table. The load-balance method line explains the last key
fact: this channel hashes by source/destination MAC, so a single PC-to-PC conversation uses one
member while many conversations spread across both.
Troubleshooting guide
| Symptom | Likely cause | Fix |
|---|---|---|
| Channel never forms; all members flag I | Speed, duplex, VLAN, or trunk state differs between members | Make members identical; re-check show etherchannel summary |
| One member P, the other D or I | Physical port down or a mismatch on that interface only | Cable/port check; match settings across both ends |
| STP still shows a blocked port after bundling | The bundle did not form, or a different link still loops | Confirm Po1 is up (SU); review the whole triangle for un-bundled parallels |
| Channel forms but no STP presence | Look for two switch links that were never grouped | Group them too — each pair of parallels needs its own channel |
| Ping fails only after a cable pull | Classic STP convergence delay on non-RSTP | Enable spanning-tree mode rapid-pvst and re-test (Lesson 19) |
The vocabulary you need
Every term below appears in the lesson text above. Select one to read its definition, then use the quiz at the end to check what stuck.
Review
Check what you have learned with these review questions.
Sources & references
- Cisco. CCNA (200-301) Exam Topics. cisco.com.
- IETF. Request for Comments (RFCs). rfc-editor.org.
- IANA. Internet Assigned Numbers Authority registries. iana.org.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.