03 / Cisco / competition

Turning a competition loss into Cisco IOS practice

I won SkillsUSA Florida Internetworking, then struggled at nationals. That experience showed me exactly where I needed more Cisco IOS practice.

Status
Training
Period
2026
Role
Competitor and lab author

Starting point

Where it started

Concept knowledge from certifications and homelab work did not automatically become fast, accurate configuration on a live console with a competition clock running.

What I did

What I worked on

  1. Named the constraint precisely: verification and configuration speed, not a broad lack of networking knowledge.
  2. Built blank, hinted, and answer-key versions of CML-friendly campus labs.
  3. Added dual-stack routing, VLANs, trunks, EtherChannel, DHCP, NAT/PAT, ACLs, OSPF, and structured fault tickets.
  4. Created show-command checklists, scoring rubrics, flashcards, and deliberate repetition plans.

Evidence

What I checked and recorded

Guided practice path

Built blank, hinted, and answer-key versions of a five-node CML-Free campus lab so configuration can be repeated without memorizing the answer file.

Break-fix coverage

Wrote five tickets covering DHCP failure, EtherChannel mismatch, NAT failure, a missing IPv6 route, and unreachable switch management.

Local validation record

Checked topology YAML for syntax, node and link consistency, duplicate IDs, and CML-Free compatibility, while documenting the limits of local validation.

Result

What changed

The competition result became a reusable learning system that turns “I understand it” into repeatable console fluency and better troubleshooting under pressure.

What I learned

What I took from it

  • A vague weakness is hard to train; a named constraint is actionable.
  • Verification commands should become muscle memory.
  • Strong technical stories include the gap, the response, and the evidence of growth.

Next case study / 04

A remote gateway for the AI tools I already use