NSP component upgrade overview

Component upgrade support
CAUTION 

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: When you upgrade a shared-mode NSP system that includes the NFM-P, the existing Service Supervision groups are migrated from the NFM-P to the NSP. The migration may take a few hours, depending on the number of services. During this time, you must not auto-create Service Supervision groups. You can use the Find Ungrouped members count in the Group Manager application to help determine when the upload is complete, after which you can auto-create groups.

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: If you have modified any NFM-P template files, contact technical support before you attempt an NSP or NFM-P system upgrade; an upgrade overwrites customized template values.

Note: NFM-P language localization files are not automatically backed up during an NSP upgrade. To preserve your language localization, you must back up your localization file before an NSP upgrade, and then redeploy the file after the upgrade.

Shared-mode upgrades
CAUTION 

CAUTION

Upgrade Failure

If the system locales of the NFM-P and the NSP components of a shared-mode deployment do not match, a system upgrade may fail.

Ensure that the NSP system locale matches the NFM-P locale before you attempt a shared-mode system upgrade. If the locales do not match, contact technical support for assistance.

The components that comprise a shared-mode 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.