• Automating EVPN fabric deployment using CVP

Print Friendly, PDF & Email

To simplify and speed up the deployment of an EVPN fabric, CloudVision Portal can be a powerful tool to work with. The intention of this post is to divide this up into steps to simplify, qualify the actions steps needed and provide an example CloudVision Portal configlet builder to execute needed tasks in CloudVision.

A complete demonstration of how CloudVision Portal is used to deploy an EVPN instance and EVPN fabric can be found here

First of all, there needs to be a decision of which deployment model of EVPN underlay and overlay that suits the particular deployment being worked on. This is a decision with many aspects and a good partner in that discussion are Arista SE, Arista AS or Arista PS resources. For the example that will follow below, an eBGP underlay has been chosen to give connectivity between loopbacks on the EVPN leaf switches. The overlay is a fully meshed iBGP connection scheme where only routes of the address family EVPN is being exchanged. The example also features a non-MLAG setup using standalone leaf switches and single uplinks to each spine. This is all reflected in the configlet builder script referenced below, but that configlet builder script example can easily be altered to fit an MLAG deployment type for the leafs, multiple uplinks to spines as well as be adapted to suit other overlay and underlay models.

First pre-requisite is that there is a working CloudVision Portal installation running that has connectivity to the switches management. Switches to be used in the EVPN fabric are intended to boot using the CloudVision Portal Zero-Touch Provisioning (ZTP) scheme for fully automated provisioning scheme.

To set up all configlets needed for the EVPN fabric, the Fabric Builder configlet builder published at GitHub needs to be downloaded: Fabric Builder

To import the configlet builder do the following:

* Download to local computer the configlet builder Fabric Builder

* Log in to CloudVision Portal

* Click on “Configlet” in the CloudVision Portal menu


* In the top right corner, click the” import” option and select the file with Fabric Builder from the local computer


Now the configlet builder is imported. To use it to build a new datacenter, leafs, spines, and configlets for the EVPN setup, do the following:

* Goto “Configlets” in CloudVision Portal

* Use search to find the Fabric Builder and click on it

* Use the edit option top right on the screen and update the highlighted IP address to the IP of CloudVision Portal

* Save the change

* The Fabric Builder is now ready for use and the following view should be seen

* Now fill out the form with data and then clock on “Generate”. The picture below serves as an example and there is a description of the data format below.


Explanation of fields:

Data Center name: A text prefix for containers and elements to deployed by the configlet builder

Number of Spines: The number of Spines in the deployment

– Number of Leafs: The number of Leafs in the deployment

– Default gateway for the OOB mgmt network: The default gateway on the network assigned to Ma1 interface, ex:

– Mgmt network prefix: The IP address prefix for network assigned to Ma1, example 10.0.0. (pls mind the trailing “.”)

Mgmt network netmask: The length of the netmask in the Mgmt network, example: 24

VXLAN loopback address prefix: The IP address prefix for network assigned to VXLAN loopback, example 10.3.0. (pls mind the trailing “.”)

– Loopback address prefix: The IP address prefix for network assigned to Loopback0, example 10.2.0. (pls mind the trailing “.”)

Fabric link network prefix: The IP address prefix for network assigned to Links between Leafs and Spines, example 10.1.0. (pls mind the trailing “.”)

HER/CVX/EVPN: Type of VXLAN control plane for the deployment. Choose between HER, CVX and EVPN.

* Goto “Network provisioning view” and the new data center will be visible.

* Move the switches from the “Undefined” container into the correct leaf or spine container.

* Use search to find relevant configlets for every device and assign them to each device. Example of DC5 with two spines and two leafs: Search for DC5spine1 and assign configlets to DC5spine1, repeat for the other spine and leafs.

* Validate the devices and make sure that “Reconcile” is used to preserve login configuration for cvpadmin, but also preserving eAPI configuration.

* When all devices have been validated and reconciled, click “Save”  in the “Network provisioning view” so that tasks are created. Execute the tasks or use “Change Ctrl” to execute the tasks with snapshots and rollback options.

After all tasks have been executed, the EVPN fabric underlay and overlay are ready to be used and EVPN instances for type 2 routes or type 5 routes can be added.


Get every new post on this blog delivered to your Inbox.

Join other followers: