To install an NFM-P auxiliary server
Purpose
The following steps describe how to install the NFM-P auxiliary server software on a station. Ensure that you record the information that you specify, for example, directory names, passwords, and IP addresses.
Note: An auxiliary server is dedicated to only SNMP statistics collection.
Note: You require root user privileges on the auxiliary server station.
Note: Performing the procedure creates the nsp user account on the auxiliary server station.
Note: The following RHEL CLI prompts in command lines denote the active user, and are not to be included in typed commands:
Steps
1 |
Start the PKI server, regardless of whether you are using the automated or manual TLS configuration method; perform To configure and enable a PKI server. Note: The PKI server is required for internal system configuration purposes. | ||||||||||||
2 |
Log in as the root user on the auxiliary server station. | ||||||||||||
3 |
Download the following installation files to an empty local directory: where R.r.p is the NSP release identifier, in the form MAJOR.minor.patch v is a version identifier Note: In subsequent steps, the directory is called the NFM-P software directory. | ||||||||||||
4 |
Navigate to the NFM-P software directory. Note: Ensure that the directory contains only the installation files. | ||||||||||||
5 |
Enter the following: # chmod +x * ↵ | ||||||||||||
6 |
Enter the following: # dnf install *.rpm ↵ The dnf utility resolves any package dependencies, and displays the following prompt: Total size: nn G Installed size: nn G Is this ok [y/d/N]: | ||||||||||||
7 |
Enter y. The following and the installation status are displayed as each package is installed: Downloading Packages: Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction check The package installation is complete when the following is displayed: Complete! | ||||||||||||
8 |
The initial NFM-P server installation on a station creates the nsp user account and assigns a randomly generated password. If this is the first installation of an NFM-P main or auxiliary server on the station, change the nsp password.
| ||||||||||||
9 |
Enter the following: # samconfig -m aux ↵ The following is displayed: Start processing command line inputs... <aux> | ||||||||||||
10 |
Enter the following: <aux> configure ↵ The prompt changes to <aux configure>. | ||||||||||||
11 |
Enter the following: <aux configure> show-detail ↵ The auxiliary server configuration is displayed. | ||||||||||||
12 |
If the default ip value is not the correct IP address of the auxiliary server, configure the ip parameter. | ||||||||||||
13 |
Configure the fips parameter to specify whether FIPS security is enabled for network management. See Enabling FIPS security for NFM-P network management for information about using FIPS security. | ||||||||||||
14 |
Configure the main-server parameters in the following table, and then enter back ↵. Table 14-64: Auxiliary server parameters —
|
Parameter |
Description |
---|---|
domain |
The NFM-P system identifier Default: NFM-P |
ip-one |
The primary main server IP address that the auxiliary server must use to reach the standalone main server, or the primary main server in a redundant system Default: — |
ip-two |
The standby main server IP address that the auxiliary server must use to reach the standby main server in a redundant system Default: — |
Configure the data-sync parameters in the following table, and then enter back ↵.
Table 14-65: Auxiliary server parameters — data-sync
Parameter |
Description |
---|---|
local-ip |
The IP address of the interface on this station that the other auxiliary server in an auxiliary server pair must use to reach this auxiliary server Default: IP address of primary network interface |
peer-ip |
The IP address of the interface on the other auxiliary server station in an auxiliary server pair that this auxiliary server must use to reach the other auxiliary server Default: — |
Configure the tls parameters in the following table, and then enter back ↵.
Table 14-66: Auxiliary server parameters — tls
Parameter |
Description |
---|---|
keystore-file |
The absolute path of the TLS keystore file To enable automated TLS deployment, enter no keystore-file. Default: — |
keystore-pass |
The TLS keystore password Default: available from technical support |
pki-server |
The PKI server IP address or hostname Default: — |
pki-server-port |
The TCP port on which the PKI server listens for and services requests Default: 2391 |
regenerate-certs |
Whether to regenerate the internal TLS certificates Certificate regeneration is required when the current certificates are about to expire, or a new internal root certificate is available. A new internal root certificate is available when the root certificate is reset, or when the PKI server is run on a station other than the station used for the previous certificate deployment. Default: false |
As required, configure the oss parameters in the following table, and then enter back ↵.
Table 14-67: Auxiliary server parameters — oss
Parameter |
Description |
---|---|
public-ip |
The IP address that the XML API clients must use to reach the auxiliary server Default: IP address of primary network interface |
xml-output |
The directory that is to contain the output of XML API file export operations Default: /opt/nsp/nfmp/server/xml_output |
Verify the auxiliary server configuration.
-
<aux configure> show-detail ↵
The auxiliary server configuration is displayed.
-
When you are certain that the configuration is correct, enter the following:
<aux configure> back ↵
The prompt changes to <aux>.
Enter the following:
<aux> apply ↵
The configuration is applied.
Enter the following:
<aux> exit ↵
The samconfig utility closes.
Start the auxiliary server.
-
Enter the following to switch to the nsp user.
# su - nsp ↵
-
Enter the following to start the auxiliary server:
bash$ /opt/nsp/nfmp/auxserver/nms/bin/auxnmsserver.bash auxstart ↵
The auxiliary server starts.
Close the open console windows.
End of steps