A-02 | Provisioning a Campus Fabric

Overview

In this lab you will be onboarding your switch using CloudVision Studios, adding your new campus leaf switch to an existing Campus Fabric.

Your environment has been pre-configured with a sample Campus to assist with these new concepts. Studios is equipped with flexible constructs that give you the ability to describe your campus footprint. These will be common throughout this workshop:

• Campus Fabrics: Your campus Workshop has been created, this would be equivalent to a site or region.
• Campus Pod: Your pod Home Office could be a building or MDF
• Access Pod: Your access pod IDF1 could be a floor or IDF

Show me an example!

CloudVision Network Hierarchy gives a better visual representation of how this might look in a real environment.

The switch in front of you is in Zero-Touch Provisioning (ZTP) mode as they would come from the factory. We will take this new switch from out of the box to provisioned without the use of CLI or the trusty console cable.

Out with the console cable

Zero-Touch Provisioning in this lab is performed using a bootstrap script delivered over DHCP option 67. This tells your device where to begin streaming for onboarding, you can read more on the CloudVision Help Center

Topology

Lab Topology

CloudVision Login

If you're not already logged into CloudVision (CVaaS), navigate to the Arista CVaaS for your lab.

Open CVaaS

Create a Workspace

We are going to create a workspace to propose changes to the Network Infrastructure. A workspace acts as a sandbox where you can stage your configuration changes before deploying them.

What is a Workspace?

To make a comparison, a workspace is like a configuration session in EOS or a branch in Git!

Studios Step 1Studios Step 2

Click on the Provisioning on the left side, then choose Studios.

Click Create a Workspace, give it any name you would like and click Create.

Onboarding Device

Workshop Lab Access Point and Switch Serial Numbers

Email	AP#1	AP#2	Switch
dane.newman@ahead.com	30862D496F5F	30862D4975EF	-
charles.hall@ahead.com	30862D497A0F	30862D497CAF	-
apsmith@cspire.com	30862D4979DF	30862D497B2F	-
cjones@udtonline.com	30862D496FEF	30862D49794F	-
jfowler@udtonline.com	30862D497A3F	30862D497ACF	-
sgrainger@adapture.com	30862D497D9F	30862D6CE2DF	-
bryan.deverell@cumberland.com	30862D49701F	30862D497D3F	-
erick.sanchez@cumberland.com	30862D4979AF	30862D497B5F	-
wallace.pederson@computacenter.com	30862D496E0F	30862D497AFF	-
dan.crews@computacenter.com	30862D49797F	30862D497D6F	-
jpucciariello@bulloch.solutions	30862D497CDF	30862D496FBF	-
jbryant@bulloch.solutions	30862D497A9F	30862D497A6F	-
stephen.norton@nwn.ai	30862D497D0F	30862D496F2F	-
cgordon@dgrsystems.com	30862D496F8F	30862D6CE30F	-
-	-	-	-
-	-	-	-
-	-	-	-
-	-	-	-
-	-	-	-
mbalagot+cws@arista.com	-	-	-

1. Navigate to the Devices tab on the left and let's look at the Inventory. There should be two devices with their Streaming status as Active. Identify your serial number (Device ID) and associated hostname (Device).

   Working with Workspace

   Your CloudVision is tied to your pod, anywhere it says pod-## you will replace with your assigned pod number.

   What's that hostname?

   The ZTP process used here will use the DHCP ip address as a suffix and produce a sw-X.X.X.X hostname. This is a good indication a switch is in ZTP.

   

2. Navigate to the Network Fabric Studio Campus Fabric (L2/L3/EVPN)

   Active Studios

   If you do not see the studios option below, there is a toggle on the right hand side you can toggle "off" the Active Studios to show all.

   

3. Click on the Add Campus Devices to launch the workflow

   

4. This workflow will take you through onboarding the device, follow the tabs below to complete the onboarding process.

   Step 1Step 2Step 3Step 4Step 5

   Select the Workshop > Home Office > IDF1 and add your assigned device from the Available Devices

   

   In the Role Assignment click on the Hostname field and name your switch pod##-leaf1. Where ## is your pod number.

   

   Validate your Inband Management Subnet and Inband Management VLAN match your assigned pod number, this will already be configured for you.

   • Subnet: 10.1.#.0/24 where # is the pod number
   • VLAN: 1## where # is the pod number

   

   This is a review of what you have configured to onboard your device, click on Build Workspace when you are ready.

   

   During this step, the Quick Action is adding your devices to the Studios inventory anf generating configuration for your new MLAG pair. If we had selected an EOS image, a task would have been created to upgrade the device during our onboarding.

   

5. The workflow is completing several steps to onboard the device, click Review Workspace to explore

   

6. We should see the detailed view of what's changing

   

7. In the workspace note the top leaf Summary box, there are several studios modified:

   1. Inventory and Topology: Devices selected are simply added to the Campus inventory
   2. Campus Fabric (L2/L3/EVPN): Devices we're added to their respective Campus Access Pod IDF1 and will inherit configuration from that part of the campus.

8. Let's leave this for now and navigate back to Studios home page and next we add some base configuration.

   You may need to click twice

   Studios will take you back to where you left off, you may need to click Studios on the side bar twice, or select Studios near the top left of your screen.

   

Applying Configuration

1. Click on Static Configuration

   

2. Let's add our new devices to this studio using the steps below

   Add Devices Step 1Add Devices Step 2

   Click on the Add + and select Devices

   

   Select your devices you recently added through the workflow

   

3. Now let's add our base configuration to these devices, this will include items like logging, banners, etc. for the lab. Use the steps below

   Device Configuration

   Here the base device configuration was generated for these devices before hand and include additional configuration for the workshop. This was done using Arista Validated Designs (AVD)

   Add Config Step 1Add Config Step 2 (Leaf1)Add Config Step 3

   Select a device and on the left and click the + Configlet to the right and select Configlet Library

   

   Select the correct configuration for the device selected.

   

   Ensure the configuration has applied!

   

4. Let's now review our workspace and the changes we've made by clicking on Review Workspace

   

5. You can review the configuration changes to the devices

   What happens to the ZTP Configuration?!

   We are replacing the Zero Touch configuration with a combination of base configuration (generated using AVD) and some dynamic configuration using Campus Studios

   

6. Click Submit Workspace to generate the Change Control

   

7. Click on View Change Control and let's explore executing a change control in the next section.

Executing a Change Control

1. Within the Change Control, you can review the configurations as we just did in the workspace. This is geared towards encouraging or enforcing review of changes prior to execution.

   

2. When you are ready, you can review Review and Approve at the top right, select the Execute Immediately toggle, and Approve and Execute.

   I approved my own change?!

   Yes, for this workshop you can approve your own change. In Settings > General Settings the toggle for Non-Author Change Control Review can be enabled enforce a change control review from a "non-author".

   

3. Let's explore what is going on during the execution of the change control, while this is happening, feel free to click Logs near the top right to watch what's happening.

   CC StartCC FinishCC Device Logs

   So what is the device doing?! There are a number of things that device goes through through a ZTP onboard

   1. The device configuration will be applied to the device
   2. The switch will reboot to bring the device out of ZTP mode (this will take about 10 mins)
   3. We did not upgrade the device, but if we had, software upgrade would then take place and reboot once more.

   

   Now that change control has finished, you will see a summary of any tasks that failed.

   

   There are a number of logs you can review, the list is long, but great detail about what's going on behind the scenes.

   

4. You can now return the Devices tab on the left and see our devices should be streaming with it's new hostname!

   

5. That's it! Your new campus switch went from out of the box ZTP mode to a configured member of the Campus fabric. We're going to explore further changes to this switch in the next lab!

🎉 CONGRATS! You have completed this lab! 🎉

LET'S GO TO THE NEXT LAB!