Now, this is a story all about how

Five All Star Dev. Advocates worked together on a KR

And I’d like to take a minute

Just sit right there

I’ll tell you how I lead an initiative called “Multi-Domain Automation” for real

The All Star Line up:

The Story:

A major retailer is standing up a new location. They require:

  • A connection to corporate remote data center for price list
  • To quickly deploy the local network at the branch including standardized configuration
  • On site compute for localized advertisement, webservers and general compute.
Multi-domain graphic
Multi Domain Story

Check out Matt’s Blog to learn more about the overall story and what we’ve done.

What I would like to focus on is how we’ve Integrated Cisco DNA Center to automate the standing up of a new network with Cisco Action Orchestrator (CAO)

The Tech:

Cisco DNA Center

I had two tasks to accomplish:

  1. Discover and provision the network in the new branch
  2. Create and deploy an SSID throughout the entire store

The way Network Discovery works in Cisco DNA Center, first I have to initiate a Discovery Task based on a range of IP addresses.

Once the task is completed and the device is part of the managed devices. I can dynamically create my sites and assign the devices to each site with the appropriate template.

The Workflow is pretty simple

  • Authenticate against DNA-Center to get a Token
  • Grab credentials IDs that are configured in DNAC to access the devices
  • Initiate Network Discovery
  • Check if the task is complete
  • Get a list of discovered devices
Kareem multi-domain DNA Center 1
Network Discovery workflow built in Cisco Action Orchestrator

If you are looking to get started with DNA Center, here are some DNA-Center resources for you.

To Initiate Network Discovery you need to POST a request to the /dna/intent/api/v1/discovery endpoint with this body

multi-domain DNA Center
Network Discovery request JSON Body

We are using an IP Range to discover our devices. We are also telling DNAC to access the devices via SSH using the configured credentials.

Once the discovery task is completed. We can check to see the results via /dna/intent/api/v1/discovery endpoint. This endpoint will return the list of all discover devices.

multi-domain DNA Center
Network Discovery result

Part Deux of this automation journey is to create a standardized SSID. There is a nice API for that which made the workflow pretty simple:

  • Authenticate against DNA-Center to get an API Token
  • POST JSON body with SSID configuration to /dna/intent/api/v1/enterprise-ssid
    and voila.
multi-domain DNA Center
CAO Workflow using Enterprise SSID Intent API

The End

Remember how I said earlier this was part of an all star team that has essentially automated the entire story you’ve read? Well what’s great about working with Cisco Action Orchestrator (CAO) is that it didn’t matter the way I’ve built my workflow. When it came time to integrate all of our work, CAO made it very simple and hence we were able to take a small bit of automation for a specific Cisco Product and integrate it into a larger multi domain effort.

would you like to get a deeper dive on what we’ve talked about here? Join me on May 7th to get a deep dive into what we’ve spoken about here. I will go through the APIs as well as show you how I’ve built this in CAO.

Register now for upcoming Multi-domain webinars:

Watch Matt Denapoli’s April 9 webinar 
Intro to Multi-Domain Deployments

Watch Stuart Clark’s April 16 webinar
Implementing SD-WAN Deployments

Watch Matt Denapoli’s on April 23 for
Implementing Meraki Deployments

Register now to join John McDonough on April 30 for
Implementing UCS/ACI Deployments

Register now to join me on May 7 for
Implementing Cisco DNA Center Deployments

If you have any feedback let me know in the comments section below, leave me a message, ask me a question, whatever you want.

Follow @kareem_isk

We’d love to hear what you think. Ask a question or leave a comment below.
And stay connected with Cisco DevNet on social!

Twitter @CiscoDevNet | Facebook | LinkedIn

Visit the new Developer Video Channel


Kareem Iskander

Technical Lead

DevNet Developer Experience