The login screen is displayed when you first connect to the application using a web browser.
The CloudVision Portal (CVP) application is accessible after the CVP service has been started on the appliance. The login screen is displayed when you first connect to the application using a web browser. JavaScript must be enabled in the browser for the web application to work.
Sections in this chapter include:
/CVP%20Login%20Page.png)
/Login%20Section.png)
The username and passwords required will depend on the authentication method and accounts previously set up. Login using the username and password created when CVP was installed. If you chose the local authentication and authorization options, login initially using cvpadmin for the username and password.
All features including Devices, Events, Provisioning, Dashboards,and Topology are displayed on the home panel.
/Homescreen.png)
The home page provides the following selections.
Starting with 2023.2.0 release, CloudVision provides you with in-product documentation support called Help Center. The Help Center allows you to access detailed information on CloudVision features and functionalities. Prior to 2023.2.0 release, Help Center was available as a beta functionality.
/HelpCenter.png)
When you click on the Help Center icon (?), the Help Center page for the corresponding CloudVision screen is displayed. The main article explains the CloudVision screen you are viewing and the workflow. Additionally, the Related Articles section displays a list of related topics that are relevant to the main topic.
/Help_Center_Search.png)
/Help_Center_Search_Page.png)
/Help_Center_Location_page.png)
/Help_Center_Arrow.png){kind=icon}
/Help_Center_Pop_Out.png)
/Help_Center_Navigation.png)
/Help_Center_Feedback.png)
The omnibox performs a search and displays results from all sections in CloudVision. You must select a result for navigating to the corresponding CloudVision section.
Click the search icon at the upper-right corner of the CVP screen to access the omnibox.
/Omnibox.png)
The Omnibox provides a variety of results classifying them by the section it belongs to, an associated device or section name, and sometimes a description that explains what kind of result it is.The list of potential search result modules are:
CloudVision displays matching results from Devices and Topology sections when a search is performed using theJPE keyword.
/Omnibox%20Search%20with%20JPE%20Keyword.png)
If you select athens from the Devices section, CloudVision displays the Device Overview screen of athens.
If you select athens from the Topology section, CloudVision displays athens node in the Topology view.
If a search is performed with the athens keyword, CloudVision displays results from Devices, Event, Metrics, and Topology sections.
/Omnibox%20Search%20with%20Athens%20Keyword.png)
CloudVision enables you to customize the visible options and dashboard logo shown on the home page. You change the visible options and dashboard logo by customizing them from the Settings page.
By default, no dashboard logo is selected. The image you select for the logo appears in the dashboard next to the notifications icon.
/Custom%20Dashboard%20Logo.png)
Complete the following steps to customize the visible and dashboard logo:
/gear_icon.png){kind=icon}
/Settings%20Screen.png)
You can access the CV-CUE service via either the CLI Access or the UI Access.
To log in to the wifimanager container using CLI, run the /cvpi/apps/wifimanager/bin/wifimanager.sh cli 2>/dev/null command on the primary or the secondary node.
/CLI%20Access.png)
You can now run wifimanager commands. See the Wifimanager CLI Commands for a list of wifimanager CLI commands and their descriptions.
The URL to access the wifimanager UI is http(s)://<CVP-IP>/wifi/wifimanager is where CVP-IP refers to the actual CloudVision Portal (CVP) IP/domain name.
The URL to access the cognitive Wifi UI is http(s)://<CVP-IP>/wifi/aware where CVP-IP refers to either the actual CVP IP or domain name.
For example, if the IP address of CVP is 10.12.3.4, then the URL to access the wifimanager UI is https://10.2.3.4/wifi.wifimanager and the cognitive Wifi UI is https:////10.12.3.4/wifi/aware.
You can access CV-CUE UI by clicking on the WiFi tab in the CVP UI, or you can access it directly using the URLs of either wifimanager UI or Wifi UI.
/UI%20Access.png)
When you access the UI for the first time, you need to apply the CV-CUE service license.
/cvw%20service%20license.png)
ifconfig command on the CV root shell to get the
eth0 MAC addresses of the primary and secondary CV servers (you need not access
the wifimanager CLI for this). You need to include both these MAC addresses
when you email support to request a license. One license is generated for the
two (primary and secondary) MAC addresses.
Once you apply the license, you must log in to the CV-CUE UI using the following default credentials:
Username: admin
Password: admin
You can then change the password and add other users.
CloudVision Portal (CVP) can be run on ESX or KVM hypervisors. Before you can begin using the CVP, you must complete the CVP setup process which, involves the following:
Deploying the CVP OVA file should be the first step in any setup. After the CVP OVA file is deployed, you can choose between the two configuration methods for CloudVision Portal (CVP).
Pre-requisites:
Use of the Deploy OVF Template requires the VMware Client Integration plugin, which is not supported by the Chrome browser after versions 42.
%20Setup/Deploy%20the%20OVA%20template.png)
%20Setup/Location%20of%20the%20OVA%20file%20.png)
%20Setup/Select%20name%20and%20folder%20location%20for%20OVA%20file.png)
%20Setup/Select%20the%20resource.png)
%20Setup/Review%20OVA%20template%20details%20.png)
%20Setup/Select%20the%20destination%20storage.png)
It is recommended to select Thick provision lazy zeroed under the Select virtual disk format dropdown menu.
%20Setup/Setup%20the%20networks.png)
%20Setup/Select%20the%20Finish%20button%20to%20accept%20these%20settings_1.png)
VCenter begins to deploy the virtual appliance. Once the appliance is deployed, you can configure the CVP application using either Shell-based Configuration or ISO-based Configuration.
The CloudVision database (hbase/hadoop) is deployed across the three nodes within the CloudVision cluster. The integrity of this database is critical to the correct functioning of CloudVision, and thus, there are specific requirements on the hypervisor and storage for these virtual machines forming these nodes.
Within the CloudVision infrastructure, data is constantly being written to Apache hadoop by all nodes. Disk snapshots used by VMware have no hooks into the hbase quiesce states, meaning a snapshot of a disk state would almost always be inconsistent and lead to database corruption during a restore process. This results in a snapshot having no meaningful use as a restore point due to the nature of the database, which is typical for database application performance using VMware Snapshots (VMware reference).
VMware Snapshots are very I/O intensive, leaving almost no I/O for the virtual machines during the snapshot process. Impact on resources, such as disk, can lead to hbase and zookeeper failures. These symptoms are evident in multiple cases where the support team has identified snapshots that were in progress before failures.
VMware does not recommend using VM Snapshots as backups (https://kb.vmware.com/s/article/1025279), therefore other backup mechanisms are recommended by Arista as outlined below.
Daily backups of the CloudVision provisioning data are automatically scheduled to be taken at 2AM UTC. This backup file is stored locally on the CloudVision cluster. Common practice by customers is to schedule a copy of this backup file from the CloudVision cluster to some external data store.
There is an example script to help automate the copying of the backup file available on the Arista Github site (link).
CloudVision telemetry data received from switches is replicated between the CloudVision clusters. In the event a single node becomes unavailable and a new node is added to the cluster, this telemetry data is replicated to the new node.
Arista EOS with the Streaming Telemetry agent (TerminAttr v1.7.1 and later) supports establishing connections to multiple CloudVision clusters. This enables the user to send the telemetry data to a backup CloudVision instance, to maintain an up-to-date redundant store.
There is a detailed explanation of this deployment model available on the Arista EOS Central site (https://arista.my.site.com/AristaCommunity/s/article/cvp-ha-deployment-guide), which would assist with the design and deployment of this HA solution.
Once you complete these tasks, you can configure the CVP VM.
You download the tarball to the host server that is configured for KVM. The files contained in the .tgz archive include:
| Filename | Description | |
|---|---|---|
| 1 | disk1.qcow2 | VM disk image for the CVP application. |
| 2 | disk2.qcow2 | Data disk image for the CVP application. |
| 3 | cvpTemplate.xml | A template for creating the XML file for libvirt domain specification. |
| 4 | generateXmlForKvm.py | A script for generating the CVP VM definition XML based on the XML template. |
| 5 | createNwBridges.py | A script for creating the network interfaces for the CVP VM. |
Complete the following steps to download and extract the CVP VM .tgz archive:
The second task in deploying CVP for KVM involves creating the bridges and interfaces that provide network connectivity for the CVP VM. You use the CreateNwBridges.py script you extracted in the previous task to create the required bridges and interfaces.
Complete the following steps to create the network interfaces for CVP KVM connectivity:
The figure below shows an example of creating a single device bridge for a single-node deployment.
%20Setup/Creating%20a%20device%20bridge%20(single%20node%20deployment).png)
The third task in deploying CVP for KVM involves generating the XML file that you use to define the CVP VM. You use generateXmlForKvm.py script and the cvpTemplate.xml file you extracted previously to generate the XML file you use to define the CVP VM.
The cvpTemplate.xml file is a template that defines wildcard values that are filled by the other parameters that are specified when you execute the script.
Complete the following steps to generate the XML file:
Generation of XML file used to define CVP VM shows an example of an XML being generated that can be used to define a CVP VM named cvpTest. The generated XML file is named qemuout.xml.
%20Setup/Generation%20of%20XML%20file%20used%20to%20define%20CVP%20VM.png)
The last task in deploying CVP for KVM is to define and launch the CVP VM. You use the XML file you generated in the previous task to define the CVP VM.
Complete the following steps to define and launch the CVP VM:
Defining and Launching the CVP VM shows an example of the use of the commands to define and launch a CVP VM named cvpTest. The XML file used to define the CVP VM is named qemuout.xml.
%20Setup/Defining%20and%20launching%20the%20CVP%20VM.png)
You can now login as cvpadmin and complete the configuration of the CVP application. See Configuring a Single-Node CVP Instance using CVP Shell for the steps used to complete the configuration.