Operation types provided by NSP

Default operation types

The NSP provides default operation types that allow you to perform backup, restore, upgrade, and audit operations. You can create additional operation types for use with your network.

The following sections describe the operation types available for each task.

Important! Operation types and workflows provided with the NSP are signed by Nokia. Signed artifacts cannot be modified. If you choose to manually clone, edit and re-deploy a signed artifact, the clone is not signed.

Backup operation types

The following table describes the backup operations provided with NSP

Operation type name

Description

Supported NE types

nsp-ne-backup

Operation for NE Backup. You can configure whether debug files, backup certificates, rollback files and TS files are included in the backup.

  • 7215 IXS SRLinux

  • 7220 IXR SRLinux

  • 7250 IXR

  • 7250 IXR SRLinux

  • 7450 ESS

  • 7730 SXR SRLinux

  • 7750 SR

  • 7950 XRS

  • Wavence SM, SA, MSS-8/MSS-4 coreEvo

  • MAG-c Appliance (See MAG-c operation requirements)

Classic mode only: 7210 SAS and variants (Mxp, D, Dxp, K, M, X, T, R, E, S/Sx)

Backup audit operation types

The following table describes the backup audit operation provided with NSP.

Operation type name

Description

Supported NE types

nsp-ne-backup-audit

Operation for NE backup audit. Use this operation to compare a backup file with the current NE configuration and display any differences.

Backup audit operations can be performed on any node, provided the backup being audited was created using the nsp-ne-backup operation type.

Restore operation types

The following table describes the restore operations provided with NSP.

Operation type name

Description

Supported NE types

nsp-ne-restore

Operation for NE restore. Requires backup files created using the NSP.

  • 7215 IXS SRLinux

  • 7220 IXR SRLinux

  • 7250 IXR

  • 7250 IXR SRLinux

  • 7450 ESS

  • 7730 SXR SRLinux

  • 7750 SR

  • 7950 XRS

  • Wavence SM, SA, MSS-8/MSS-4 coreEvo

  • MAG-c Appliance (See MAG-c operation requirements)

Classic mode only: 7210 SAS and variants (Mxp, D, Dxp, K, M, X, T, R, E, S/Sx)

Upgrade operation types

The NSP provides signed upgrade operation types for some NEs.

The following table describes the upgrade operations provided with NSP.

Operation type name

Description

Supported NE types

nsp-ne-upgrade-with-phases

Operation for Multi-Phase Upgrade

The operation phases are:

  • Pre-checks for NE upgrade

  • Software image download to NE

  • Software image activation on NE

  • Reboot NE or perform CPM switchover to complete upgrade

Each phase is a workflow.

SR OS NEs, including 7750 SR, 7950 XRS, 7450 ESS, 7250 IXR, 7705 SAR, and 7210 SAS

SR Linux NEs: 7220 IXR SRLinux, 7250 IXR SRLinux

MAG-c Appliance (see MAG-c operation requirements)

MAG-u (see MAG-u operation requirements)

Classic mode only:

  • 7210 SAS and variants (Mxp, D, Dxp, K, M, X, T, R, E, S/Sx)

  • Wavence SM, SA, MSS-8/MSS-4 coreEvo

Upgrade is available to versions for which node software images can be found on the support portal.

nsp-ne-upgrade-eth-sat

Operation for Ethernet Satellite Upgrade

nsp-ne-wavence-upgrade

Operation for Wavence NE Multi-Phase Upgrade

Wavence NEs

nsp-magc-appl-upgrade-phases

Operation for MAG-c a2 Appliance NE upgrade

MAG-c a2 Appliance NEs

See the Device Management tutorials on the Network Developer Portal for information about working with Operations APIs.

Each operation calls one or more workflows. See the Workflows tutorial on the Network Developer Portal for information about updating workflows.

MAG-c operation requirements

The NSP supports performing backup, restore, upgrade, and audit operations on MAG-c Appliance NEs, with the following requirements:

  • A CLI mediation policy with a common username and password attached to both MAG-c a2 Appliance NE and MAG-c NE

  • An FTP mediation policy attached to both MAG-c a2 Appliance NE and MAG-c NE using the NSP UI

  • The MAG-c a2 Appliance NE name must be unique in the NSP

  • For upgrade operations, the MAG-c a2 Appliance NE must be Release 24.3 R1 or later.

  • When performing an upgrade operation, only select the active MAG-c a2 Appliance NE as the target.

  • For backup operations, ensure the backup file storage directory in the NSP File Server is named the following:

    lsom/neBackup/Nokia/MAG_c_Appliance

    The directory may be incorrectly named after upgrading the NSP from Release 25.4 or earlier.

MAG-u operation requirements

The NSP supports performing upgrade operations with the following considerations:

  • Before starting the upgrade, predefined BNG queries must be configured on the connected MAG-c using the following commands:

    /configure mobile-gateway system bng queries session fwa user-access-type fwa

    /configure mobile-gateway system bng queries session "fwa" output-options count

  • When using the single-phase upgrade operation (nsp-ne-upgrade), the reboot action should not be triggered, as it may result in the loss of only FWA sessions.

  • Do not modify the PFCP configuration of the MAG-u in the 10 minutes before starting an upgrade

  • Only FWA sessions are drained during an upgrade