Search the VMware Knowledge Base (KB)
View by Article ID

How to change the IP address of a vRealize Operations Manager 6.1 or Up Node in a Multiple-Node Cluster (2127442)

  • 3 Ratings
Language Editions

Details

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

Solution

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 master 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.
    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

  4. For each node that you want to change, perform these steps:

    Note: Start with the master node, then replica (if present), then data nodes. Do not proceed to the next step before completing the sub steps on each node.

    1. Open the /storage/db/casa/webapp/hsqldb/casa.db.script file using a text editor.
    2. Locate any instances of the old IP address, and update them to the new IP address.
    3. Save and close the casa.db.script file.
    4. Open the /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/data/roleState.properties file using a text editor.
    5. Locate any instances of the old IP address, and update them to the new IP address.
    6. Save and close roleState.properties file.

  5. For each node that you want to change, perform these steps:

    Note: Start with the master 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.

      (Master node)

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

      (Data nodes)

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

      For clusters with high availability, run these commands.

      (Master node)

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


      (Replica node)

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

      (Data nodes)

      $VMWARE_PYTHON_BIN ./vcopsConfigureRoles.py --adminCS=master _ip


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

      The script updates the IP address in these files. Alternatively, you could edit the files using a text editor:

      /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

  6. To ensure persistence after a reboot:

    1. On the node receiving the new IP, open the /opt/vmware/etc/vami/ovfEnv.xml.bak file using a text editor.
    2. 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="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"/>

    3. Save and close the file.

  7. Use the vRealize Operations Manager administrator interface to bring the cluster online.

Additional Information

For more information on changing the IP address of a vRealize Operations Manager 6.0.x node, see Change the IP address of a vRealize Operations Manager 6.0.x node in a multiple-node cluster (2108697).

For translated versions of this article, see:

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 3 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 3 Ratings
Actions
KB: