Why automate networks?
Manual CLI doesn't scale. Network automation reduces error, accelerates change, and enables consistency at scale. This chapter introduces the why and the high-level patterns: configuration management, intent-based, GitOps.
What you'll learn
- Spot the four ways hand-typed changes go wrong at scale — drift, delay, no audit trail, copy-paste mistakes.
- Define configuration management, infrastructure as code, and intent-based networking.
- Recognize the trade-off between flexibility and consistency.
What manual CLI gets wrong at scale
Picture one change: add a logging server to 200 access switches. By hand that is 200 SSH sessions. At three minutes each it is ten hours of typing, and if one session in a hundred goes wrong (a typo, a skipped line, the wrong switch), two switches end up different from the rest. Nobody notices until the day those logs are needed.
- Drift — small inconsistent changes accumulate across devices over time.
- Latency — operator-by-operator changes take days for simple rollouts.
- Audit — who changed what, when? Often impossible to answer.
- Repeatability — copy-paste mistakes when applying the same change to 200 switches.
Automation patterns
Automation replaces the typing with two things: a written description of what every device should look like, kept in one place, and a tool that makes each device match it. The four common patterns differ in what they describe and in who applies it.
- Configuration management — Ansible pushes over SSH; Puppet and Chef agents pull from their server; all apply declarative configs.
- Infrastructure as Code — Terraform / Pulumi versioned in git, applied with one command.
- Intent-based networking — declare what you want; controller computes the device-by-device steps.
- GitOps — git is the source of truth; CI pipeline applies merged changes to devices.
7 more sections in this chapter, plus a 4-question quiz.
Modules 2–8 are part of the Course & Lab Pass and All-Access Max — start with a free account
You can see the title, summary, learning objectives and the opening sections. The rest of this chapter, like all of modules 2–8, comes with the Course & Lab Pass and All-Access Max. A free account opens Module 1: How Networks Work end-to-end and saves your labs — start there, no card required.
- Read every chapter in Module 1 — How Networks Work
- Save labs of up to 5 devices
- Save up to 3 topologies
- See the full course syllabus + chapter titles
Free account · no card required · compare plans any time