Regional operations: Neighbor recovery is only the first repair
The incident
Operations collectors reach polling and trap-receiver networks over three routed transport stages. Three two-hop regional branches meet at one interchange, separating client, service and partner traffic. Both service networks are unreachable after a configuration rollout. Restoring the service-edge neighbor alone does not restore every required flow. Investigate monitoring transport from R1: 10.169.192.0/24 to 10.169.200.0/24 (UDP/161), and 10.169.193.0/24 to 10.169.201.0/24 (UDP/162).
Your objective
Restore both authorized service transports and return reachability, including clients and service hosts in both halves of the primary subnet. Keep R7 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 (6)
- R1 R2
10.169.208.0/30 - R2 R3
10.169.209.0/30 - R3 R4
10.169.210.0/30 - R4 R5
10.169.211.0/30 - R3 R6
10.169.212.0/30 - R6 R7
10.169.213.0/30
What you’ll practice
Interview exercises are inspired by common industry competencies. They are not proprietary interview questions.