How do I change the auxiliary database external IP addresses?
Purpose
Perform this procedure when the IP addresses that an auxiliary database uses to communicate with other NFM-P components must change, for example, when the auxiliary database moves to a different subnet, or when the protocol in use by the NFM-P components changes from IPv4 to IPv6.
Note: Changing the internal IP addresses of the auxiliary database cluster members is not supported.
Steps
Stop NFM-P main servers, auxiliary database | |||
1 |
Perform the following steps on each NFM-P main server station to stop the server. Note: In a redundant system, you must perform the steps on the standby main server first.
| ||
2 |
Perform the following steps on each auxiliary database station.
| ||
Reconfigure addresses | |||
3 |
Log in to one of the auxiliary database stations as the root user. | ||
4 |
Open the /opt/nsp/nfmp/auxdb/install/config/install.config file using a plain-text editor such as vi. | ||
5 |
Changing a parameter in the auxiliary database install.config file can have serious consequences that include service disruption. Do not change any parameter in the install.config file, other than the parameters described in the steps, without guidance from technical support. Locate the following line and change each export_IP value to the new IP address: export_hosts=internal_IP1[export_IP1],internal_IP2[export_IP2]...internal_IPn[export_IPn] | ||
6 |
Save and close the install.config file. | ||
7 |
Enter the following on the same station: # /opt/nsp/nfmp/auxdb/install/bin/auxdbAdmin.sh updateInterfaces ↵ The following prompt is displayed. Please enter auxiliary database dba password [if you are doing initial setup for auxiliary database, press enter]: | ||
8 |
Enter the password. Messages like the following are displayed. Dropping host public interfaces for 10.1.2.105 Dropped interface PUBLIC_IF_10_1_2_105 on node v_samdb_node0001. Creating public interface for host 10.1.2.105[new_external_address] Dropping host public interfaces for 10.1.2.106 Dropped interface PUBLIC_IF_10_1_2_106 on node v_samdb_node0002. Creating public interface for host 10.1.2.106[new_external_address] Dropping host public interfaces for 10.1.2.107 Dropped interface PUBLIC_IF_10_1_2_107 on node v_samdb_node0003. Creating public interface for host 10.1.2.107[new_external_address] Distributing install.config to all nodes Output captured in /opt/nsp/nfmp/auxdb/install/log/auxdbAdmin.sh.timestamp.log | ||
9 |
Perform the following steps on each auxiliary database station.
| ||
Update NFM-P main servers | |||
10 |
Perform the following steps on each main server station.
| ||
Reconfigure NSP clusters | |||
11 |
Perform Step 12 to Step 18 on the NSP cluster in each data center. | ||
12 |
Stop the NSP cluster. Note: In a standalone deployment, performing this step marks the beginning of the service outage.
| ||
13 |
Open the following file using a plain-text editor such as vi: /opt/nsp/NSP-CN-DEP-release-ID/NSP-CN-release-ID/config/nsp-config.yml | ||
14 |
Locate the following section: auxDb: ipList: "cluster_1_IP1,cluster_1_IP2...cluster_1_IPn" standbyIpList: "cluster_2_IP1,cluster_2_IP2...cluster_2_IPn" | ||
15 |
Edit the IP addresses as required. | ||
16 |
Save and close the file. | ||
17 |
Enter the following to start the NSP cluster: # /opt/nsp/NSP-CN-DEP-release-ID/bin/nspdeployerctl install --config –-deploy ↵ The NSP cluster starts, and the configuration update is put into effect. | ||
18 |
Close the console window. | ||
Start NFM-P main servers | |||
19 |
Perform the following steps on each main server station to start the main server. Note: In a redundant system, you must start the primary main server first.
| ||
20 |
Close the open console windows. End of steps |