Cisco Cisco Packet Data Gateway (PDG)
Software Management Operations
Performing Dynamic Software Updates ▀
ASR 5000 System Administration Guide, StarOS Release 16 ▄
143
Performing Dynamic Software Updates
This section describes the dynamic software update (DSU) process that can be used to incrementally update plugins
without having to update StarOS and reload the system.
without having to update StarOS and reload the system.
Overview
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.
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.).
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.
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.
A plugin module is a specific instance of a plugin version consisting of at least one file that can be added to a running,
in-service system. The module contains the information or instructions for a specific component's incremental update.
Typically this would be a single file.
in-service system. The module contains the information or instructions for a specific component's incremental update.
Typically this would be a single file.
The Version Priority List (VPL) is a linked list of module versions associated with a specific plugin. Each plugin has
one VPL. The list is sorted in ascending order by the priority number that is assigned by the administrator. When
updating, the lowest priority number is tried first. If that version is not successful, the version in the VPL with the next
sequentially greater priority number is tried. This list is iterated until a successful version is found. The VPL also
supports manual rollback to a previous version (higher priority number) via a CLI command.
one VPL. The list is sorted in ascending order by the priority number that is assigned by the administrator. When
updating, the lowest priority number is tried first. If that version is not successful, the version in the VPL with the next
sequentially greater priority number is tried. This list is iterated until a successful version is found. The VPL also
supports manual rollback to a previous version (higher priority number) via a CLI command.
The basic sequence for the dynamic software process is as follows:
Downloading the Patch Kit
The Exec mode patch plugin command copies a patch intended for a specific plugin onto the running system.
The plugin kit includes a compressed plugin file (.tgz extension) and a certificate file (.cert extension). The command
syntax is as follows:
syntax is as follows:
patch plugin name [ http | ftp | sftp ]://host/directory/file certificate [ http
| ftp | sftp ]://host/directory/file
| ftp | sftp ]://host/directory/file