Upgrade operation requirements
Prerequisites
Performing an upgrade operation on a node requires the fulfillment of certain prerequisites, depending on the node configuration and management. Before you perform a node upgrade operation, you must import a node software image. For nodes managed using MDM, see How do I import a node software image?. For nodes managed using the NFM-P, see the NFM-P User Guide.
For nodes managed using MDM, the adaptors for the new software version must be present on the NSP; see “How do I install or upgrade MDM adaptors?” in the NSP System Administrator Guide.
The following additional general requirements apply to all upgrades:
-
do not delete node software images from the LSO 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 node, 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.
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 Guidefor information about modifying workflows
7x50 node upgrades
7x50 nodes can only be upgraded to a version N+2 later than the current version.
Node software images can be downloaded from the Nokia Support Portal for the node type and release.
NFM-P managed nodes
Both CLI and FTP/SFTP mediation must be configured for the target nodes. The upgrade image must be imported into the NFM-P. 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.
For the multi-phase upgrade operation type nsp-ne-upgrade-with-phases, the following three policies must be configured on 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) |