Change the IP Address of a vRealize Operations Manager 7.x and higher Multi Node Deployment

Products

• VMware Aria Suite

Issue/Introduction

This article provides steps to change a node IP address in a multiple-node vRealize Operations Manager cluster after installing and configuring vRealize Operations Manager.

Environment

VMware vRealize Operations Manager 6.5.x
VMware vRealize Operations Manager 7.0.x
VMware vRealize Operations 8.0.x
VMware vRealize Operations Manager 6.1.x
VMware vRealize Operations Manager 6.7.x
VMware vRealize Operations Manager 6.4.x
VMware vRealize Operations Manager 6.6.x
VMware vRealize Operations 8.1.x
VMware vRealize Operations Manager 6.2.x
VMware vRealize Operations Manager 7.5.x
VMware vRealize Operations 8.x
VMware vRealize Operations Manager 6.3.x

Resolution

To change the node IP address:

1. Use the vRealize Operations Manager administrator interface to take the cluster offline.
2. In vCenter Server, shut down all nodes in the cluster.
3. For each node that you want to change, perform these steps:
   
   Note: Start with the primary node, then replica (if present), then data nodes. Do not proceed to the next step before completing the sub steps on each node.
    
   1. In vCenter Server, select the virtual machine and Edit Settings.
   2. Navigate to vApp Options (Web client) or Options > vApp Options (C# client), and verify that the vApp options are enabled.
   3. Navigate to vApp Options > Networking Properties (Web client) or Options > vApp Options > Properties (C# client), and enter the new IP address.

Note: In the HTLM5 Web Client, vApp Options are located under [select vRealize Operation VM] > Configure > vApp Options > Properties

4. Power on the node.
5. Log in to the console on the node.
6. Use the Linux/Windows operating system to change the IP address as you normally would for RHEL and Windows. For VA installations run these commands on the node, depending on whether you are using DHCP or Static IP:
   
   Static:
   
   /opt/vmware/share/vami/vami_set_network eth0 STATICV4 ipv4_addr netmask gatewayv4
   
   Note: Replace ipv4_addr, netmask, and gatewayv4 with the correct network addresses.
   
   DHCP:
   
   /opt/vmware/share/vami/vami_set_network eth0 DHCPV4
    
7. Restart the node.
8. Stop the CaSA service by running this command:
   
   service vmware-casa stop
    
9. For each node that you want to change, perform these steps:
   
   Note: Start with the primary node, then replica (if present), then data nodes. Do not proceed to the next step before completing the sub steps on each node.
    
   1. Run the following command to backup the casa.db.script file:

cp /storage/db/casa/webapp/hsqldb/casa.db.script /tmp/

10. Open the /storage/db/casa/webapp/hsqldb/casa.db.script file using a text editor.
11. Locate any instances of the old IP address, and update them to the new IP address.
12. Save and close the casa.db.script file.
13. Open the /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/data/roleState.properties file using a text editor.
14. Locate any instances of the old IP address, and update them to the new IP address.
15. Save and close roleState.properties file.

 

4. For each node that you want to change, perform these steps:
   
   Note: Start with the primary node, then replica (if present), then data nodes. Do not proceed to the next step before completing the sub steps on each node.
    
   1. Run this command to start the CaSA service:
      
      service vmware-casa start
       
   2. Navigate to:
      
      /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/bin
       
   3. For clusters without high availability, run these commands.
      
      (primary node)
      
      $VMWARE_PYTHON_BIN ./vcopsConfigureRoles.py --adminCS=primary_ip
      
      (Data nodes)
      
      $VMWARE_PYTHON_BIN ./vcopsConfigureRoles.py --adminCS=primary_ip

(Remote Collectors, this only needs to be run if the primary and/or replica node's IPs were changed)

$VMWARE_PYTHON_BIN ./vcopsConfigureRoles.py --adminCS=primary_ip,replica_ip
 

For clusters with high availability, run these commands where primary_ip and replica_ip equal the current acting roles of each node, as seen in the Admin UI.
 

(Primary node)

$VMWARE_PYTHON_BIN ./vcopsConfigureRoles.py --adminCS=primary_ip,replica_ip

(Replica node)

$VMWARE_PYTHON_BIN ./vcopsConfigureRoles.py --adminCS=primary_ip,replica_ip

(Data nodes)

$VMWARE_PYTHON_BIN ./vcopsConfigureRoles.py --adminCS=primary_ip,replica_ip
 

(Remote Collectors, this only needs to be run if the primary and/or replica node's IPs were changed)

$VMWARE_PYTHON_BIN ./vcopsConfigureRoles.py --adminCS=primary_ip,replica_ip
 

Note: Replace primary_ip, replica_ip with the new address of the primary node, replica node and data node respectively.

The script updates the IP address in the below files. Alternatively, you could edit the files using a text editor, after a backup is created using this command:
cp /usr/lib/vmware-vcops/user/conf/gemfire.properties /tmp/; cp /usr/lib/vmware-vcops/user/conf/gemfire.locator.properties /tmp/; cp /usr/lib/vmware-vcops/user/conf/gemfire.native.properties /tmp/; cp /usr/lib/vmware-vcops/user/conf/persistence/persistence.properties /tmp/

 

• /usr/lib/vmware-vcops/user/conf/gemfire.properties
• /usr/lib/vmware-vcops/user/conf/gemfire.locator.properties
• /usr/lib/vmware-vcops/user/conf/gemfire.native.properties
• /usr/lib/vmware-vcops/user/conf/persistence/persistence.properties

4. To ensure persistence after a reboot:
    
   1. Copy /opt/vmware/etc/vami/ovfEnv.xml to /opt/vmware/etc/vami/ovfEnv.xml.bak.
   2. On the node receiving the new IP, open the /opt/vmware/etc/vami/ovfEnv.xml file using a text editor.
   3. Edit the vami.DNS, vami.gateway, vami.ip0, and vami.netmask0 lines to reflect the new IP addresses.
      
      For example:
      
      <Property oe:key="vami.DNS.vRealize_Operations_Manager_Appliance" oe:value="<strong>192.168.1.2"/>
      <Property oe:key="vami.gateway.vRealize_Operations_Manager_Appliance" oe:value="<strong>192.168.0.1"/>
      <Property oe:key="vami.ip0.vRealize_Operations_Manager_Appliance" oe:value="<strong>192.168.3.77"/>
      <Property oe:key="vami.netmask0.vRealize_Operations_Manager_Appliance" oe:value="<strong>255.255.240.0"/>
       
   4. Save and close the file.
   5. Stop the CaSA service by running this command:
      
      service vmware-casa stop
       
   6. Copy /usr/lib/vmware-vcops/user/conf/cis.properties to /usr/lib/vmware-vcops/user/conf/cis.properties.bak.
   7. On the node receiving the new IP, open the /usr/lib/vmware-vcops/user/conf/cis.properties file using a text editor.
   8. Ensure hosts= and MY_LDUID= show the correct cluster name as the other nodes.
      
      Example: If your cluster name is ops.vcloud.local, then the entries should look like the following:
      hosts=opsvcloudlocal,localhost:6061
      MY_LDUID=opsvcloudlocal
5. Open /etc/apache2/listen.conf in a text editor.
6. Find the line Listen old_IP:443.
   
   Note: old_IP will be the old IP address assigned to the node.
    
7. Replace old_IP with the new IP address assigned to the node.
   
   Example: Listen 192.168.1.10:443
    
8. Save and close the file.
9. Start the CaSA service by running this command:
   
   service vmware-casa start
    
10. Save and close the file.

 

If the Primary Replica Node IP Address is Changed

1. On the Primary node, open /storage/db/vcops/vpostgres/repl/pg_hba.conf with a text editor.

Note: If a Swap file error appears, type E to Edit anyway.

2. Find the host replication vcopsrepl old_IP/32 md5 line and change old_IP to the new IP address.

Example: host replication vcopsrepl 192.168.2.20/32 md5

3. Save and close the file.
4. Restart the cluster from the vRealize Operations admin UI.

Verify that the /storage/db/vcops/vpostgres/repl/ directory on the Primary Replica node roughly matches the size of the same directory on the Primary node.  This would indicate that the sync is successful.

Additional Information

When adding a new node to the cluster, the LDUID on the newly added node should match the LDUID set in /usr/lib/vmware-vcops/user/conf/cis.properties on the other nodes.