CAUTION

Service disruption

Prepare for migration

In order to be compatible with the NSP, an NFM-P system must use OAUTH2 user authentication.

If the NFM-P system currently uses OAUTH2 user authentication, go to Step 3.

As required, edit NFM-P user accounts to prepare for importing to the NSP local user database; for example, remove duplicate user IDs, or enter e-mail addresses.

Note: For users whose user account includes an e-mail address, the import operation sends a new randomly generated temporary password. Users who lack an e-mail address are assigned a global temporary password.

Configure NFM-P main servers

If the NFM-P system is redundant, perform Step 5 to Step 11 on the standby main server.

Perform Step 5 to Step 11 on the standalone or primary main server.

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

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 to stop the main server:

   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> 

If the NFM-P is at Release 23.11 or earlier and is using CAS user authentication, set the authentication mode to OAUTH2.

1. Enter the following:

   <main> configure nspos authMode oauth2 ↵

   The prompt changes to <main configure nspos>.

2. Enter the following:

   <main configure nspos> exit ↵

   The prompt changes to <main>.

Update the NFM-P TLS configuration.

1. Enter the following:

   <main> configure tls ↵

   The prompt changes to <main configure tls>.

2. Enter the following:

   <main configure tls> no keystore-file ↵

3. Enter the following:

   <main configure tls> no truststore-file ↵

4. Enter the following:

   <main configure tls> no keystore-pass ↵

5. Enter the following:

   <main configure tls> no truststore-pass ↵

6. Enter the following:

   <main configure tls> pki-server address ↵

   where address is one of the following in the platform—ingressApplications—ingressController section of the nsp-config.yml file on the local NSP deployer host:

   In the internalAddresses subsection, if configured, otherwise, in the clientAddresses subsection:

   • if configured, the advertised value

   • otherwise, the virtualIp value

7. Enter the following:

   <main configure tls> pki-server-port 80 ↵

8. Enter the following:

   <main configure tls> exit ↵

   The prompt changes to <main>.

9. Enter the following:

   <main> apply ↵

   The configuration is applied.

10. Enter the following:

    <main> exit ↵

    The samconfig utility closes.

If the NFM-P includes auxiliary servers, stop each Preferred and Reserved auxiliary server of the main server.

1. Log in as the root user on the auxiliary server station.

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

   # su - nsp ↵

3. Enter the following:

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

4. Enter the following to stop the auxiliary server:

   bash$ ./auxnmsserver.bash auxstop ↵

5. Enter the following:

   bash$ ./auxnmsserver.bash auxappserver_status ↵

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

   Auxiliary 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 back to the root user:

   bash$ su - ↵

If the NFM-P includes auxiliary servers, update the NFM-P TLS configuration.

1. Enter the following:

   # samconfig -m aux ↵

   The following is displayed:

   Start processing command line inputs...

   <aux>

2. Enter the following:

   <aux> configure tls ↵

   The prompt changes to <aux configure tls>.

3. Enter the following:

   <aux configure tls> no keystore-file ↵

4. Enter the following:

   <aux configure tls> no keystore-pass ↵

5. Enter the following:

   <aux configure tls> pki-server address ↵

   where address is one of the following in the platform—ingressApplications—ingressController section of the nsp-config.yml file on the local NSP deployer host:

   In the internalAddresses subsection, if configured, otherwise, in the clientAddresses subsection:

   • if configured, the advertised value

   • otherwise, the virtualIp value

6. Enter the following:

   <aux configure tls> pki-server-port 80 ↵

7. Enter the following:

   <aux configure tls> exit ↵

   The prompt changes to <aux>.

8. Enter the following:

   <aux> apply ↵

   The configuration is applied.

9. Enter the following:

   <aux> exit ↵

   The samconfig utility closes.

Apply compatibility patch

If the NFM-P system is at Release 24.4, no compatibility patch is required; go to Step 20.

Perform the following steps on each main server station to transfer the patch files for the NFM-P release from the NSP.

Note: In a redundant NFM-P system, it is recommended to perform the steps on the primary main server station first.

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

2. Open a console window.

3. Enter the following:

   # mkdir -p /opt/nsp/patches ↵

4. Enter the following:

   # scp -rp address:/opt/nsp/NSP-CN-DEP-release-ID/NSP-CN-release-ID/src/ansible/roles/

   config/files/compatibility/nfmp/NFMP_R_r/* /opt/nsp/patches/ ↵

   where

   address is the address of the NSP deployer host

   R_r is the release of the NFM-P system

If the NFM-P is at Release 22.11, go to Step 17.

If the NFM-P is at Release 23.4 or 23.8, go to Step 18.

If the NFM-P is at Release 23.11, go to Step 19.

Apply the compatibility patch to a Release 22.11 NFM-P system.

Note: In a redundant NFM-P system, you must perform the steps on each main server station.

Perform each action in Table 11-1, Compatibility actions, NFM-P Release 22.11 by executing the commands associated with the action.

To facilitate the command execution, you can copy a command block and paste the block into the console window.

Table 11-1: Compatibility actions, NFM-P Release 22.11

After applying the compatibility patch, set the sso mode to oauth2 in the nmswebserver.xml.:

Apply the compatibility patch to a Release 23.4 or 23.8 NFM-P system.

Note: In a redundant NFM-P system, you must perform the steps on each main server station.

Perform each action in Table 11-2, Compatibility actions, NFM-P Releases 23.4 and 23.8 by executing the commands associated with the action.

To facilitate the command execution, you can copy a command block and paste the block into the console window.

Table 11-2: Compatibility actions, NFM-P Releases 23.4 and 23.8

After applying the compatibility patch, set the sso mode to oauth2 in the nmswebserver.xml.:

Apply the compatibility patch to a Release 23.11 NFM-P system.

Note: In a redundant NFM-P system, you must perform the steps on each main server station.

Perform each action in Table 11-3, Compatibility actions, NFM-P Release 23.11 by executing the commands associated with the action.

To facilitate the command execution, you can copy a command block and paste the block into the console window.

Table 11-3: Compatibility actions, NFM-P Release 23.11

Start NFM-P servers

Perform the following steps on each main server to start the main server.

Note: You must perform the steps first on the standalone or primary main server.

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

   bash$ su - nsp ↵

2. Enter the following:

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

3. Enter the following to start the main server:

   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.

5. Close the console window.

Perform the following steps on each auxiliary server to start the auxiliary server.

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

   bash$ su - nsp ↵

2. Enter the following:

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

3. Enter the following to start the auxiliary server:

   bash$ ./auxnmsserver.bash auxstart ↵

4. Enter the following:

   bash$ ./auxnmsserver.bash auxappserver_status ↵

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

   Auxiliary Server process is running.  See auxnms_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.

5. Close the console window.

Import NFM-P users and groups

If you are not importing NFM-P users to the NSP local user database as described in Step 2, go to Step 26.

Sign in to the NSP as the admin user.

Perform “How do I import users and groups from NFM-P?” in the NSP System Administrator Guide.

Inform each imported NFM-P user of the new password sent to their e-mail address, or of the global temporary password assigned to the user account, if an e-mail address is not assigned.

Close the open console windows.

End of steps