To configure and start NFM-P server

Purpose

The following steps describe how to configure and start an NFM-P server in an NSP deployment with an auxiliary database.

CAUTION 

CAUTION

Service Disruption

If the NSP deployment includes the NFM-P, a service-affecting restart of each NFM-P main server is required.

Perform this procedure only during a scheduled maintenance period.

Note: You must perform the procedure in each NSP data center.

Note: In a redundant deployment, you must perform the procedure first in the standby data center.

Steps
Configure NFM-P main server
 
1 

Log in to the main server station as the nsp user.

2 

Open a console window.

3 

Stop the main server.

  1. Enter the following:

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

  2. Enter the following:

    bash$ ./nmsserver.bash stop ↵

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

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

    bash$ su ↵

4 

Enter the following:

# samconfig -m main ↵

The following is displayed:

Start processing command line inputs...

<main>

5 
CAUTION 

CAUTION

Misconfiguration Risk

If the station IP-address order in each main server configuration is not identical, the auxiliary database addition fails.

Ensure that the auxiliary database station addresses are listed in the same order in each main server configuration.

In a geo-redundant auxiliary database deployment, the order of the IP addresses must match in each main server configuration in each data center.

Enter the following:

<main> configure auxdb enabled ip-list cluster_1_IP1,cluster_1_IP2,cluster_1_IPn;cluster_2_IP1,cluster_2_IP2,cluster_2_IPn ↵

where

cluster_1_IP1, cluster_1_IP2,cluster_1_IPn are the external IP addresses of the stations in one cluster

cluster_2_IP1, cluster_2_IP2,cluster_2_IPn are the external IP addresses of the stations in the geo-redundant cluster; required only for geo-redundant auxiliary database

The prompt changes to <main configure auxdb>.

6 
CAUTION 

CAUTION

Misconfiguration Risk

After you configure any auxdb parameter on a main server and start the main server, you cannot modify the redundancy-level parameter.

Ensure that you are certain of the redundancy-level setting before you save the configuration.

Perform one of the following.

  1. If the auxiliary database is distributed among multiple stations, enter the following:

    <main configure auxdb> redundancy-level 1 exit ↵

  2. If the auxiliary database is deployed on one station, enter the following:

    <main configure auxdb> redundancy-level 0 exit ↵

7 

Enter the following:

<main> apply ↵

The configuration is applied.

8 

Enter the following:

<main> exit ↵

The samconfig utility closes.

9 

Enter the following to switch back to the nsp user:

# exit ↵

Start main server, verify statistics migration
 
10 

Enter the following to start the main server:

bash$ /opt/nsp/nfmp/server/nms/bin/nmsserver.bash start ↵

The main server creates the required database elements and begins the migration of statistics data, if any, from the main database to the auxiliary database.

11 

In the event that a statistics migration fails on any auxiliary database station, the migration is retried up to 10 times. If after 10 retries the migration remains unsuccessful, the main server shuts down and displays the following message:

Failed to migrate Application Assurance statistics from main database to auxiliary database

If the migration fails, you must do the following:

  1. Restore the main database.

  2. Resolve the cause of the migration failure.

  3. Start the main server.

12 

Close the console window.

End of steps