To perform an OmniSwitch on-demand software upgrade or ISSU

Purpose

Perform this procedure to upgrade the device software on an OmniSwitch.

On-demand software upgrades are supported on all OmniSwitch variants.

Not all OmniSwitch variants support ISSU. This procedure describes how to perform an ISSU on the OS 6860, OS 6860E, OS 6860N, OS 6900, OS 9700E, OS 9800E, and OS 10K. For information about performing an ISSU on an OS 6400, OS 6850E, or OS 6855, see To perform an OS 6400, OS 6850E, or OS 6855 ISSU .

You can perform the following types of software upgrades:

  • Image file

  • Boot files

  • CPLD/FPGA files (OS 6250 and OS 6450, Release 6.6.3-453R01 and later only)

OmniSwitch restrictions
CAUTION 

CAUTION

Service Disruption

An OmniSwitch may require a firmware upgrade before a device software upgrade.

To avoid a service outage, ensure that the device firmware version supports the software upgrade. See the device software Release Notes for information about firmware and software version compatibility.

CAUTION 

CAUTION

Service Disruption

Nokia recommends that you establish a physical console session on the device that you need to upgrade.

This console session will allow you to monitor the upgrade and recover the device in the event of an upgrade failure.

The following conditions must be true before you can perform a device software upgrade on an OmniSwitch:

  • You have an NFM-P user account with an administrator or network element software management scope of command role or a scope of command role with write access to the mediation package.

  • FTP is configured in the NE mediation policy.

The following are the OmniSwitch software upgrade restrictions and requirements.

  • You can perform an ISSU on the OS 6860, OS 6860E, OS 6860N, and OS 6900, when stacked in virtual chassis mode.

  • The OS 9700E, OS 9800E, and OS 10K NE platforms must be fully synchronized and certified.

  • Target images must be loaded to the /flash/issu directory.

  • Sufficient flash memory must be available for upgrade images.

  • OS 9700E and OS 9800E NEs running an ‘R##’ build, such as 6.4.1.123.R01 do not support ISSU patches. The NE must first be upgraded to an ‘S##’ build such as 6.4.1.123.S01. This does not apply to OS 10K NE platforms.

  • The directory structure that stores the image and configuration files is divided into two parts:

    • The certified directory contains files that have been certified by an authorized user as the default files for the switch.

    • The working directory contains files that may or may not be modified from the certified directory. The working directory is a holding place for new files. Files in the working directory must be tested before you commit them to the certified directory.

Note: To perform an ISSU, use the software upgrade window only.

The OS 6400, OS 6850E, OS 9700E, OS 9800E, and OS 10K support standard software upgrades in addition to ISSU. On an OmniSwitch, the introduction of new images requires a system reload which disrupts all data traffic during the reload process. Data traffic loss is limited to L3 base routing instance traffic; no loss of Layer 2 data traffic should occur.

Steps
 
1 

Choose Administration→NE Maintenance→Software Upgrade from the NFM-P main menu. The Software Upgrade form opens.

2 

Perform one of the following:

  1. If you need to upgrade the image files or the image and boot files, go to Step 3 .

  2. If you need to upgrade the boot files, go to Step 17 .

  3. If you need to upgrade the FPGA files, go to Step 30 .

3 

Select the appropriate software upgrade policy.

Note: The NFM-P performs the upgrade according to the configuration in the software upgrade policy that is assigned to the NE.

4 

Click on the Software Images and AOS Software tabs.

5 

Select a software image.

If you are performing an ISSU on an OS 6860, OS 6860E, OS 6860N, or OS 6900, in virtual chassis mode, the ISSU package is identified in the list on the AOS Software tab by the word “present” in the AOS Software ISSU file column. The NFM-P will not validate the ISSU software package; it assumes that the ISSU software package is valid and contains the required files and image. During an ISSU, the NFM-P upgrades the secondary shelves and automatically switches one secondary shelf to become the primary shelf, then upgrades the former primary shelf, which becomes a secondary shelf.

6 

Click Transfer to Sites. A list of NEs opens. The list is filtered to display only the device type that is appropriate for the selected software image.

7 

Select one or more NEs.

8 

Click OK. The selected software image file is uploaded to the working directory of the selected NEs.

9 

Click on the Software Upgrade Status tab to view the status of the upgrade as it progresses. Wait until the files have been successfully transferred before going to Step 10 .

10 

Click Reload working Sites. A list of NEs opens.

11 

Select one or more NEs.

12 
CAUTION 

CAUTION

Service Disruption

Rebooting an NE that is in service is service-affecting.

Ensure that the reboot activity occurs during a maintenance window.

Click OK. The selected NEs reboots using the new software image that was uploaded to the working directory.

Note: Nokia recommends monitoring the switch to ensure that the reboot completes successfully.

13 

Click Certify Sites. A list of NEs opens.

Note: Only software that is thoroughly validated as viable and reliable software should be copied to the certified directory. After you copy the software to the certified directory, you cannot recover a previous version of the image or configuration files.

14 

Select one or more NEs.

15 

Click OK. The software image stored in the NE working directory is copied to the certified directory. The working directory and the certified directory are synchronized so that the same files are in both directories.

16 

Perform one of the following:

  1. If you need to upgrade the boot files, go to Step 24 .

  2. If you need to upgrade the FPGA files, go to Step 31 .

  3. If you are upgrading only the image files, go to Step 35 .

17 

Select the appropriate software upgrade policy.

Note: The NFM-P performs the upgrade according to the configuration in the software upgrade policy that is assigned to the NE.

18 

Click on the Software Images and AOS Software tabs.

19 

Select a software image.

20 

Click Transfer to Sites. A list of NEs opens. The list is filtered to display only the device type that is appropriate for the selected software image.

21 

Select one or more NEs.

22 

Click OK. The boot files are uploaded to the root directory of the selected NEs.

23 

Click on the Software Upgrade Status tab to view the status of the upgrade as it progresses. Wait until the files have been successfully transferred before going to Step 24 .

24 

Click Upgrade Boot files. A list of NEs opens. The list is filtered to display only the device type that is appropriate for the selected files.

25 

Select one or more NEs.

26 

Click OK. The boot files are upgraded on the selected NEs.

27 

Click on the Software Upgrade Status tab to view the status of the upgrade as it progresses. Wait until the files have been successfully transferred before going to Step 28 .

28 

Click Delete boot files.

29 

Perform one of the following:

  1. If you need to upgrade the FPGA files, go to Step 31 .

  2. If you do not need to upgrade the FPGA files, go to Step 35 .

30 

Click on the Software Images and AOS Software tabs.

31 

Select a software image.

32 

Click Upgrade FPGA files. A list of NEs opens. The list is filtered to display only the device type that is appropriate for the selected file type.

33 

Select one or more NEs.

34 

Click OK. The selected FPGA files are uploaded to the root directory of the selected NEs.

35 

Click on the Software Upgrade Status tab to monitor the upgrade progress. The Upgrade State column displays the current upgrade status.

After the FPGA files are successfully transferred, the selected NEs are rebooted.

End of steps