System Requirements

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.
Table 1. Minimum System Requirements
Required Hardware
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:

  • CPUs: 16 cores
  • RAM: 32 GB
  • Disk: 1 TB GB (use RPM installer)
  • Disk Throughput: 20 MB/s
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:
  • CPUs: 28 cores
  • RAM: Recommended 52 GB
  • Disk: 1 TB
  • Disk Throughput: 40 MB/s
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.
Table 2. Latency Requirements
Latency Requirements
  • The latency between two CVP nodes must be up to 10 ms (recommended 5 ms or less).
  • The latency from a CVP node to an EOS device must be up to 500 ms.
  • All three nodes must be installed in the same physical location and on the same local area network.
  • Physical appliances should be installed in the same rack so that traffic can flow between the appliances while only traversing a top-of-rack switch (or a redundant pair preferably).
  • Physical appliances can be installed in adjacent locations but the latency between devices should be minimized, enough bandwidth must be available, and no firewall devices should be placed in between the appliances.
  • Virtual appliances should be deployed as part of the same/local virtual infrastructure instance with low latency and no restrictions on traffic between the cluster nodes.
Table 3. Required Software Versions
Required Software Versions
The software versions compatible with CVP are:
  • EOS license: Z license
  • CVP license: Full subscription license
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
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.

Related topics: