How do I update the NFM-P license in a redundant deployment?
Note: The license files that you import to the primary and standby main servers must contain identical license quantity and option values.
Note: To reduce the risk of importing mismatched licenses, it is recommended that you obtain one license file that contains the system ID of each main server, and then import the same file on each main server.
Note: The primary and standby main server licenses must be synchronized to ensure correct NFM-P operation in the event of a server activity switch. The main servers compare license values after a system reconfiguration. If a difference is detected, the NFM-P raises an alarm that you can clear when the licenses are synchronized.
Steps
Update license on primary main server | |
1 |
Open a client GUI to monitor the NFM-P during the license update. |
2 |
Log in to the primary main server station as the nsp user. |
3 |
Open a console window. |
4 |
Navigate to the /opt/nsp/nfmp/server/nms/bin directory. |
5 |
Enter the following: bash$ ./nmsserver.bash import_license license_file ↵ where license_file is the absolute file path of the NFM-P license zip file The following prompt is displayed: Detected an NFM-P license key. Do you want to proceed? (YES/no): |
6 |
Enter the following: YES ↵ The primary main server reads the license file, copies the license file to a backup location, and displays the following status information: Importing NFM-P license key... Original license key file has been backed up to /opt/nsp/nfmp/server/timestamp/SAMLicense.zip Done. where timestamp is a directory name in the following format: yyyy.mm.dd-hh.mm.ss Note: Importing the new license on the primary main server creates a license mismatch with the standby main server. As a result, the NFM-P raises an alarm that you can clear when the license import on each main server is complete. |
7 |
Close the console window. |
Update license on standby main server | |
8 |
Log in to the standby main server station as the nsp user. |
9 |
Open a console window. |
10 |
Navigate to the /opt/nsp/nfmp/server/nms/bin directory. |
11 |
Enter the following: bash$ ./nmsserver.bash import_license license_file ↵ where license_file is the absolute file path of the NFM-P license zip file The following prompt is displayed: Detected an NFM-P license key. Do you want to proceed? (YES/no): |
12 |
Enter the following: YES ↵ The standby main server reads the license file, copies the license file to a backup location, and displays the following status information: Importing NFM-P license key... Original license key file has been backed up to /opt/nsp/nfmp/server/timestamp/SAMLicense.zip Done. where timestamp is a directory name in the following format: yyyy.mm.dd-hh.mm.ss |
13 |
Enter the following to restart the standby main server: bash$ ./nmsserver.bash force_restart ↵ The main server restarts. |
14 |
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. |
15 |
Close the console window. |
Restart auxiliary servers | |
16 |
In order to apply the license values to an NFM-P auxiliary server, you must restart the auxiliary server. If the NFM-P deployment includes one or more auxiliary servers, restart each auxiliary server.
|
Verify new license information | |
17 |
Perform How do I view the NFM-P license information? to verify the imported license information. |
18 |
If a license parameter is incorrect, contact technical support. |
19 |
After you verify that the license information is correct, clear the license mismatch alarm. |
20 |
Close the GUI client, if it is no longer required. End of steps |