HomeIncident briefing
Back to the library
INCIDENT #205 · ROUTING

Industrial campus: The second client subnet gets no reply

Hard25 minutesPro lab

The incident

Engineering stations reach plant service gateways through the site core and two production aggregation layers. Four routed metro nodes form a ring; the service gateway has a separate handoff. Requests reach both service networks, but the second client subnet cannot receive replies. The first client subnet still works. Investigate plant gateway transport from R2: 10.176.130.0/24 to 10.176.136.0/24 (TCP/502), and 10.176.131.0/24 to 10.176.137.0/24 (TCP/4840).

Your objective

Restore both authorized service transports and return reachability, including clients and service hosts in both halves of the primary subnet. Keep R3 blocked from both service transports, keep SSH blocked to both service subnets, and preserve monitoring between R2 and R1. Do not change physical topology or addressing. These are network forwarding checks, not application-level transactions.

The network

Network topology5 devices 5 links

Industrial campus: The second client subnet gets no reply — network topologyR1: West metro. R2: Client metro. R3: South metro. R4: East metro. R5: Service gateway. R1 connects to R2. R2 connects to R3. R3 connects to R4. R4 connects to R1. R4 connects to R5. Connections show physical links, not service health.R1 ↔ R2 · 10.176.144.0/30R2 ↔ R3 · 10.176.145.0/30R3 ↔ R4 · 10.176.146.0/30R4 ↔ R1 · 10.176.147.0/30R4 ↔ R5 · 10.176.148.0/30R1West metroR1 · West metroR2Client metroR2 · Client metro · Starting deviceR3South metroR3 · South metroR4East metroR4 · East metroR5ServicegatewayR5 · Service gateway
Physical links · Service health not shown
5 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.