Finding your way in this guide
Basic platform configuration
Some platform configuration requirements are common to all NSP deployment types, as described in Common deployment configuration elements.
When the platform configuration is complete, see NSP deployment information map. for the topics that are relevant to your deployment path.
Common deployment configuration elements
The following topics outline the final platform configuration actions required before you deploy the NSP software.
Note: Depending on the OS installation method in a new or expanded deployment, the order in which you deploy the OS and partition the disks varies, as described below.
Disk partitioning
A physical component or VM that hosts NSP software requires a specific disk partitioning scheme. For a new or expanded deployment, when you establish the partitions depends on the OS deployment method, and is one of the following:
-
during NSP OEM image deployment, as described in NSP disk-image deployment
-
after a manual RHEL OS installation; see one of the following, based on your deployment environment:
For a deployment upgrade, you must ensure that the current disk partitions on each component are of sufficient capacity as defined for the new NSP release.
OS deployment
You must deploy or update each component OS, as required.
-
new or expanded system—install the OS on each new NSP VM and component on physical hardware using one of the following methods; see Chapter 3, RHEL OS deployment for the NSP:
-
system or component upgrade—apply the latest update to each OS instance as described in the following, depending on the OS deployment method:
Security
The NSP is a highly secure system that has stringent security requirements. Chapter 4, Configuring NSP security describes how to configure and deploy TLS for the NSP, and provides information about system-level and application-level user accounts and authentication.
NSP network management environment
Chapter 5, NSP deployment basics describes the NSP Kubernetes infrastructure and includes Kubernetes upgrade procedure To upgrade the NSP Kubernetes environment. The chapter also describes aspects of internal and external system communication such as IP-version support and optional logging options that include remote forwarding.
Note: Typically, the NSP Kubernetes environment requires an upgrade before you can upgrade the NSP software.
Chapter 6, NSP software configuration explains how to set the NSP deployment parameters and enable specific NSP functions that may require additional configuration.
NSP deployment information map
The NSP Installation and Upgrade Guide topics of interest vary depending on the current and projected deployments. The information in Table 1-2, Guide topics by deployment path can help you identify the relevant topics based on your proposed deployment path, and identify chapters and topics that are not of interest. The topics are listed in the order that best defines the overall flow of deployment operations.
Note: The table provides a high-level path through NSP Installation and Upgrade Guide topics; you are strongly encouraged to also read any topic overview material that is not explicitly listed.
Note: The NSP system upgrade procedure include references to topics in Chapter 14, NSP component upgrade for upgrading ancillary components.
Table 1-2: Guide topics by deployment path
Current deployment |
Projected deployment |
Relevant topics / notes |
---|---|---|
None; new to the NSP |
NSP Release 25 |
|
With Classic Management |
||
With NSP auxiliary database |
||
System upgrade and migration | ||
NSP Release 24.11 |
NSP Release 25 |
|
With Classic Management |
||
With NSP auxiliary database |
||
NSP Release 24.8 |
NSP Release 25 |
|
With Classic Management |
||
With NSP Flow Collectors |
||
With NSP auxiliary database |
||
NSP Release 23.4 to 24.4 |
NSP Release 25 |
|
With Classic Management |
||
With NSP Analytics |
||
With NSP Flow Collectors |
||
With NSP auxiliary database |
||
NSP Release 22 or earlier without Classic Management |
NSP Release 25 without Classic Management |
You must first perform intermediate NSP and NFM-P system upgrades to at least Release 23 using the documentation for the upgrade release, and then use this guide to upgrade the NSP to Release 25. If you are also upgrading the NFM-P to Release 25, see NFM-P system upgrade and NSP auxiliary database upgrade, as required. If the NFM-P is to stay at the intermediate release, see To enable NSP compatibility with an earlier NFM-P system. |
NSP Release 22 or earlier with Classic Management |
NSP Release 25 with Classic Management | |
Release 22 or earlier NFM-P, no NSP cluster |
NSP Release 25 with MDM and Classic Management |
You must first perform an intermediate NFM-P system upgrade to Release 23 using the Release 23 documentation, and then perform the NFM-P migration described in To migrate from an independent NFM-P system to an NSP cluster deployment. If you are not retaining Classic Management, see Uninstalling the NFM-P. |
NSP Release 25 with MDM only | ||
NSP Release 25 system conversion | ||
Standalone NSP without Classic Management |
DR NSP clusters without Classic Management |
|
Standalone NSP with Classic Management |
DR NSP clusters with Classic Management |
|
NSP without Classic Management using IPv4 |
NSP cluster without Classic Management using IPv6 communication |
|
NSP cluster with Classic Management using IPv4 |
NSP cluster with Classic Management using IPv6 communication |
|
Single-interface NSP clusters |
Multi-interface NSP clusters |
|
NSP Release 25 system integration | ||
NSP without Classic Management |
NSP integrated with NFM-P currently at Release 22 or earlier |
You must perform an NFM-P upgrade to Release 23 using the Release 23 documentation. |
NSP integrated with NFM-P currently at Release 23 |
You can upgrade the NFM-P to Release 25 as described in NFM-P system upgrade, or integrate the Release 23 NFM-P; see To add an independent NFM-P to an existing NSP deployment. | |
NSP without integrated WS-NOC product |
NSP integrated with Release 24.6 or later WS-NOC |
|
NSP Release 25 deployment expansion or component addition | ||
NSP cluster with insufficient dedicated VMs |
NSP cluster with additional dedicated VMs |
|
NSP cluster without auxiliary database |
NSP cluster with auxiliary database |