For optimum performance, you must match the minimum recommendations for the deployment.

Recommendations for the Platform Deployment

Table 1. Specifications for Platform Brick Size
Brick Size Cores required

for 2.1 GHz CPU

Cores required

for 2.3 GHz CPU

Cores required

for 2.6 GHz CPU

RAM Disk
Medium 10 9 8 32 GB 1 TB
Large 15 14 12 48 GB 1 TB
Extra Large 20 18 16 64 GB 2 TB
Note:
Table 2. Non-Cluster Deployment - Maximum Capacity
Brick Size Number of VMs

(in thousands)

Flows per Day

(in millions)

Total Flows

(in millions)

Flow Planning

(in millions)

Medium 4K 1M 4M 2M
Large 6K 2M 8M 4M
Table 3. Non-Cluster Deployment - Maximum Capacity for VMware SD-WAN
Brick Size Number of Edges

(in thousands)

Flows per Day

(in millions)

Total Flows

(in millions)

Medium 2K 1M 4M
Large 2K 2M 8M
Note:
  • The count of VMs includes the templates on the vCenter as well.
  • Total Flows is the maximum count of flows the system can store for the retention period.
  • Flow Planning is the total flows for which the system can perform security planning.
Table 4. Cluster Deployment - Maximum Capacity
Brick Size Cluster Size Number of VMs

(in thousands)

Flows per Day

(in millions)

Total Flows

(in millions)

Flow Planning

(in millions)

Number of Edges for VMware SD-WAN

(in thousands)

Large 3 10K 2M 8M 4M 4K
Extra Large 3 18K 6M 24M 4M 6K
Extra Large 5 30K 10M 40M 4M 10K
Extra Large 10 100K 15M 55M 4M 10K
Note:
  • The count of VMs includes the templates on the vCenter as well.
  • Cluster size is the total number of nodes in the cluster.
  • Total Flows is the count of flows in the system for the retention period.
  • The query to determine the Total Flows is count of flows in last 31 days, assuming the retention period as 31 days.
  • Flow Planning is the total flows for which the system can perform security planning.

Recommendation for the Collector Deployment

Table 5. Specifications for Collector Brick Size
Brick Size Cores required for 2.1 GHz CPU Cores required for 2.3 GHz CPU Cores required for 2.6 GHz CPU RAM Disk
Medium 5 5 4 12 GB 200 GB
Large 10 9 8 16 GB 200 GB
Extra Large 10 9 8 24 GB 200 GB
Note: The reservation for the CPU speed and RAM for each node must be 100% of the value specified above.
Table 6. Collector Deployment - Maximum Capacity
Collector Size Number of VMs

(in thousands)

Flows per Day

(in millions)

Flow count in 4 days

(in millions)

Number of Edges for VMware SD-WAN

(in thousands)

Medium 4K 2.5M 3.25M 4K
Large 10K 5M 6.5M 6K
Extra Large 20K 10M 13M 10K
Note:
  • The count of VMs includes the templates on the vCenter as well.
  • For a single deployment with more than one collector, the limitation on the total flows across collectors is based on the capacity of the platform.

Other Requirements and Considerations

  • The maximum time skew between the platform nodes has to be lesser than 30 seconds.
  • The availability of the NTP service is critical to system operations. Ensure that you do not reboot the platform node or the collector node when the NTP service is not available.
  • When the existing compute resources are completely used by the other processes on the platform, vRealize Network Insight crashes and does not recover automatically. If the services fail to recover, reboot the platform node.
  • If the network latency between platform node and upgrade server is greater than 500ms, the vRealize Network Insight upgrade might encounter an error. So, the network latency must be less than 500ms.
  • The recommended disk latency for optimal performance is up to 5ms. If the disk latency is greater than 5ms, the system performance degrades.
  • The recommended disk IOPS is 7500.

Supported Web Browser

  • Google Chrome: The latest two versions.
  • Mozilla Firefox: The latest two versions.

Recommendations to Support High Availability

You can customize vSphere HA options to enable vSphere high availability.
  • Host Failure - Restart VMs
  • Host Isolation- Disabled
  • Guest not heartbeating- Disabled