How would you change Vertica to use a separate NIC/IP Address for the intra-cluster heartbeat?
search cancel

How would you change Vertica to use a separate NIC/IP Address for the intra-cluster heartbeat?

book

Article ID: 215457

calendar_today

Updated On:

Products

CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

How would you change Vertica to use a separate NIC/IP Address for the intra-cluster heartbeat?

Environment

Release: 20.2

 

Resolution

The current method to alter IP Addresses is the re_ip functionality within adminTools:

https://www.vertica.com/docs/9.1.x/HTML/index.htm#Authoring/AdministratorsGuide/ManageNodes/ReMapIPs/CreateMapFile.htm

 

What we are looking to do is to update the controlAddress entry in:

 

oldIPaddress newIPaddress, controlAddress (optional), controlBroadcast (optional)


So you would need to create a file that contains:

 

node1_current_ip node1_current_ip, node1_new_spread_ip
node2_current_ip node2_current_ip, node2_new_spread_ip
node3_current_ip node3_current_ip, node3_new_spread_ip

 

You would then run the command:

 

/opt/vertica/bin/adminTools -t re_ip -f <mapfile>

 

where <mapfile> is the file created above

 

To back out of these changes, edit the mapfile to contain the below and rerun the re_ip command:

 

node1_current_ip node1_current_ip, node1_current_ip
node2_current_ip node2_current_ip, node2_current_ip
node3_current_ip node3_current_ip, node3_current_ip