Week 12 · Lesson 3

SDN Architecture: Control and Data Planes

Software-defined networking is the formal architecture behind controller-based networks. It defines clean layers, names the interfaces between them (northbound and southbound APIs), and introduces the modern data-centre design — a spine-leaf underlay with an overlay fabric built on VXLAN.

CCNA 200-301 Domain 6.0 Automation and Programmability Verified 2026-10-11
Part 1

What is SDN?

Software-defined networking (SDN) is an architecture that separates the network’s decision-making (control plane) from its forwarding (data plane), and exposes the decision-making through programmable interfaces. The word “software-defined” means the behaviour of the network is defined by software running in a controller, not hard-wired into each device’s firmware.

Definition — SDN. An architecture that centralises the control plane in a software controller and communicates with the data-plane devices through open APIs, making the network programmable.

SDN grew out of research (notably OpenFlow, from Stanford and the ONF) that wanted to make networks as easy to program as computers. The essential move is the same one from Lesson 2: centralise control, distribute forwarding. In a fully SDN architecture, the controller is the only place intelligence lives; devices are programmable forwarders.

Three ideas carry the whole architecture, and you will meet all three in every diagram this week: the planes (who decides, who forwards, who manages), the APIs that connect them (northbound and southbound), and the fabric (underlay plus overlay) that carries the traffic.

Part 2

Control, data, and management planes

SDN formalises the three planes we touched on earlier. Getting these straight is the most commonly tested part of this lesson.

PlaneJobExamples
ManagementConfigure, monitor, and manage the deviceSSH, SNMP, syslog, NETCONF/RESTCONF
ControlDecide where traffic goes; build forwarding tablesOSPF, EIGRP, BGP, STP, SDN controller
Data (forwarding)Move the actual user packets/framesASIC forwarding, switching, routing at line rate
Definition — management plane. The plane used by administrators and management tools to configure and monitor devices. It sits above the control plane and delivers policy and configuration into it.

The management plane is where your automation tools live. When Ansible or a Python script SSHes into a switch, or when a REST call configures a controller, that is management-plane traffic. SDN does not remove the management plane; it makes it programmable.

Exam tip. Keep the direction of travel straight. Configuration flows management → control → data: you (or a tool) configure in the management plane, the control plane computes forwarding, and the data plane forwards. A question asking “which plane does SNMP belong to?” is asking for the management plane.
Where configuration travels · select a layer
Management plane SSH · SNMP · syslog · NETCONF/RESTCONF · the REST API Control plane OSPF · EIGRP · BGP · STP · the SDN controller Data (forwarding) plane ASIC forwarding · switching and routing at line rate config flows down

Part 3

Northbound and southbound APIs

An API (application programming interface) is a defined way for one piece of software to ask another to do something. SDN controllers expose two kinds, named for their position relative to the controller.

Definition — northbound vs southbound. The northbound API connects applications to the controller (often REST/JSON). The southbound API connects the controller to the underlying devices (OpenFlow, NETCONF, RESTCONF, vendor protocols).
The SDN stack · select an interface
Applications / Orchestration / Scripts the management plane, made programmable northbound REST API (JSON) SDN Controller control plane · intent southbound API Device 1 Device 2 Device 3 devices keep the data plane; the controller holds the control plane

Part 4

Underlay, overlay, and fabric

Modern design separates the physical network from the logical network it carries. Three terms describe that separation, and the exam expects you to keep them apart.

Definition — underlay vs overlay. The underlay is the physical routed network that gives IP reachability. The overlay is a logical, tunneled network built on top of it. Together they form the fabric.

The point of an overlay is freedom from the physical topology. A host in one rack can be in the same logical Layer 2 segment as a host ten rows away, even though the traffic between them is routed across the underlay. That is what makes workload mobility and segmentation possible in a data centre.

Three layers of the design · select one

Cisco implements this idea as SD-Access (software-defined access) for the campus and SD-WAN (software-defined WAN) for the wide area. In SD-Access, the fabric is built from underlay switches, routed with a control-plane protocol (LISP), and carries an overlay tunneled with VXLAN; the controller defines who can talk to whom as a policy rather than as box-by-box VLAN and ACL configuration. SD-WAN applies the same controller-driven, overlay-based approach to branch and WAN links.

Part 5

Spine-leaf underlay

The standard data-centre topology for a fabric is spine-leaf (also called a Clos network). It replaces the old three-tier core/distribution/access design.

PropertyThree-tier (core/dist/access)Spine-leaf
Hops server to serverVariablePredictable (leaf-spine-leaf)
Adding capacityAdd bigger core/distribution boxesAdd a leaf or a spine horizontally
East-west trafficCan bottleneck at coreSpread evenly across spines
DesignHierarchical, oversubscribedFlat, low-latency, scalable
Note. The underlay in a spine-leaf fabric is usually a routed Layer 3 network. Each leaf-spine link is its own subnet, and a simple routing protocol advertises the loopback addresses of the switches so every device can reach every other. The overlay (VXLAN) then tunnels endpoint traffic across it.
Part 6

VXLAN at a high level

VXLAN (Virtual Extensible LAN, RFC 7348) is the tunnelling technology most fabrics use to build the overlay. The problem it solves is a limit inherited from VLANs: a VLAN tag is 12 bits, so only about 4,000 VLANs are possible, and VLANs do not naturally stretch across a routed data centre. VXLAN removes both limits.

FeatureVLAN (802.1Q)VXLAN
Identifier size12-bit VLAN ID24-bit VNI (VXLAN Network Identifier)
Segments possible~4,096~16 million
ScopeLayer 2 domain, bridgedOver a Layer 3 IP network (overlay)
EncapsulationAdds a 4-byte 802.1Q tagAdds a UDP/IP header + VXLAN header
Definition — VXLAN. A tunnelling protocol that encapsulates Layer 2 frames inside UDP/IP packets so they can cross a Layer 3 network, using a 24-bit VNI to identify up to about 16 million logical segments.

VXLAN uses VTEPs (VXLAN Tunnel Endpoints) — typically the leaf switches — to encapsulate a frame, send it across the IP underlay, and decapsulate it at the far end. The original frame is unchanged; the underlay only ever sees ordinary IP packets, which is exactly what lets the underlay stay simple and fast.

Segment identifier · drag the bit width
24 bits

Exam tip. Remember the number that separates VXLAN from VLAN: VXLAN’s identifier is 24 bits (about 16 million segments), versus a VLAN’s 12 bits (about 4,096). If a question contrasts the two, that is the key fact.
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Key termMeaning
SDNSoftware-defined networking; centralised control plane with programmable devices over APIs.
Northbound APIInterface between applications and the controller, often REST/JSON.
Southbound APIInterface between the controller and devices (OpenFlow, NETCONF, RESTCONF).
UnderlayThe physical IP-routed network providing reachability between devices.
OverlayA logical, tunneled network built on top of the underlay.
FabricThe combined underlay and overlay managed as one programmable system.
Spine-leafA flat data-centre topology where every leaf connects to every spine.
VXLANTunnelling protocol that encapsulates L2 frames in UDP/IP using a 24-bit VNI.
VTEPVXLAN Tunnel Endpoint; the device that encapsulates/decapsulates VXLAN traffic.
Sources & references
  1. Cisco. CCNA (200-301) Exam Topics, Domain 6.0 Automation and Programmability. cisco.com.
  2. Mahalingam, M. et al. RFC 7348: Virtual eXtensible Local Area Network (VXLAN) (2014). rfc-editor.org/rfc/rfc7348.
  3. Open Networking Foundation. Software-Defined Networking: The New Norm for Networks. opennetworking.org.
  4. IEEE. IEEE 802.1Q: Bridges and Bridged Networks (VLAN tagging). standards.ieee.org.
Sources

Sources & references

  1. Cisco. CCNA (200-301) Exam Topics, Domain 6.0 Automation and Programmability. cisco.com.
  2. Mahalingam, M. et al. RFC 7348: Virtual eXtensible Local Area Network (VXLAN) (2014). rfc-editor.org/rfc/rfc7348.
  3. Open Networking Foundation. Software-Defined Networking: The New Norm for Networks. opennetworking.org.
  4. IEEE. IEEE 802.1Q: Bridges and Bridged Networks (VLAN tagging). standards.ieee.org.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.