When you create the nodes of the vRealize Operations Manager cluster, you address certain requirements at deployment or installation time, before you log in to configure the role for any nodes, including the master node.

Deployment Type. Except for the remote collector, all cluster nodes must be the same kind of deployment: vApp, Linux, or Windows. Do not mix vApp, Linux, and Windows nodes in the same analytics cluster.

When you add a remote collector of a different deployment type, only the following combinations are supported:

vApp analytics cluster and Windows remote collector

Linux analytics cluster and Windows remote collector

Uniform Sizing. When you create nodes; CPU, memory, and disk sizing must be identical among nodes in the analytics cluster. Data nodes, master node, and replica node must be the same size. Remote collector nodes may be of different sizes.

You must be able to successfully reverse-DNS all nodes to their fully qualified domain name (FQDN), currently the node hostname. Nodes deployed by OVF have their hostnames set to this retrieved FQDN.

The master node and replica node must be addressed by static IP address or FQDN with a static IP address. Other nodes can use dynamic host control protocol (DHCP).

All nodes must be bidirectionally routable by IP address or FQDN.

Nodes in the analytics cluster must not be separated by network address translation (NAT), load balancer, firewall, or a proxy that inhibits bidirectional communication by IP address or FQDN.

Multiple nodes in the analytics cluster may not have the same hostname.