To manage the Wavence running software

Purpose

Perform this procedure to manage the software in the Wavence committed and standby banks. You can upgrade or downgrade the running software release on a Wavence NE.

See “NE software upgrade overview” in the NSP NFM-P Classic Management User Guide for information about creating software upgrade policies and performing software upgrades.

CAUTION 

CAUTION

Service Disruption

To avoid a service outage:

A Wavence NE 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 to obtain information about firmware and software release compatibility.

CAUTION 

CAUTION

Service Disruption

Perform this procedure only in a maintenance window:

When you reboot a Wavence SA that is in service, it is service-affecting. Ensure that the reboot activity occurs during a maintenance window.

Note: During a software upgrade, the NE audit function is not supported for Wavence NEs.

Steps
 
1 

In the navigation tree Equipment view, right-click on a Wavence shelf and choose Properties. The Shelf (Edit) form opens.

2 

Click on the Software Bank Details tab. The committed and standby software information is displayed. The committed software is the software currently running on the NE. The standby software is new software uploaded to the NE, or formerly committed software.

3 

Verify that the operational state of the standby software is Enabled by examining the Operational State value.

You can also examine the Software Version of the standby and committed software. If the software version of the standby software is more recent than the committed software version, the NE can be upgraded. If the standby software version is older than the committed software version, the NE can be downgraded.

4 

Select the standby entry and click Properties. The MPR Software Package (Edit) form opens.

5 

Configure the Activation parameter and click OK. The Shelf (Edit) form reappears.

6 

Save your changes and close the form. When the standby and committed software versions are different or the forced activation option is selected, the NE reboots using the standby software. If the standby and committed software versions are the same and the activation option is chosen, the NE does not reboot and the Shelf (Edit) form closes.

Note: For nodes with a radio LAG configured, the Activation parameter may take some time to update due to the node enabling all of the associated peripherals.

The Activation Status parameter displays Activated for the committed software package, Not Applicable for the standby software package, and In Progress for a package undergoing activation.

7 

After the NE reboots, you can confirm that the NE is running the software stored in the former standby bank. The former standby software is the committed software and the previous committed software is the standby software.

End of steps