If your disaster recovery plan requires, change the IP address for the vRealize Operations Manager multinode clustered configuration to update the new IP addresses on all the nodes, with or without high availability enabled.

Procedure

  1. Open a console on the virtual machine or start an SSH session on the virtual machine if SSH is enabled.
  2. Take slice offline on all the nodes. From /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/bin, run the $VMWARE_PYTHON_BIN ./vcopsConfigureRoles.py --action bringSliceOffline --offlineReason <Put Comment Here> command .
  3. Shut down the virtual machines on which the IP addresses must change and change the required IP addresses, gracefully.
  4. Power on the virtual machines. If the nodes were not offline, the reboot might take 15 minutes. If it takes more than 15 minutes, take the slice offline on all the nodes.
  5. If the virtual machines are not powered on in 15 minutes, take the slice offline on all the nodes. From /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/bin, run $VMWARE_PYTHON_BIN ./vcopsConfigureRoles.py --action bringSliceOffline --offlineReason <Put Comment Here>.
  6. Verify that all nodes are offline. On all the nodes, starting with the master node, run the service vmware-casa stop command to stop the CaSA service.
  7. Edit the /storage/db/casa/webapp/hsqldb/casa.db.script file to update the old IP address with the new IP address for every node for all the instances.
  8. Update the $VCOPS_BASE/user/conf/cassandra/cassandra.yaml file with the new IP addresses for the listen_address and broadcast_rpc_address values. Change the seeds value to the new master node IP address and add the replica node IP address if high availability is enabled.
  9. On all the nodes starting with the master node, run the service vmware-casa start command to start the CaSA service.
  10. Update the IP addresses of the master node and replica node. From /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/bin, run the $VMWARE_PYTHON_BIN ./vcopsConfigureRoles.py --adminCS <Master IP Here>, <replica IP here> command.

    This command updates the IP address in the following files. You can also change the IP addresses in these files manually.

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

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

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

  11. Verify that the bind-address property in these files points to the new IP address. You can edit the files manually, if required.
    • /usr/lib/vmware-vcops/user/conf/gemfire.locator.properties

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

  12. On all the nodes starting with the master node, bring the slice online. From /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/bin, run the $VMWARE_PYTHON_BIN ./vcopsConfigureRoles.py --action bringSliceOnline command.

    Do not wait for the script to finish before bringing online the next node. All nodes must be brought online in parallel, because components must rediscover their remote partners during startup.

  13. Verify that all the nodes are online. Log in to the administration UI of the master node and verify that all nodes in the cluster are up and collecting data.
  14. Enable high availability from the Admin UI, if required.