supports automatic dependency management. While the user is updating an RPM,
the system automatically identifies all relevant dependent packages and updates
Until this release,
users downloaded the software image and required RPMs from CCO on a network
server (the repository). They used the
activate commands to add and activate the downloaded files on the
. Then, users needed to manually identify relevant
dependent RPMs, to add and activate them.
dependency management, users need not identify dependent RPMs to individually
add and activate them. They can execute new install commands to identify and
install dependent RPMs automatically.
The new commands are
upgrade . The
command identifies and updates dependent packages. The command does not update
the base package. The
command upgrades the base package.
Cisco IOS XR Version 6.0.2 and later does not provide 3rd-party and host package SMUs as part of automatic dependency management
(install update and install upgrade commands). The 3rd party and host package SMUs must be installed separately, and in isolation from other installation procedures
(installation of SMUs and RPMs in IOS XR or admin containers).
Cisco IOS XR Version 6.0.2 and later does not support asynchronous package upgrades.
The rest of this
chapter contains these sections:
Update RPMs and
An RPM may contain a fix for a specific defect, and you may need to update the system with that fix. To update RPMs and SMUs
to a newer version, use the install update command. When the install update command is issued for a particular RPM, the router communicates with the repository, and downloads and activates that RPM.
If the repository contains a dependent RPM, the router identifies that dependent RPM and installs that too.
The syntax of the
install update source
Four scenarios in
which you can use the
When a package name is not
When no package is
specified, the command updates the latest SMUs of all installed packages.
install update source [repository]
When a package name is
If the package
name is specified, the command installs that package, updates the latest SMUs
of that package, along with its dependencies. If the package is already
installed, only the SMUs of that package are installed. (SMUs that are already
installed are skipped.)
You may choose to upgrade to a newer version of the base software when it becomes available. To upgrade to the latest base
software version, use the install upgrade command. With the upgrade of the base version, RPMs that are currently available on the router are also upgraded.
SMUs are not upgraded as part of this process.
The syntax of the
upgrade command is:
install upgrade source repository version version [rpm]
VRF and TPA on dataport is not supported. If the server is reachable only through non-default VRF interface, the file must
already be retrieved using ftp, sfp, scp, http or https protocols.
You can use the
upgrade command when:
The version number is
The base software
(.mini) is upgraded to the specified version; all installed RPMs are upgraded
to the same release version.
install upgrade source [repository] version 6.2.2
The version number for an RPM
When performing a
system upgrade, the user can choose to have an optional RPM to be of a
different release (from that of the base software version); that RPM can be
install upgrade source [repository] version 6.2.2 ncs5k-mcast-184.108.40.206-r623.x86_64.rpm
After an RPM is activated, you may need to downgrade it by activating an RPM of a lower version. Use the force option with the install activate command to activate an RPM of a lower version.
The syntax of the
install activate [rpm] force
For example, to add and activate an RPM of a lower version, use the following steps.