Introduction

Component upgrade support

CAUTION Deployment failure

You cannot successfully upgrade an NSP component that has never initialized.

Before you attempt an NSP component upgrade, ensure that the component has successfully initialized.

Before you attempt to perform a procedure in this chapter, you must ensure that your deployment meets the hardware and software requirements described in the NSP Planning Guide.

Note: It is strongly recommended that you verify the GPG signature of each RPM file that you download from Nokia to ensure that each file has a valid Nokia signature.

Note: It is strongly recommended that you verify the message digest of each NSP image file or software bundle that you download from the Nokia Support portal. The download page includes the MD5, SHA256, and SHA512 checksums for comparison with the output of the RHEL md5sum, sha256sum, or sha512sum command. See the associated RHEL man page for command usage information.

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.

Upgrade order

The elements of an NSP deployment must be upgraded in a specific order, starting with the NSP cluster. During the upgrade, the NSP UI is unavailable, as is an NFM-P or WS-NOC that is part of the NSP system. After the NSP component upgrade, the NFM-P and WS-NOC can be upgraded in any order.

See the NSP compatibility matrix in the NSP Release Notice to ensure that the proposed upgrade results in a supported configuration.