How do I change an NFM-P main database password in a standalone system?

Purpose

Perform this procedure to change the password of a user associated with the main database in a standalone NFM-P system.

CAUTION 

CAUTION

Service Disruption

The procedure requires a restart of the NFM-P main server, which is service-affecting.

It is strongly recommended that you perform this procedure only during a scheduled maintenance period.

Note: Before you perform the procedure, you must ensure that each main server, auxiliary server, and main database is running and operational.

You can use the procedure to change only one user password at a time. To change multiple user passwords, you must perform the procedure multiple times.

When you change a password on one station, the NFM-P automatically updates the password on all other NFM-P stations.

Steps
 

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


Open a console window.


Navigate to the /opt/nsp/nfmp/server/nms/bin directory.


Enter the following:

bash$ ./nmsserver.bash passwd ↵

The script prompts you for the current Oracle SYS user password.


Enter the password. The script validates the password, and then displays a list of user names like the following:

SAM Database Users:

 - sys

 - database_user (installation default is samuser)

Other Database Users:

- sqltxplain

- appqossys

- outln

- dip

- system

- exit


Enter a user name. The script prompts you for a password.


Enter the new password, which must:

  • Be between 4 and 30 characters long

  • Contain at least three of the following:

    • lower-case alphabetic character

    • upper-case alphabetic character

    • numeric character

    • special character, which is one of the following:

      # $ _

  • Not contain four or more of the same character type in sequence

  • Not be the same as the user name or the reverse user name

  • Not contain a space character

  • Differ by at least four characters from the current password

If the password is valid, the script prompts you to retype the password.


Enter the new password again. The following prompt is displayed:

WARNING: Changing passwords may cause instability to the NFM-P server as well as the Oracle proxy on the database server.

Do you want to proceed (yes/no)?:


Enter yes ↵. The script displays status messages and then exits. If the status indicates a password change failure, contact technical support.


10 

Record the password in a secure location.


11 

Perform the following steps.

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

  2. Open a console window.

  3. Enter the following to stop the Oracle proxy:

    systemctl stop nfmp-oracle-proxy.service ↵

  4. Enter the following to stop the main database:

    systemctl stop nfmp-main-db.service ↵


12 

Start the main database.

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

  2. Enter the following:

    systemctl start nfmp-main-db.service ↵

  3. Enter the following:

    systemctl start nfmp-oracle-proxy.service ↵


13 

Restart the main server.

  1. Navigate to the /opt/nsp/nfmp/server/nms/bin directory on the main server station.

  2. Enter the following to restart the main server:

    bash$ ./nmsserver.bash force_restart ↵

  3. Enter the following to display the server status:

    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.


14 

Synchronize the auxiliary database password with the NSP cluster.

  1. Log in as the root user on the NSP deployer host.

  2. Open a console window.

  3. Enter the following:

    cd /opt/nsp/NSP-CN-DEP-release-ID/NSP-CN-release-ID/tools/database ↵

  4. Enter the following:

    ./sync-auxdb-password.bash ↵

    Messages like the following are displayed:

    timestamp: Synchronizing password for Auxiliary DB Output...

    timestamp: deployment.apps/tlm-vertica-output scaled

    timestamp: secret/tlm-vertica-output patched

    timestamp: deployment.apps/tlm-vertica-output scaled

    timestamp: Synchronization completed.


15 

Close the open console windows.

End of steps