CCNP VRF & GRE: Two Tenants, One Router
Two tenants share one edge router. Give each its own routing table, so both can use the same service address.
Free with an account
268 hands-on CCNA scenarios you build in your own Cisco Modeling Labs instance and grade against the answer key. Aligned to the CCNA certification track — exam-ready configuration and troubleshooting practice.
Included with a subscription
Two tenants share one edge router. Give each its own routing table, so both can use the same service address.
Free with an account
Building B came back from maintenance broken: staff PCs get no address and the kiosks can't reach their gateway.
A new building-systems VLAN has been provisioned. Carry it, route it and advertise it so its controllers reach the edge.
Finance must be walled off from general users. Write two filters and put each where its VLAN's traffic enters the switch.
The static routes are gone. Bring the distribution switch into OSPF so the campus and the edge learn each other.
Hosts now get their addresses from a server two hops away. Make the switch relay the requests and keep the gateway range out of the pools.
Connect the campus to the edge router over a routed link, and give traffic a way out and back.
The router-on-a-stick is gone. Turn the distribution switch into the gateway for both VLANs.
Free with an account
A full-path break/fix capstone for CCNA troubleshooting. A single floor was renumbered and re-cabled. Users on that floor cannot reach anything — not their default gateway, not other subnets, and not the internet. The change record mentions both the access switch and the internet edge. Your job: prove the path hop-by-hop from the client outward and repair every break. Fixing only one side does not change the symptom; both layers must be corrected.
A late-night rollback restored configs from before a WAN carrier change. Since then, both branches report OSPF neighbors that appear, start exchanging, and then reset—never reaching FULL. Users at Branch A cannot reach Branch B. Your task is to observe the partial adjacency behavior, isolate why the database exchange never completes, and restore the carrier’s standard everywhere it applies so reachability returns end-to-end.
Troubleshoot a dual-stack hub-and-spoke where IPv6 traffic never flowed after go-live. IPv4 works end-to-end, but IPv6 static routes are present in running-config and missing from the RIB. Compare configured vs installed routes, trace next-hop reachability per link, and correct the next-hop so each static becomes active. Validate from the user LAN.
Two internal subnets behind a branch router stopped working after a summarization tidy-up. Everything else inside the same /16 summary is fine, and the edge still has a discard route for the summary. Your job: trace which route each hop actually matches for those destinations, then restore reachability without removing or weakening the summary.
An office floor’s redundant default gateway pair keeps needing manual intervention. During an uplink outage the active gateway stays active and strands users, and when the repaired router returns it seizes the VIP immediately and the floor bounces. Troubleshoot the pair’s failover behavior by examining what each router monitors and when it is allowed to take the role back. Bring the pair into compliance with the convergence standard without changing anything else.
A DMZ server was rebuilt onto a new IP last week. Since then, outside users cannot open its three published services, while the server itself can browse out normally. Your job: work from the public address toward the inside, diagnose where the forwarding breaks, and republish all three services on the advertised public IP without disrupting outbound internet access.
Two sites have dual WAN links (primary and backup). Both circuits are up and end-to-end connectivity works, yet every intersite flow rides the slow backup path. Your job: read which routes each router actually installed for the opposite site and why, then restore the intended path preference so traffic uses the primary circuit while keeping the backup standing by.
An overnight hardening change reached the core but not the branches. By morning, both OSPF adjacencies to the core were down even though every point-to-point link still pings and no addressing changed. Restore end-to-end reachability by diagnosing what the core and each spoke now disagree about on the carrier-facing transits and finishing the change on the branch ends.
Daily CCNA troubleshooting repair: two branch floors were renumbered and now users report DHCP failures and no Internet access. Work end-to-end from each floor’s client to the WAN: trace DHCP pool-to-interface bindings, validate NAT policy per floor, and restore both floors so leases are issued from the new plan and both can reach the provider loopback.
A replacement branch router came up on three carrier handoffs. All subinterfaces and /30s look correct and line protocols are up, yet no traffic passes. Your job: read what each circuit actually puts on the wire and bring the branch into alignment with the remote ends — including the carrier-published IP MTU on one circuit — without altering addressing or static routes.
A security audit showed that routers accepted SSH from outside the management LAN despite an existing filter. Diagnose how the management ACL is bound to the VTY lines and make it govern which inbound sessions the routers accept, without breaking data-plane reachability.
A dual-stack static routing lab with a subtle IPv6-only failure. IPv4 reaches across the WAN from a branch PC to an HQ server and loopback, while IPv6 to the same destinations fails. The IPv6 addressing on interfaces is correct; the break lies elsewhere. Compare what IPv4 knows versus what IPv6 knows for the same four destinations and make IPv6 match the working IPv4 design.
Daily CCNA troubleshooting drill: Two branches can ping the core over their transit links, yet the core does not learn any branch routes. Your job is to trace how OSPF is enabled on each device, isolate why the core’s routing table is missing the branch LANs and loopbacks, and bring both branches into the correct OSPF area without changing how the core enables it.
Free with an account
A branch user in VLAN 10 cannot reach the data center's line-of-business server, stalling the end-of-day batch upload. Two faults sit behind the one complaint, and clearing either alone leaves the user where they started. The client gets no answer from its own gateway either.
Branch staff cannot reach the server at 172.16.100.100, and they cannot close a day's tickets without it. Policy also requires Telnet from the user LAN to that server be denied while everything else passes, and the security review cannot confirm it is being enforced. Work the path from a client and find what is wrong.
A branch reaches its provider through one edge router that hides the user LAN behind its upstream address. Since a change window, everyone on 192.168.10.0/24 reports that nothing beyond the branch answers, while the router itself reaches the provider's test address. Find what is wrong.
1Network Fundamentals20%
2Network Access20%
VLANs, Trunking & Inter-VLAN Routing · Spanning Tree (STP) · EtherChannel
VLAN labs (63) · EtherChannel labs (15)
3IP Connectivity25%
Static & Default Routing · OSPF · First-Hop Redundancy (HSRP & VRRP)
Static routing labs (37) · OSPF labs (37) · HSRP labs (13)
4IP Services10%
NAT & PAT · DHCP · Network Services & Management
NAT labs (21) · DHCP labs (17)
5Security Fundamentals15%
Access Control Lists (ACLs) · Device Security & SSH
6Automation and Programmability10%
No labs here — this domain is studied by reading, not by graded CLI labs.
Bundles: IP Addressing & Subnetting · VLANs & Network Segmentation · VLAN Trunking (802.1Q) · Inter-VLAN Routing · Spanning Tree Protocol (STP) · EtherChannel & Link Aggregation · Static & Default Routing · OSPF: Adjacency to Multi-Area Mastery · First-Hop Redundancy (HSRP & VRRP) · DHCP & Address Services · NAT & PAT · NTP & Network Time · Network Discovery & Monitoring · Access Control Lists (ACLs) · Switchport Port Security · Layer 2 Security Hardening · Device Hardening: SSH, AAA & Secure Access · CCNA Break/Fix II: Read the Symptom · CCNA Break/Fix: Diagnose and Repair · CCNA Layer 3 Switching: Route on the Switch
The CCNA exam rewards one thing above all: comfort on the command line. You can memorize the difference between a broadcast and a collision domain, but you pass — and keep the job the cert helps you land — by being able to configure VLANs, OSPF, ACLs, and static routing quickly and correctly, and to troubleshoot them when they break. These CCNA-aligned labs are built to give you that muscle memory.
Every lab in this track is a free-tier Cisco Modeling Labs topology you import in one click and build on real Cisco IOS — VLANs and trunking, inter-VLAN routing, single-area OSPFv2, standard and extended ACLs, static and default routing, and the day-two troubleshooting the exam loves. Build each one, verify it with the same show commands the exam expects, then upload your CML export for grading against the answer key so you know it's genuinely correct. Do a lab a day and the CCNA objectives stop being a reading list and become reps you can perform under time pressure.
They cover the hands-on configuration and troubleshooting objectives thoroughly, which is where most candidates are weakest. Pair them with a theory resource for the conceptual and subnetting questions and you have both halves of the exam covered.
No — just your own Cisco Modeling Labs instance. Every lab is a YAML package built on CML free-tier images (IOL/IOL-L2) that imports in one click.
Start with VLANs and static routing to get comfortable on the CLI, then move to OSPF and ACLs, then the troubleshooting labs. The daily cadence is designed so each lab builds on the last.
Looking for something else? Browse the full lab archive, narrow it to self-standing labs, see today's daily lab, or follow the CCNA study path.