HomeIncident briefing
Back to the library
INCIDENT #211 · OSPF

Industrial campus: Neighbor recovery is only the first repair

Expert35 minutesPro lab

The incident

Engineering stations reach plant service gateways through the site core and two production aggregation layers. A partner branch shares the aggregation router but not the service handoff. Both service networks are unreachable after a configuration rollout. Restoring the service-edge neighbor alone does not restore every required flow. Investigate plant gateway transport from R1: 10.177.64.0/24 to 10.177.70.0/24 (TCP/502), and 10.177.65.0/24 to 10.177.71.0/24 (TCP/4840).

Your objective

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

The network

Network topology5 devices 4 links

Industrial campus: Neighbor recovery is only the first repair — network topologyR1: Branch edge. R2: Aggregation. R3: Service handoff. R4: Service gateway. R5: Partner edge. R1 connects to R2. R2 connects to R3. R3 connects to R4. R2 connects to R5. Connections show physical links, not service health.R1 ↔ R2 · 10.177.80.0/30R2 ↔ R3 · 10.177.81.0/30R3 ↔ R4 · 10.177.82.0/30R2 ↔ R5 · 10.177.83.0/30R1Branch edgeR1 · Branch edge · Starting deviceR2AggregationR2 · AggregationR3ServicehandoffR3 · Service handoffR4ServicegatewayR4 · Service gatewayR5Partner edgeR5 · Partner edge
Physical links · Service health not shown
5 devices · Cisco IOS syntax · Simulated network

What you’ll practice

ospf adjacencyospf advertisementcompound failures

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