Week 12 · Lesson 4

Cisco DNA Center and Catalyst Center

Cisco’s campus controller is the concrete product behind the ideas in the last two lessons. Called Cisco DNA Center when it launched and Cisco Catalyst Center today, it turns “intent” into device configuration and gives you a single dashboard for design, policy, provisioning, and assurance.

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

Intent-based networking

Intent-based networking (IBN) is the design philosophy the controller implements. Instead of typing commands that describe how to configure each device, you state the outcome you want — the intent — and the system works out the device configuration needed to achieve it, then keeps the network aligned with that intent over time.

Definition — intent-based networking. A network management approach in which an administrator expresses the desired business or operational outcome, and the system continuously translates, applies, and verifies that intent across the devices.

A useful example: instead of assigning a VLAN and QoS policy interface by interface, an administrator says “voice endpoints on this floor get priority treatment.” The controller translates that into the specific VLAN, access-port, and QoS commands on the relevant switches, and then verifies that voice traffic is actually getting the priority it should. The user states what; the controller decides how.

IBN has three recurring properties worth memorising:

Exam tip. If a question lists “translation, activation, assurance” it is describing intent-based networking. The last step — assurance — is what turns a one-off automation script into a self-correcting system, and it is the step exam writers focus on.
The three steps of intent · select one

Part 2

The four pillars

Cisco organises the controller’s features into four areas. You do not need to operate them for the exam, but you should be able to match each name to its job.

PillarWhat you doWhat it gives you
DesignModel sites, buildings, floors, device types, and credentials once.A logical map of the whole campus
PolicyExpress security and QoS intent as reusable rules.Consistent policy applied across the fabric
ProvisionPush configuration and fabric (VXLAN) rollout to devices.Fast, templated deployment
AssuranceMonitor health, collect telemetry, run analytics.Early warning and root-cause insight
Note. The four pillars are often remembered as Design → Policy → Provision → Assurance, which mirrors the lifecycle of a real rollout: plan the site, define the rules, push the configuration, then watch it run.
The rollout order · pick a pillar

Part 3

Automation and configuration

The controller automates by combining device discovery, templates, and policy. When a new switch is racked, the administrator adds it to the controller’s inventory. From then on, the controller owns its configuration: it can push a baseline from a template, apply the site’s policies, and keep the device consistent with the rest of its class.

This is where the idempotency and drift ideas from Lesson 1 pay off. Because the controller holds a model of what each device should look like, it can detect when a device has been changed by hand and either report it or restore the intended state. A command-line example of the kind of configuration the controller generates looks exactly like what you would type by hand — the difference is that a machine writes it, once, for every device, identically:

! Baseline template the controller would push to an access switch
Switch(config)# vlan 20
Switch(config-vlan)# name DATA
Switch(config)# interface GigabitEthernet1/0/10
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan 20
Switch(config-if)# no shutdown
Definition — template. A reusable configuration pattern with variables (for example, a site name or VLAN ID) that the controller fills in and applies consistently to many devices.

Beyond templates, the controller’s northbound REST API lets external systems drive it. A ticketing system can open a change, a script can call the controller’s API, and the controller applies the configuration. That is the full automation chain from this week: intent → controller API → device configuration.

Part 4

Assurance and analytics

Automation without visibility is risky. Assurance is the controller’s monitoring and analytics engine. It continuously collects data from devices — interface counters, client onboarding, application experience, and telemetry — and turns it into a health score for the network, a site, or an individual client.

Assurance is what distinguishes a modern controller from an older management tool. Traditional tools showed you raw counters; assurance tells you that a specific client is having a bad experience and points at the likely cause, using machine learning on the collected data to separate normal variation from a genuine problem.

Assurance in action · drag the error rate
100health score for this interface

Part 5

Fabric provisioning

For a campus fabric, the controller can take the spine-leaf underlay plus the VXLAN overlay and build the whole thing from intent. The administrator defines the fabric sites, the control-plane and border nodes, and the policy; the controller then generates the underlay routing, the VXLAN encapsulation, the VTEP configuration, and the overlay policies on every participating switch.

Fabric node roles · select one
Control-planemaps endpoints Borderconnects outside Edgeattaches endpoints Intermediateonly forwards a campus fabric: every node has a role assigned by the controller adding a switch to the fabric means assigning it a role — the controller computes the rest

Fabric roleFunction
Control-plane nodeRuns the fabric control protocol (LISP/VXLAN) that maps endpoints to locations.
Border nodeConnects the fabric to the outside world (WAN, other routing domains).
Edge nodeA leaf that connects wired or wireless endpoints into the fabric.
Intermediate nodeA switch inside the fabric that only forwards fabric traffic.

Because the topology is defined once in the controller, adding a new switch to the fabric is a matter of assigning it a role; the controller computes the rest. That is the scale benefit of controller-based design made concrete.

Part 6

Dashboards and APIs

Operators interact with the controller in two ways, and the exam may ask you to tell them apart:

Both do the same underlying thing: they talk to the controller, which talks to the devices. The dashboard is the API with a face on it. Everything from Lesson 5 onward — REST, HTTP methods, status codes, and JSON — is the toolkit for driving the API directly.

Exam tip. If a question asks how an automated tool reaches Catalyst Center, the answer is the northbound REST API (JSON over HTTPS) — not SSH into the devices and not SNMP polling.
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Key termMeaning
Intent-based networkingStating the desired outcome; the system translates, applies, and verifies it.
TranslationConverting business intent into device configuration.
ActivationApplying the translated configuration to the network automatically.
AssuranceContinuous monitoring that verifies the network matches intent.
Catalyst CenterCisco’s campus controller (formerly DNA Center).
TelemetryContinuous streaming of device/client data for analytics.
TemplateReusable configuration pattern with variables the controller fills in.
Border nodeA fabric node that connects the fabric to external networks.
Sources & references
  1. Cisco. CCNA (200-301) Exam Topics, Domain 6.0 Automation and Programmability. cisco.com.
  2. Cisco. Cisco Catalyst Center (formerly DNA Center) Data Sheet. cisco.com.
  3. Cisco. Cisco Software-Defined Access (SD-Access) Solution Overview. cisco.com.
  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 (formerly DNA Center) Data Sheet. cisco.com.
  3. Cisco. Cisco Software-Defined Access (SD-Access) Solution Overview. cisco.com.
  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.