How do I upgrade software on a 7750 SR NE?

Purpose

This procedure shows the process of upgrading software on an MDM-managed 7750 SR NE. Before performing this procedure, verify that the NE to be upgraded is reachable, and that adaptors for the new software version are installed on the NSP.

Nokia recommends using the nsp-ne-upgrade-with-phases operation type to upgrade a 7750 SR. 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.

The following table shows the general process for this example procedure.

Phase

Workflow

Process

Pre-checks

LSO_7x50_Pre_Checks

which calls

LSO_7x50_Upgrade_MD_Mixed_Pre_Checks for MD mode

  • Checks current software version: if the update is already done, no workflow is called

  • Checks the BOF

  • Checks on CPM redundancy

  • Checks availability of adaptors and supported equipment

  • Checks for deprecated cards and MDAs on the node

  • Retrieves details of the target software image

  • Runs a cleanup of stale images on the the /images/ folder

Download

LSO_7x50__Download

which calls

LSO_7x50_Upgrade_MD_Mixed_Download for MD mode

  • Reads and processes the BOF

  • Creates a directory on the NE and transfers the image files

  • Confirms the file integrity and sends a success message

Activate

LSO_7x50__Activate

which calls

LSO_7x50_Upgrade_MD_Mixed_Activate for MD mode

  • Saves the updated configuration on the NE and performs an admin save

  • Synchronizes the CPM

  • Resets redundancy settings as needed and sends a success message

Reboot

LSO_7x50_Reboot

which calls

LSO_7x50_Upgrade_MD_Mixed_Reboot for mixed mode

  • Checks BOF instructions for reboot and CPM redundancy requirements

  • Processes redundancy

  • Triggers a reboot and checks the device version.

  • Sends a success message.

Steps
 
1 

Perform How do I import an NE software image?.

2 

Open Device Management, All Operations.

3 

Click png2.pngOPERATION.

4 

In the form that opens, click png2.pngOPERATION TYPE.

5 

In the Select an Operation Type form, choose nsp-ne-upgrade-with-phases and click ADD.

Fields required for the operation appear in the Operation Inputs panel.

6 

In the General panel, enter a name for the operation and an optional description, and configure Operation Control.

You can identify the operation by the name you enter.

7 

In the Select Targets panel, click png2.png SELECT, Resources, Network Elements.

8 

In the Select Network Elements form, choose one or more NEs to add them to the Bin on the right of the form.

Use the fields above the list of NEs to filter the list as needed.

9 

Click ADD. The NEs you selected appear in the Select Targets panel.

You can change the list of selected targets if needed:

  • Click png2.png SELECT to reopen the Select Network Elements form and add additional NEs.

  • Choose an NE and click png6.png (Delete) to remove the NE from the list of targets.

  • Click CLEAR to clear the list.

10 

In the Operation Inputs panel, configure the mandatory parameters:

Parameter

Description

Target Software Version

Specifies the node software version you are upgrading to.

For a 7750 SR NE, the format of the software version must be must be TiMOS-xx.yy.Rz, for example, TiMOS-21.5.R1.

Is ISSU

Specifies whether the upgrade operation is an in service software upgrade.

This parameter is only valid for MDM-managed NEs.

Auto Cleanup

Specifies whether automatic flash cleanup should be performed on the NE as part of the operation.

Free Space Post Upgrade (Enter a Number)

Specifies the expected free disk space after upgrade, as a percentage. Enter a number.

11 

Configure the Advanced Inputs as needed:

Parameter

Description

Window Size

Failure Threshold

These two parameters work together to define an automatic stopping point for the operation due to failed workflow executions:

  • Window size specifies the sample size to use when calculating whether a threshold has been crossed.

  • Failure threshold specifies the percentage of executions failed that will trigger the automatic stop.

For example, with a window size of 200 and a failure threshold of 50%, the operation will automatically stop after 100 failed executions. The phase and operation are paused and any not-started executions remain in not-started status.

The following parameters can be configured separately for each phase of the operation: pre-checks, software download, software activation, and NE reboot or CMP switchover.

  • Concurrency Count

  • Phase Timeout (minutes)

  • Average Execution Threshold (minutes)

These parameters specify how the workflow executions will be managed. The pre-check steps themselves are defined in the applicable workflow.

  • Concurrency Count: maximum number of executions to run concurrently

  • Phase Timeout and Average Execution Threshold: if these parameters are configured, the operation automatically stops after the specified time. The phase and operation are paused and any not-started executions remain in not-started status.

12 

If you selected Per Target execution for Operation Control in the General panel, configure phase execution scheduling in the View/Edit Schedule panel. You can specify for each phase what happens when a target reaches that phase.

13 

Perform one of the following to finished creating the operation.

  1. To start the operation immediately, click RUN. The operation appears in the All Operations view and begins executing the first phase.

  2. To save the operation for later, click SAVE. The operation appears in the Operation Schedules view, and you can configure or start the operation at a later time.

End of steps