Network Automation Overview

Watch first

Plain-English explanation

Network automation replaces repetitive CLI with programmatic, repeatable changes — scripts, APIs, and templates. Instead of typing the same VLAN on fifty switches, you declare desired state once and tooling applies it consistently.

Controller-based networking centralizes policy — Cisco DNA Center, Meraki dashboard, WLC — while devices still forward packets locally. SDN separates control plane (brain) from data plane (forwarding) conceptually; CCNA tests vocabulary more than building SDN.

Deep dive

Traditional vs automated:

| Traditional | Automated | |-------------|-----------| | Manual CLI per device | API/SSH scripts, templates | | Drift over time | Version-controlled configs | | Slow at scale | Bulk changes in minutes | | Human copy-paste errors | Validated pipelines |

API directions:

• Southbound — controller to devices (NETCONF, RESTCONF, SNMP, CLI scraping)
• Northbound — consumer apps to controller (REST APIs exposing network intent)

IaC (Infrastructure as Code): Treat configs like software — Git history, review, rollback. Ansible and Terraform appear in Week 10.

Automation benefits: speed, consistency, audit trail, less human error. Risks: bad script scales mistakes fast — test in lab first.

Step-by-step — simple automation mindset

Goal: Ensure NTP on 20 routers.

1. Inventory — list devices and IPs in YAML or CSV
2. Template — Jinja template with ntp server {{ ntp_ip }}
3. Tool — Ansible playbook loops inventory
4. Validate — show ntp status on sample devices
5. Version control — commit playbook to Git

You won't build full pipelines on CCNA exam — but you will recognize the pattern.

Commands to know

show run | section ntp
show inventory
show version

Troubleshooting

| Automation issue | Human equivalent | |------------------|------------------| | Auth failure | Wrong credentials, SSH key, API token | | Partial deploy | Timeout, ACL blocking API port | | Config not applied | Wrong device group, dry-run left on | | Drift returns | Manual CLI changes outside automation |

Automation doesn't remove need to read show commands — it changes how configs get there.

Exam relevance

Practice checklist

• Define southbound vs northbound with one example each
• List three benefits and one risk of automation
• Explain why Git matters for network configs
• Identify controller vs autonomous AP management overlap from Week 8
• Preview REST/JSON lesson next