To install the NSP auxiliary database

Purpose

The following steps describe how to install and initialize the NSP auxiliary database software.

To perform this procedure, the RHEL 9 OS must be installed on the auxiliary database station.

Note: You must perform the procedure in each auxiliary database cluster of a geo-redundant NSP deployment.

Note: You require root user privileges on each auxiliary database station.

Note: Nokia recommends that password-free SSH is enabled between auxiliary database cluster hosts for the root user.

Note: A leading # character in a command line represents the root user prompt, and is not to be included in a typed command.

Steps

Note: The software is installed on one station, and then automatically propagated to the other stations in the cluster.

Open a console window.

Enter the following:

# cd /opt/nsp/nfmp/auxdb/install/config ↵

Enter the following:

# cp install.config.default install.config ↵

If you are performing the installation as a non-root user and intend to allow non-root users other than the NSP super user to edit the file, perform one of the following.

Set the user and group ownership of the file to samauxdb:nsp.
Set the group ownership to nsp, and grant read/write access to the nsp group.

Open the install.config file using a plain-text editor such as vi.

CAUTION

Service disruption

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:

hosts=internal_IP1,internal_IP2...internal_IPn

export_hosts=internal_IP1[export_IP1],internal_IP2[export_IP2]...internal_IPn[export_IPn]

where

internal_IP1, internal_IP2...internal_IPn are the IP addresses that the auxiliary database stations use to communicate with each other

export_IP1, export_IP2...export_IPn are the IP addresses that the stations use for communication with other components in the deployment

The following is an export_hosts configuration example; see Table 14-1, Auxiliary database station addressing for more information.

export_hosts=10.1.1.10[198.51.100.10],10.1.1.11[198.51.100.11],10.1.1.12[198.51.100.12]

Table 14-1: Auxiliary database station addressing

Auxiliary database station address

install.config parameter entries

Definition

Internal

hosts

export_hosts ¹

Private address on segregated network for intra-cluster auxiliary database communication

External

export_hosts values in brackets, such as [198.51.100.10] in the example

Address on NSP internal network that is routable from other NSP components on the NSP internal network that require auxiliary database access

Notes:

If required, for a single-station auxiliary database you can specify the same address for internal and external communication. In such a scenario, you specify the same address for internal_IP and export_IP.

Edit the following lines in the file to read as shown below.

Note: Security is always enabled. The secure flag is no longer required and may be removed.

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:

if configured, the advertised value
otherwise, the virtualIp value

Save and close the install.config file.

Enter the following:

# cd /opt/nsp/nfmp/auxdb/install/bin ↵

Enter the following:

# ./auxdbAdmin.sh install ↵

The script sequentially prompts you to enter and re-enter new passwords for the following database user accounts:

samauxdb
samuser
samanalytic
samanalytic_ano

At each prompt, enter or re-enter a password, as required.

The script then sequentially prompts for the root user password of each auxiliary database station.

At each prompt, enter the required password.

Messages like the following are displayed as the software is installed on each station and the database is created:

Populating auxiliary database user passwords in the vault

Installing auxiliary database on IP_address ....

Cleaning auxiliary database host(s) in ssh known_hosts for root and samauxdb users.

Creating auxiliary database cluster

Successfully created auxiliary database cluster

--------------------------------------------------------------------------------

Refreshing auxiliary database host(s) in known_hosts for root and samauxdb on IP_address

Raising shields on host IP_address

--------------------------------------------------------------------------------

Creating auxiliary database

Distributing changes to cluster.

Creating database samdb

Starting bootstrap node node_name (IP_address)

...

Starting nodes:

node_name (IP_address

...

Starting Vertica on all nodes. Please wait, databases with a large catalog may take a while to initialize.

Installing OS_package package

Success: package OS_package installed

Database creation SQL tasks completed successfully.

Database samdb created successfully.

Successfully created auxiliary database

Performing post install configuration tasks

Creating public interface for host IP_address[IP_address]

...

CREATE NETWORK INTERFACE

ALTER NODE

Setting DB samdb restart policy to never and replicating to cluster...

Database samdb policy set to never

Installing user defined extension libraries and functions.

Unzipping Python libraries.

Ensuring that all directories under /opt/vertica have at least 0755 mode.

Setting sticky bit on all nodes.

INFO: About to configure TLS ....

Generating TLS certificates

Generating external certificate artifacts for alias [nsp] using default key-size [4096]

...

Distributing configuration to all nodes

INFO: About to validate key and certificate

Make sure the certificate has not expired and that the specified date range is current and valid.

Not Before: date

Not After : date

INFO: Complete validating key and certificate

INFO: Adding certificate to AuxDB

Post install configuration tasks completed successfully.

Successfully installed auxiliary database.

Output captured in /opt/nsp/nfmp/auxdb/install/log/auxdbAdmin.sh.timestamp.log

The script installs the software on each station.

If you are deploying a geo-redundant auxiliary database, perform the following steps to configure password-free ssh between the current cluster and the remote geo-redundant cluster:

Enter the following:

bash$ su - samauxdb ↵
Enter the following for each station in the remote geo-redundant cluster:

bash$ ssh-copy-id station_IP ↵

where station_IP is the external IP address of a station in the remote geo-redundant cluster
Enter the following:

bash$ exit ↵

Enter the following to enable and start the auxiliary database services:

# ./auxdbAdmin.sh startAndEnableServices ↵

Note: In a geo-redundant deployment, the auxiliary database services for both clusters should only be enabled and started after both clusters are installed.

End of steps