To upgrade the ISA-AA MDA software

Purpose and prerequisites

Perform this procedure to upgrade only the ISA-AA MDA software on an NE, for example, when the new software includes new AA protocol signatures.

Note: You cannot use the procedure to upgrade between major releases; only minor-release ISA-AA upgrades within the same major release are supported.

An ISA-AA MDA software upgrade is an in-service upgrade that does not require an NE reboot. Although the Software Upgrade parameter in the associated software upgrade policy must be selected for the image activation and upgrade to occur, the Software Upgrade Options in the policy do not apply to an ISA-AA MDA software upgrade.

The 7450 ESS and 7750 SR support ISA-AA MDA upgrades.

The following must be true before you attempt an ISA-AA software upgrade.

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

  • The FTP or secure FTP credentials are configured in the NE mediation policy.

CAUTION 

CAUTION

Service Disruption

Nokia recommends that you open a physical console session on the device that you need to upgrade. The console session allows you to monitor the upgrade and recover in the event of an upgrade failure.

Read the software upgrade information in the device documentation before you perform a software upgrade.

Before you attempt an ISA-AA MDA software upgrade, see the appropriate device release notice and the NSP NFM-P Network Element Compatibility Guide for information about the supported upgrade paths. See NE software upgrade overview for general ISSU information.

Steps
 
1 

Perform the following steps.

  1. Verify that the device supports the new ISA-AA software.

  2. Extract the isa-aa.tim and md5sums.txt files from the Nokia software package to a directory that is reachable by the NFM-P. Ensure that there are no other files in the directory.

  3. Manually verify the software image file checksum against the file checksum listed in the md5sums.txt file.

  4. Verify that the device file system has space for the software image file.

  5. For NEs with redundant CPMs, verify that the boot environments are synchronized by using the appropriate CLI command.

  6. Configure the appropriate software upgrade policy, as described in To configure a software upgrade policy ; apply the policy to the NEs that you need to upgrade.

2 

Back up the device configuration.

3 

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

4 

Click on the Software Images tab and click Import. The Open window appears.

5 

Navigate to the directory that contains the software image, select the directory, and click Open.

Note: The directory must contain only the isa-aa.tim and md5sums.txt files.

6 

The NFM-P verifies the isa-aa.tim checksum and imports the file to the NFM-P database. An entry for the image is listed on the Software Upgrade form.

7 

Select the required ISA-AA image.

8 

Click Upgrade Sites. A list of NEs is displayed. Only the devices that support the software image are listed.

9 

Select one or more NEs.

10 

Click OK. A dialog box appears.

11 

Ensure that the conditions described in the dialog box are met, and then click Yes. The software upgrade begins.

12 

Click on the Software Upgrade Status tab to monitor the upgrade progress.

The following Upgrade State value is displayed:

  • Transferring Image Files—The NFM-P imports the image file from the specified directory to the NFM-P database.

Note: Each upgrade stage also has one or more specific failure values.

If the Software Upgrade parameter in the software upgrade policy is selected, the NFM-P activates the new software image and displays the following sequence of Upgrade State values during the activation:

  • Backing Up ISA-AA File—The NFM-P makes a backup copy of the isa-aa.tim file in the primary-image location specified by the BOF.

  • Updating ISA-AA File—The new isa-aa.tim file is downloaded to the primary-image location specified by the BOF, and the appropriate ISA-AA upgrade command is issued on each NE.

  • Pending ISA MDA Reboot—A reboot of the ISA-AA MDA is required.

13 

If the Software Upgrade parameter in the software upgrade policy is unselected, you must activate the software image.

Note: Alternatively, you can select the required ISA-AA image on the Software Images tab and click Activate Image.

Perform the following steps.

  1. Edit the following software upgrade policy settings, as described in To configure a software upgrade policy :

    • Deselect the Software Download parameter.

    • Select the Software Upgrade parameter.

  2. Select the required software image and click Upgrade Sites. The Select Sites form opens.

  3. Use the form to select the required NEs, and then click OK. A dialog box appears.

  4. Ensure that the conditions described in the dialog box are met, and then click Yes. The software image upgrade begins.

  5. Click on the Software Upgrade Status tab to monitor the upgrade progress. The Upgrade State displays the following sequence of values:

    • Backing Up ISA-AA File—The NFM-P makes a backup copy of the isa-aa.tim file in the primary-image location specified by the BOF.

    • Updating ISA-AA File—The new isa-aa.tim file is downloaded to the primary-image location specified by the BOF, and the appropriate ISA-AA upgrade command is issued on each NE.

    • Pending ISA MDA Reboot—A reboot of the ISA-AA MDA is required.

14 

Perform the following steps on each upgraded ISA-AA MDA to shut down and reboot the MDA.

  1. In the navigation tree equipment view, navigate to the upgraded ISA-AA MDA. The path is Network→NE→Shelf→Card Slot n→Daughter Card Slot n.

  2. Right-click on the Daughter Card Slot object and choose Shut Down. A dialog box appears.

  3. Click View Dependencies. A dialog box displays the number of objects that shutting down the ISA-AA MDA may affect.

  4. Click OK.

  5. When you are certain that shutting down the MDA has no unintended effects, select the check box and click Yes. The NFM-P shuts down the ISA-AA MDA.

  6. Right-click on the Daughter Card Slot object and choose Reboot. A dialog box appears.

  7. Click View Dependencies. A dialog box displays the number of objects that rebooting the ISA-AA MDA may affect.

  8. Click OK.

  9. When you are certain that rebooting the MDA has no unintended effects, select the check box and click Yes. The NFM-P reboots the ISA-AA MDA.

  10. After the MDA reboots, right-click on the Daughter Card Slot object and choose Turn Up. A dialog box appears.

  11. Click Yes. The NFM-P turns up the ISA-AA MDA.

15 

Click on the Software Upgrade Status tab to monitor the upgrade progress.

The Upgrade State column displays the current upgrade status, which is one of the following:

  • Success—The new image is successfully loaded on each ISA-AA MDA.

  • Failed to upgrade ISA—The upgrade is a failure on at least one ISA-AA MDA.

16 

If required, use the NFM-P FTP or SSH file browser to verify that the transferred file and configuration are on each upgraded NE. See To view an NE file system using an FTP file browser for information about using the FTP file browser, and To view an NE file system using an SSH file browser for information about using the SSH file browser.

17 

Update each ISA-AA policy, as required, to enable the new protocol signatures. See Chapter 87, Application assurance for information about configuring AA policies.

End of steps