Upgrade operation requirements

Prerequisites

Performing an upgrade operation on an NE requires the fulfillment of certain prerequisites, depending on the NE configuration and management. Before you perform an NE upgrade operation, you must import an NE software image. For NEs managed using MDM, see How do I import an NE software image?. NE software images can be downloaded from the Nokia Support Portal for the NE type and release.

For NEs managed using MDM, the adaptors for the new software version must be present on the NSP; see “How do I install adaptor artifacts that are not supported in the Artifacts view?” in the NSP System Administrator Guide.

The following additional general requirements apply to all upgrades:

• 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.

NSP classically-managed NEs

You can use the NSP to upgrade NEs managed through NSP Classic mediation. The following requirements apply:

• The upgrade image must be imported into the NFM-P. See the Classic Management User Guide.

• Both CLI and FTP/SFTP mediation must be configured for the target NEs. For nodes managed through mixed-mode mediation, the following types of CLI access must be enabled, in the order shown: md-cli, and classic-cli.

• NFM-P upgrade policies should have the Validate Disk Space parameter enabled. The upgrade policy used by the upgrade operation is specified in the operation mapping file.

• Confirm that the components installed on the node support the planned upgrade. When you perform an upgrade operation on a 7x50, 7210 SAS, or 7705 SAR NE that is managed using NSP Classic Management, the NSP does not check for deprecated or unsupported components (for example, switch fabric cards or ethernet satellites).

For the multi-phase upgrade operation type nsp-ne-upgrade-with-phases, the following three policies must be configured on the NFM-P with the settings specified below:

Policy name	Required settings
download	download=true, activate=false, reboot=false
activate	download=false, activate=true, reboot=false
reboot	download=false, activate=false, reboot=true (issu=true if issu upgrade triggered)