You can set up vRealize Network Insight Cloud collector by importing OVA to your VMware vCenter server.
To add a Collector VM, you must do the following:
- Download the Collector VM OVA.
- Generate and copy the shared secret
- Deploy the data collector VM OVA using vSphere web client or vSphere windows native client.
Note: Before you add a Collector VM, ensure that you review and meet Recommendation for the Collector Deployment for optimum performance. To know about the Collector deployment requirement, see the
System Recommendations and Requirements topic.
Generate a Shared Secret
You can generate and import the vRealize Network Insight Cloud collector virtual appliance.
Procedure
Deployment Using vSphere Web Client
You can import the vRealize Network Insight Cloud Collector OVA using vSphere Web Client.
Procedure
Collector Recommendation and Other Requirements
For optimum performance, you must match the minimum recommendations for the deployment.
Recommendation for the Collector Deployment
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.
Collector Size | Number of VMs (K = Thousand) |
Flows per Day (M = Million) |
Flow count in 4 days (M = Million) |
Number of Edges for VMware SD-WAN (K = Thousand) |
---|---|---|---|---|
Medium | 4K | 2.5M | 3.25M | 4K |
Large | 10K | 5M | 6.5M | 6K |
Extra Large | 35K | 10M | 13M | 10K |
Note:
- The count of VMs and edges mentioned in the table is the maximum individual limit for a single deployment. So, if you have edges in your setup, you might have to reduce the VM count.
- The count of VMs includes the templates on the VMware 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 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.
- The recommended network latency between platform and collector VMs for optimal performance is up to 150ms. The system performance might degrade beyond this limit.
- For Network Map, the maximum supported firewall rules per VMware NSX-T Manager (including of DFW and edge rules) is 5000.
Supported Web Browser
- Google Chrome: The latest two versions.
- Mozilla Firefox: The latest two versions.
Recommendations to Support High Availability for Collector
You can customize vSphere HA options to enable vSphere high availability for the Collector.
- Host Failure - Restart VMs
- Host Isolation- Disabled
- Guest not heartbeating- Disabled