Update Data Repository Database cluster nodes after IP Address or Host Name changes

book

Article ID: 191796

calendar_today

Updated On:

Products

CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

How can we update the Data Repository after the server it is installed on has a new IP address assigned.

How do we change the IP address for the Data Repository if the server is moved to a new subnet?

How can we update the Data Repository after the server it is installed on has a new Host Name assigned?

The Data Repository cluster nodes have had their Host Names changed. What changes are needed?

What changes are needed when the Data Repository cluster nodes have their Host Name changed?

Cause

The server the Data Repository is installed on has had it's IP Address or Host Name changed.

Environment

All supported Performance Management releases

Resolution

The following steps apply ONLY to Vertica versions used in the r3.6 or newer releases of Performance Management.

See below in the Additional Information section for details related to Vertica versions used with r3.5 or older Performance Management releases.

These instructions are an overview of a basic IP Address change scenario when using a standard 3 node database cluster.

NOTE: If the Host Name has changed but not the IP Address, the same instructions below apply. Just substitute the Host Name anywhere it references the IP Address and change where needed.

The following Vertica documentation provides addition options for making the IP Address changes.

  • https://www.vertica.com/docs/9.0.x/HTML/index.htm#Authoring/AdministratorsGuide/ManageNodes/ReMapIPs/ReMapIPOverview.htm


A sample of a basic version of the command used to change the IP Address is:

  • ./admintools -t re_ip -f <mapfile>


Notes on running the command:

  1. The <mapfile> is a file that has to be created.
    • It does not exist until it is manually created.
    • It must be populated with the correct values.
    • It must be in the correct format.
    • It should contain a mapping of old<->new IP Addresses.
  2. The admintools command is found by default in the /opt/vertica/bin directory.
  3. The admintools command should be run as the dradmin or equivalent Database admin user.
  4. The admintools command can be run from any node in the cluster
  5. The admintools command should be run when all nodes in the cluster are DOWN.
If we were to, for example, create a mapping file named mapping.out in /tmp and cat it to review the contents, it might look like the following sample using example IPs.

[[email protected]_Node tmp]$ more /tmp/mapping.out
192.0.2.254 198.51.100.255
192.0.2.255 198.51.100.256
192.0.2.256 198.51.100.257


When making these changes for all Performance Management releases:

  • Review the Data Aggregator file /opt/IMDataAggregator/apache-karaf-<version>/etc/dbconnection.cfg.
  • If the dbHostNames variable value is set with IP Addresses for the Data Repository cluster nodes, update them to use the new IP Addresses.
  • If it uses host names, if they've remained the same no change is needed.
  • If in use for host resolution, ensure the Data Aggregator /etc/hosts file is updated with the new IP Addresses of the Data Repository cluster nodes.

Additional Information


IP Change Instructions for older r3.5 and earlier Performance Management releases.

  1. Vertica versions used in r3.5 and earlier Performance Management releases used a different IP Address change process than is seen in the Vertica versions present in r3.6 and later Performance Management releases.
  2. If running an r3.5 or older Performance Management release use the re-ip script documented in the following Knowledge Base article.