HomeIncident briefing
Back to the library
INCIDENT #090 · OSPF

Campus: A healthy control plane hides a dropped host

Hard25 minutesPro lab

The incident

Staff workstations reach the student services platform through the campus distribution layer. Four routed metro nodes form a ring; the service gateway has a separate handoff. OSPF neighbors and the service /24 route look healthy, but one host at .10 is unreachable. Another host in the same subnet responds. Investigate student services from R2: 10.162.34.0/24 to 10.162.40.0/24 (TCP/443), and 10.162.35.0/24 to 10.162.41.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 R3 blocked from both service transports, keep SSH blocked to both service subnets, and preserve monitoring between R2 and R1. Do not change physical topology or addressing. These are network forwarding checks, not application-level transactions.

The network

Network topology5 devices 5 links

Campus: A healthy control plane hides a dropped host — network topologyR1: West metro. R2: Client metro. R3: South metro. R4: East metro. R5: Service gateway. R1 connects to R2. R2 connects to R3. R3 connects to R4. R4 connects to R1. R4 connects to R5. Connections show physical links, not service health.R1 ↔ R2 · 10.162.48.0/30R2 ↔ R3 · 10.162.49.0/30R3 ↔ R4 · 10.162.50.0/30R4 ↔ R1 · 10.162.51.0/30R4 ↔ R5 · 10.162.52.0/30R1West metroR1 · West metroR2Client metroR2 · Client metro · Starting deviceR3South metroR3 · South metroR4East metroR4 · East metroR5ServicegatewayR5 · Service gateway
Physical links · Service health not shown
5 devices · Cisco IOS syntax · Simulated network

What you’ll practice

ospf routinglongest prefix matchcontrol vs data plane

Interview exercises are inspired by common industry competencies. They are not proprietary interview questions.