Week 12 · Lesson 2

Traditional vs Controller-Based Networking

Every router and switch has always had to think for itself. A controller-based network changes that: one central brain decides, and the devices simply obey. To understand the difference you must first split each device into its control plane and its data plane.

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

The traditional model

In a traditional network, every device is an independent control point. A router runs a routing protocol, builds its own routing table, and makes its own forwarding decisions. A switch runs Spanning Tree, learns MAC addresses, and forwards frames on its own. If two switches disagree, nothing forces them to agree — there is no higher authority.

You configure each device directly. Reach a router over SSH, enter global configuration mode, type commands. The device’s operating system (Cisco IOS, IOS XE, NX-OS) is a distributed system: the intelligence is spread across every box. This is robust — if one device fails the rest keep running — but it is hard to manage at scale, because there is no single place that knows the whole network’s intent.

Definition — traditional (distributed) networking. A model in which each network device holds its own control logic and is configured individually; there is no centralised source of control or truth.

The classic symptom is the “box-by-box” workflow. To add a VLAN, you log into every access switch. To change an ACL, you touch every router that carries the traffic. Consistency is enforced by discipline alone, and we already saw in Lesson 1 how that ends: drift.

Where the control plane lives · select a model
Traditional (per device) Control plane OSPF / STP / ARP Data plane forward frames every device decides for itself Controller-based Controller control plane SW1 data only SW2 data only one brain, many obedient devices

Part 2

Control plane and data plane

To see what a controller changes, you must split a device into two functional planes. These are logical roles, not physical parts, and every router or switch performs both.

Definition — control plane vs data plane. The control plane builds the forwarding tables by running routing and switching protocols. The data plane uses those tables to forward the actual user traffic.

A useful analogy: the control plane is a city’s traffic-planning office, which studies the roads and publishes a map of the best routes. The data plane is every driver following that map. The planners never drive; the drivers never plan. (There is also a management plane — the interfaces you use to configure and monitor the device, such as SSH, SNMP, and syslog. Lesson 3 covers it in more detail.)

Three planes · pick one to inspect it

Part 3

The controller-based model

Controller-based networking centralises the control plane. One or more controllers run the protocols and compute all the forwarding decisions for the network. The devices below them become thinner: they still forward traffic at line rate (data plane), but they no longer make independent routing or switching decisions. Instead, the controller programs them with the forwarding rules to use.

Definition — controller-based networking. An architecture in which a centralised software controller holds the control plane, computes the desired network state, and programs the forwarding behaviour of the underlying devices, which perform the data plane.

Because the controller keeps a model of the whole network, it can express change as intent: “these two hosts must reach each other on this VLAN with this policy.” The controller then translates that intent into the individual device configurations. This is the heart of SDN, which Lesson 3 explores.

The controller talks to the devices over application programming interfaces (APIs). Programmers and tools talk to the controller over a northbound API, while the controller talks to the devices over a southbound API — for example, Cisco’s DNA Center / Catalyst Center platform, which we meet in Lesson 4.

Add VLAN 20 to 200 access switches · two ways

      

Part 4

Comparing the two models

The table below is the core of this lesson. Learn the rows, not just the words — almost every exam question about controller-based networking maps onto one of them.

AspectTraditional (per-device)Controller-based
Control planeDistributed — on every deviceCentralised — on the controller
ConfigurationDevice by device over CLINetwork-wide, expressed as intent
ConsistencyDepends on engineer disciplineEnforced by the controller
Change scopeOne box at a timeWhole fabric from one policy
ProgrammabilityLimitedAPIs for automation and integration
Failure impactOne device fails, rest continueController outage is significant (mitigated by clustering)
Note. Controller-based does not mean the devices are “dumb”. They still have CPUs, memory, and operating systems; they still need local forwarding tables. What changes is that the decision-making happens centrally, not that the forwarding hardware disappears.
Part 5

Cisco DNA Center / Catalyst Center

Cisco’s flagship controller for campus and branch networks was launched as Cisco DNA Center. It has since been renamed Cisco Catalyst Center; the two names refer to the same product family, and either may appear on an exam or in documentation. It is a software appliance that provides a single dashboard and API for automating and managing a Cisco campus fabric.

The four areas of the controller · select one

Exam tip. Know that DNA Center and Catalyst Center are the same platform under two names (Cisco renamed it). If a question uses “Catalyst Center” and a distractor uses “DNA Center” as if they were different products, they are not — it is a naming trap.

DNA Center is an example of intent-based networking (IBN): you state what you want, and the controller keeps the network converged on that intent, correcting drift automatically. Lesson 4 covers its features in depth.

Part 6

Benefits and trade-offs

The controller-based model buys consistency and speed, but it concentrates risk and complexity in a new place.

BenefitsTrade-offs
Network-wide policy applied from one placeThe controller becomes a critical system to protect and back up
Automation through northbound APIsRequires new skills (APIs, data formats)
Faster, more reliable changesVendor-specific controllers can limit multi-vendor flexibility
Continuous visibility and assuranceRollout and licensing cost and effort

Controllers are deployed in clusters (typically three nodes) so that the loss of one does not take down management of the whole network. That clustering is the standard answer to the single-point-of-failure objection, and it is worth remembering.

Exam tip. If a question asks how a controller-based network survives the loss of its controller, the expected answer is a cluster of controller nodes (usually three), not redundant cabling and not putting the controller on every switch.
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Key termMeaning
Control planeThe set of protocols and processes that decide where traffic goes and build the forwarding tables.
Data planeThe forwarding function that moves packets/frames using the tables the control plane built.
Management planeThe interfaces used to configure and monitor a device (SSH, SNMP, syslog).
Traditional networkingPer-device, distributed model where each device holds its own control logic.
Controller-based networkingCentralised control plane that programs the underlying forwarding devices.
Controller clusterMultiple controller nodes working together to remove a single point of failure.
Intent-based networkingExpressing the desired outcome; the controller configures devices to achieve it.
Catalyst CenterCisco’s campus controller platform, formerly Cisco DNA Center.
Sources & references
  1. Cisco. CCNA (200-301) Exam Topics, Domain 6.0 Automation and Programmability. cisco.com.
  2. Cisco. Cisco Catalyst Center Data Sheet. cisco.com.
  3. Open Networking Foundation. Software-Defined Networking (SDN) Definition. opennetworking.org.
  4. Cisco. What is Intent-Based Networking? cisco.com.
Sources

Sources & references

  1. Cisco. CCNA (200-301) Exam Topics, Domain 6.0 Automation and Programmability. cisco.com.
  2. Cisco. Cisco Catalyst Center Data Sheet. cisco.com.
  3. Open Networking Foundation. Software-Defined Networking (SDN) Definition. opennetworking.org.
  4. Cisco. What is Intent-Based Networking? cisco.com.

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