Change the IP Address of a VMware Aria Operations 8.14 or later Deployment
search cancel

Change the IP Address of a VMware Aria Operations 8.14 or later Deployment

book

Article ID: 336690

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

This article provides steps to change a node's IP address in a VMware Aria Operations 8.14 and later cluster after installing and configuring VMware Aria Operations.

Environment

VMware Aria Operations 8.14.x

Resolution

Quick Links:
Change IP Address
PostgreSQL Configuration for HA/CA
Verify

Change IP Address

  1. Log into the VMware Aria Operations Admin UI as the local admin user.
  2. Click Take Offline under Cluster Status.
Note: Wait for Cluster Status to show as Offline.
  1. Log into the vSphere UI as an administrator.
  2. Perform a Guest Shutdown on all VMware Aria Operations nodes in the cluster.
  3. Forward and reverse DNS resolution is a requirement for each node in the Aria Operations cluster.
    Please update your DNS records to the new IP address on your DNS server.
  4. For each node that you want to change, perform these steps:
Note: Start with the Primary node, then Primary Replica (if present), and then data nodes. Do not proceed to the next step before completing the sub steps on each node.
  1. In vSphere UI, select the virtual machine and navigate to Configure > vApp Options > Properties.
Note: If vApp Properties are missing, please refer to Restoring vApp properties in VMware Aria Operations 8.14 and Later (93138).
  1. For each Key below, select the Key, then click Set Value.  Enter the below values and click OK.
Note: If your existing network properties contain the vami. prefex, include that in the value.  Otherwise, remove the vami. prefex.

With vami. prefex
  • IP address: vami.ip0.vRealize_Operations_Manager_Appliance
  • Subnet Mask: vami.netmask0.vRealize_Operations_Manager_Appliance
  • Gateway: vami.gateway.vRealize_Operations_Manager_Appliance
  • DNS: vami.DNS.vRealize_Operations_Manager_Appliance
Without vami. prefex
  • IP address type: ipv4_type.VMware_Aria_Operations
  • IP address: ipv4_address.VMware_Aria_Operations
  • Subnet Mask: ipv4_netmask.VMware_Aria_Operations
  • Gateway: ipv4_gateway.VMware_Aria_Operations
  • DNS: DNS.VMware_Aria_Operations
  1. Power on the node.
  2. Log into the Console as root by pressing ALT+F1 to log in.
  3. Run the following command to stop the CaSA service:
service vmware-casa stop
  1. For each node that you want to change, perform these steps:
Note: Start with the Primary node, then Primary 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 commands on all nodes to backup the important files:
  • cp /storage/db/casa/webapp/hsqldb/casa.db.script /tmp/
  • cp /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/data/roleState.properties /tmp/
  • 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/
  • cp /opt/vmware/etc/vami/ovfEnv.xml /tmp
  • cp /usr/lib/vmware-vcops/user/conf/cis.properties /tmp
  1. Run the following command to open the /storage/db/casa/webapp/hsqldb/casa.db.script file in a text editor:
vi /storage/db/casa/webapp/hsqldb/casa.db.script
  1. Press i to enter insert mode, then locate any instances of the old IP address (or FQDN’s) and update them to the new IP address (or FQDN’s).
  2. Press Esc, then type :wq to save and close the casa.db.script file.
  3. Run the following command to open the /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/data/roleState.properties file in a text editor:
vi /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/data/roleState.properties
  1. Press i to enter insert mode, then locate any instances of the old IP address, and update them to the new IP address.
Example:
adminroleconnectionstring = 192.168.1.10,192.168.1.11
internaladminroleconnectionstring = 192.168.1.10,192.168.1.11
  1. Press Esc, then type :wq to save and close roleState.properties file.
  2. Run the following command to open the /usr/lib/vmware-vcops/user/conf/persistence/persistence.properties file in a text editor:
vi /usr/lib/vmware-vcops/user/conf/persistence/persistence.properties
  1. Press i to enter insert mode, then locate the line with the old Primary node's IP address and update it to the new Primary node's IP address.
  2. Locate the line with the old Primary Replica (if present) node's IP address and update it to the new Primary Replica node's IP address.
  3. Press Esc, then type :wq to save and close the persistence.properties file.
  4. Run the following command to start the CaSA service:
service vmware-casa start
  1. Run the following command to navigate to the /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/bin folder:
cd /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/bin
  1. The following command needs to be run in a particular order.  Choose the command applicable to your cluster and follow each sub-step carefully.
Command for single node or non-HA multi node cluster:
$VMWARE_PYTHON_BIN ./vcopsConfigureRoles.py --adminCS=primary_ip > /dev/null 2>&1

Command for HA multi node or CA multi node cluster:
$VMWARE_PYTHON_BIN ./vcopsConfigureRoles.py --adminCS=primary_ip,replica_ip > /dev/null 2>&1

Note: Replace primary_ip and replica_ip in the above commands with the IP address of your VMware Aria Operations primary node's IP, and replica node's IP
  1. First, run the command on the Primary node in the cluster, and wait for the task to complete.
  2. Next, run the command on the Primary Replica node (if present) in the cluster, and wait for the task to complete.
  3. Next, run the command on all Data nodes (if present) and the Witness node (if present), and wait for the task to complete.
Note: This script updates the IP addresses in the below files:
  • /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
After the script has been run, verify that the IP addresses have been successfully updated in the above mentioned files.
  1. Log into the VMware Aria Operations Admin UI as the local admin user.
  2. Click Bring Online under Cluster Status.
Note: Wait for Cluster Status to show as Online.

 

PostgreSQL Configuration for HA/CA

The following steps are only applicable if the IP address of the Primary Replica (if present) node has been changed.

  1. On the Primary node, run the following command to open /storage/db/vcops/vpostgres/repl/pg_hba.conf in a text editor:
vi /storage/db/vcops/vpostgres/repl/pg_hba.conf

Note: If a Swap file error appears, type E to Edit anyway.
  1. Press i to enter insert mode, then find the host replication vcopsrepl replica_old_IP/32 md5 line and change replica_old_IP to the new IP address of the Primary Replica node.
Example: host replication vcopsrepl 192.168.1.11/32 md5
  1. Press Esc, then type :wq to save and close the /storage/db/vcops/vpostgres/repl/pg_hba.conf file.
  2. Verify that the /storage/db/vcops/vpostgres/repl/recovery.conf file exists on the Primary Replica node and it is not empty.
  3. Run the following commands to restart the vpostgres and vpostgres-repl services:
service vpostgres reload
service vpostgres-repl reload



 

Verify

To verify the configuration changes, complete the following.

  1. Check the /opt/vmware/etc/vami/ovfEnv.xml file for vami.DNS, vami.gateway, vami.ip0, and vami.netmask0 lines to reflect the new IP addresses.
Example (with vami prefix):
<Property oe:key="vami.DNS.vRealize_Operations_Manager_Appliance" oe:value="192.168.1.2"/>
<Property oe:key="vami.gateway.vRealize_Operations_Manager_Appliance" oe:value="192.168.0.1"/>
<Property oe:key="vami.ip0.vRealize_Operations_Manager_Appliance" oe:value="192.168.3.77"/>
<Property oe:key="vami.netmask0.vRealize_Operations_Manager_Appliance" oe:value="255.255.240.0"/>

Example (without vami prefix):
<Property oe:key="DNS.VMware_Aria_Operations " oe:value="192.168.1.2"/>
<Property oe:key="ipv4_type.VMware_Aria_Operations" oe:value="Static"/>
<Property oe:key="ipv4_gateway.VMware_Aria_Operations" oe:value="192.168.0.1"/>
<Property oe:key="ipv4_address.VMware_Aria_Operations" oe:value="192.168.3.77"/>
<Property oe:key="ipv4_netmask.VMware_Aria_Operations" oe:value="255.255.240.0"/>
  1. In the same file, 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
  1. Cat the /storage/db/casa/webapp/hsqldb/casa.db.script file to ensure that FQDN’s (or IP addresses) are changed to the new values in all nodes.
Example: 
...INSERT INTO CASA_DOCS VALUES..."slices":{"<UUID_1>":{"slice_uuid":"<UUID_1>","pair_uuid":null,"is_admin_node":true,"ip_address":"host031. hostname.local","preferred_addresses":{},"slice_name":"master","membership_state":null,"region":null},"<uuid>":{"slice_uuid":"########-####-####-####-############","pair_uuid":null,"is_admin_node":false,"ip_address":"host033. hostname.local","preferred_addresses":{},"slice_name":"Data","membership_state":null,"region":null},"<uuid>":{"slice_uuid":"<uuid>","pair_uuid":null,"is_admin_node":false,"ip_address":"host032. hostname.local","preferred_addresses":{},"slice_name":"Replica","membership_state":null,"region":null},"<uuid>":{"slice_uuid":"<uuid>","pair_uuid":null,"is_admin_node":false,"ip_address":"host034. hostname.local","preferred_addresses":{},"slice_name":"RC","membership_state":null,"region":null}}}')
  1. In other configuration files, verify that all instances of the old IP addresses have been changed to the new values in all nodes.  Run the following command on all nodes where node_old_IP will be the old IP address assigned to the node, primary_old_IP will be the old IP address assigned to the Primary node, and replica_old_IP will be the old IP address assigned to the Primary Replica node (if present).  If  the command output is not empty, fix the address mentioned in the output file according to above instructions in Change IP Address.
grep -E 'node_old_IP|primary_old_IP|replica_old_IP' /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/data/roleState.properties /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 /etc/httpd/listen.conf
  1. Verify the PostgreSQL configuration, only if a Primary Replica Node exists.
    1. Find the host replication vcopsrepl IP/32 md5 line in /storage/db/vcops/vpostgres/repl/pg_hba.conf in the Primary node and verify that IP address is changed.
    2. Find the line that contains primary_conninfo in /storage/db/vcops/vpostgres/repl/pg_hba.conf in the Primary Replica node and verify that the IP address mentioned in the line is changed to the Primary node's new IP address.

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.

If any of your VMware Aria Operations nodes are missing the required vApp properties, see the following Knowledge Articles to restore them:



Powered by Wolken Software