Cisco DNA Center API for Network Management

Let's start by breaking down the big terms into something you already understand.

First, what is a 'network'? Think of it as a system of connected roads, except instead of cars, data packets travel between computers, phones, and servers. Traditionally, if you wanted to change something on these roads—like adding a new turn lane (a new Wi-Fi network) or closing a road to traffic (blocking a dangerous device)—you had to drive to every single traffic light (router/switch) and manually flip switches. This was slow, error-prone, and required a lot of specialised knowledge.

Now, what is 'Intent-Based Networking' (IBN)? This is the idea that you, the network operator, should only have to tell the network your 'intent'—your desired outcome—and the network should figure out the rest. For example, your intent might be: "I need to securely onboard 50 new employees by tomorrow." You do not want to configure each port, create each user account, and set up each Wi-Fi password by hand. You want a system that understands your goal and executes the entire process automatically.

This is where Cisco DNA Center comes in. Cisco DNA Center is a central software controller—think of it as the master brain of the network. It sits above all your physical switches, routers, and wireless access points (the hardware that carries your data). Instead of logging into each device separately, you log into DNA Center, and it acts as a single pane of glass to manage everything.

But how do you tell DNA Center what to do? Through an API. API stands for Application Programming Interface. It is a set of standard commands that one piece of software (your automation script or another application) can use to talk to another piece of software (DNA Center). Instead of clicking buttons on a screen, you can send a message to DNA Center's API saying, "Get me the status of all switches" or "Create a new wireless network called Guest_Zone." The API then translates your request into the correct actions for the network devices.

The magic happens because DNA Center uses 'intent-based' logic. When you use its API to say, "I want to make the network secure for visitors," DNA Center does not just turn on a single setting. It analyses the situation, applies global security policies, configures firewalls (devices that block unauthorised access), and creates separate 'VLANs' (virtual local area networks—basically, separate lanes for different types of traffic). This is the 'closed-loop' model: you state your intent, DNA Centre implements it, and then it constantly monitors the network to ensure the intent is still being fulfilled (e.g., it checks that no unauthorised device is trying to sneak onto the guest Wi-Fi).

What does this replace? The old way of 'CLI' (Command Line Interface) scripting. In the past, a network engineer would write a script that sent individual text commands to each router. If a command failed, the script often kept going, causing a partial, broken configuration. DNA Center APIs replace this with a higher-level, safer method. You send a single API call to create a 'policy' (a rule about how the network should behave), and DNA Center ensures the policy is applied consistently everywhere.

Why does this matter for the 200-901 exam? You do not need to be an expert network engineer to understand the value. The exam expects you to know that the Cisco DNA Center API provides specific endpoints (the addresses used to make API calls) for tasks like: - Site Management: Creating and managing physical locations (offices, campuses). - Device Management: Adding, removing, and configuring switches and routers. - Policy Management: Defining who can access what (e.g., employees vs. guests). - Assurance: Getting health scores and insights about network performance. - Automation: Automatically deploying configurations across hundreds of devices.

In summary, the Cisco DNA Center API is the bridge between a human's high-level goal (an 'intent') and the low-level, complex world of network hardware. It makes the network programmable, consistent, and much faster to manage. For the exam, remember that 'intent' is the goal, 'API' is the method to communicate the goal, and 'DNA Center' is the engine that executes it.

Imagine you work for a medium-sized company called 'TechFinance', which has three offices: London, Manchester, and a new office opening soon in Bristol. You are the IT support person (no fancy title yet), and your boss asks you to set up the entire network for the new Bristol office, which will have 100 employees. They need Wi-Fi, secure access for the finance team who handle sensitive data, a printer network, and a guest network for visitors.

In the old way of doing things, you would have to:

This is where the Cisco DNA Center API saves your life. Here is the step-by-step process of what an IT professional actually does:

First, they install Cisco DNA Center as a virtual appliance (a software version of a physical server) in the company data centre. This is the central brain. Then, they connect all the new switches and access points in Bristol to the company's Wide Area Network (WAN), which connects the offices. The devices boot up and automatically discover the DNA Center and register themselves—this is called 'Plug and Play' (PnP).

Now, the real work begins with the API: 1. Define the new site: The engineer uses a Python script (or a tool like Postman) to send an API call to DNA Center to create a new site object called 'Bristol_Office'. The call might look like POST /dna/site with a JSON payload (a structured data message) containing the address and building details. 2. Assign devices to the site: The engineer sends another API call to tell DNA Centre that the switches in Bristol belong to the 'Bristol_Office' site. DNA Center now knows which device is where. 3. Create a policy for secure finance access: The engineer drafts a 'policy' via the API. This policy says: "Anyone from the Finance_User_Group can access the Finance_Server on VLAN 10." The API call (POST /dna/policy) sends this rule to DNA Center, which then automatically configures every switch in Bristol to enforce this rule. The engineer does not touch a single switch. 4. Deploy the guest Wi-Fi: The engineer uses the API to call the 'SSID' (Service Set Identifier—the Wi-Fi network name) endpoint, creating a SSID called 'Guest_TechFinance'. The API also automatically sets up a captive portal (a login page guests see) and isolates guest traffic from the main corporate network. 5. Monitor and adjust: After everything is running, the engineer does not sit back. They set up a monitoring script that uses DNA Center's 'Assurance' API to pull real-time health data. If the script sees that the guest Wi-Fi has high latency (slowness), it can automatically alert the engineer or even trigger an API call to adjust the Quality of Service (QoS) settings to prioritise guest traffic.

What happens when something goes wrong? In Bristol, a switch develops a faulty port. The DNA Center detects this via telemetry (continuous data streaming from the device). The system's 'Assurance' API returns a health score of 60 out of 100 for that switch. The engineer receives an alert. Using the API, they query: 'Show me all devices with health score below 70.' They get a list, isolate the faulty switch, and order a replacement—all without a site visit.

In this scenario, the IT professional's job changed from being a manual configurator to being an orchestrator. They wrote scripts that leverage the DNA Center API to perform large-scale, error-free changes. The exam tests your understanding of this shift: from CLI-based 'box-by-box' management to API-driven 'intent-based' management.