Upgrading from Release 22.9 or later

NSP system upgrade process
CAUTION 

CAUTION

Service Disruption

An NSP system upgrade requires a thorough understanding of NSP system administration and platform requirements, and is supported only under the conditions described in this guide, the NSP Planning Guide, and the NSP Release Notice.

Such an operation must be planned, documented, and tested in advance on a trial system that is representative of the target live network. Contact NSP professional services to assess the requirements of your NSP deployment, and for information about the upgrade service, which you are strongly recommended to engage for any type of deployment.

The following workflows provide comprehensive overviews of the required upgrade activities for advance planning purposes:

Each workflow includes links to the required procedures for completing the upgrade.

Note: An NSP system that manages a large number of NEs may require several hours, or potentially a full day for a very large network, to resynchronize the network following an NSP upgrade. It is important to consider the resynchronization time when planning a maintenance window for NSP upgrade activity.

Note: After an upgrade from Release 23.11 or earlier, in the Network Health view, service-related dashlet KPIs including Service Health and Affected Services reset to 0. The dashlet counts are restored after KPIs are recalculated, which may take a few hours in a large network.

Licensing

Your NSP system may require a new or updated license, depending on your deployment and the NSP release from which you upgrade. It is recommended that you contact Nokia early in the planning process to obtain the required license for your upgraded deployment.

Kubernetes version

The NSP requires specific Kubernetes registry and deployment software versions. The NSP cluster upgrade procedure includes steps for performing the required Kubernetes environment upgrade.

Note: Attempting to upgrade an NSP system without upgrading Kubernetes as prescribed results in failure.

You can also perform an off-cycle Kubernetes upgrade independent of an NSP software upgrade; see Kubernetes deployment environment for information.

DR NSP system upgrade

After the preliminary upgrade preparation of each NSP cluster, the standby cluster is stopped while the primary is upgraded. Network visibility is lost during the primary cluster upgrade, as indicated in Workflow for DR NSP system upgrade from Release 22.9 or later, which lists the upgrade operations that are to be performed on each NSP cluster.

Some stages of the DR upgrade process can be performed on each cluster concurrently, for example, data and configuration backups, software downloads, and file transfers.