This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Mapping new IP addresses

Sometimes, nodes of an existing, operational Vertica database cluster require new IP addresses.

1: Changing node IP addresses with a mapping file
2: re_ip command-line options
3: Restarting a node with new host IPs

Sometimes, nodes of an existing, operational Vertica database cluster require new IP addresses. Cluster nodes might also need to run based on different IP protocols—for example, when changing the protocol from broadcast to point-to-point.

Note

You cannot change from one address family—IPv4 or IPv6—to another. For example, if hosts in the database cluster are identified by IPv4 network addresses, you can only change host addresses to another set of IPv4 addresses.

To change the IP addresses of hosts in your database cluster, use re_ip to map old addresses to the new ones, using the specified mapping file:

$ admintools -t re_ip -f mapfile

Use re_ip in the following cases:

If the Vertica database cluster has the same data and control messaging address, you can use re_ip to remap database cluster node IP addresses:
```
$ admintools -t re_ip -f mapfile
```
Change the database cluster control messaging protocol:

From broadcast mode to point-to-point (unicast) mode:
```
$ admintools -t re_ip -d dbname -T
```
From point-to-point (unicast) mode to broadcast mode:
```
$ admintools -t re_ip -d dbname -U
```
Change the control address of the database cluster. In this case the mapping file must contain the control messaging IP address and associated broadcast address:
$ admintools -t re_ip -f mapfile
Change database addresses without changing the admintools configuration.

Note
Database-only re-IP operations are useful for error recovery. Node names and IP addresses must be the same as the node information in admintools.conf. You can query the system table NODES for node information.

re_ip and export IP address

By default, a node's IP address and its export IP address are identical. For example:

=> SELECT node_name, node_address, export_address FROM nodes;
    node_name      | node_address    | export_address
------------------------------------------------------
v_VMartDB_node0001 | 192.168.100.101 | 192.168.100.101
v_VMartDB_node0002 | 192.168.100.102 | 192.168.100.101
v_VMartDB_node0003 | 192.168.100.103 | 192.168.100.101
v_VMartDB_node0004 | 192.168.100.104 | 192.168.100.101
(4 rows)

The export address is the IP address of the node on the network. This address provides access to other DBMS systems, and enables you to import and export data across the network.

If node IP and export IP addresses are the same, then running re_ip changes both to the new address. Conversely, if you manually change the export address, subsequent re_ip operations leave your export address changes untouched.

Finding IP addresses

IP addresses for the hosts and nodes are stored in opt/vertica/config/admintools.conf:

[Cluster]
hosts = 203.0.113.111, 203.0.113.112, 203.0.113.113

[Nodes]
node0001 = 203.0.113.111/home/dbadmin,/home/dbadmin
node0002 = 203.0.113.112/home/dbadmin,/home/dbadmin
node0003 = 203.0.113.113/home/dbadmin,/home/dbadmin

You can also use admintools to display a list of IP addresses:

$ admintools -t list_allnodes
Node             | Host          | State | Version        | DB
-----------------+---------------+-------+----------------+-----------
v_vmart_node0001 | 203.0.113.111 | UP    | vertica-10.1.1 | VMart
v_vmart_node0002 | 203.0.113.112 | UP    | vertica-10.1.1 | VMart
v_vmart_node0003 | 203.0.113.113 | UP    | vertica-10.1.1 | VMart

Tip

list_allnodes can help you identify issues that you might have to access Vertica. For example, if hosts are not communicating with each other, the Version column displays Unavailable.

1 - Changing node IP addresses with a mapping file

Mapping new IP addresses includes:.

Mapping new IP addresses includes:

Creating a mapping file that maps the old IP addresses to the new IP addresses.
Using the mapping file to update configuration files and the database catalog.

If you use control messaging for communication between hosts, you might also need to update IPs with new controlAddress and controlBroadcast IP addresses.

Important

re_ip does not change export addresses and any functionality that relies on them. Before running re_ip, check whether you need to update the subnet, network interface, load balance groups, and load balancing rules to match the new IPs. Mismatches can lead to load balancing or import/export failures.

Create a mapping file

Create a mapping file as follows:

Get the new IP addresses and save them in a text file.

Get the old IP addresses with list_allnodes:

$ admintools -t list_allnodes
Node             | Host          | State | Version        | DB
-----------------+---------------+-------+----------------+-----------
v_vmart_node0001 | 192.0.2.254   | UP    | vertica-10.1.1 | VMart
v_vmart_node0002 | 192.0.2.255   | UP    | vertica-10.1.1 | VMart
v_vmart_node0003 | 192.0.2.256   | UP    | vertica-10.1.1 | VMart

Copy the contents of the Host column into the text file where you saved the new IP addresses, in this format:
```
oldIPaddress newIPaddress
```
For example:
```
192.0.2.254 198.51.100.255
192.0.2.255 198.51.100.256
192.0.2.256 198.51.100.257
```
Use the text file to create a mapping file that you can use to perform one of these tasks:

Update IP addresses

Create a mapping file that uses this format:

oldIPaddress newIPaddress[, controlAddress, controlBroadcast]

For example:

192.0.2.254 198.51.100.255, 198.51.100.255, 203.0.113.255
192.0.2.255 198.51.100.256, 198.51.100.256, 203.0.113.255
192.0.2.256 198.51.100.257, 198.51.100.257, 203.0.113.255

controlAddress and controlBroadcast are optional. If omitted:

controlAddress defaults to newIPaddress.
controlBroadcast defaults to the host of newIPaddress’s broadcast IP address.

Run re_ip as follows:
```
$ admintools -t re_ip -f mapfile
```

Update IP addresses and change control messaging mode

Create a mapping file that uses this format:

oldIPaddress newIPaddress, controlAddress, controlBroadcast

For example:

192.0.2.254 198.51.100.255, 203.0.113.255, 203.0.113.258
192.0.2.255 198.51.100.256, 203.0.113.256, 203.0.113.258
192.0.2.256 198.51.100.257, 203.0.113.257, 203.0.113.258

Run re_ip and change the control messaging mode as follows:
- Change control messaging mode to point-to-point:
```
$ admintools -t re_ip -d dbname -T
```
- Change control messaging mode to broadcast:
```
$ admintools -t re_ip -d dbname -U
```
  The embedded messages subsystem operates based on the controlAddress and controlBroadcast IPs when you use the -U option.

Change database node control addresses

Create a mapping file that uses this format:

nodeName nodeIPaddress, controlAddress, controlBroadcast

For example:

v_vmart_node0001 192.0.2.254, 203.0.113.255, 203.0.113.258
v_vmart_node0002 192.0.2.255, 203.0.113.256, 203.0.113.258
v_vmart_node0003 192.0.2.256, 203.0.113.257, 203.0.113.258

Run re_ip as follows:

$ admintools -t re_ip -f mapfile -O -d dbname

For details, see Mapping IP Addresses on the Database below.

Update IP addresses

After creating a mapping file, you can update IP addresses with re_ip. re_ip automatically backs up admintools.conf so you can recover the original settings if necessary.

Stop the database.

Run re_ip to map old IP addresses to new IP addresses:

$ admintools -t re_ip -f mapfile

re_ip issues warnings for the following mapping file errors:

IP addresses are incorrectly formatted.
Duplicate IP addresses, whether old or new.

If re_ip finds no syntax errors, it performs the following tasks:

Remaps the IP addresses as listed in the mapping file.
If the -i option is omitted, asks to confirm updates to the database.
Updates required local configuration files with the new IP addresses.
Distributes the updated configuration files to the hosts using new IP addresses.

For example:

Parsing mapfile...
New settings for Host 192.0.2.254 are:

address: 198.51.100.255

New settings for Host 192.0.2.255 are:

address: 198.51.100.256

New settings for Host 192.0.2.254 are:

address: 198.51.100.257

The following databases would be affected by this tool: Vmart

Checking DB status ...
Enter "yes" to write new settings or "no" to exit > yes
Backing up local admintools.conf ...
Writing new settings to local admintools.conf ...

Writing new settings to the catalogs of database Vmart ...
The change was applied to all nodes.
Success. Change committed on a quorum of nodes.

Initiating admintools.conf distribution ...
Success. Local admintools.conf sent to all hosts in the cluster.

Restart the database.

Mapping IP addresses on the database

You can map IP addresses for the database only. This task involves mapping the name of the nodes in the database to the new IP addresses. This is useful for error recovery because admintools.conf does not get updated. Vertica updates only spread.conf and the catalog with the changes.

You can also map IP addresses on the database only to set controlAddress and controlBroadcast on a single database. This task allows nodes on the same host to have different data and controlAddress.

Stop the database.

Create a mapping file in the following format:

nodeName nodeIPaddress, controlAddress, controlBroadcast

For example:

vertica_node001 192.0.2.254, 203.0.113.255, 203.0.113.258
vertica_node002 192.0.2.255, 203.0.113.256, 203.0.113.258
vertica_node003 192.0.2.256, 203.0.113.257, 203.0.113.258

Run the following command to map the new IP addresses:
```
$ admintools -t re_ip -f mapfile -O -d dbname
```
Restart the database.

2 - re_ip command-line options

re_ip supports the following options:.

re_ip supports the following options:

Option	Description
`-h ‑‑help`	Displays online help.
`-f mapfile ‑‑file=mapfile`	Name of the mapping text file used to map old addresses to the new ones.
`-O --dba-only`	Used for error recovery, updates and replaces data on the database cluster catalog and control messaging system. If the mapping file fails, Vertica automatically recreates it when you re-run the command. For details, see Changing node IP addresses with a mapping file. This option updates only one database at a time, so it requires the `-d` option: `$ admintools -t re_ip -f` `mapfile``-O -d``database`
`-i ‑‑noprompts`	System does not prompt to validate new settings before executing the `re_ip` operation. Prompting is on by default.
`-T ‑‑point‑to‑point`	Sets control messaging to the point-to-point (unicast) protocol. This option updates only one database at a time, so it requires the `-d` option. This option does not require a mapping text file.
`-U ‑‑broadcast`	Sets control messaging to broadcast protocol. This option updates only one database at a time, so you must use the `-d` option. This option does not require a mapping text .
`-d` `dbname` `‑‑database=``dbname`	Database name, required with the following `re_ip` options: -O -T -U

3 - Restarting a node with new host IPs

For information about remapping node IP addresses on a non-Kubernetes database, see Mapping New IP Addresses.

Kubernetes only

Note

For information about remapping node IP addresses on a non-Kubernetes database, see Mapping new IP addresses.

The node IP addresses of an Eon Mode database on Kubernetes must occasionally be updated—for example, a pod fails, or is added to the cluster or rescheduled. When this happens, you must update the Vertica catalog with the new IP addresses of affected nodes and restart the node.

Note

You cannot switch an existing database cluster from one address family to another. For example, you cannot change the IP addresses of the nodes in your database from IPv4 to IPv6.

Vertica's restart_node tool addresses these requirements with its --new-host-ips option, which lets you change the node IP addresses of an Eon Mode database running on Kubernetes, and restart the updated nodes. Unlike remapping node IP addresses on other (non-Kubernetes) databases, you can perform this task on individual nodes in a running database:

admintools -t restart_node \
  {-d db-name |--database=db-name} [-p password | --password=password] \
  {{-s nodes-list | --hosts=nodes-list} --new-host-ips=ip-address-list}

nodes-list is a comma-delimited list of nodes to restart. All nodes in the list must be down, otherwise admintools returns an error.
ip-address-list is a comma-delimited list of new IP addresses or hostnames to assign to the specified nodes.

Note
Because a hostname resolves to an IP address, Vertica recommends that you use the IP address to eliminate unneeded complexity.

The following requirements apply to nodes-list and ip-address-list:

The number of node hosts and IP addresses or hostnames must be the same.
The lists must not include any embedded spaces.

For example, you can restart node v_k8s_node0003 with a new IP address:

$ admintools -t list_allnodes
  Node           | Host       | State    | Version        | DB
 ----------------+------------+----------+----------------+-----
  v_k8s_node0001 | 172.28.1.4 | UP       | vertica-10.1.1 | K8s
  v_k8s_node0002 | 172.28.1.5 | UP       | vertica-10.1.1 | K8s
  v_k8s_node0003 | 172.28.1.6 | DOWN     | vertica-10.1.1 | K8s

$ admintools -t restart_node -s v_k8s_node0003 --new-host-ips 172.28.1.7 -d K8s
 Info: no password specified, using none
*** Updating IP addresses for nodes of database K8s ***
        Start update IP addresses for nodes
         Updating node IP addresses
         Generating new configuration information and reloading spread
*** Restarting nodes for database K8s ***
         Restarting host [172.28.1.7] with catalog [v_k8s_node0003_catalog]
         Issuing multi-node restart
         Starting nodes:
                 v_k8s_node0003 (172.28.1.7)
         Starting Vertica on all nodes. Please wait, databases with a large catalog may take a while to initialize.
         Node Status: v_k8s_node0003: (DOWN)
         Node Status: v_k8s_node0003: (DOWN)
         Node Status: v_k8s_node0003: (DOWN)
         Node Status: v_k8s_node0003: (DOWN)
         Node Status: v_k8s_node0003: (RECOVERING)
         Node Status: v_k8s_node0003: (UP)
$ admintools -t list_allnodes
  Node           | Host       | State | Version        | DB
 ----------------+------------+-------+----------------+-----
  v_k8s_node0001 | 172.28.1.4 | UP    | vertica-10.1.1 | K8s
  v_k8s_node0002 | 172.28.1.5 | UP    | vertica-10.1.1 | K8s
  v_k8s_node0003 | 172.28.1.7 | UP    | vertica-10.1.1 | K8s