In the previous lesson on Cisco Catalyst Center, you saw the controller push config, read inventory, and run show commands on the devices.
But how does Catalyst Center communicate?
It uses APIs in two directions: one going up to apps, one going down to devices.
Figure 1 – Catalyst Center sits between external apps (northbound) and network devices (southbound)
Two directions, two jobs:
Northbound: apps talk to Catalyst Center
Southbound: Catalyst Center talks to the devices
Northbound
Northbound is the direction your scripts and tools use to reach Catalyst Center.
Catalyst Center exposes a REST API that exchanges JSON over HTTPS.
It uses standard verbs: GET to read, POST to create, PUT to update, DELETE to remove.
Figure 2 – A script calls Catalyst Center over HTTPS and gets JSON back
Imagine your script needs the list of every switch in the network.
Instead of opening SSH on each one, the script sendsGET /dna/intent/api/v1/network-deviceand Catalyst Center returns the inventory as JSON.That's the whole northbound idea: your script describes what it wants, Catalyst Center figures out the how.
Answer the question below
Which encoding format do Catalyst Center northbound APIs use?
Answer the question below
Which API direction is used when a script asks Catalyst Center for the list of devices?
Southbound
Southbound is the direction Catalyst Center uses to reach your devices.
It does not invent a new protocol.
It uses the ones your switches, routers, WLCs, and APs already understand.
Figure 3 – Catalyst Center reaches the network through four southbound protocols
Catalyst Center speaks four southbound protocols:
NETCONF: structured config over SSH, XML payloads, YANG models
RESTCONF: same YANG models, but over HTTPS with JSON or XML
SNMP: for reading telemetry and inventory from devices
SSH: for pushing CLI commands when a device does not support NETCONF or RESTCONF
The first two are modern and structured.
SNMP and SSH cover what these newer protocols can't reach.Answer the question below
Which model-driven protocol does Catalyst Center use southbound over SSH?
Answer the question below
Which southbound protocol does Catalyst Center use to push CLI commands when a device does not support NETCONF or RESTCONF?
In the SD-WAN Architecture lesson, you met vManage, the management plane of the SD-WAN fabric, now rebranded as Cisco SD-WAN Manager.
Same logic as Catalyst Center: one direction goes up to apps, one goes down to devices.
The details differ a bit.
Figure 4 – vManage sits between external apps (northbound) and WAN Edge routers (southbound)
Northbound
vManage exposes a REST API that returns JSON, just like Catalyst Center.
Every endpoint sits under
/dataservice/.
For example,GET /dataservice/devicereturns the list of WAN Edge routers in your fabric.
Figure 5 – A script calls vManage over HTTPS and gets JSON back
To help you find your way around, Cisco groups the API into five categories:
Configuration: templates, policies, device certificates, and the device inventory itself
Real-time monitoring: live status of devices, links, applications, and tunnels
State and statistics: aggregated data and bulk queries over time
Alarms and events: notifications, alarm queries, and audit logs
Administration: users, groups, tenants, backups, software upgrades
You don't have to memorize every endpoint. What matters is that you know where to look:
if you want to push config, you go to Configuration.
If you want live data, you go to Real-time monitoring. And so on.Answer the question below
Under which vManage API category do you find templates, policies, and the device inventory?
Southbound
On the southbound side, vManage mainly uses NETCONF with YANG data models to configure the WAN Edge routers.
One detail worth knowing: NETCONF normally runs over SSH, but here it travels inside a DTLS or TLS tunnel that already secures every connection in the SD-WAN fabric.

Figure 6 – vManage reaches WAN Edge routers using NETCONF inside the SD-WAN secure tunnel
A single template change pushed from the GUI or the API turns into a NETCONF transaction sent to every matching WAN Edge router.
NETCONF is the main protocol you need to remember, but vManage also uses SNMP to collect data from the routers and ICMP to check that they are alive.
Compared to Catalyst Center, vManage southbound is simpler:
NETCONF does most of the work, because every WAN Edge router is a modern Cisco device that speaks it natively.Answer the question below
Which protocol does vManage mainly use southbound to configure WAN Edge routers?
Answer the question below
One API call edits DT-BRANCH, used by 25 of 40 routers: how many get a NETCONF transaction?
Both controllers follow the same north/south pattern, but the details differ.
Catalyst Center
vManage
Northbound protocol
REST API, JSON
REST API, JSON
Northbound base URL
/dna/intent/api/v1//dataservice/Southbound protocols
NETCONF, RESTCONF, SNMP, SSH
NETCONF (mainly), with SNMP and ICMP
Manages
Campus networks (fabric and non-fabric)
SD-WAN fabric (WAN Edge routers)
Table 1 – Catalyst Center and vManage side by side
The takeaway: same northbound language on both.
A single dashboard can query Catalyst Center and vManage with the same REST/JSON logic.Answer the question below
What is one common characteristic of Catalyst Center and vManage northbound APIs?