By default, vRealize Operations Manager does not provide a solution for load-balanced UI user sessions across nodes in the cluster. You associate vRealize Operations Manager with the shared load balancer in the region.

The lack of load balancing for user sessions results in the following limitations:

Users must know the URL of each node to access the UI. As a result, a single node might be overloaded if all users access it at the same time.

Each node supports up to four simultaneous user sessions.

Taking a node offline for maintenance might cause an outage. Users cannot access the UI of the node when the node is offline.

To avoid such problems, place the analytics cluster behind an NSX load balancer that is configured to allow up to four connections per node. The load balancer must distribute the load evenly to all cluster nodes. In addition, configure the load balancer to redirect service requests from the UI on port 80 to port 443.

Load balancing for the remote collector nodes is not required.

Networking Failover and Load Balancing Design Decisions

Decision ID

Design Decision

Design Justification

Design Implication


Use an NSX Edge services gateway as a load balancer for the vRealize Operation Manager analytics cluster.

Enables balanced access of tenants and users to the analytics services with the load being spread evenly across the cluster.

You must manually configure the NSX Edge devices to provide load balancing services.


Do not use a load balancer for the remote collector nodes.

Remote collectors must directly access the systems that they are monitoring.

Remote collectors do not require access to and from the public network.