To add an NSP auxiliary database to the NSP
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.
Note: The auxiliary database must be installed and running before you perform the procedure.
Note: After you perform the procedure:
-
The existing AA statistics values are automatically transferred from the NFM-P main database to the NSP auxiliary database.
-
The auxiliary database begins to store new data. However, no migration of current data, such as accounting or performance statistics, event timeline, or OAM results occurs, and the existing data are no longer retrievable.
-
The initial collection for some data types does not include periodic values, as the previous values are not included in the data migration.
Steps
Verify auxiliary database operation | |||
1 |
Ensure that the auxiliary database is operational. Note: After you add an auxiliary database to an NFM-P main server configuration, you cannot start the main server unless the auxiliary database is reachable by the main server.
| ||
Configure TLS on auxiliary database station | |||
2 |
Open the following file using a plain-text editor such as vi: /opt/nsp/nfmp/auxdb/install/config/install.config | ||
3 |
Changing a parameter in the auxiliary database install.config file can have serious consequences that include service disruption. Do not change any parameter in the install.config file, other than the parameters described in the step, without guidance from technical support. Edit the following lines in the file to read as shown below: secure=true pki_server=address pki_server_port=80 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: | ||
4 |
Save and close the install.config file. | ||
5 |
If the NSP deployment does not include the NFM-P, go to Step 18. | ||
Configure NFM-P main server | |||
6 |
Log in to the main server station as the nsp user. | ||
7 |
Open a console window. | ||
8 |
Stop the main server.
| ||
9 |
Enter the following: # samconfig -m main ↵ The following is displayed: Start processing command line inputs... <main> | ||
10 |
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>. | ||
11 |
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.
| ||
12 |
Enter the following: <main> apply ↵ The configuration is applied. | ||
13 |
Enter the following: <main> exit ↵ The samconfig utility closes. | ||
14 |
Enter the following to switch back to the nsp user: # exit ↵ | ||
Start main server, verify statistics migration | |||
15 |
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. | ||
16 |
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: | ||
17 |
Close the console window. | ||
Configure NSP cluster | |||
18 |
Open the following file using a plain-text editor such as vi: /opt/nsp/NSP-CN-DEP-release-ID/NSP-CN-release-ID/config/nsp-config.yml | ||
19 |
Locate the following section: auxDb: secure: "true" ipList: "" standbyIpList: "" | ||
20 |
Edit the section to read as follows: Note: For a geo-redundant auxiliary database, ensure that you record the following, which must be correctly specified in the local NFM-P main server configuration:
Note: You must preserve the leading spaces in each line. auxDb: secure: "true" ipList: "cluster_1_IP1,cluster_1_IP2...cluster_1_IPn" standbyIpList: "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 the local cluster cluster_2_IP1, cluster_2_IP2...cluster_2_IPn are the external IP addresses of the stations in the peer cluster; required only for geo-redundant deployment | ||
21 |
Save and close the nsp-config.yml file. | ||
22 |
Enter the following to start the NSP cluster: Note: If the NSP cluster VMs do not have the required SSH key, you must include the --ask-pass argument in the command, as shown in the following example, and are subsequently prompted for the root password of each cluster member: nspdeployerctl --ask-pass install --config --deploy # /opt/nsp/NSP-CN-DEP-release-ID/bin/nspdeployerctl install --config --deploy ↵ The NSP configuration is updated to include the auxiliary database. | ||
Verify backup configuration | |||
23 |
Regular auxiliary database backups are strongly recommended. Ensure that scheduled database backups are enabled to ensure minimal data loss in the event of a failure. See the NSP System Administrator Guide for information. End of steps |