API-Structured Tools Make Cisco Device Monitoring and Management Simpler

Cisco’s Intent-Based Networking (IBNG) Innovation Team is in charge of providing training labs, demos and bootcamps for clients, partners, internal product sales at public and personal events. After each teaching we need to reset a huge selection of devices and several controllers like Cisco DNA Middle, ISE, DHCP, WLC etc. This guide reset takes the team a whole lot of time. During a few of our events, weekly or daily we have been necessary to reset multiple times. To reduce the manual function and become more efficient, some API was made by us based equipment that can complete the complete process in under 30 minutes.

If any necessity is had by you for similar use instances, you can test our API-based equipment that can save time and decrease the tedious work!

We’ve 20-30 pods in each training laboratory. A pod can be an individual testbed which has different gadgets, such as edge/access, core and distribution devices. These products mimic a little customer Enterprise atmosphere, with Catalyst3k and 9k switches, ISR and asr routers and wifi controllers. Through the lab, the gadgets are configured per different use cases. Write-up each event, the products need to be introduced to the start state back. By using the scripts and APIs, we automated this reset procedure.

API-based Tools

For resetting gadgets such as for example Cat9ks, Cat3ks, ASRs and ISRs we have been using SecureCRT APIs that may reset these devices to a default condition or configure these devices to a base condition. Using these scripts in case a change is in configuration setting, enable setting or in virtually any other mode it’ll do necessary configuration adjustments and perform the reset on the products. Sometimes after reset you want to provide extra configuration that’s not area of the base. For that people use another script that may operate on multiple devices simultaneously.

API-based tools

We also created the button bar inside secure CRT and pointed the script to the button. This key bar is really a quick solution to run scripts, deliver strings and concern protocol simultaneously instructions on multiple sessions. Step by step directions for configuring this switch could be referred here. If we desire to execute a script on a variety of sessions just simply clicking the key will execute the script on all of the sessions opened. The next is an instance for mapping a python script to a switch in a key bar. All the hyperlinks to these scripts will be referred in What Following? section.

API-based equipment 2

Next step would be to reset Cisco DNA Middle. For Cisco DNA Middle, we have been using Cisco DNA Middle internal APIs to execute the restore and backup functions. We can also make use of these APIs to check on the position of restoration and backups procedures. Backup/restore APIs are usually for inner purposes only currently, these will undoubtedly be published in potential future. We incorporated these backup/restore scripts with Webex teams furthermore. So, if you execute any back-up or restore script it’ll send out a notification to the Webex groups and everyone for the reason that Webex group will undoubtedly be alert to the changes.

API-based equipment 3

Next step would be to reset additional controllers such as for example ISE/DHCP/DNS/Cat9800. We set up these controllers as VMs on ESXI hosts. To reset these VMs, the snapshots are increasingly being utilized by us and non-persistent settings for the VMs. Utilizing the PowerCLI cmdlets we have been creating brand-new VMs from the snapshots and resetting the VMs for non-persistent setting. The following can be an illustration to reset the controllers and generate VMs from snapshots. All of the hyperlinks to these scripts will be referred in What Following? section.

API-based equipment 4

Monitoring API-Based Equipment

After the reset approach has completed, we have been monitoring the devices through the use of python applications also. If something occurs to the device, like a link or change down goes, we are notified in Webex Groups of the presssing issue. We incorporated Cisco DNA Middle with Webex groups and configured the activities on Cisco DNA Middle to notify us of the alerts. If any problem happens, we shall get yourself a notification in the webex teams as alert. The following can be an example for the change unreachable notification in Webex groups that DNAC has delivered via APIs.

API-based equipment 5

The following can be an example a subscription to a meeting in Cisco DNA center and offer receiver information for sending the alerts. It is possible to sign up to specific events that could occur in your system. After your subscription, if the function occurs you shall get a notification by REST APIs. It is possible to refer here for additional information on how to sign up to events.

API-based equipment 6

What Next?

Using these API instruments, it is possible to automate lab plus demo reset processes plus configure the devices or even controllers to a bottom state while also overseeing the devices to get notifications via webex groups for any issue.

Make reference to SecureCRT scripts for gadget reset and construction, scripts for resetting plus cloning VMs such as for example ISE, CSR1k plus clients and DNAC webhook receiver scripts for supervising the gadgets from DNAC.

Related resources

The post API-Based Tools Make Cisco Device Management and Monitoring Easier appeared initial on Cisco Blogs.

%d bloggers like this: