Verify The Running Software Version; Restoring The Previous Software Image; Upgrading Icsr Chassis; Performing Dynamic Software Updates - Cisco ASR 5000 Administration Manual

Software Management Operations
After the system reboots, establish a CLI session and enter the show version command to verify that the active
software version is correct.
Optional for PDSN: If you are using the IP Pool Sharing Protocol during your upgrade, refer to Configuring
IPSP Before the Software Upgrade in the PDSN Administration Guide.

Verify the Running Software Version

After the system has successfully booted, verify that the new StarOS version is running by executing the Exec
mode show version command.
[local]
You can run the Exec mode show build command to display additional information about the running StarOS
build release.

Restoring the Previous Software Image

If for some reason you need to undo the upgrade, perform the upgrade again except:
• Specify the locations of the upgrade software image and configuration files. Then
• Specify the locations of the original software image and configuration files.

Upgrading ICSR Chassis

The procedure for upgrading primary and backup ICSR chassis is described in the Interchassis Session
Recovery chapter. Essentially the procedure requires upgrading the primary and standby chassis using the
off-line method while each is in standby mode.

Performing Dynamic Software Updates

StarOS allows the runtime loading of plugins. All StarOS builds include a "default" baseline plugin.
This feature is currently used to dynamically update the detection logic used to filter P2P applications via the
Application Detection and Control (ADC) feature.
Patching is the process used to install a plugin as an incremental update to a StarOS release. One plugin can
be provided to multiple, compatible, concurrent product releases. A plugin is distributed in the form of a
compressed distribution kit via the internet or by other means (USB stick, CD, etc.).
A plugin is a functional software entity that provides incremental updates to a pre-existing StarOS software
component. Plugins have the characteristic of being dynamically loadable at runtime and do not require a
system restart. A plugin has a name and one or more versions. All plugin names are known to the system at
product release.
For complete information on the Dynamic Software Update process, refer to the ADC Administration Guide.
host_name
show version
#
Verify the Running Software Version
ASR 5000 System Administration Guide, StarOS Release 21.1
143