Upgrade prerequisites

For classic nodes upgrade

Complete the following prior to running a classic node upgrade:

  • Verify that the classic mediation policy is correctly set in NSP.

For MD nodes upgrade

Complete the following prior to running an MD node upgrade:

  1. Install adaptors for the new node version; Pre-check will fail if adaptors are not installed. See “How do I install adaptor artifacts that are not supported in the Artifacts view?” in the NSP System Administrator Guide for more information.

  2. Configure FTP policy:

    An FTP mediation policy must be assigned to the NE before you can perform a backup. FTP mediation policies are created and assigned using a REST API. See the Device Management tutorials on the Network Developer Portal.

Additional requirements

The following additional general requirements apply to all upgrades:

  • Make sure there is enough space on the node for the upgrade.

  • Do not delete NE software images from the NSP during an upgrade operation.

  • Both primary and secondary images should be stored on the same flash drive number (for example, cf3 or cf1).

  • bof.cfg should be stored on the same cf where the primary image is stored.

  • Backout files are stored locally on the NE, and are required if an upgrade fails.

  • Pre-check removes images not referenced in the BOF configuration. If insufficient space is freed up, the upgrade cannot proceed.

  • Tertiary images are not supported.

An upgrade operation can fail if a workflow task times out; for example, fetching upgrade status or validating downloads and CPM synchronization. You may need to customize the upgrade workflow for your network; see the NSP Network Automation Guide for information about modifying workflows.

ISSU upgrade path limitations

Before performing an upgrade operation, consult the NE documentation to confirm that the upgrade you need to perform is supported on that NE. For example, a 7750 NE only supports upgrades to releases one or two major releases later than the current release: from Release 21.x to Release 22.x or 23.x, but not to Release 24.x or later.

Nokia recommends using the nsp-ne-upgrade-with-phases operation type to upgrade all nodes that support upgrade with phases. When you create an operation with this operation type and NE type, the parameter values are provided as input for the upgrade workflow. NSP monitors the status of workflow executions.

Note: Scale limits apply for number of concurrent executions and number of targets per operation; see Scale limits for large-scale operations in the NSP Planning Guide.