π Scenario
User reports: βApplication is down (app.local not working)β
π― Goal
Quickly identify whether the issue is:
- DNS
- Network (IP / routing)
- VLAN / switching
- Server / application
π Step-by-Step Troubleshooting
1. Check DNS Resolution
ping app.local
Result:
- β Fails β possible DNS issue
- β Works β DNS is OK β go to Step 2
2. Check IP Connectivity
ping 192.168.50.10
Result:
- β Fails β network/routing problem
- β Works β network OK β go to Step 3
3. Verify IP Configuration (Client)
ipconfig
Check:
- IP address assigned?
- Correct subnet?
- Gateway present?
- DNS server present?
Common issues:
- No IP β DHCP failure
- Wrong subnet β VLAN issue
- Missing DNS β DHCP misconfig
4. Check Default Gateway
ping 192.168.X.1
(X = client VLAN)
Result:
- β Fails β VLAN / switch / trunk issue
- β Works β gateway OK β continue
5. Check Server Reachability
ping 192.168.50.10
If fails:
- Server down
- VLAN 50 issue
- Routing issue
6. Check Server Services
On Server:
- DNS β ON
- HTTP β ON
Test:
Browser:
http://192.168.50.10
7. Check VLAN Configuration
On Switch:
show vlan brief
Verify:
- PC ports in correct VLAN
- Server in VLAN 50
8. Check Trunk Links
show interfaces trunk
Verify:
- VLANs 10,20,30,50 allowed
- trunk is active
9. Check Routing (Router)
show ip interface brief
Verify:
- g0/0.10 β 192.168.10.1
- g0/0.20 β 192.168.20.1
- g0/0.30 β 192.168.30.1
- g0/1.50 β 192.168.50.1
10. Check DHCP Relay
show run | include helper
Verify:
ip helper-address 192.168.50.10
π§ Root Cause Mapping
| Symptom | Likely Issue |
|---|---|
| ping app.local fails, IP works | DNS issue |
| no IP assigned | DHCP issue |
| gateway unreachable | VLAN/trunk issue |
| server unreachable | routing or VLAN 50 issue |
| IP works, app fails | application/service issue |
β‘ Quick Diagnosis Flow
- DNS?
- IP?
- Gateway?
- Server?
- VLAN?
- Routing?
π‘ SRE Insight
Always troubleshoot layer by layer:
- DNS
- Network
- Routing
- Application
Never jump randomly β follow the chain.
Top comments (0)