CloudVision Portal (CVP) abstracts the physical network to support turn-key automation for zero touch provisioning, configuration management and network-wide upgrades and rollback. CVP allows the user to quickly deploy new switches into the network using predefined, user created, configuration snippets called configlets. This functionality allows the user to simply automate the deployment of new network elements.
What happens if the network elements are already deployed in the network and the user wishes to introduce CVP to automate configuration updates?
How would these switches be brought into CVP and their configurations integrated into the configuration hierarchy?
This guide will look at providing a solution to these questions and explain how to build a hierarchy based on the configuration already deployed. By following the steps in this guide the switch configurations will be converted into configlets and the switches imported into the CVP configuration hierarchy. The different types of configlets and their role in the hierarchy will be reviewed to aid the creation of the switch configlets, then a typical organisation hierarchy will be considered to provide an example. The import process will then be outlined in a step by step guide.
This guide is intended for the following audience:
• End user getting familiar with CloudVision
• End user familiar with Arista’s EOS CLI
Access to the “Importing Existing Switches Guide”
Preview the guide below or download it here.
If you have any issues, please do not hesitate:
• Post a comment or question on here, or
• Feel free to reach out to firstname.lastname@example.org (24x7x365 TAC support), or
• Feel free to reach out to your Arista systems engineer