HomeIncident briefing
Back to the library
INCIDENT #066 · OSPF

The advertised network misses the actual loopback

Hard25 minutesPro lab

The incident

The secondary application subnet is connected on R3 and all transit neighbors are healthy, but the subnet is not learned on R1. Check whether the routing statement actually matches an interface.

Your objective

Restore the documented flows for 10.146.31.0/24, including the return path to the affected client. Preserve the other service branch, all transit links, and SSH isolation. Do not change interface addresses or the physical topology.

The network

Network topology4 devices 3 links

The advertised network misses the actual loopback — network topologyR1: Client edge. R2: Transit core. R3: Application edge. R4: Telemetry edge. R1 connects to R2. R2 connects to R3. R2 connects to R4. Connections show physical links, not service health.R1 ↔ R2 · 10.146.12.0/30R2 ↔ R3 · 10.146.23.0/30R2 ↔ R4 · 10.146.24.0/30R1Client edgeR1 · Client edge · Starting deviceR2Transit coreR2 · Transit coreR3ApplicationedgeR3 · Application edgeR4Telemetry edgeR4 · Telemetry edge
Physical links · Service health not shown
4 devices · Cisco IOS syntax · Simulated network

What you’ll practice

ospf advertisementchange validation

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