HomeDaily challenge
DAILY PRACTICE

Daily challenge

One free incident for everyone. Inspect the network, make your repair, and submit it for verification.

Resets at 00:00 UTC
INCIDENT #009OSPFEasy

Everyone is a neighbor

Portland lab. Each of three routed leaves connects to both spines. Partner monitoring and service gateways sit behind different leaves. OSPF neighbors are established and the primary service works. Only the secondary service prefix is missing from remote route tables. Investigate the two service networks from R1: 10.202.32.0/24 to 10.202.42.0/24 (TCP/443), and 10.202.33.0/24 to 10.202.43.0/24 (TCP/8443).

Your objective

Restore both authorized service transports and return reachability, including clients and service hosts in both halves of the primary subnet. Keep R4 blocked from both service transports, keep SSH blocked to both service subnets, and preserve monitoring between R1 and R7. Do not change physical topology or addressing. These are network forwarding checks, not application-level transactions.

About 15 minutes · Free practice

Free to practice. No account required.

Read the full briefing

The network you’ll work on

Network topology7 devices 8 links

Everyone is a neighbor — network topologyR1: Client leaf. R2: Spine A. R3: Spine B. R4: Partner leaf. R5: Service leaf. R6: Service gateway. R7: Monitoring edge. R1 connects to R2. R1 connects to R3. R4 connects to R2. R4 connects to R3. R5 connects to R2. R5 connects to R3. R5 connects to R6. R4 connects to R7. Connections show physical links, not service health.R1 ↔ R2 · 10.202.48.0/30R1 ↔ R3 · 10.202.49.0/30R4 ↔ R2 · 10.202.50.0/30R4 ↔ R3 · 10.202.51.0/30R5 ↔ R2 · 10.202.52.0/30R5 ↔ R3 · 10.202.53.0/30R5 ↔ R6 · 10.202.54.0/30R4 ↔ R7 · 10.202.55.0/30R1Client leafR1 · Client leaf · Starting deviceR2Spine AR2 · Spine AR3Spine BR3 · Spine BR4Partner leafR4 · Partner leafR5Service leafR5 · Service leafR6ServicegatewayR6 · Service gatewayR7MonitoringedgeR7 · Monitoring edge
Physical links · Service health not shown
Link addressing (8)
  • R1 R210.202.48.0/30
  • R1 R310.202.49.0/30
  • R4 R210.202.50.0/30
  • R4 R310.202.51.0/30
  • R5 R210.202.52.0/30
  • R5 R310.202.53.0/30
  • R5 R610.202.54.0/30
  • R4 R710.202.55.0/30

7 routers · Browser terminal · Cisco IOS syntax

  1. InspectRun show commands and trace the affected path.
  2. RepairEdit the configuration while preserving working connections.
  3. VerifySubmit your diagnosis and repair. Network tests confirm whether the fault is fixed and working services are preserved.

A lab from the free library is featured each day at midnight UTC. Take your time reading the brief; your session starts when you select Start daily lab. Each attempt has its own time limit.

New here? Learn how labs work