HomeIncident briefing
Back to the library
INCIDENT #011 · ROUTING

Warehouse scanners offline

Easy15 minutesPro lab

The incident

Memphis warehouse. Two transit stages separate the branch from its service gateway. The primary service cannot be reached from either half of the client subnet. The secondary service and monitoring destination are still reachable. Investigate the two service networks from R1: 10.202.96.0/24 to 10.202.102.0/24 (TCP/443), and 10.202.97.0/24 to 10.202.103.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 topology4 devices 3 links

Warehouse scanners offline — network topologyR1: Branch edge. R2: Access handoff. R3: Service transit. R4: Service gateway. R1 connects to R2. R2 connects to R3. R3 connects to R4. Connections show physical links, not service health.R1 ↔ R2 · 10.202.112.0/30R2 ↔ R3 · 10.202.113.0/30R3 ↔ R4 · 10.202.114.0/30R1Branch edgeR1 · Branch edge · Starting deviceR2Access handoffR2 · Access handoffR3ServicetransitR3 · Service transitR4ServicegatewayR4 · Service gateway
Physical links · Service health not shown
Link addressing (3)
  • R1 R210.202.112.0/30
  • R2 R310.202.113.0/30
  • R3 R410.202.114.0/30
4 devices · Cisco IOS syntax · Simulated network

What you’ll practice

static routingroute lookupchange validation

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