CAUTION

Service Disruption

Start the PKI server, regardless of whether you are using the automated or manual TLS configuration method; perform To configure and enable a PKI server.

Note: The PKI server is required for internal system configuration purposes.

If you are using the manual TLS deployment method, generate and distribute the required TLS files for the system, as described in To generate custom TLS certificate files for the NSP.

If the NFM-P is deployed in a standalone configuration, go to Step 7.

Perform Step 7 to Step 17 on the standby main server, which is called Server B.

Perform Step 7 to Step 17 on the primary main server, which is called Server A.

Note: After you stop the primary main server in Step 1, a server activity switch occurs and Server B begins to manage the network. If required, you can revert to the previous primary and standby roles of Server A and Server B by performing the activity switch described in in Step 18.

Go to Step 19.

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

Open a console window.

Stop the main server.

1. Enter the following to switch to the nsp user:

   # su - nsp ↵

2. Enter the following:

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

3. Enter the following:

   bash$ ./nmsserver.bash stop ↵

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

5. Enter the following to switch back to the root user:

   bash$ su ↵

Enter the following:

# samconfig -m main ↵

The following is displayed:

Start processing command line inputs...

<main>

Enter the following:

<main> configure aux ↵

The prompt changes to <main configure aux>.

Configure the parameters in the following table, and then enter back ↵.

Note: At least one auxiliary server that you specify must be a Preferred auxiliary server.

Table 14-67: Main server

aux

parameters

Enter the following:

exit ↵

The prompt changes to <main>.

Verify the configuration; enter the following:

<main> show-detail ↵

The main server configuration is displayed.

If the configuration is correct, enter the following:

<main> apply ↵

The configuration is applied.

Enter the following:

<main> exit ↵

The samconfig utility closes.

Start the main server.

1. Enter the following to switch to the nsp user:

   # su - nsp ↵

2. Enter the following:

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

3. Enter the following:

   bash$ ./nmsserver.bash start ↵

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

To revert to the previous primary and standby main server roles in a redundant deployment, perform the following steps.

1. Log in to Server B as the nsp user.

2. Open a console window.

3. Enter the following to initiate a server activity switch:

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

   The server activity switch begins; Server B restarts as the standby main server, and Server A begins to manage the network as the primary main server.

4. Log in to Server A as the nsp user.

5. Open a console window.

6. Enter the following:

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

   The command returns server status information.

   If the main server is not completely started, the first line of status information is the following:

   Main Server is not ready...

   The main server is completely started when the command returns the following line of output:

   -- Primary Server is UP

7. If the command output indicates that the server is not completely started, wait five minutes and then return to Step 18 6 .

   Do not proceed to the next step until the server is completely started.

If IP validation is enabled for database access, perform the following steps on each main database station to enable validation of each auxiliary server.

Note: In a redundant NFM-P system, you must perform the steps on the primary main database station first, and then on the standby main database station.

1. Log in to the main database station as the Oracle management user.

2. Open a console window.

3. Enter the following:

   bash$ cd /opt/nsp/nfmp/oracle19/network/admin ↵

4. Create a backup copy of the sqlnet.ora file.

5. Open the sqlnet.ora file with a plain-text editor, for example, vi.

6. Locate the section that begins with the following:

   # IP Validation

7. Edit the following lines to read:

   • TCP.VALIDNODE_CHECKING = yes 

   • TCP.INVITED_NODES = (aux_server_1,aux_server_2...aux_server_n...)

   where aux_server_1,aux_server_2...aux_server_n is a comma-separated list of the auxiliary server IP addresses

8. Save and close the sqlnet.ora file.

9. Enter the following to stop the Oracle database listener:

   bash$ /opt/nsp/nfmp/oracle19/bin/lsnrctl stop ↵

10. Enter the following to start the Oracle database listener:

    bash$ /opt/nsp/nfmp/oracle19/bin/lsnrctl start ↵

Close the open console windows.

End of steps