Commission new stations, if required

If you are deploying any NSP Flow Collector or Flow Collector Controller on a new station, commission the station according to the platform specifications in this guide and in the NSP Planning Guide.

Note: The hostname and IP address of a replacement station must match the hostname and IP address of the station being replaced.

For information about deploying the RHEL OS using an NSP OEM disk image, see NSP disk-image deployment.

Stop NSP Flow Collector Controllers

Perform the following steps on each NSP Flow Collector Controller station to stop the NSP Flow Collector Controller.

Note: If an NSP Flow Collector is also installed on the station, the Flow Collector stops automatically.

1. Log in to the station as the nsp user.

2. Enter the following:

   bash$ /opt/nsp/flow/fcc/bin/flowCollectorController.bash stop ↵

   The NSP Flow Collector Controller stops.

Stop NSP Flow Collectors

Stop each NSP Flow Collector that is not collocated with an NSP Flow Collector Controller.

Note: Any NSP Flow Collector that is collocated with a Flow Collector Controller is automatically stopped earlier in the procedure.

1. Log in to the NSP Flow Collector station as the nsp user.

2. Enter the following:

   bash$ /opt/nsp/flow/fc/bin/flowCollector.bash stop ↵

   The NSP Flow Collector stops.

Uninstall software

Log in as the root user on a station that has the downloaded and extracted NSP component installer package.

Open a console window.

Enter the following:

# cd path/NSD_NRC_R_r/bin ↵

where

path is the directory path of the NSP component installer package

R_r is the NSP software release, in the form MAJOR_minor

Enter the following:

# ./uninstall.sh --ask-pass --target address_1,address_2,...address_n ↵

where address_1, address_2,...address_n is a comma-separated list of the local NSP Flow Collector Controller and Flow Collector IP addresses

You are prompted for the common root password of the stations.

Enter the password.

The NSP software is removed from each station, and the following backup directory is created:

/opt/nsp/backup_flow

Back up configurations

Back up the configuration of each NSP Flow Collector Controller and Flow Collector; perform the following steps on each station that hosts an NSP Flow Collector Controller, and on each station that hosts only an NSP Flow Collector.

1. Log in as the root user on the station.

2. Open a console window.

3. Enter the following:

   # cd /tmp ↵

4. Enter the following:

   # tar -czf host_backup_flow /opt/nsp/backup_flow ↵

   where host is a unique station identifier such as the station hostname, or a name that indicates the station role, such as FCCn for a Flow Collector Controller, or FCAAn for a Flow Collector in AA mode

   A host_backup_flow.tar.gz file is created in the /tmp directory.

5. Transfer the /tmp/host_backup_flow.tar.gz file to a secure location on a separate station that is not affected by the upgrade activity.

Recommission stations, if required

If you are reusing any NSP Flow Collector Controller or Flow Collector station, recommission the station according to the platform specifications in this guide and the NSP Planning Guide.

For information about deploying the RHEL OS using an NSP OEM disk image, see NSP disk-image deployment.

Note: If you are using RHEL OpenStack VMs, you must re-image each VM using the rebuild option, which preserves the current VM IP addresses, and specify the required new RHEL version.

Start PKI server

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.

Upgrade software

Perform the following steps on each new or recommissioned station.

1. Log in as the root user.

2. Open a console window.

3. Transfer the appropriate host_backup_flow.tar.gz file created Step 9 to the /tmp directory on the station.

4. Enter the following:

   # cd /tmp ↵

5. Enter the following to extract the file content:

   # tar xvf host_backup_flow.tar.gz ↵

   The /tmp/backup_flow directory is created, and the configuration files are extracted to the directory.

6. Enter the following:

   # mv backup_flow /opt/nsp ↵

Download the NSP component installer package (NSP_NSD_NRC_R_r.tar.gz) from OLCS and extract it on any station running a supported version of RHEL. This does not have to be the station on which the NSP Flow Collector Controller or an NSP Flow Collector is installed; the installer can perform remote upgrades.

An NSD_NRC_R_r directory is created in the current directory, where R_r is the release identifier in the form MAJOR_minor.

Note: In subsequent steps, the directory is called the NSP installer directory or NSP_installer_directory.

Log in as the root user on the station that has the downloaded NSP software bundle.

Enter the following:

# cd NSP_installer_directory/NSD_NRC_R_r/bin ↵

Create a hosts file in the current directory that contains the required entries in the following sections:

• [nspos]—one entry for each ZooKeeper host; the ZooKeeper hosts are one of the following:

  • if the NSP system includes only the NFM-P, the NFM-P main servers

  • otherwise, the VIP address of each NSP cluster

• [fcc]—one line entry for each Flow Collector Controller

• [fc]—one line entry for each Flow Collector

Note: If an NSP Flow Collector Controller and Flow Collector are to be collocated on one station, specify the same address for in the [fc] and [fcc] sections; for example:

[fcc] 203.0.113.3 advertised_address=198.51.100.3 ansible_host=198.51.100.3

[fc] 203.0.113.3 ansible_host=198.51.100.3 fc_mode=AA

See NSP hosts file for configuration information.

Note: A sample hosts file is in the following directory; you must use a modified copy of the file for installation:

• NSP_installer_directory/NSD_NRC_R_r/examples

  where R_r is the NSP software release

Create a config.yml file in the NSP installer directory that includes the following sections; see NSP RPM-based configuration file for information.

• multi-component deployment:

  • sso

  • tls

  • section for each component to install

• independent deployment, for example, if you are adding a Flow Collector or Flow Collector Controller to an NFM-P-only system:

  • sso

  • tls

Note: The following parameter values in the tls section must match the values in the NSP configuration file; otherwise, the values must match the values in the NFM-P main server configuration:

• secure

• PKI server parameters

You can use the samconfig “show” command on a main server to display the tls parameters. See NFM-P samconfig utility for information about using the samconfig utility.

Note: A sample config.yml file is in the following directory; you must use a modified copy of the file for installation:

• NSP_installer_directory/NSD_NRC_R_r/examples

  where R_r is the NSP software release

Enter the following:

Note: Include the --ask-pass option only if each target station has the same root user password.

# ./install.sh --ask-pass --target target_list ↵

where target_list is a comma-separated list of the NSP Flow Collector Controller and NSP Flow Collector IP addresses

The NSP Flow Collector Controller or NSP Flow Collector software is upgraded on each station.

Configure NFM-P in DR deployment

If the NSP cluster and NSP Flow Collector Controllers are not in a DR deployment, go to Step 25.

Log in as the root user on the NFM-P main server in the same data center as the NSP Flow Collector Controller.

Open a console window.

Stop the main server.

1. Enter the following to switch to the nsp user:

   # su - nsp ↵

2. Enter the following:

   bash$ cd /opt/nsp/nfmp/server/nms/bin ↵

3. Enter the following:

   bash$ ./nmsserver.bash stop ↵

4. Enter the following:

   bash$ ./nmsserver.bash appserver_status ↵

   The server status is displayed; the server is fully stopped if the status is the following:

   Application Server is stopped

   If the server is not fully stopped, wait five minutes and then repeat this step. Do not perform the next step until the server is fully stopped.

5. Enter the following to switch back to the root user:

   bash$ su - ↵

6. If the NFM-P is not part of a shared-mode NSP deployment, enter the following to display the nspOS service status:

   # nspdctl status ↵

   Information like the following is displayed.

   Mode:     DR

   Role:     redundancy_role

   DC-Role:  dc_role

   DC-Name:  dc_name

   Registry: IP_address:port

   State:    stopped

   Uptime:   0s

   SERVICE           STATUS

   service_a         inactive

   service_b         inactive

   service_c         inactive

   You must not proceed to the next step until all NSP services are stopped; if the State is not ‘stopped’, or the STATUS indicator of each listed service is not ‘inactive’, repeat this substep.

You must create an association between the local NSP Flow Controller and the local NFM-P main server to ensure that the Flow Collector and Controller remain in communication with the local NFM-P during NSP DR activity.

Add the local data center name to the main-server configuration.

Note: The data center name must be a name other than “default”.

1. Enter the following:

   # samconfig -m main ↵

   The samconfig utility opens, and the following is displayed:

   Start processing command line inputs...

   <main>

2. Enter the following:

   <main> configure nspos dc-name data_center ↵

   where data_center is the data center name, which must match the dcName value for the local NSP cluster in the NSP configuration file

   The prompt changes to <main configure nspos>.

3. Enter the following:

   <main configure nspos> exit ↵

   The prompt changes to <main>.

4. Enter the following:

   <main> apply ↵

   The configuration is applied.

5. Enter the following:

   <main> exit ↵

   The samconfig utility closes.

Start the main server.

1. Enter the following to switch to the nsp user:

   # su - nsp ↵

2. Enter the following:

   bash$ cd /opt/nsp/nfmp/server/nms/bin ↵

3. Enter the following:

   bash$ ./nmsserver.bash start ↵

4. 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.

Start NSP Flow Collector Controllers

Perform the following steps on each NSP Flow Collector Controller station.

Note: If an NSP Flow Collector is also installed on the station, the Flow Collector starts automatically.

1. Log in to the station as the nsp user.

2. Enter the following:

   bash$ /opt/nsp/flow/fcc/bin/flowCollectorController.bash start ↵

   The NSP Flow Collector Controller starts.

3. Close the console window.

Start NSP Flow Collectors

Start each NSP Flow Collector that is not collocated with an NSP Flow Collector Controller.

Note: Any NSP Flow Collector that is collocated with a Flow Collector Controller is automatically started earlier in the procedure.

1. Log in to the NSP Flow Collector station as the nsp user.

2. Enter the following:

   bash$ /opt/nsp/flow/fc/bin/flowCollector.bash start ↵

   The NSP Flow Collector starts.

3. Close the console window.

Perform the following steps for each NSP Flow Collector.

1. Use a browser to open the web UI at the following URL:

   https://server:8443/fc/admin

   where server is the NSP Flow Collector IP address or hostname

   The Collection Policy configuration page opens.

2. Verify the settings on each configuration page to ensure that the settings from before the upgrade are preserved.

If no other components are to be deployed, stop the PKI server by entering Ctrl+C in the console window.

Close the open console windows.

End of steps