The quiet transit
The incident
Baltimore data center. Four routed leaves share two spines; clients and services use separate access handoffs while partner and monitoring traffic terminate on other leaves. Both service networks are unreachable after a configuration rollout. Restoring the service-edge neighbor alone does not restore every required flow. Investigate the two service networks from R1: 10.205.32.0/24 to 10.205.46.0/24 (TCP/443), and 10.205.33.0/24 to 10.205.47.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 R5 blocked from both service transports, keep SSH blocked to both service subnets, and preserve monitoring between R1 and R6. Do not change physical topology or addressing. These are network forwarding checks, not application-level transactions.
The network
Link addressing (10)
- R1 R2
10.205.48.0/30 - R2 R3
10.205.49.0/30 - R2 R4
10.205.50.0/30 - R5 R3
10.205.51.0/30 - R5 R4
10.205.52.0/30 - R6 R3
10.205.53.0/30 - R6 R4
10.205.54.0/30 - R7 R3
10.205.55.0/30 - R7 R4
10.205.56.0/30 - R7 R8
10.205.57.0/30
What you’ll practice
Interview exercises are inspired by common industry competencies. They are not proprietary interview questions.