Skip to content

CVP Advanced Change Control

Learn how to use CloudVision's Change Control. A Change Control can be associated with one or more Tasks. CloudVision will configuration sessions when a Change Control is executed to give us a state to revert back should there be any issues after the change.

We can take this a step further by creating a template that can be applied easily to a change control to give us additional information to validate our changes. In this lab, we will create a template for routing changes.

Getting Started

  1. Log into the Arista Test Drive portal with your assigned URL. If you don't have one, please see your ATD staff.

    CVP Overview

  2. Click on the link Click Here To Access Topology and navigate to the below page.

    CVP Landing

  3. Log into the Console Access Jumpserver and select cvp or 6 to prepare the lab environment for this lab.

    Warning

    The script will configure all devices in the lab so you can complete this lab.

    Note

    Did you know → the "cvp" script is composed of python code that uses the CloudVision Portal Rest API to automate the provisioning of CVP Configlets.

  4. Click the CVP link on the left side of the screen. You will come to a login screen for CloudVision Portal. Enter the username arista and the password {REPLACE_PWD}

Adding Devices to Studios

First let's add all of the devices to Studios.

  1. Navigate to the Studios page under the Provisioning tab.
  2. Select Inventory and Topology
  3. Select Create Workspace to create a new workspace
  4. Add a name to the Name field. Then select Create
  5. Select Network Updates
  6. Select Accept All Updates
  7. Select Review Workspace
  8. Select Submit Workspace

ADV CC 1

Creating Snapshots

The snapshot for this lab has already been created, but let's add an additional command.

  1. Navigate to the Snapshot Configuration page under the Provisioning tab.
  2. Select the Validate_Routing Snapshot.
  3. Add the show ip route command to the EOS Commands section.
  4. Select the Save button to save the updated Snapshot.

ADV CC 2

Creating Action Bundles

The first step of creating a template is setting up action bundles. Action bundles are single actions or groups of actions that can be included in a change control. We will explore a few actions that can be included in a change control or change control template.

  1. Navigate to the Action Bundles page under the Provisioning tab (You may have to expand the Change Control Menu).
  2. Create the Set Configuration Action Bundle:
    1. Select the New Action Bundle button.
    2. Add Set Configuration for the Bundle Name.
    3. Select the Add Action dropdown and select Set Configuration from the Provisioning Actions section.
    4. Verify Parallel executition is selected.
    5. Then select the Save button.
  3. Create the Validate Routing Snapshot Action Bundle:
    1. Select the New Action Bundle button.
    2. Add Validate Routing Snapshot for the Bundle Name.
    3. Select the Add Action dropdown and select Validate_Routing from the Snapshots section.
    4. Set the DeviceID to Provide via template.
    5. Verify Parallel executition is selected.
    6. Then select the Save button.
  4. Create the Sleep Timer Action Bundle:
    1. Select the New Action Bundle button.
    2. Add Sleep Timer for the Bundle Name.
    3. Select the Add Action dropdown and select Sleep from the Change Control Actions section.
    4. Set the Duration to 15.
    5. Verify Parallel executition is selected.
    6. Then select the Save button.

ADV CC 3

Creating a Change Control Template

Now let's create the change control template. Once we have the template created, it can be used for any routing change controls.

  1. Navigate to the Templates page under the Provisioning tab (You may have to expand the Change Control Menu).
  2. Select the New Template button.
  3. Set the Name field to: Routing Update and select Save.
  4. Set the Executition Mode to Series instead of Parallel.
  5. Select the Add Stage Rule Button three times. There should be four stage rules in total.
  6. Setup the Pre-Commit Snapshot Stage:
    1. Set the first stage name to Pre-Commit Snapshot.
    2. Select the Validate Routing Snapshot bundle.
    3. Set Arrange Bundles to Parallel.
  7. Setup the Set Configuration Stage:
    1. Set the second stage name to Set Configuration.
    2. Select the Set Configuration bundle.
    3. Set Arrange Bundles to Parallel.
  8. Setup the Sleep Timer Stage:
    1. Set the second stage name to Sleep Timer.
    2. Select the Sleep Timer bundle.
    3. Set Arrange Bundles to Parallel.
  9. Setup the Post-Commit Snapshot Stage:
    1. Set the first stage name to Post-Commit Snapshot.
    2. Select the Validate Routing Snapshot bundle.
    3. Set Arrange Bundles to Parallel.
  10. Select Save Template button.

ADV CC 4

Adding Loopbacks to the Fabric

Now lets add the new Loopbacks using the Static Configuration Studio.

  1. Navigate to the Studios page under the Provisioning tab.
  2. Select Static Configuration
  3. Select Create Workspace to create a new workspace
  4. Set the Name field to Routing Update. Then select Create
  5. Select the + Configuration Container button.
  6. Under Create a Tag, Set Tag Label to Role and the Tag Value to Leaf. Then select the + Create button
  7. Select the Three Dots and select Add Device.
  8. Select the four S1-Leaf switches and select Add.
  9. Add loopbacks to s1-leaf1
    1. Select s1-leaf1
    2. Select + Configlet button.
    3. Select New Configlet and set the name to s1-leaf1
    4. Copy the configuration into the configlet: 
      int lo1
    ip address 10.1.1.1/32
int lo2
    ip address 10.1.1.2/32
int lo3
    ip address 10.1.1.3/32
int lo4
    ip address 10.1.1.4/32

router bgp 65101
    network 10.1.1.1/32
    network 10.1.1.2/32
    network 10.1.1.3/32
    network 10.1.1.4/32
  10. Add loopbacks to s1-leaf2
    1. Select s1-leaf2
    2. Select + Configlet button.
    3. Select New Configlet and set the name to s1-leaf2
    4. Copy the configuration into the configlet: 
      int lo1
    ip address 10.1.2.1/32
int lo2
    ip address 10.1.2.2/32
int lo3
    ip address 10.1.2.3/32
int lo4
    ip address 10.1.2.4/32

router bgp 65101
    network 10.1.2.1/32
    network 10.1.2.2/32
    network 10.1.2.3/32
    network 10.1.2.4/32
  11. Add loopbacks to s1-leaf3
    1. Select s1-leaf3
    2. Select + Configlet button.
    3. Select New Configlet and set the name to s1-leaf3
    4. Copy the configuration into the configlet: 
      int lo1
    ip address 10.1.3.1/32
int lo2
    ip address 10.1.3.2/32
int lo3
    ip address 10.1.3.3/32
int lo4
    ip address 10.1.3.4/32

router bgp 65102
    network 10.1.3.1/32
    network 10.1.3.2/32
    network 10.1.3.3/32
    network 10.1.3.4/32
  12. Add loopbacks to s1-leaf1
    1. Select s1-leaf1
    2. Select + Configlet button.
    3. Select New Configlet and set the name to s1-leaf1
    4. Copy the configuration into the configlet: 
      int lo1
    ip address 10.1.4.1/32
int lo2
    ip address 10.1.4.2/32
int lo3
    ip address 10.1.4.3/32
int lo4
    ip address 10.1.4.4/32

router bgp 65102
    network 10.1.4.1/32
    network 10.1.4.2/32
    network 10.1.4.3/32
    network 10.1.4.4/32
  13. Select Review Workspace
  14. Select Submit Workspace
  15. Select View Change Control

ADV CC 5

Submitting the Change Control

Finally let's apply the new Routing Update template and run the change control.

  1. The Change Control should be visible from the last step. If not, navigate to the Change Control page under the Provisioning tab. Then select the latest Change Control.
  2. Select the Routing Update template from the Select a Template drop down and select Apply Template.
  3. Select the Expand all Stages button.
  4. Select the Review and Approve Button
  5. Select the Execute Immediately radial button.
  6. Select Approve and Execute
  7. Select any of the Post-Commit Snapshot tasks to look at the snapshot diff from the Pre-Commit Snapshot. You should see the routing changes caused by adding loopbacks to the leaf switches.

ADV CC 6

In this lab we looked at creating snapshots, creating action bundles, creating a change control template using the action bundles, and finally using the template when executing a change control. There are many other actions that can be leveraged during change controls including updating EOS using SSU, removing old EOS images, checking MLAG peer health, etc. Spend a few minutes looking at other actions that could be used in other templates for common tasks.

Success

Lab Complete!