HomeIncident briefing
Back to the library
INCIDENT #086 · ROUTING

Campus: Both services fail after route cleanup

Hard30 minutesPro lab

The incident

Staff workstations reach the student services platform through the campus distribution layer. Independent north and south core paths connect the ingress and egress routers. Both service subnets stopped responding after a route cleanup. Monitoring traffic still succeeds and the client route table is not empty. Investigate student services from R1: 10.161.160.0/24 to 10.161.170.0/24 (TCP/443), and 10.161.161.0/24 to 10.161.171.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 R1 and R4. Do not change physical topology or addressing. These are network forwarding checks, not application-level transactions.

The network

Network topology6 devices 6 links

Campus: Both services fail after route cleanup — network topologyR1: Client edge. R2: Ingress. R3: North core. R4: South core. R5: Egress. R6: Service gateway. R1 connects to R2. R2 connects to R3. R2 connects to R4. R3 connects to R5. R4 connects to R5. R5 connects to R6. Connections show physical links, not service health.R1 ↔ R2 · 10.161.176.0/30R2 ↔ R3 · 10.161.177.0/30R2 ↔ R4 · 10.161.178.0/30R3 ↔ R5 · 10.161.179.0/30R4 ↔ R5 · 10.161.180.0/30R5 ↔ R6 · 10.161.181.0/30R1Client edgeR1 · Client edge · Starting deviceR2IngressR2 · IngressR3North coreR3 · North coreR4South coreR4 · South coreR5EgressR5 · EgressR6ServicegatewayR6 · Service gateway
Physical links · Service health not shown
6 devices · Cisco IOS syntax · Simulated network

What you’ll practice

summary routeslongest prefix matchsafe remediation

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