Yasin Engin OMU Computer Engineering
CCNP Labs - Enterprise Networking Practice
A practical certification and engineering lab track for routing, switching, troubleshooting, and automation habits.
Problem
Certification notes are useful, but they become stronger when they are connected to real configuration files, troubleshooting paths, and repeatable labs. This project turns CCNP Enterprise study into an engineering workflow instead of a passive reading list.
Architecture
The lab repository is organized around topics, topology notes, device configurations, verification commands, troubleshooting steps, and automation scripts. The important pattern is traceability: concept, config, validation, and lesson learned should stay together.
Technologies
- Cisco IOS configuration practice for routing and switching.
- GNS3-style lab topology planning and validation.
- Python and automation scripts for repeatable checks.
- Structured notes for CCNP Enterprise learning and review.
What I Built
- CCNP lab note structure with topic-based configuration references.
- Repository-backed learning material for repeated review.
- Automation-oriented habit of checking configs and outputs systematically.
- Portfolio-linked project structure for connecting CCNP labs with broader network automation work.
Screenshots / Diagrams
GitHub Repository
What I Learned
- Lab notes are more valuable when each command has a reason and a verification step.
- Certification study can reinforce production habits: document, validate, and troubleshoot systematically.
- Automation becomes easier when manual verification is already structured.
Future Improvements
- Add topology diagrams for each major CCNP topic.
- Add automated config linting and command-output snapshots.
- Connect CCNP labs to network automation examples from the SR Linux lab track.