For the production instance of vRealize Operations Manager to function optimally, your environment must conform to certain configurations. Review and familiarize yourself with these configurations before you deploy a production instance of vRealize Operations Manager.


vRealize Operations Manager supports up to 240,000 monitored resources spread across six extra large analytic nodes.

Size your vRealize Operations Manager instance to ensure performance and support. For more information about sizing, see the following KB article 54370.


Deploy analytic nodes in the same vSphere cluster and use identical or similar hosts and storage. If you cannot deploy analytic nodes in the same vSphere cluster, you must deploy them in the same geographical location. vRealize Operations Manager does not support deploying analytics nodes in multiple geographical locations.

Analytics nodes must be able to communicate with one another always. The following vSphere events might disrupt connectivity.

  • vMotion

  • Storage vMotion

  • High Availability (HA)

  • Distributed Resource Scheduler (DRS)

Due to a high level of traffic between analytics nodes, all analytics nodes must be Layer 2 Adjacent. Layer 2 Adjacent means that each node is located on the same VLAN and IP subnet, and that VLAN is not stretched between data centers. Latency between analytics nodes cannot exceed 5 milliseconds, and the bandwidth must be equal to or higher than 1 GB per second. It is recommended that bandwidth be 10 GB per second at minimum.

If you deploy analytics nodes in to a highly consolidated vSphere cluster, configure resource reservations. A full analytics node, for example a large analytics node that monitors 10,000 resources, requires one virtual CPU to physical CPU. If you experience performance issues, review the CPU ready and co-stop to determine if the virtual to physical CPU ratio is the cause of the issues. For more information about how to troubleshoot VM performance and interpret CPU performance metrics, see Troubleshooting a virtual machine that has stopped responding: VMM and Guest CPU usage comparison (1017926).

You can deploy remote collectors behind a firewall. You cannot use NAT between remote collectors and analytics nodes.

Multiple Data Centers

If vRealize Operations Manager is monitoring resources in additional data centers, you must use remote collectors and deploy the remote collectors in the remote data centers. You might need to modify the intervals at which the configured adapters on the remote collector collect information depending on latency.

It is recommended that latency between sites is less than 200ms. When latency exceeds 200ms, it is recommended that you monitor collections to validate that they are completing in less than five minutes. If collections are not completed in this time limit, increase the interval to 10 minutes.


A valid certificate signed by a trusted Certificate Authority, private, or public, is an important component when you configure a production instance of vRealize Operations Manager. Configure a Certificate Authority signed certificate against the system before you configure End Point Operations Management agents.

You must include all analytics, remote collectors, and load balancer DNS names in the Subject Alternative Names field of the certificate.

You can configure End Point Operations Management agents to trust the root or intermediate certificate to avoid having to reconfigure all agents if the certificate on the analytics nodes and remote collectors are modified. For more information about root and intermediate certificates, see Specify the End Point Operations Management Agent Setup Properties.


It is recommended that you configure adapters to remote collectors in the same data center as the analytics cluster for large and extra large deployment profiles. Configuring adapters to remote collectors improves performance by reducing load on the analytics node. As an example, you might decide to configure an adapter to remote collectors if the total resources on a given analytics node begins to degrade the node's performance. You might configure the adapter to a large remote collector with the appropriate capacity.

Configure adapters to remote collectors when the number of resources the adapters are monitoring exceeds the capacity of the associated analytics node.


You can use the Platform Services Controller for user authentication in vRealize Operations Manager. For more information about deploying a highly available Platform Services Controller instance, see VMware vCenter Server 6.0 Deployment Guide.

Load Balancer

For more information about load balancer configuration, see the vRealize Operations Manager Load Balancing Guide.