Change vROPs IPs

In this article I’m going to show how you can change vRealize Operations Manager’s IP address. I followed this VMware KB during ip changes.

https://kb.vmware.com/s/article/2127442

In this scenario I’m going to change Master (172.24.0.182) and Master replica (172.24.0.183) nodes IPs. I want to change this two IP to 172.24.0.140 and 172.24.0.141. This two nodes ware deployes by vRealize Suite Lifecicle Manager. I use my environment DNS server. I’m not man of the words so let’s go and change IPs.

Preparing

When you are working in a high security environment check double FW rules. The new IP address need to reach same subnets, IPs and use same ports as your previous. If you are 100% sure that your FW rules are good follow the next steps.

  1. LogIn to vROPs Admin UI
  2. Take cluster Offline
  3. PowerOff: Remote Collectors/Data / Replica / Master nodes (ARC is not part of vROPs cluster)
  4. Create snapshot from all Nodes
  5. PowerOn: Master / Replica / Data nodes/Remote Collectors (ARC is not part of vROPs cluster)
  6. Check status on Admin UI after restart
  7. Follow the next steps below
  8. wait and check/test
  9. After 2-5 days delete snapshots

Change Nodes IP

Open Master node in console window, login by root user and copy this command:

/opt/vmware/share/vami/vami_set_network eth0 STATICV4 ipv4_addr netmask gatewayv4

ipv4_addr = your new IP (Eg.: 172.24.0.140)
netmask = your netmask eg.: 255.255.255.0
gateway = eg.: 172.24.0.1

When you changed IP, ping an other IP in the same subnet.
!!! Do not forget change new IP on DNS !!!
Repeate the steps above on Master Replica node and restart both nodes. After rebooted nodes login by root but now you are able to use Putty and stop vmware-casa service. Run this command Master and Master replica nodes.

service vmware-casa stop

Change IP address in config files

Copy casa.db.script file to tmp folder as a backup. Start with Master node then Replica node.

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

Open casa.db.script file by VI.

vi /storage/db/casa/webapp/hsqldb/casa.db.script

Little help if you are not familier in VI
push “Insert” button twice and VI is going to REPLACE mode. Navigate IP address and replace characters. Press ESC to exit REPLACE mode.
:w – save file
:q – quit editor

vRealize Suite Lifecycle Manager deploy vROPs with DNS (FQDN) name instead of IP address. If you use in your environment IP please change the old value to new and safe the file. Repeat this step Master Replica node.

Open releState.properties file and modify IPs on Master and Master replica nodes.

vi /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/data/roleState.properties

Start CaSA service Master and Master Replica nodes

service vmware-casa start

Check the status of service on Master and Master replica nodes. From this point you can login into Admin UI.

service vmware-casa status

Modify IPs in GemFire configs, type or copy the commands below:

cd /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/bin

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

This command will change IPs the following congig 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

I’m a little bit paranoid so I decided to check all config files. I want to 100% sure the IPs changed every files.

gemfire.properties
gemfire.locator.properties
gemfire.native.properties
persistence.properties

Now please log in to Admin UI and verify your all nodes State (Not running) and Status (Offline).

Change OVF config

Make a copy from ovfEnv.xml file to tmp folder.

cp /opt/vmware/etc/vami/ovfEnv.xml /tmp/

Open xml file and edit IPs. Becouse I didn’t change my DNS and use IP from same subnet as previous I need to modify only “vami.ip0” line.

vi /opt/vmware/etc/vami/ovfEnv.xml

<Property oe:key="vami.DNS.vRealize_Operations_Manager_Appliance" oe:value="<strong>172.24.0.177"/>
<Property oe:key="vami.gateway.vRealize_Operations_Manager_Appliance" oe:value="<strong>172.24.0.1"/>
<Property oe:key="vami.ip0.vRealize_Operations_Manager_Appliance" oe:value="<strong>172.24.0.XXX"/>
<Property oe:key="vami.netmask0.vRealize_Operations_Manager_Appliance" oe:value="<strong>255.255.255.0"/>

Repeate this step Master replica node.

Configure vPostgre replication

On the Master node open “pg_hba.conf” file. If a Swap file error appears, type E to Edit anyway.

vi /storage/db/vcops/vpostgres/repl/pg_hba.conf

Find the line below and replca old IP to new IP and save the file.

host replication vcopsrepl old_IP/32 md5

Check repl folder size on Master and Master replica nodes. The size of folder roughly matches. Use the du -sh command to show folder size.

du -sh / storage/db/vcops/vpostgres/repl/

Bring cluster online

Login to Admin UI and push “BRING CLUSTER ONLINE” button on Claster Status and wait.

If you use vRealize Suite Lifecycle Manager do not forget make a Inventory Sync becouse the steps above was manual process and vRLM need to discover the changes.

I hope this step by step guide help you if you have to change IP of vROPs.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.