NSP auxiliary database installation pathway
Description
![]() |
CAUTION Deployment Requirement |
An NSP auxiliary database requires one or more dedicated stations.
You cannot install the auxiliary database software on a station if another NSP system component is installed on the station.
This section describes how to install and enable an NSP auxiliary database in a new or existing NSP deployment; see Pathway for NSP auxiliary database installation
Note: You must set CPU frequency scaling to “performance” in the BIOS of each auxiliary database station, or the auxiliary database installation fails. See the RHEL power management documentation for information about enabling the “performance” CPU frequency scaling governor on a station.
Setting CPU frequency scaling to “performance” effectively disables the function, so may result in greater energy consumption by a station.
Note: After the auxiliary database is installed and running:
-
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.
Pathway for NSP auxiliary database installation
Use this pathway through the documentation to access detailed procedures for installing and enabling an NSP auxiliary database. You can use the pathway and associated procedures to deploy a standalone auxiliary database cluster in one data center, or geo-redundant auxiliary database clusters in separate data centers.
Stages | |
1 |
Perform the following sequence of procedures in the standalone or primary data center.
|
2 |
If you are deploying a geo-redundant auxiliary database, perform the following sequence of actions in the standby data center.
|