Lab Guide 1 - Multi-vendor

1. Configuration Deviation

CloudLabs can simulate a manual configuration change on a device in the blueprint. Inserting an extraneous configuration statement on a device activates an anomaly indicator. This serves as an illustration of Apstra’s IBA capabilities.

  1. Go to your CloudLabs portal, and toggle the Insert a Configuration Change slider. The slider will turn green and you will see this message:

    portal_insert_config_change

  2. Return to the Apstra UI. Soon, a config deviation anomaly will appear. Notice the different location where red indicators have appeared.

    config anomaly

  3. Click the Anomalies tab to move to the Anomaly Details view.

    active_anomalies_330.png

  4. Click spine2 to go to the telemetry view for spine2. This anomaly and any others for this devices are listed in this view.

    spine2_telemetry_330.png

  5. Click the Config tab to see the anomalie’s details. Scroll down to see the config deviation.

    config_dev_details_330.png

    config_dev_actual_330.png

  6. After you’ve identified the problem, you can restore the original config by returning to the CloudLabs portal and toggling off Insert a Configuration Change and the blueprint anomaly will clear. In a production environment, any configuration deviations could have their alerts acknowledged using the Accept Changes button. You would also be able to use the Apply Full Config in the Apstra UI to revert the device back to the golden configuration

Milestone 4

When you have viewed the config deviation and how Apstra notifies you of the problem, you have completed the exercise.