To avoid availability disruptions in the vRealize Operations Manager analytics cluster during a disaster in the region, you reconfigure the domain name and domain search path on all vRealize Operations Manager analytics cluster nodes to add the root domain of Region B.

Table 1. vRealize Operations Manager Analytics Cluster Nodes

Role

Virtual Machine

Domain Name

Search Path

Primary node

xreg-vrops01a

rainpole.io

rainpole.io sfo.rainpole.io lax.rainpole.io

Replica node

xreg-vrops01b

Data node

xreg-vrops01c

Prerequisites

Take a snapshot of each analytics cluster node.

Procedure

  1. Log in to the vRealize Operations Manager primary node by using a Secure Shell (SSH) client.
    Setting Value
    FQDN xreg-vrops01a.rainpole.io
    User name root
    Password vrops_root_password
  2. Open the VAMI network configuration utility by running the command. 
    /opt/vmware/share/vami/vami_config_net
  3. To start the DNS reconfiguration, enter 4 and press Enter.
  4. At the DNS server 1 prompt, press Enter.
  5. At the DNS server 2 (optional) prompt, enter 172.17.11.4 and press Enter.
  6. At the Domain name (optional) prompt, press Enter.
  7. At the Search path (space separated) (optional) prompt, enter lax.rainpole.io and press Enter.
  8. To exit the VAMI network configuration utility, enter 1 and press Enter.
  9. Verify the updated DNS configuration.
    1. View the content of the /etc/resolv.conf file by running the command. 
      cat /etc/resolv.conf
    2. Verify the value of the search parameter. 
      nameserver 172.16.11.4
nameserver 172.17.11.4
search rainpole.io sfo.rainpole.io lax.rainpole.io
  10. Repeat this procedure for each of the remaining vRealize Operations Manager analytics cluster nodes.

What to do next

After you updated the domain search path on all vRealize Operations Manager analytics cluster nodes, delete the snapshots to avoid performance degradation.