Cisco Cisco Packet Data Interworking Function (PDIF)
Software Management Operations
▀ Performing Dynamic Software Updates
▄ ASR 5000 System Administration Guide, StarOS Release 16
144
For example:
[local]asr5k# patch plugin p2p http://192.168.1.2/tmp/patch_libp2p-1.17.4343.tgz
certificate http://192.168.1.2/tmp/patch_libp2p-1.17.4343.cert
New patch for plugin p2p available for installation
certificate http://192.168.1.2/tmp/patch_libp2p-1.17.4343.cert
New patch for plugin p2p available for installation
The patch kit is copied to the /flash/patch/module-name directory on the system.
Unpacking the Patch Kit
The Exec mode install patch command unpacks a patch kit and validates its contents. This command does not actually
distribute the contents to the packet processing card /var/opt directories
distribute the contents to the packet processing card /var/opt directories
The command syntax is as follows:
install plugin plugin-name patch-file-name
For example:
[local]<host_name># install patch plugin p2p patch_libp2p-1.17.4343.tgz
Install patch file patch_libp2p-1.17.4343.tgz [Yes/No]?
Install module p2p version 1.17.4343 successful
Install patch file patch_libp2p-1.17.4343.tgz [Yes/No]?
Install module p2p version 1.17.4343 successful
When a new plugin module is installed, the patch file is checked against the certificate which is provided with the patch
file for authenticity of contents. If the certificate matches the patch file, the contents are extracted to the
/flash/install/<plugin-name>/contents directory.
file for authenticity of contents. If the certificate matches the patch file, the contents are extracted to the
/flash/install/<plugin-name>/contents directory.
Once the contents are extracted, the Plugin Manager looks for the file patch.bom which contains a list of files which are
considered a complete set for the patch. In addition, for each file listed, the.bom file contains an intended final
destination directory where the content file should reside at the end of the installation.
considered a complete set for the patch. In addition, for each file listed, the.bom file contains an intended final
destination directory where the content file should reside at the end of the installation.
For each file listed in the.bom file, the installation procedure copies the specified file to the destination directory. Once
this has completed, the installation procedure is finished. The primary SMC is responsible for ensuring that the /flash
partitions on the standby SMC are up-to-date.
this has completed, the installation procedure is finished. The primary SMC is responsible for ensuring that the /flash
partitions on the standby SMC are up-to-date.
Configuring the Plugin
The Global Configuration mode plugin command specifies a plugin to be configured and enters the Plugin
Configuration mode. The plugin name must match the name of a plugin which has been copied to and unpacked on the
system or an error message is displayed.
Configuration mode. The plugin name must match the name of a plugin which has been copied to and unpacked on the
system or an error message is displayed.
The command syntax is as follows:
plugin plugin-name
module priority number version module_version
For example:
[local]<host_name># configure
[local]<host_name>(config)# plugin p2p
[local]<host_name>(plugin-p2p)# module priority 1 version 1.17.4343
[local]<host_name>(config)# plugin p2p
[local]<host_name>(plugin-p2p)# module priority 1 version 1.17.4343