A-04 | Operations, Dashboards, and Events¶
Overview¶
In this lab we will explore some of the features of CloudVision to manage and operate your campus network.
Intro to Network Hierarchy¶
Campus networks can be rather extensive in size and their reach, including many sites, buildings, and floors where your precious network gear is deployed. The Network Hierarchy view aligns closely with the same way you'll manage your wireless access points in CV-CUE:
-
Click on the
Network Hierarchytab on the left -
Note your
Networkcontains the workshop campus, campus pod, and access-pod as you drill down. - Click on
Workshopto view a summary of all the devices deployed under the top level campusWorkshop -
Click on
IDF1and note we now get more detail about the switches and clients connected to those devices in theOverviewtab. -
Click on the
Front Paneltab to view more detail about what's connected, the capabilities of your switches in the stack, and access to quick actions to make changes on the interfaces. -
Let's now use Network Hierarchy to drill down into a compliance issue.
Configuration Compliance¶
The Network Hierarchy view is one of many ways to visualize your campus, namely to drill down to a specific area of the network to configure or troubleshoot an issue.
to showcase compliance panel and 2 devices should flagged (due to rollback above). This will open the compliance dashboard and we can sync the config from there via Change Control.
- If you're not already on the
Network Hierarchypage, click the tab on the left. -
Click the top level
Networkobject, and take note of theCompliancepanel on the right -
We have 2 devices that are violating the
Configurationcompliance item -
Click on
Complianceand you should see theCompliance Overviewwith our 2 devices out of configuration compliance -
Let's select your device below and click
Sync Config -
This will create a
Change Controlwith our two devices -
Click on the
Review and ApproveWhy is our configuration out of sync?!
Recall CloudVision is designed to act as the "Source of Truth" for your configuration. It contains a designed configuration it considers the standard, driven through configuration in Studios. When we added our Vlan in the previous step, we rolled that change back, and now there is a discrepancy.
This could be a real life scenario where a VLAN was added, rolled back due to an unforeseen issue, and scheduled to be added at a later date. We need that vlan, we are reminded the device is out of compliance, and possibly for a good reason!
-
Click on
Approve and Executewhen you're ready -
This is pushing the designed configuration back to the device
-
Let's go back to our
Network HierarchyorDevices > Compliance Overviewand we should see are switches are not in compliance again.
Dashboards¶
Dashboards are an important way to visualize commonly requested information, we've already seen the Campus Health Dashboard a few times in previous labs. This lab section shows you how to navigate the built-in dashboards and customize your own.
Campus Health Overview¶
-
Open the Dashboards Section and we will see the Campus Health Overview dashboard is set to our home dashboard.
Dashboard Home Page
CloudVision has a couple features that customize a users experience. There is a built in profile for
Campus Monitoringthat can be applied to a user role, this will set the "Campus Health Overview" dashboard as the primary dashboard. A user can also select any built-in or custom dashboard as the home/primary dashboard. -
You’ll be presented with a curated selection of common campus related monitoring tools
-
Feel free to explore the Campus Health dashboard briefly and then navigate back to the Dashboards landing page by selecting Dashboards in the upper left.
Device Health¶
-
Next, Select the Device Hardware dashboard
-
By default, this dashboard selects all devices.
-
Change the dashboard to select only
leaf1aorleaf1bby changing fromdevice: *todevice:to match a single device. Once you’ve selected an individual device, the dashboard will filter to results for only this device. -
Navigate back to the Dashboards landing page by clicking Dashboards in upper left.
Custom Dashboard¶
Next, let’s add a new customized dashboard. There are three main constructs we will touch on here:
- Metrics (Devices): telemetry data specific to a device
- Metrics (Interfaces): telemetry data specific to the interfaces of a device
- Summaries: a metric or set of metrics summarized into a single view
There is a lot to unpack in dashboards as you have a significant amount of power in customizing the data and look of your dashboard. See how dashboards are quickly created before we get started.
Let's get started:
-
Click the
+ New Dashboardbutton. -
Provide a useful
Namefor the Dashboard, such asPod##-Student# -
Next, let’s add a combination of visualizations that we want to capture
- First, click the drop down on the upper right and change from
MetricstoSummaries -
Within the
Summarieslist, click on, or drag theEventswidget into the dashboard canvas -
Within the
Eventstile now added to your dashboard, click theConfigurebutton -
Within the right side menu bar, select the following:
Dashboard Settings
Key Value View Mode Severity Timeline Show Active Only True Dataset Access-Pod: IDF1 -
Dismiss the customization menu by clicking the in upper right corner
-
Next, change the
Summariesmenu back toMetrics -
Within the Metrics menu, click and drag a
Tableand aHorizon Graphto the canvasDrag the tiles
You can drag the tiles around by the respective menu bars and resize each tile using the lower right corner handles.
-
Let's configure the
Tablefirst by clicking the then click the three-dots menu and clickConfigureTable Settings
Key Value Data Source Devices Metrics #1 802.1X Interface Count Metrics #2 CPU Utilization Metrics #3 Total Power Granted Metrics #4 ARP Table Size Metrics #5 Boot Time -
Dismiss the customization menu with the button in upper right
-
Now let's configure the
Horizon Graphby clicking the then click the three-dots menu and clickConfigureHorizon Graph Settings
Target your student device below!
Key Value Data Source Interfaces View Type Multiple Metrics for One Source Interface (device) pod##-leaf1Interface (interface) Ethernet1Metrics #1 Bitrate In Metrics #2 Bitrate Out Metrics #3 Operational Status Metrics #4 Interface Authentication State -
Dismiss the customization menu with the button in upper right
-
You can resize and drag the components around, but you should have a new dashboard that looks something like this.
-
Save and completed the dashboard customization by clicking the
Donebutton in upper menu bar
Events¶
In this section, we will explore the Events stream and the tools and filters to help process and manage critical errors versus informational data.
-
First, open
Eventsfrom the menu bar -
Next, select a different time frame for the summary visualization, click the current time selection and change this to
1 Hour -
You can also toggle between a bar graph and event count display
-
Focusing on the
Event Listnext, Note theExportbutton to download the current Event list as CSV. Notice you can downloadAll Eventsor onlySelected -
Next, select the Gear icon to toggle
Event List Roll Up. This setting combines repeated events into groups. Toggle this On and Off, watch the effect this has on the list of Events. -
Next, utilizing the Event Filters on the right pane is important to reduce the amount of data displayed.
Filter Settings
Key Value Severity Critical,ErrorType #1 `Unexpected Link Shutdown Type #2 Device Clock Out of Sync -
Acknowledge and Unacknowledging events
-
To acknowledge from the filtered event list, select specific events and Acknowledge them.
-
Adding a note is optional, select the
Acknowledgebutton to mark these selected events. -
Acknowledged events are not deleted from the event list, only flagged as acknowledged and can be referenced by changing the filtered
Acknowledgement State. ClickAcknowledgement Stateand selectAcknowledged -
Un-acknowledging an event can be done in the same way, click the box to the left of the
Acknowledged event, and clickUnacknowledgeat the top of the event list.
-
-
Events and filtering lab section complete!
Customize Notifications¶
In this lab, you will configure CloudVision to send an email alert to an email address using the built-in “SendGrid” email service. There are other notification systems natively supported in CloudVision, but we'll focus on email for this lab (Example: email, chat, SNMP, Syslog, etc).
- Configure
SendGridemail service. - If you are not already, click on the
Eventsmenu option. -
Click on the
Notificationsbutton in the top right of the screen. -
Check the system status for the
Config back-endandRelay back-endStatus Unknown!?
Before receivers and notifications are configured, the status will be “Unknown”.
-
Now, configure the SendGrid receiver by clicking on
Receiversin the menu, then click on theAdd Receiverbutton. Name the receiverSendGrid for Campus ATD, then click theAdd Configurationbutton and selectSendGridfrom the menu options. -
Type in
cvaas-alerts@arista.comin the email address field. This is a shared email address that you can receive emails at during this lab and check theSend notification when events are resolvedcheckbox. Click theSavebutton in the upper right hand side of the screen to save your new receiver. -
Once you are happy with receiver’s configuration, click the
Savebutton at the top of the screen -
Next, configure a
Ruleto use the new receiver. Click on theRulesmenu option, then clickAdd Rule -
Configure
Rule Conditionsfor this rule. Click on the+ Devicebutton, then choose your switch from theDevicedrop down box. -
Now click on the
+ Event Typebutton. AddEvent Typesby choosing them from the drop down box as shown in the image below: -
Select all of the severity options by clicking on the
+ Severitybutton and choosing the options from the drop down box. -
Next, choose your new
SendGrid for Campus ATDreceiver from theReceiverdropdown box, select theContinue Checking Rulesbox, and save your changes by clicking on theSavebutton.SAVE the changes!!
Make sure to save your changes in this screen with the Save button along the top of your screen.
-
Now lets test your new receiver and rule
-
Click on the
Statusmenu option. Configure theTest Notification Senderby changing theEvent Typeto beDevice Stopped Streamingand selecting your switch from theDevicedrop down box. Click theSend Test Notificationbutton. -
After a minute or two, you should receive the email alert at the email address you configured in the Receiver
-
You can remove your event receiver to avoid additional emails before continuing!
🎉 CONGRATS! You have completed the Wired labs! 🎉

















































