How do I remove an auxiliary database station?

Purpose

Perform this procedure to remove a station from an auxiliary database.

CAUTION 

CAUTION

Service Disruption

This procedure requires a restart of each main server, which is service-affecting.

Perform this procedure only during a scheduled maintenance period.

Note: If the auxiliary database is geo-redundant, the primary and standby clusters must have the same number of stations; if you remove a station from one cluster, you must also remove a station from the other cluster.

Note: release-ID in a file path has the following format:

R.r.p-rel.version

where

R.r.p is the NSP release, in the form MAJOR.minor.patch

version is a numeric value

Steps
 
1 

If the auxiliary database is geo-redundant, you must identify which auxiliary database cluster is currently primary.

If you do not know which cluster is currently the primary cluster, perform How do I check the auxiliary database status?.

Stop auxiliary database proxies
 
2 

Perform the following steps on each auxiliary database station.

Note: If the auxiliary database is geo-redundant, you must stop the database proxy on each station in each auxiliary database cluster.

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

  2. Open a console window.

  3. Enter the following:

    # systemctl stop nspos-auxdbproxy.service ↵

  4. Verify that the proxy is stopped; enter the following:

    # systemctl status nspos-auxdbproxy ↵

Remove station from standalone or primary cluster
 
3 

Log in to the auxiliary database station as the root user.

4 

Open a console window.

5 

Enter the following:

# cd /opt/nsp/nfmp/auxdb/install/bin ↵

6 

Enter the following to block external access to the auxiliary database ports:

# ./auxdbAdmin.sh shieldsUp ↵

7 

Enter the following to stop the auxiliary database:

# ./auxdbAdmin.sh force_stop ↵

8 

Enter the following to start the auxiliary database:

# ./auxdbAdmin.sh start ↵

9 

Enter the following:

# ./auxdbAdmin.sh removeNode internal_IP ↵

where internal_IP is the IP address that the station uses to communicate with the other auxiliary database stations

You are prompted for the database user password.

10 

Enter the password.

The removal operation begins.

Note: If a cluster rebalance is required, the operation may take considerable time, depending on the volume of data in the auxiliary database.

The station is removed from the auxiliary database.

11 

If the NSP deployment does not include the NFM-P, or is geo-redundant, go to Step 13.

Reconfigure NFM-P, standalone auxiliary database
 
12 

If the NSP deployment includes the NFM-P, perform the following steps on each NFM-P main server station.

Note: In a redundant NFM-P deployment, you must perform the steps on the standby main server station 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:

    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.

  6. Enter the following to switch to the root user:

    bash$ su - ↵

  7. Enter the following:

    # samconfig -m main ↵

  8. Enter the following:

    <main> configure auxdb ip-list station_1_IP,station_2_IP,...station_n_IP exit ↵

    where

    station_1_IP,station_2_IP,...station_n_IP are the IP addresses of the remaining stations in the cluster

  9. Enter the following:

    <main> apply ↵

    The configuration is applied.

  10. Enter the following:

    <main> exit ↵

    The samconfig utility closes.

  11. Enter the following to switch back to the nsp user:

    # exit ↵

Reconfigure auxiliary database cluster
 
13 

Log in as the root user on one of the remaining auxiliary database stations in the cluster.

14 

Open the /opt/nsp/nfmp/auxdb/install/config/install.config file using a plain-text editor such as vi.

15 
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 delete the IP address of the station that is being removed:

hosts=internal_IP1,internal_IP2...internal_IPn

16 

Locate the following line and delete the IP address entries of the station that is being removed:

export_hosts=internal_IP1[export_IP1],internal_IP2[export_IP2]...internal_IPn[export_IPn]

17 

Save and close the install.config file.

18 

Enter the following:

# /opt/nsp/nfmp/auxdb/install/bin/auxdbAdmin.sh distributeConfig ↵

The updated configuration is distributed to the other auxiliary database stations in the cluster.

19 

Enter the following to allow external access to the auxiliary database ports:

# /opt/nsp/nfmp/auxdb/install/bin/auxdbAdmin.sh shieldsDown ↵

20 

Enter the following on each remaining auxiliary database station in the cluster to start the database proxy:

# systemctl start nspos-auxdbproxy.service ↵

21 

If the auxiliary database is standalone, go to Step 29.

Configure standby cluster
 
22 

Log in as the root user on the station that is to be removed from the standby auxiliary database cluster.

Note: The station that you remove from the standby cluster must be the station that occupies the same list position in the NFM-P main server configuration. For example, if the stations in the primary cluster are listed in the order 1, 2, 3, and you are removing station 2, you must remove the second station listed in the configuration of the standby cluster.

23 

Enter the following:

# /opt/nsp/nfmp/auxdb/install/bin/auxdbAdmin.sh removeNode internal_IP ↵

where internal_IP is the IP address that the station uses to communicate with the other auxiliary database stations in the cluster

You are prompted for the database user password.

24 

Enter the password.

The operation begins.

Note: If a cluster rebalance is required, the operation may take considerable time, depending on the volume of data in the auxiliary database.

The station is removed from the auxiliary database.

25 

Log in as the root user on one of the remaining auxiliary database stations in the standby cluster.

26 

Enter the following:

# cd /opt/nsp/nfmp/auxdb/install/bin ↵

27 

Perform Step 14 to Step 20.

28 

If the NSP deployment does not include the NFM-P, go to Step 30.

Reconfigure NFM-P, geo-redundant auxiliary database
 
29 

Perform the following steps on each main server in each data center.

Note: In a redundant NFM-P deployment, you must perform the steps on the standby main server first.

  1. Log in to the main server 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:

    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.

  6. Enter the following to switch to the root user:

    bash$ su - ↵

  7. Enter the following:

    # samconfig -m main ↵

  8. Enter the following:

    Note: The order of the IP addresses must be the same on each main server in the geo-redundant system.

    <main> configure auxdb ip-list IP_list exit ↵

    where

    IP_list is a list of the IP addresses in the following format:

    cluster_1_IP1,cluster_1_IP2,cluster_1_IPn;cluster_2_IP1,cluster_2_IP2,cluster_2_IPn

  9. Enter the following:

    <main> apply ↵

    The configuration is applied.

  10. Enter the following:

    <main> exit ↵

    The samconfig utility closes.

  11. Enter the following to switch back to the nsp user:

    # exit ↵

Configure NSP clusters
 
30 

Perform Step 32 to Step 38 on the NSP cluster in each data center.

31 

Go to Step 39.

32 

Log in as the root or NSP admin user on the NSP deployer host.

33 

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

34 

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"

35 

Delete the IP address of each auxiliary database station that you are removing.

36 

Save and close the file.

37 

Enter the following to start the NSP cluster:

Note: If the NSP cluster VMs do not have the required SSH key, you must include the --ask-pass argument in the nspdeployerctl command, as shown in the following example, and are subsequently prompted for the root password of each cluster member:

nspdeployerctl --ask-pass install --config –-deploy

# /opt/nsp/NSP-CN-DEP-release-ID/bin/nspdeployerctl install --config –-deploy ↵

The NSP cluster starts, and the configuration update is put into effect.

38 

Close the console window.

Start NFM-P main servers
 
39 

If the NSP deployment includes the NFM-P, start each main server.

Note: In a DR deployment, you must start the primary 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 start ↵

The main server starts.

40 

Close the open console windows.

End of steps