End of Support

The configuration guide is no longer being updated. Please refer to the CloudVision Help Center going forward.

Tips for Applying Profiles to the Interfaces

When interface profiles are added to configlets, the user should ensure the interface profiles are first applied to all the interfaces, and only after that the interface profile is completed.

Apply empty profiles to the interface first and then fill out the profile.The commands should look similar to the following:

```
interface et1-49
profile test
!
interface profile test
command description test
```

Note: If the profile is created first and then applied to the interfaces, the config validation and commit can take several minutes as opposed to just a few seconds if the profile is first applied and then created.

The configuration guide is no longer being updated. Please refer to the CloudVision Help Center going forward.

Deleting Configlets

Only unused Configlets can be deleted. If a Configlet is assigned to a device or a container, it cannot be deleted from the inventory. To delete a specific Configlet, its association should be removed from the devices and container.

Select a Configlet in the grid. A “trash can” icon will appear.
Click the Trash icon to delete the Configlet.
Related topics:

The configuration guide is no longer being updated. Please refer to the CloudVision Help Center going forward.

Importing and Exporting Configlets

You can import and export Configlets using the CloudVision graphical user interface (GUI). This enables you to easily share Configlets with others and back up specific Configlets.

For Configlets shared with you by another system user, you import Configlets from your desktop. When you share Configlets with another system user, you export Configlets to your desktop. You use the Configlets page to import and export Configlets or Configlet Builders.

Note: Both Configlets and Configlet Builders can be imported and exported using the GUI.

For more information, see:

Protection from Overwriting Configlets or Configlet Builders

CloudVision provides protection from accidentally overwriting exiting Configlets or Configlet Builders when importing a Configlet or Configlet Builder.

If you import a file that contains one or more Configlets or Configlet Builders that are named the same as Configlets or Configlet Builders already in CVP, the system automatically adds a suffix to the names of the items you are importing. The suffix that is added is in the format of “<number>”.

Importing Configlets or Configlet Builders

You import Configlets or Configlet Builders into CVP when another system user has shared a Configlet or Configlet Builder with you. Once you import Configlets or Configlet Builders, the imported items are available for use in CVP. You import Configlets or Configlet Builders from your desktop using the Configlets page.

Complete the following steps to import Configlets or Configlet Builders.

Open the Configlets page.
Click the Import icon, located in the upper right of the page.

Figure 1. Configlets Page Showing Import Icon

A dialog appears that you use to select the file that contains the Configlets or Configlet Builders you want to import.

Figure 2. Selecting Configlets or Configlet Builders to be Imported
Select the file that contains the items you want to import.
Click Open.

The Configlets or Configlet Builders in the file you selected are imported into CVP.

Exporting Configlets or Configlet Builders

You export Configlets or Configlet Builders when you want to share them with another system user. Once you export Configlets or Configlet Builders, the exported items are available to be sent to and then imported by the other system user. You export Configlets or Configlet Builders to your desktop using the Configlets page.

Complete the following steps to export Configlets or Configlet Builders.

Open the Configlets page.
Select the checkbox of each Configlet and Configlet Builder you want to export.

Figure 3. Configlets Page Showing Items Selected to be Exported
Click the Export icon (located in the upper right of the page).

A single file (.zip archive) that contains all of the items you selected is automatically downloaded to your desktop.
(Optional) You can rename the downloaded file and make a copy of it before sharing it.
Share the file with one or more system users.
Note: The items you share can be imported only on systems that support the import of Configlets and Configlet Builders (the Import icon on the Configlets page indicates support for this feature).

Related topics:

The configuration guide is no longer being updated. Please refer to the CloudVision Help Center going forward.

Image Management (CVP)

The Extensible Operating System (EOS) used by the switches are uploaded into CloudVision, and details about them are maintained in the Image Management Inventory.

The main purpose of the Image Management module is to enable you to manage the EOS operating system images across the devices in your current CloudVision environment. It provides you with the functionality required to:

Validate images
Upload EOS images to CloudVision
Maintain the inventory of available EOS images
Assign images to devices in your CloudVision environment

Sections in this chapter include:

The configuration guide is no longer being updated. Please refer to the CloudVision Help Center going forward.

Image Management Page

The Image Management page shows the current operating system images that are available for upload to CloudVision. Once uploaded, they can be assigned to devices.

You can navigate to the Image Management page through Provisioning > Image Management.

Related topics:

The configuration guide is no longer being updated. Please refer to the CloudVision Help Center going forward.

Validating Images

CloudVision Portal (CVP) provides automatic EOS image validation. This automated validation process helps to ensure that all devices in your CVP environment have EOS images that are supported by CVP.

The automatic validation of EOS images takes place whenever you:

Upload images to CVP or add images to images bundles.
Add devices to your CVP environment.

The automatic image validation ensures that images that are available to be included in image bundles and assigned to devices are supported by CVP.

Note: EOS images that are not supported cannot be added to an image bundle, or assigned to devices.

For more information refer to Alerts Indicating Unsupported EOS Image Versions.

Alerts Indicating Unsupported EOS Image Versions

If you attempt to include an unsupported version of an EOS image when creating an image bundle, CVP alerts you with an error to let you know that the upload cannot be done, because the version of the EOS image you are trying to upload is not supported.

If you attempt to add a device to CVP that has an unsupported EOS image, the Status column of the Inventory page indicates that an upgrade is required.

The Network Provisioning page also indicate that the device is running an unsupported image (this alert shows only when placing your cursor over the device icon).

Related topics:

The configuration guide is no longer being updated. Please refer to the CloudVision Help Center going forward.

Managing Configurations

CloudVision Portal (CVP) enables you to manage configurations by assigning configurations to containers and to devices. Configurations that you assign to containers are applied to all devices under the container's hierarchy. CVP also enables you to easily view the configuration currently assigned to containers and devices.

Applying Configurations to Containers

Applying configurations to containers involves adding Configlets to containers or removing Configlets from containers.

Adding Configlets

Locate the container.
Right-click the container and choose Manage >Configlet. This will open the window display the inventory of configlets.
Select the configlet and click Update. This will provision configlet add for the container and all the devices under it.

Removing Configlets

To remove the configlet inventory from a container.

Locate the container.
Right-click the container and choose Manage>Configlet .
Remove the configlets.
Click Update.

Figure 1. Remove the configlet and select Update

Applying Configurations to a Device

Applying configurations to devices involves adding Configlets to devices.

Note:When you update a device configuration using configlets, CVP replaces the entire device configuration with the Designed Configuration for the device. For new devices with pre-existing configurations added into CVP, you must explicitly perform a one-time reconciliation to save the desired device-specific running configuration in CVP. If you do not, that configuration may be lost, or the configuration update task may fail (see Reconciling Device Configurations at the Device Level).

Adding Configlets

Select the device and choose Manage > Configlets.
This loads the configlet inventory screen.
Select the configlets.
You are required to validate the configuration.
To validate the configurations, select Validate.
The validation screen will be loaded.
Select Save to propose a Config Assign action.
When saving the session, this will spawn a Config Assign task.

Viewing the Configuration Applied to Devices

CloudVision Portal (CVP) enables you to use the Network Provisioning screen to view the configuration (Confliglets) currently assigned to devices. When you view the Configlets, you can also see which Configlets are inherited from Containers, and which are applied directly to the device.

Complete the following steps to view the Configlets applied to a device.

Go to the Network Provisioning screen.
Make sure you are using the topology view, not the list view.
Click on the device in the topology.
Click the Configlet icon.
The Configlets applied to the device are listed in a drop-down list.
- If a Configlet is inherited from a Container to which the device belongs, the Container icon appears in front of the Configlet name.
- If a Configlet is directly applied to the device, no Container icon is shown next to the Configlet name.

Figure 2. Viewing the Configlets applied to a device

Rolling Back Configurations Assigned to a Device

CloudVision's Network Rollbacks feature enables you to restore a previous configuration to devices. You can apply the rollback to all the devices in a container, or to single devices. When you rollback a container or device, you select the date and time for the rollback and whether you want to rollback the configuration or EOS image (or both).

See Rolling Back Images and Configurations for details.

The configuration guide is no longer being updated. Please refer to the CloudVision Help Center going forward.

Configuration Validation

The validation screen consists of three panes.

Pane 1: Shows the proposed configuration.
Pane 2: Shows the designed configuration. (This shows how a resulting running configuration will look like after successful configuration push.)
Pane 3: Shows the current running configuration of a device.

Figure 1. Validating your configurations

The configuration guide is no longer being updated. Please refer to the CloudVision Help Center going forward.

Using Hashed Passwords for Configuration Tasks

Some EOS commands take a password or a secret key as a parameter. There are usually two ways of passing EOS command parameters:

As plain text.
As a hashed string.

Note: Because EOS always returns the hashed version of the command in its running configuration, using the plain text version of commands in Configlets results in the following issues:

CVP shows that there are configuration differences that need reconciling, even if there are none.
Compliance checks show devices to be out of compliance.

To avoid these issues, you should use the hashed version of EOS commands in Configlets (for example, use ntp authentication-key 11 md5 7 <key> instead of ntp authentication-key 11 md5 0 <key> ). Using the hashed versions of commands also keeps the real password hidden.

The configuration guide is no longer being updated. Please refer to the CloudVision Help Center going forward.

Reconciling Configuration Differences

CloudVision enables you to reconcile differences between the designed (managed) configuration and running configuration on devices so that CVP is maintaining the full configuration of each device.

Key Terms

Reconcilable differences	Configuration differences between the designed configuration and the running configuration, which do not conflict with the configuration in any configlets, other than the reconcile configlet.
Reconcile configlet	A specially marked device configlet that is system generated and used to store reconcilable differences in order for the designed configuration to match the running configuration.

Reconciling device configuration differences does not require a task, because there is no configuration to be pushed out to the device. Reconcilable differences are only adjusted in the reconcile configlet, to match the running configuration. Because of this, there is no task pushed to change the running configuration.

When you reconcile device configuration differences, you add the reconcilable differences found in the running configuration to the reconcile configlet of the designed configuration.

For details on reconciling device configuration differences, see:

Reconciling Device Configurations Differences at the Container Level

CloudVision enables you to reconcile device configuration differences for all devices under the hierarchy of a selected container, instead of having to initiate this device by device.

Note: The designed configurations of devices in the container that do not have reconcilable differences are not changed.

For devices that have reconcilable differences, the lines or commands on the device that are not present in the designed configuration are pulled into the reconcile configlet for that device in one of two ways:

Using the existing reconcile configlet that is specific to that device.
Creating a new reconcile configlet that is specific to that device. This is done when there is no existing reconcile configlet specific for the device. The system automatically creates a unique name for the configlet.

A green checkmark beside the configlet indicates it as the reconcile configlet for the device.

Complete the following steps to reconcile device configuration differences for a container:

Go to the Network Provisioning screen.
Locate the container in the topology where you want to reconcile the configurations of all devices under that container hierarchy.
Right-click the container, hover the cursor on Reconcile, and click either Reconcile All or Reconcile New.

Figure 1. Device configuration reconciliation at the container level

The Reconcile New option reconciles only the configuration lines that exist on the device, but not in the designed configuration.

The Reconcile All option reconciles new lines and also lines that differ in designed and running configurations. This usually brings the device into compliance because the resulting designed configuration will be identical to running configuration. However, there can be cases where in spite of reconciling device configuration lines, the designed configuration may not end up identical to running configuration. In these cases, no changes are made to the reconcile configlet. Arista recommends to go through the device-level reconcile process (See Reconciling Device Configurations at the Device Level), and select the desired lines.

Note: The bell icon in the upper right corner turns yellow to indicate unread notifications.
(Optional) To view the notification for the reconciliation, click the bell icon. The notification list appears showing the container-level configuration reconciliation, and any other unread notifications.

Figure 2. List of unread notifications

Reconciling Device Configurations at the Device Level

CloudVision enables you to reconcile device configuration differences at the device level (specific, individual devices). Configuration differences at the device level occur when there are reconcilable differences in the running configuration of the device.

The Configuration Validation screen shows details of the configuration differences. When the system identifies a reconcilable difference, the Reconcile option becomes available, and the extra reconcilable configuration is listed in a text editor on the screen.

Reconcile Configlets

You use a type of configlet called a reconcile configlet to reconcile device configuration differences at the device level. A reconcile configlet is a configlet for a single specific device, and is explicitly marked as the reconcile configlet for that device. The reconcile configlet for a device contains the additional running configuration for that device.

Note: There is only one reconcile configlet for any device. It is the only configlet that contains the additional running configuration for the device.

Every time a device-level or a container-level reconcile is performed, the reconcile configlet for each device included in the reconcile action is modified to include the extra running configuration.

To reconcile device level configuration, perform the following steps:

If required, select additional lines from running configuration to reconcile.
Click the blue Reconcile button to add the reconcilable configuration in the running configuration to the reconcile configlet of the designed configuration.

Figure 3. Configuration validation screen showing device-level configuration differences
(Optional) Click Edit next to the configlet name to edit or rename the reconciled configlet.
(Optional) Click the reconcile disk icon next to the configlet name to save the reconciled configlet with the extra commands present in the running configuration.

Figure 4. Reconcile Disk icon

Note: CVP will not execute pushing a configuration that causes CVP to lose connectivity with the device if the management interface or IP is missing in the configuration. When the task is executed, it will fail.
Click Save.

Page 9 of 19

End of Support

CloudVision Configuration Guide - Tips for Applying Profiles to the Interfaces

Tips for Applying Profiles to the Interfaces

CloudVision Configuration Guide - Deleting Configlets

Deleting Configlets

CloudVision Configuration Guide - Importing and Exporting Configlets

Importing and Exporting Configlets

Protection from Overwriting Configlets or Configlet Builders

Importing Configlets or Configlet Builders

Exporting Configlets or Configlet Builders

CloudVision Configuration Guide - Image Management (CVP)

Image Management (CVP)

CloudVision Configuration Guide - Image Management Page

Image Management Page

CloudVision Configuration Guide - Validating Images

Validating Images

Alerts Indicating Unsupported EOS Image Versions

CloudVision Configuration Guide - Managing Configurations

Managing Configurations

Applying Configurations to Containers

Applying Configurations to a Device

Viewing the Configuration Applied to Devices

Rolling Back Configurations Assigned to a Device

CloudVision Configuration Guide - Configuration Validation

Configuration Validation

CloudVision Configuration Guide - Using Hashed Passwords for Configuration Tasks

Using Hashed Passwords for Configuration Tasks

CloudVision Configuration Guide - Reconciling Configuration Differences

Reconciling Configuration Differences

Key Terms

Reconciling Device Configurations Differences at the Container Level

Reconciling Device Configurations at the Device Level