CVP EVPN-ConfigBuilder Files

This tool allows the CVP tool to be used on EVPN Arista fabrics when eBGP is used between the Leaf and Spine.  The reason such a tool is needed is that the "router bgp ASN" command is unique between each Leaf pair, because the ASN is different.  This problem does not exist within an iBGP environment, but the problem with unique Router ID and RD information is still unique to the pair, so this may still be useful for those use cases.  The following describes how to setup and use this script.

This script works by combining other source configlets based on the configuration in the "Globals" configlet.  None of these source configlets or the "Globals" configlet are applied directly to any container or device; they are automatically included and modified based on the configuration.

The "Globals" configlet contains two key details, in JSON format.  The first is the "Containers" key, which lists the names, or start of the names which should be included for all devices that fall under that container.  The second part lists the device specific information, with one key per device.  This key is the management IP of the device.  Within that details are the search/replace strings used when processing the source configlets.  A sample Globals configlet is provided, along with some sample source configlets.

I have provided a sample picture with a container hierarchy that I believe will best help you utilize this script, and maintain a production environment.  You may need to add additional containers under Leaf, or perhaps other containers at the Leaf/Spine level.  

To utilize this script, apply it to the highest level of your container hierarchy that makes sense.  Then right click the container, and click manage->configlet.  With the configbuilder script seen on the left (you may have to scroll through your configlets) the "Generate" button should appear.  When you push this, individualized configlets for each of the devices within the container hierarchy will be built.  Pictures attached.

When making changes to the source configlets, be sure to delete all the generated configlets and rerun the configbuilder script via the Network Provisioning tab.  This will create the new generated configlets.

Good luck.