HomeIncident briefing
Back to the library
INCIDENT #024 · ROUTING

Half a connection

Hard25 minutesPro lab

The incident

Las Vegas office. A metro ring feeds a separate aggregation router and service gateway rather than attaching the service directly to the ring. Requests reach both service networks, but the second client subnet cannot receive replies. The first client subnet still works. Investigate the two service networks from R1: 10.204.0.0/24 to 10.204.10.0/24 (TCP/443), and 10.204.1.0/24 to 10.204.11.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 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

Network topology6 devices 6 links

Half a connection — network topologyR1: Client metro. R2: South metro. R3: Southeast metro. R4: Service metro. R5: Service aggregation. R6: Service gateway. R1 connects to R2. R2 connects to R3. R3 connects to R4. R4 connects to R1. R4 connects to R5. R5 connects to R6. Connections show physical links, not service health.R1 ↔ R2 · 10.204.16.0/30R2 ↔ R3 · 10.204.17.0/30R3 ↔ R4 · 10.204.18.0/30R4 ↔ R1 · 10.204.19.0/30R4 ↔ R5 · 10.204.20.0/30R5 ↔ R6 · 10.204.21.0/30R1Client metroR1 · Client metro · Starting deviceR2South metroR2 · South metroR3SoutheastmetroR3 · Southeast metroR4Service metroR4 · Service metroR5ServiceaggregationR5 · Service aggregationR6ServicegatewayR6 · Service gateway
Physical links · Service health not shown
6 devices · Cisco IOS syntax · Simulated network

What you’ll practice

return pathstatic routingbidirectional verification

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