Domain 6Automation & ProgrammabilityCORE

Network Automation Concepts

The impact of automation on network management, comparing traditional manual configurations with automated orchestration and scalability.

Domain: Domain 6: Automation and Programmability•Updated: 2026-08-26
#Automation#Manual vs Auto#Orchestration#Network Management#Scalability

Network Automation (CCNA 200-301 Section 6.0)

Introduction to Network Automation

  • Concept: Network automation replaces manual, device-by-device CLI management with programmatic, scalable solutions. The CCNA exam (10% of total) focuses on the ability to explain, compare, describe, recognize, and interpret automation concepts, not hands-on scripting.
  • Traditional Model Downsides:
    • High risk of human error (e.g., typos in IP addresses).
    • Time-consuming and inefficient for large-scale networks.
    • Configuration drift: Individual manual changes cause devices to deviate from organizational standard configuration templates, complicating troubleshooting.
  • Automation Benefits:
    • Reduced human error: Eliminates manual CLI typos.
    • Increased scalability: Network-wide changes and deployments happen in a fraction of the time.
    • Policy compliance: Ensures all devices adhere to standard configurations and software versions.
    • Reduced OpEx (Operating Expenses): Fewer man-hours required, freeing engineers for higher-value tasks.
  • Common Automation Tools: SDN, Ansible, Puppet, Python scripts.

Logical Planes of Network Functions

  • Concept: Router and switch functions are logically categorized into three distinct “planes” to understand how traffic is processed and managed.
  • Details:
Plane Function Examples Traffic Type
Data Plane (Forwarding Plane) Forwards user data from one interface to another based on tables. Routing table lookup, MAC address table lookup, NAT, ACL filtering, 802.1Q tagging. Transit traffic (passing through the device).
Control Plane Builds and maintains the tables used by the data plane. Considered “overhead” work. OSPF, STP, ARP, building routing/MAC/ARP tables. Control traffic (destined for or generated by the device to manage forwarding).
Management Plane Protocols used to manage, monitor, and configure the device itself. Does not directly affect data forwarding. SSH, Telnet, Syslog, SNMP, NTP. Management traffic (destined to the device for administration).
  • Hardware Acceleration (Data Plane):
    • CPU: Processes Control and Management plane traffic. Too slow for high-speed data plane forwarding.
    • ASIC (Application-Specific Integrated Circuit): Specialized hardware chips designed for ultra-fast data plane forwarding logic (e.g., switching frames).
    • TCAM (Ternary Content-Addressable Memory): Specialized memory allowing extremely fast, parallel lookups for MAC addresses (also known as CAM or Content-Addressable Memory table) and routing entries.
graph TD
    A[Incoming Traffic] --> B{Destination IP/MAC?}
    B -->|Device Itself| C[CPU Processing]
    C --> D[Control Plane: OSPF, STP, ARP]
    C --> E[Management Plane: SSH, SNMP, NTP, Syslog]
    B -->|Passing Through| F[ASIC Processing]
    F --> G[TCAM Lookup]
    G --> H[Data Plane: Forward/Drop]

Things to note: A common misconception is that switches only forward Layer 2 frames. They also run control plane protocols (STP) and management plane protocols (SSH, Syslog). Layer 3 switches run routing protocols (OSPF) just like routers.

Software-Defined Networking (SDN)

  • Concept: An architectural approach that centralizes the control plane into a software application called a Controller (also known as Software-Defined Architecture or Controller-based networking).
  • Details:
    • Traditional Networking: Distributed control plane. Every router runs OSPF, calculates its own routes, and maintains its own routing table.
    • SDN: Centralized control plane. The controller calculates routes and programs the data plane tables of the network devices directly. The devices primarily act as simple forwarding engines (similar to Lightweight APs in a Wireless LAN Controller architecture).
graph TD
    subgraph Traditional Network
        R1_T[Router 1: Data + Control Plane] <-->|OSPF| R2_T[Router 2: Data + Control Plane]
    end
    
    subgraph SDN Architecture
        App[Applications] -->|NBI| Controller[SDN Controller<br/>Centralized Control Plane]
        Controller -->|SBI| R1_S[Router 1: Data Plane Only]
        Controller -->|SBI| R2_S[Router 2: Data Plane Only]
    end

SDN Interfaces and APIs

  • Concept: Software interfaces (code, not physical ports) that facilitate programmatic communication between different components of the SDN architecture.
  • Details:
    • API (Application Programming Interface): A set of rules that allows different software programs to exchange data.
    • SBI (Southbound Interface): Communication between the Controller and the Network Devices (drawn at the “south” of the controller in diagrams).
      • Examples: OpenFlow, Cisco OpFlex, Cisco onePK, NETCONF.
    • NBI (Northbound Interface): Communication between Applications and the Controller (drawn at the “north”). Allows apps to request data or push configuration changes to the controller.
      • Examples: REST API (Representational State Transfer).
    • Data Serialization: The process of structuring data into a standard format that is easy for programs to parse and interact with.
      • JSON (JavaScript Object Notation)
      • XML (Extensible Markup Language)

Things to note: REST is not a specific API, but a type or architectural style of API. An app might send an HTTP GET request via a REST API, and the controller replies with network topology data formatted in JSON or XML.

Traditional Scripting vs. SDN Automation

Feature Traditional Scripting (e.g., Python) SDN Architecture
Data Collection SSH into each device individually; run show commands. Controller maintains a centralized, real-time, network-wide view.
Data Parsing Requires Regular Expressions (Regex) to parse human-readable CLI output (e.g., finding “BW 1000000 Kbit” in show interfaces). Data is natively provided in machine-readable, structured formats (JSON/XML) via NBIs. No Regex needed.
Expertise Required Requires scripting and Regex programming knowledge. Many SDN tools provide GUIs; scripting is optional (though powerful via APIs).
Analytics Difficult; requires correlating data manually from multiple devices. Built-in, centralized network-wide analytics.

Practice Questions Analysis

  1. Which of the following are benefits of network automation? (Select two)
    • Answer: Reduced human error, Reduced OpEx. (Automation eliminates manual CLI typos and reduces the man-hours required for tasks).
  2. Which of the following are SBIs? (Select two)
    • Answer: OpenFlow, OpFlex. (Others include Cisco onePK and NETCONF).
  3. Which of the following network functions would you expect to be centralized in SDN?
    • Answer: Calculating routes. (This is a Control Plane function. Forwarding messages, NAT, and ACL filtering are Data Plane functions and remain distributed on the devices).
  4. What is the purpose of the SBI in SDN architecture?
    • Answer: To facilitate data exchange between the controller and network devices. (The NBI facilitates exchange between the controller and apps).
  5. Which of the logical planes of networking does NTP’s function fit in?
    • Answer: Management plane. (NTP maintains accurate time for device management/logging; it does not forward data or build forwarding tables).

Command Reference

! Traditional CLI command often parsed by automation scripts
Router# show interfaces
! Example output snippet parsed by Regex:
!   BW 1000000 Kbit/sec, DLY 1000 usec,

Things to note: While the CCNA does not require you to write Python scripts, you must recognize that traditional automation relies on parsing human-readable CLI outputs (like show interfaces), whereas modern SDN/API automation relies on structured data (JSON/XML).