To upgrade the vCPAA OS software using the NFM-P client GUI

Important information

For the vCPAA, software upgrades performed from the NFM-P client GUI use the software download method. Ensure that the Software Download option is selected when you create a software upgrade policy for the vCPAA. The software download method does not provide automatic reboot of the NE; you must perform a manual reboot using a CLI. You must also use a CLI to modify the NVRAM.DAT and bof.cfg files.

See the “NE software upgrades” chapter in the NSP NFM-P User Guide for more information about NE software upgrades.

You must configure the system IP address and enable SNMP and the FTP server on the vCPAA. See the “Device commissioning and management” chapter in the NSP NFM-P User Guide for information.

Steps
 

The vCPAAs you are upgrading must be administratively down. To turn down the vCPAA, perform the following:

  1. Choose Tools→Route Analysis→Admin Domains/CPAAs from theNFM-P main menu. The Admin Domains/CPAAs form opens.

  2. Choose CPAA (CPAM: Topology) from the object drop-down and click Search. A list of discovered CPAAs appears.

  3. For each vCPAA that you need to turn down, double-click on the entry in the list. The CPAA (Edit) form opens.

  4. Set the Administrative State parameter to Down and click Apply.

  5. Close the CPAA (Edit) form.

  6. Close the Admin Domains/CPAAs form.


Import the new CPAA software image into the NFM-P database.

  1. Copy or move the files to a location that is accessible to the NFM-P

    The required files are:
    • boot.tim

    • both.tim

    • md5sums.txt

    Ensure that the required files are all within the same folder. For more information see “To import device software files to the NFM-P” in the NSP NFM-P User Guide.

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

  3. Click on the Software Images tab, then on the SR Software Images subtab, if required.

  4. Click on the Import button. The Open form opens.

  5. Navigate to the directory that contains the software image and click Open. The Open form closes.

    The NFM-P verifies the file set, imports the files to the database, and displays an entry for the imported image in the list on the Software Images tab.

    For the CPAA, the Target Product name is Alcatel-SR/ESS-7XXX by default.

  6. Confirm that the image is valid, and is the correct version.


Create a CPAA software upgrade policy.

  1. Click on the Software Upgrade Policy tab, then click Create. The Software Upgrade Policy (Create) form opens.

  2. Configure the following parameters:

    • Policy ID

    • Auto-Assign ID

    • Name

    • Policy Type

    • CFlash Image Root Path

    You must choose SR Based Node as the Policy Type.

    The vCPAA does not require a CFlash Backup Root Path.

  3. Enable the Software Download parameter and click Apply. The Software Upgrade Policy (Create) form refreshes with additional tabs, and the form name changes to Software Upgrade Policy (Edit).


Assign the policy to the required vCPAAs.

  1. Click on the Software Upgrade Policy Assignment tab. The Software Upgrade Policy (Edit) Filter form opens.

  2. Configure a filter, if required, and click OK. A list of CPAAs is displayed in the Unassigned Sites panel.

  3. Select one or more vCPAAs in the Unassigned Sites list and click on the right-arrow button to move them to the Assigned Sites list.

  4. Click OK and confirm the action. The policy is assigned to the NEs, and the Software Upgrade Policy (Edit) form closes. The Software Upgrade form is displayed.


Perform the CPAA upgrade.

  1. On the Software Upgrade form, click on the Software Images tab.

  2. Select the new CPAA software image that you imported in Step 2 and click Upgrade Sites. The Select Sites form opens.

  3. Select one or more vCPAAs from the list and click OK, then confirm the action.

The NFM-P downloads the software to the selected CPAAs, in the directory TiMOS-B-Release number, where Release number is the version of the downloaded software.


Open a CLI session on each CPAA to perform the following:

  • Modify the NVRAM.DAT and bof.cfg files to point to the new files in TiMOS-B-Release number.

  • Reboot the upgraded vCPAAs

  • Verify that the upgrade was successful

See To upgrade the vCPAA software using a CLI .

End of steps

© 2022 Nokia. Nokia Confidential Information

Use subject to agreed restrictions on disclosure and use.