Network Automation Concepts

You need to add a new VLAN to 40 access switches. Manually, that's 40 SSH sessions, 40 config edits, and 40 opportunities to typo the VLAN ID. It's also 40 chances to forget one switch — which gets discovered a week later when a user on that switch complains. Automation turns 40 sessions into one task that runs identically on all 40 devices and reports success or failure per device.

Network automation is the practice of using software to configure, manage, and operate network devices instead of doing it manually. It's not about eliminating engineers — it's about letting engineers focus on design and exceptions while software handles the repetitive, deterministic work.

#Why Automation Matters#link

• ▪Consistency — every device gets the same configuration, no drift
• ▪Speed — 40 devices in minutes instead of hours
• ▪Auditability — every change is logged, reviewed, and version-controlled
• ▪Reliability — no typos, no missed steps, no 'I forgot one switch'
• ▪Scalability — manage 5,000 devices with the same effort as 50
• ▪Repeatability — the same input always produces the same output

#Configuration Management vs Orchestration#link

Configuration management is 'make these devices look like this.' Orchestration is 'accomplish this business outcome, involving multiple systems.' A well-designed workflow combines both — orchestration calls configuration management tasks, which call device APIs or CLI. The orchestrator handles ordering, error handling, and rollback.

#The Modern Automation Toolchain#link

• ▪Ansible — agentless, YAML-based configuration management
• ▪Python — scripting language for custom automation and API interactions
• ▪REST APIs — programmatic interface to network devices and controllers
• ▪NETCONF/YANG — model-driven configuration (structured data, not CLI)
• ▪RESTCONF — RESTful interface to YANG models over HTTPS
• ▪Git — version control for config templates and playbooks
• ▪CI/CD — pipelines that test and deploy changes automatically

#Check Your Understanding#link