Automation & SDN

Network Programmability & SD-WAN

Where the CLI era gives way to APIs and controllers: the automation stack — model-driven APIs, Python and Ansible — that treats network state as structured data, and Cisco SD-WAN, the controller-based overlay that replaced box-by-box WAN routing with centrally managed policy.

read in order, or dip in
2 chapters

read in order, or dip in

updated 31 Aug 2026
Free — no signup

updated 31 Aug 2026

Contents

  1. 01Network Automation: APIs, Python and the Model-Driven StackNetwork automation replaces per-box CLI sessions with programmatic interfaces: REST APIs and NETCONF/RESTCONF expose configuration and state as structured JSON or XML modelled in YANG, consumed from Python (requests, netmiko, ncclient) or declaratively through Ansible. The payoff is consistency at scale — intended state defined once, pushed everywhere, verified continuously.
  2. 02Cisco SD-WAN Architecture: vManage, vSmart and OMPCisco SD-WAN (Viptela) separates the WAN into four planes: vManage for management, vBond for zero-trust orchestration and device onboarding, vSmart controllers running OMP to distribute routes and policy, and WAN edge routers forwarding over IPsec tunnels across any transport. OMP advertises reachability, TLOCs and policy between edges and controllers, letting application-aware policy choose paths per traffic class instead of per destination.

Spotted something out of date? Tell us — this library is maintained by the faculty.