vRealize Operations Manager consists of one or more nodes, in a cluster. To create nodes, you download and run the vRealize Operations Manager Enterprise installer for Linux.

Verify that vRealize Operations Manager ports are open at the firewall. See How vRealize Operations Manager Uses Network Ports.

Verify that prerequisite packages are installed. See Required Linux Packages for vRealize Operations Manager.

Verify that the Linux machine does not contain an underscore character (_) in its host name or anywhere in the fully qualified domain name (FQDN).

Configure the Linux machine IP address.

The master node and replica node require a static IP address or FQDN. A data node or remote collector node may use DHCP, static IP, or FQDN.

When you use virtual machines and this node will be a high availability (HA) replica node, deploy the node on different hardware from the master node.

Be aware that vRealize Operations Manager uninstalls httpd if it is installed, because vRealize Operations Manager installs its version of Apache.

If vRealize Operations Manager uninstalls httpd, it backs up the /etc/httpd configuration directory.

Verify that all machines in the file ntp.conf are resolvable. If you are unsure about the contents of ntp.conf, make a backup copy of the file, and overwrite the original with the default version from a new machine installation.

Locate your copy of the vRealize Operations Manager Enterprise bin installer for Linux.


Log in with an account that has root privileges.


Turn off the firewall.

# su -
# service iptables save
iptables: Saving firewall rules to /etc/sysconfig/iptables:[  OK  ]
# service iptables stop
iptables: Flushing firewall rules:                         [  OK  ]
iptables: Setting chains to policy ACCEPT: filter          [  OK  ]
iptables: Unloading modules:                               [  OK  ]
# chkconfig iptables off
# service iptables status
iptables: Firewall is not running.

Ensure that the open file limit is appropriate by configuring the required minimum.

echo "* - nofile 64000" >> /etc/security/limits.conf

Set SELinux to Permissive.

setenforce 0
sed -i "s/SELINUX=[^ ]*/SELINUX=permissive/g" /etc/selinux/config

Ensure that node hostname is resolvable.


Run the vRealize Operations Manager Enterprise bin installer.

Add -i console, -i silent, or -i gui to set the installation mode. The default mode conforms to your session type, for example, console for terminal connections or gui for X-Windows.

cd /tmp
sh ./vRealize_Operations_Manager_Enterprise.bin -i gui

If you are creating a multiple node vRealize Operations Manager cluster, repeat Step 1 through Step 6 on each Linux machine that will serve as a node in your vRealize Operations Manager cluster.

Use a Web browser client to configure a newly added node as the vRealize Operations Manager master node, a data node, a high-availability master replica node, or a remote collector node. The master node is required first.


For security, do not access vRealize Operations Manager from untrusted or unpatched clients, or from clients using browser extensions.