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.

Prerequisites

  • Plan to use the system only as a vRealize Operations Manager node. Do not host other applications on the same machine.

  • 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.

  • If this node is to be the master node, reserve a static IP address for the virtual machine, and know the associated domain name server, default gateway, and network mask values.

    Plan to keep the IP address because it is difficult to change the address after installation.

  • If this node is to be a data node that will become the HA replica node, reserve a static IP address for the virtual machine, and know the associated domain name server, default gateway, and network mask values.

    Plan to keep the IP address because it is difficult to change the address after installation.

    In addition, familiarize yourself with HA node placement as described in About vRealize Operations Manager High Availability.

  • Preplan your domain and machine naming so that the Linux machine name will begin and end with alphabet (a–z) or digit (0–9) characters, and will only contain alphabet, digit, or hyphen (-) characters. The underscore character (_) must not appear in the host name or anywhere in the fully qualified domain name (FQDN).

    Plan to keep the name because it is difficult to change the name after installation.

    For more information, review the host name specifications from the Internet Engineering Task Force. See www.ietf.org.

  • Preplan node placement and networking to meet the requirements described in General vRealize Operations Manager Cluster Node Requirements and vRealize Operations Manager Cluster Node Networking Requirements.

  • If you expect the vRealize Operations Manager cluster to use IPv6 addresses, review the IPv6 limitations described in Using IPv6 with vRealize Operations Manager.

  • 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.

  • Uninstall any existing copies of PostgreSQL, and remove PostgreSQL directories and data.

    vRealize Operations Manager must install its own copy of PostgreSQL.

  • 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.

Procedure

  1. Log in with an account that has root privileges.
  2. Turn off the firewall.

    If using IPv4:

    # 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.

    If using IPv6:

    # su -
    # service ip6tables save
    ip6tables: Saving firewall rules to /etc/sysconfig/ip6tables: [ OK ]
    # service ip6tables stop
    ip6tables: Flushing firewall rules:                           [ OK ]
    ip6tables: Setting chains to policy ACCEPT: filter            [ OK ]
    ip6tables: Unloading modules:                                 [ OK ]
    # chkconfig ip6tables off
    # service ip6tables status
    ip6tables: Firewall is not running.
  3. Ensure that the open file limit is appropriate by configuring the required minimum.
    echo "* - nofile 64000" >> /etc/security/limits.conf
  4. Set SELinux to Permissive.
    setenforce 0
    sed -i "s/SELINUX=[^ ]*/SELINUX=permissive/g" /etc/selinux/config
  5. Ensure that node hostname is resolvable.
  6. Run the vRealize Operations Manager Enterprise bin installer, and follow the prompts.

    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
  7. If you are creating a multiple node vRealize Operations Manager cluster, repeat all the steps on each Linux machine that will serve as a node in your vRealize Operations Manager cluster.

What to do next

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.

Caution:

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