re_ip command
Updates database cluster node IP addresses and reconfigures spread messaging between nodes.
Syntax
admintools -t re_ip { -h
   | -f mapfile [-O -d dbname]
   | -d dbname { -T | U }
} [-i]
Options
| Option | Description | 
|---|---|
| -h | --help | Displays online help. | 
| -f mapfile | --file=mapfile | Name of the mapping text file used to map old addresses to 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 Change Node Control and Broadcast Addresses. This option updates only one database at a time, so it requires the  | 
| -T | --point-to-point | Sets control messaging to the point-to-point (unicast) protocol. Vertica can change the messaging protocol on only one database at a time, so you must specify the target database with the  Use point-to-point if nodes are not located on the same subnet. Point-to-point supports up to 80 spread daemons. You can exceed the 80-node limit by using large cluster mode, which does not install a spread daemon on each node. | 
| -U | --broadcast | Sets control messaging to the broadcast protocol, the default setting. Vertica can change the messaging protocol on only one database at a time, so you must specify the target database with the  Broadcast supports up to 80 spread daemons. You can exceed the 80-node limit by using large cluster mode, which does not install a spread daemon on each node. | 
| -d dbname | --database=dbname | Database name, required with the following  
 | 
| -i | --noprompts | System does not prompt to validate new settings before executing the re_ipoperation. Prompting is on by default. |