HomeIncident briefing
Back to the library
INCIDENT #095 · BGP

Campus: Export recovery leaves a return-path failure

Expert35 minutesPro lab

The incident

Staff workstations reach the student services platform through the campus distribution layer. Client, partner and service access branches attach to different vertices of a routed core triangle. Clients cannot reach the primary service. Restoring its BGP advertisement still leaves replies to one client address failing. Investigate student services from R1: 10.162.192.0/24 to 10.162.202.0/24 (TCP/443), and 10.162.193.0/24 to 10.162.203.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 R4 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 topology6 devices 6 links

Campus: Export recovery leaves a return-path failure — network topologyR1: Client edge. R2: Client core. R3: Partner core. R4: Partner edge. R5: Service core. R6: Service gateway. R1 connects to R2. R2 connects to R3. R3 connects to R5. R5 connects to R2. R3 connects to R4. R5 connects to R6. Connections show physical links, not service health.R1 ↔ R2 · 10.162.208.0/30R2 ↔ R3 · 10.162.209.0/30R3 ↔ R5 · 10.162.210.0/30R5 ↔ R2 · 10.162.211.0/30R3 ↔ R4 · 10.162.212.0/30R5 ↔ R6 · 10.162.213.0/30R1Client edgeR1 · Client edge · Starting deviceR2Client coreR2 · Client coreR3Partner coreR3 · Partner coreR4Partner edgeR4 · Partner edgeR5Service coreR5 · Service coreR6ServicegatewayR6 · Service gateway
Physical links · Service health not shown
6 devices · Cisco IOS syntax · Simulated network

What you’ll practice

bgp originationreturn pathcompound failures

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