Projects › Monday-Morning Broken Network: Work the Ticket Queue
Monday-Morning Broken Network: Work the Ticket Queue
You are the on-call engineer at a regional distributor. A weekend change window went badly and Monday opened with twelve tickets: users who cannot reach the file server, a branch that is offline, a warehouse that lost its scanners, an audit finding, two NOC alerts and an internet outage. Every ticket is a symptom; the faults behind them run from a shut port to a swapped NAT boundary. Work the queue from the symptom to the root cause, fix each one without breaking anything that still worked, and close it.
Difficulty: expert · Time: about 120 minutes
Why it matters
Troubleshooting is the skill most network job postings ask for, and the interview question is always "tell me about something you fixed". This is that story twelve times over, across every layer the sandbox models, with a regression check that holds you to the rule every change board has: leave it better, never worse.
Technologies
- Troubleshooting
- VLANs
- 802.1Q Trunking
- HSRP
- OSPFv2
- Static Routing
- Access Lists
- NAT
- PAT
Related projects
- Dual-Stack Collapsed-Core Campus with Per-VLAN Root Placement
- Campus Gateway High Availability with HSRPv2 and Uplink Tracking
- Campus Automation & Assurance Deployment via Catalyst Center
- Cross-Switch LACP EtherChannel & PortFast BPDU Guard
- Enterprise Wireless LAN with Catalyst 9800 WLC & FlexConnect
- Network Observability: Secure SNMPv3, Remote Syslog, and Flexible NetFlow
- IPv6-Only Multi-Area OSPFv3 for a Research Campus
- Capstone: Multi-Tier Global Enterprise Network Architecture