Network Automation

Network Automation — CCNA 200-301 Study Lesson Network automation makes up 10% of the CCNA 200-301 exam and is entirely conceptual — there are no CLI simulations, only multiple-choice and drag-and-drop questions, making this one of the highest return-on-investment chapters to study efficiently. --- ## Why Networks Need Automation Traditionally, network engineers configured every device manually via CLI — one command at a time, one device at a time. As networks scaled to hundreds or thousands of devices, this approach became error-prone, slow, and impossible to audit reliably. Network automation replaces or supplements manual CLI work with programmatic tools and controllers that can configure, monitor, and troubleshoot many devices simultaneously, consistently, and repeatably. Key benefits of automation: - Eliminates human error from repetitive configuration tasks - Enables version control for network configurations (treat config like code) - Supports intent-based networking — define *what* you want, not *how* to do it - Reduces mean time to repair (MTTR) through faster, consistent changes --- ## Controller-Based Networking and SDN Software-Defined Networking (SDN) separates the control plane (decisions about where traffic goes) from the data plane (actually forwarding the traffic). A central controller makes forwarding decisions and pushes them to devices. ### API Planes | Plane | Direction | Purpose | Example | |-------|-----------|---------|---------| | Northbound API | Controller → Applications | Apps talk to the controller | REST API calls from automation scripts | | Southbound API | Controller → Devices | Controller programs network devices | NETCONF, OpenFlow, RESTCONF | Cisco Catalyst Center (formerly DNA Center) is Cisco's primary SDN controller for enterprise networks. It provides a GUI and REST API for network-wide configuration and assurance. Cisco SD-WAN extends SDN…