EtherChannel Consistency: Repair a Mode Mismatch
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.
EtherChannel Load Balancing with LACP (VLAN 60)
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.
L3 Routed EtherChannel Between Two Routers (LACP)
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.
EtherChannel Troubleshooting Capstone (L2 LACP)
Advanced CCNP EtherChannel troubleshooting capstone on Cisco IOS L2 switches. Two ioll2-xe switches are joined by two parallel links intended to bundle as one LACP Port-channel. The lab ships pre-broken with two independent faults on SW1: the parallel links are placed into different channel-groups and their switchport L2 parameters are inconsistent. Learners must use show commands to diagnose, then correct both faults so Port-channel 100 bundles both members as an access link for VLAN 100, restoring host-to-host reachability.
Lab 7: EtherChannel + Rapid-PVST — One Logical Link
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.
Lab 8: L3 EtherChannel + Static Routing
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.
Root Guard on Designated Ports
Advanced Rapid-PVST+ and Root Guard implementation on a three-switch triangle with a real loop. SW1 is the intentional root for VLAN 90 and protects its designated ports with Root Guard to prevent root re-parenting. Two Alpine hosts on VLAN 90 verify end-to-end forwarding remains stable even if a superior BPDU appears downstream.
STP Lab 8: Per-VLAN Load Balancing Across Two Roots
Use Rapid-PVST+ to elect different root bridges per VLAN across two parallel trunks, spreading VLAN 80 and VLAN 81 across distinct physical links without modifying path cost or port priority. Validate independent per-VLAN trees and confirm hosts in VLAN 80 can communicate over the surviving path. Includes a drift-check to diagnose/restore trunk allow-lists.
STP 10: Spanning Tree Troubleshooting Capstone
Advanced Rapid-PVST+ troubleshooting on a 3-switch triangle with a real Layer-2 loop. Two deliberate faults are seeded: an unintended root bridge wins VLAN 100 due to a mis-set/default priority, and PortFast/BPDU Guard are mistakenly applied on an inter-switch trunk. Two Alpine hosts in VLAN 100 verify user impact. Your job: use show commands to diagnose, then restore the correct root and remove edge features from the trunk while preserving them on access ports.
OSPF Network Types: DR/BDR, Broadcast vs P2P
Hands-on CCNP OSPF lab comparing broadcast and point-to-point network types. Three routers share a multi-access Ethernet via an access switch to observe DR/BDR election, manipulate interface priorities, and then convert to point-to-point. Includes a user LAN behind R1 and realistic troubleshooting: neighbor stuck in 2-Way due to type mismatch, area mismatch isolating a router, and incorrect interface priority preventing desired DR/BDR roles.
OSPF Stub vs Totally-Stubby: Fault & Recovery
Deploy a compact enterprise multi-area OSPF with a backbone (area 0) and one branch area (area 10). You will configure area 10 as a stub, then transition it to a totally-stubby area from the ABR, validate reduced LSDB and routing tables, and simulate an operational fault (area mismatch) to diagnose adjacency loss and restore full transit. The lab uses three routers and two hosts to verify end-to-end reachability and real-world outcomes.
OSPF Inter-Area Summarization with ABR Area Range
Build a 5-node CML lab to design OSPFv2 across two areas with an ABR that summarizes non-backbone routes using area range. Validate adjacencies, end-to-end reachability, and that the backbone learns a single summary in place of specific inter-area routes. Intentionally introduce an area mismatch, diagnose why the adjacency does not form, and repair it.
