Larger environments with multiple-node vRealize Operations clusters contain one primary node and one or more data nodes for additional data collection, storage, processing, and analysis.

Prerequisites

  • Create nodes by deploying the vRealize Operations vApp.
  • Create and configure the primary node.
  • Note the fully qualified domain name (FQDN) or IP address of the primary node.

Procedure

  1. In a Web browser, navigate to the name or IP address of the node that will become the data node.
    The setup wizard appears, and you do not need to log in to vRealize Operations.
  2. Click Expand an Existing Installation.
  3. Click Next.
  4. Enter a name for the node (for example, Data-1).
  5. From the Node Type drop-down, select Data.
  6. Enter the FQDN or IP address of the master node and click Validate.
  7. Select Accept this certificate and click Next.
    If necessary, locate the certificate on the primary node and verify the thumbprint.
  8. Verify the vRealize Operations administrator username of admin.
  9. Enter the vRealize Operations administrator password.
    Alternatively, instead of a password, type a pass-phrase that you were given by your vRealize Operations administrator.
  10. Click Next, and click Finish.
    The administration interface appears, and it takes a moment for vRealize Operations to finish adding the data node.

What to do next

After creating a data node, you have the following options.

  • New, unstarted clusters:
    • Create and add more data nodes.
    • Create and add remote collector nodes.
    • Create a high availability primary replica node.
    • In a Web browser, navigate to the master node administration interface at https://master-node-name-or-ip-address/admin. Verify that all the nodes are listed under the Nodes in the vRealize Operations Manager Cluster. Then, click Start vRealize Operations Manager to start the cluster and to finish configuring the product.

      The cluster might take from 10 to 30 minutes to start, depending on the size of your cluster and nodes. Do not make changes or perform any actions on cluster nodes while the cluster is starting.

  • Established, running clusters:
    • Create and add more data nodes.
    • Create and add remote collector nodes.
    • Create a high availability primary replica node, which requires a cluster restart.