I’ve been working in software development/IT/technology my entire 17-year career. Time and time again I’m confronted with what ends up being the same challenge: how do I/we cobble together different pieces of software, platforms, and/or functionality to build one cohesive and observable solution.

Piecing solutions together

My first development job out of school was with a mortgage origination software company.  We provided custom installations depending on how your bank did business.  To provide viable tools for our bank customers to use, we had to piece together credit reporting, payment, and government regulation systems all onto our platform.

A few years later, I had a similar experience at a hospital billing software firm.  In this instance, we had to manage connections from scanned OCR documents, Medicare, insurance billing, and mainframe hospital systems. (The software that interacted with the mainframe emulators was SO COOL!)  These fed into a common billing database that took into account the incongruencies of all of those systems.

Finally, I’ve come across this same kind of challenge at least a half dozen times in my career here at Cisco!  Likely we all have, whether we realize or not. Because that’s what IT solutions (hardware and/or software) really are.

A multi-domain solution consolidates deployments

That brings us to the concept of Multi-domain solutions.  Cisco products cover enterprise/campus, data center, security, and WAN.  Depending on the need, these products are deployed individually or as a combination for a larger solution.  Organizations then choose to manage these deployments via the device, the controller GUI, or API.  A multi-domain solution consolidates these deployments “as one.” This offers the capability of provisioning and configuring all necessary components of the solution.

You can register for my April 9th webinar where we’ll discuss multi-domain solutions in greater detail. For now, let’s look at an example of one such solution.

The Scenario

Consider we have a number of retail branches being set up and a centralized data center.  The POS system at each branch needs secure access to the datacenter price list.  In addition, there is a need for a local network at the sites, requiring wireless access over a standardized SSID.  Finally, a local web server and ad server is required for advertisement.  This scenario is ripe for a multi-domain solution.

First, let’s look at access to the data center.  This is achieved through Cisco SD-WAN (or Cisco Meraki), and makes each added branch device part of the organization’s WAN.  Next, we provision wireless networking devices at the branches through Cisco DNA Center (or Cisco Meraki). This provides our local network SSID.  Finally, we deploy our branch host servers via Cisco UCS and manage their application connectivity via Cisco ACI.  Now, we could deploy and provision all of these elements for each branch manually through various GUIs for each platform. But why? There is a better way!

Multi-Domain Automation with Cisco Action Orchestrator

All of the platforms mentioned above have robust APIs as part of their platforms.  This allows for applications and scripts to be written to automate repeatable tasks.  Now, a network automation engineer may take a look at this problem and think, “well, I could script all of this out in Python using REST APIs. Or maybe Ansible would be a good solution.”  Those would both be valid tactics. But they could take some time to develop, and come with a list of requirements. This is where Cisco Action Orchestrator can help.

Cisco Action Orchestrator saves time and effort in automation tasks

Cisco Action Orchestrator (CAO) allows a network automation engineer to create individual tasks, like making calls to REST APIs, that can be linked together to repeatedly perform complex linear and parallel workflows.  In our example, tasks can be created to call Cisco SD-WAN vManage API. And when that completes (or in parallel) the task to call Cisco DNA Center intent APIs to setup wireless networks is triggered.  We can also implement messages to platforms like Webex Teams for monitoring the success of the tasks and workflows.  CAO abstracts the necessity of writing code or YAML from scratch and lets you focus on building the solution.

Register for one of the live webinars!

Want to know more?  Starting on April 9th, 2020, and continuing for the next 5 Thursdays, we will be holding BrightTALK webinars.  These 45-minute sessions will cover in detail the implementation of the above solution using Cisco Action Orchestrator and all of the platforms mentioned above.  Join one or join all!

April 9 — Intro to Multi-Domain Deployments

April 16 — Implementing SD-WAN Deployments

April 23 — Implementing Meraki Deployments

April 30 — Implementing UCS/ACI Deployments

May 7  —  Implementing Cisco DNA Center Deployments

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


Matt DeNapoli

Developer Advocate - Meraki & CMX

Developer Experience