The CloudVision Portal is deployed as a virtual or physical appliance.
Note: As of 2022.2.0, production instances of CloudVision should be deployed in a 3-node cluster. Single-node clusters must be used only for lab deployments.
|Lab Deployment (< 25 devices)||Production Deployment|
Single node instances of CVP are supported only in lab environments. The minimum hardware requirements to use CVP in a lab environment are:
|A 3-node cluster must be used for production deployment. Each node must be configured to meet the minimum system requirements. The recommended hardware required per node to deploy CVP in a production environment (3-node cluster) are:
Note: For production deployments, information about device scale is available in the release specific version of the product release notes. For more information on throughput, refer to Troubleshooting and Health Checks.
Note: Deploying a single node instance in a production environment does not provide load sharing or redundancy capabilities; which, in node failure scenarios could lead to data loss or data corruption. Due to these reasons, single node deployments will no longer be supported starting CVP release 2022.1.0. Cloud service deployment model of CloudVision (CVaaS) is recommended for production environments with smaller device scale.
|Required Software Versions|
|The software versions compatible with CVP are:
Note: For updates on compatible EOS switches, supported browsers, and supported TerminAttr versions, refer to the release specific version of the product release notes available at https://www.arista.com/en/support/software-download.
Note: CVP 2020.1.0 and future releases support host-to-host vmotion where the storage is shared betweenESXI hosts. Only one host can be in vMotion at a given time.