The focus of thisepisodeof our ongoing Catalyst Center Automation Series is Onboarding Templatesand setting up a lab or production environment to enable this capability. This second lab in the series aims to understand the various concepts required to support device onboarding. The labs within this series, allow for use in the DCLOUD environment; however, you may equally utilize them as part of a Proof of Concept setup at a customer's lab. You may use these procedures to ensure that all the necessary steps are complete before onboarding any devices within Catalyst Center. These procedures may also help form part of a deployment or implementation.
Within this series, we cover the following;
Each of the Labs builds on the concepts that we cover, and this lab has a prerequisite of completing the first lab. This labaddresses how to use Onboarding Templates within Catalyst Center to onboard network devices at Day Zero, where they have no configuration initially. This lab will go through the flow involved in building the supporting settings within Catalyst Center to support onboarding. The lab will also allow you to deploy a template for a Catalyst switch through Catalyst Center using Onboarding workflows. To prepare the environment, make sure you complete the steps outlined in our first, and second blogs in the series.
In this lab, customers will start by building out an Onboarding Template that typically deploys only enough information to initialize the device. This lab delves into the practical application of how to set up Catalyst Center settings and hierarchy and how to prepare a template for delivery. It also lightly explains some of the various philosophies surrounding how we might deploy configuration.
While you might think to include the entire configuration for a traditional network device, there is a better way. We are better served by Day N Templates for large configuration constructs, allowing for modularization and reuse and simplification of operations. Day N Templates should be utilized to apply complex configuration and ongoing changes allowing device modifications after initial deployment.
Other considerations surround the use of the UI-centric approach and the impact that it has on a typical configuration. A configuration could include some lines of code, which may be delivered through the UI-centric settings. If these Design components are used, we need to understand the impact that may have on simplifying our configuration and how easy that may make the network maintain.
We will gain a practical understanding of the steps associated with setting up Catalyst Center and an environment to support Plug and Play and Device Onboarding during this lab. The lab is aimed at aiding engineers in rapidly begin using Catalyst Center automation and help them work towards a template strategy. Additionally, this lab will give customers a permanent place to try out the onboarding templates and includes configurations for various use cases. Finally, this environment will enable engineers to reduce the time and effort needed to instantiate the network.
The lab covers these topics in-depth:
In this lab, we will use APIs to build out design settings and credentials with Catalyst Center to reduce the time required to deploy. Postman will be the client application that we will use to rapidly build the design settings within Catalyst Center and provides an environment to build these APIs and test them but also helps us troubleshoot if required.
In this lab, we will use JSON files to Import and Export templates to Catalyst Center to reduce the time required to deploy. This capability also includes all the elements edited in the form editor, so all the various settings are sent with the logical cli constructs. This results in a useful tool for moving templates from test environments to production.
In this lab, we provide JSON files, examples of templates that you may Import to Catalyst Center to reduce the time required to deploy. This alleviates the guesswork involved in figuring out how a variable might be set up, as all the form editor elements are also included within the JSON file.
While using the lab, if the given examples and the deployment method need to change to support some testing you are doing, you may take the files and environment and modify them to suit your use case. We use a layer two trunk across a port-channel for connectivity, but equally, you could test out other connectivity methods for layer three routed access.
Within DCLOUD, several sandbox-type labs are available. These self-contained environments are there to allow you to use them as you please within the time scheduled. In addition, this allows us a place to start practicing various concepts without fear of impacting production environments.
Therefore, to aid customers in the transition toward automation, we have put together a set of small helpful labs within a GitHub repository. As a result, we hope to demystify some of the complexities of setting up plug-and-play and help guide customers through the complexities and caveats. In this way, these self-guided labs provide a glimpse into the fundamentals of building velocity templates and provide examples that you can download and expand from. In addition, thesample templates and JSON files supplied are for easy import into Catalyst Centers' template editor for quicker adoption. Lastly, some scripts are ready-made excerpts of code that allow you to build the environment to test.
First, in a practical lab guide, we step by step delve into the concepts of building templates and methodologies for using both Onboarding and DayN templates. Second, we provide answers and explanations to many of the questions that come up during automation workshops. Our hope is that you find the information both helpful and informative. Thus, we hope to give a well-rounded explanation of automation methods and concepts that we can easily expand upon for production purposes. Finally, the lab Onboarding Templates content explains the overall device onboarding setup steps.
To help customers succeed with Cisco Catalyst Center automation, you may utilize the above labs as they have been designed to work within DCLOUD's Cisco Enterprise Networks Hardware Sandbox Labs in either:
The DCLOUD labs allow you to run these labs and gives an environment to try the various code samples. You may choose to develop and export your code for use in production environments. Also, this gives you an environment where you can safely POC/POV methods and steps without harming your production environments. The DCLOUD environment also negates the need for shipping equipment, lead times, and licensing issues needed to get moving rapidly. Please do adhere to the best practices for the DCLOUD environment when using it.
The environment allows for use with a web-based browser client for VPN-less connectivity, access as well as AnyConnect VPN client connectivity for those who prefer it. You may choose from labs hosted out of our San Jose Facilities by selecting US West. Choose the Cisco Enterprise Network Sandbox. To access this or any other content, including demonstrations, labs, and training in DCLOUD please work with your Cisco Account team or Cisco Partner Account Team directly. Your Account teams will schedule the session and share it for you to use. Once booked follow the guide within GitHub to complete the tasks adhering to the best practices of the DCLOUD environment.
The Onboarding Templates lab content is located within the existing DNAC-TEMPLATES repository to give a one-stop-shop for all the necessary tools, scripts, templates, and code samples. Within it are four labs, which build upon the tutorials to test the methods in a lab environment. The repository was featured in a previous post on Cisco Blogs about Catalyst Center Templates earlier in May 2021.
The previously named DNAC Template LABS within theDNAC-TEMPLATES GitHub repository aim to guide you through the typical steps required to enable the various automation tasks delivered by Catalyst Center. This lab will give examples of templates used in Catalyst Center that we can modify for our use and test on equipment within the LAB environment. Additional information within the lab provides a well-rounded explanation of Automation methods with Templates. Lastly, the lab allows for customers to use Catalyst Center workflows to practice deploying Onboarding, DayN Templates, and Application Policy automation on both Wired and Wireless Platforms.
This lab Onboarding Templateswill give examples of templates used in Catalyst Center to modify our use and test on equipment within the LAB environment to onboard devices through Plug and Play into Catalyst Center. Additional information within the lab provides a well-rounded explanation of Automation methods with Templates.
The goal of this lab is for it to be a practical guide to aid engineers to rapidly begin using Catalyst Center automation and help them work towards a template strategy. Additionally, this lab will give customers a permanent place to try out the templates and include configurations for various use cases. Finally, this environment will enable engineers to reduce the time and effort needed to instantiate the network.
As a result, you will gain experience in setting up Plug and Play onboarding and templates. Additionally, you will use advanced templating methods and troubleshooting tools. These may help during faultfinding to determine what is failing in a deployment.
Please use this menu to navigate the various sections of this GitHub repository. Within the multiple folders are examples and explanation readme files for reference. There are now two sets of labs, and these are being continually expanded upon.
This newer and more modular lab approach is designed to deal with and includes concepts from the legacy labs in a newer more modular format.
In this section you will continue to find all the existing labs which deal with specifics in separate easy to do labs.
We will share additional labs and content in an ongoing effort to fulfill all your automation needs with Catalyst Center.
In conclusion, if you found this set of labs and repository helpful,
please fill in comments and feedback on how it could be improved.
We'd love to hear what you think. Ask a question or leave a comment below.
And stay connected with Cisco on social!
Check out our Cisco Networking video channel
Subscribe to the Networking blog