Service edge: The service edge stops exchanging BGP routes
The incident
Internal API clients and an independent observability edge share a transit network with an isolated partner segment. A metro ring feeds a separate aggregation router and service gateway rather than attaching the service directly to the ring. Direct uplink connectivity works, but remote routers no longer learn either service prefix from the service edge. Investigate internal API transport from R1: 10.172.96.0/24 to 10.172.106.0/24 (TCP/8443), and 10.172.97.0/24 to 10.172.107.0/24 (TCP/443).
Your objective
Restore both authorized service transports and return reachability, including clients and service hosts in both halves of the primary subnet. Keep R2 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
Link addressing (6)
- R1 R2
10.172.112.0/30 - R2 R3
10.172.113.0/30 - R3 R4
10.172.114.0/30 - R4 R1
10.172.115.0/30 - R4 R5
10.172.116.0/30 - R5 R6
10.172.117.0/30
What you’ll practice
Interview exercises are inspired by common industry competencies. They are not proprietary interview questions.