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.

  1. Log in to the station as the nsp user.

  2. Open a console window.

  3. Enter the following:

    bash$ cd /opt/nsp/nfmp/server/nms/bin ↵

  4. Enter the following

    bash$ ./nmsserver.bash stop ↵

  5. Enter the following to display the NFM-P server status:

    bash$ ./nmsserver.bash appserver_status ↵

    The server status is displayed; the server is fully stopped if the status is the following:

    Application Server is stopped

    If the server is not fully stopped, wait five minutes and then repeat this step. Do not perform the next step until the server is fully stopped.

2 

Perform the following steps on each auxiliary database station.

  1. Log in to the station as the root user.

  2. Open a console window.

  3. Enter the following:

    # systemctl stop nspos-auxdbproxy.service ↵

    The auxiliary database proxy service stops.

  4. Open the /etc/hosts file using a plain-text editor such as vi.

  5. Change the IP address that is mapped to the station hostname to the new IP address associated with the hostname.

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 
CAUTION 

CAUTION

Service disruption

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.

  1. Log in to the station as the root user.

  2. Open a console window.

  3. Enter the following:

    # systemctl start nspos-auxdbproxy.service ↵

    The auxiliary database proxy service starts.

Update NFM-P main servers
 
10 

Perform the following steps on each main server station.

  1. Log in to the main server station as the root user.

  2. Open a console window.

  3. Enter the following:

    # samconfig -m main ↵

  4. Enter the following:

    <main> configure auxdb ip-list address1,address2...addressN exit ↵

    where address1,address2...addressN are the new IP addresses of the auxiliary database stations

  5. Enter the following:

    <main> apply ↵

    The configuration is applied.

  6. Enter the following:

    <main> exit ↵

    The samconfig utility closes.

Reconfigure NSP clusters
 
11 

Perform Step 12 to Step 20 on the NSP cluster in each data center.

12 

Log in as the root user on the NSP deployer VM.

13 

Preserve the existing NSP cluster configuration.

  1. 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

  2. Edit the following line in the platform section, kubernetes subsection to read:

      deleteOnUndeploy:false

  3. Save and close the file.

14 

Enter the following to stop the NSP cluster:

# /opt/nsp/NSP-CN-DEP-release-ID/bin/nspdeployerctl –-undeploy ↵

The cluster stops.

15 

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

16 

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"

17 

Edit the IP addresses as required.

18 

Save and close the file.

19 

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.

20 

Close the console window.

Start NFM-P main servers
 
21 

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.

  1. Return to the open console window on the main server station.

  2. Enter the following:

    bash$ ./nmsserver.bash start ↵

  3. Enter the following:

    bash$ ./nmsserver.bash appserver_status ↵

    The server status is displayed; the server is fully initialized if the status is the following:

    Application Server process is running.  See nms_status for more detail.

    If the server is not fully initialized, wait five minutes and then repeat this step. Do not perform the next step until the server is fully initialized.

22 

Close the open console windows.

End of steps