System Setup and Software Installation Guide for Cisco ASR 9000 Series Routers, IOS XR Release 6.5.x
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Flexible packaging supports automatic dependency management. While you update an RPM, the system automatically identifies
all relevant dependent packages and updates them.
Until this release, you downloaded the software image and required RPMs from CCO on a network server (the repository), and
used the install add and the install activate commands to add and activate the downloaded files on the router. Then, you manually identify relevant dependent RPMs, to add and activate them.
With automatic dependency management, you need not identify dependent RPMs to individually add and activate them. You can
execute new install command to identify and install dependent RPMs automatically.
The command install source adds and activates packages. The command install replace adds and activates packages in a given golden ISO (GISO).
Cisco IOS XR Version 6.1.1 does not provide third party SMUs as part of automatic dependency management (install source command). The third party SMUs must be installed separately, and in isolation from other installation procedures (installation
of SMUs and RPMs in IOS XR or admin containers).
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 source command. When this 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
The syntax of the install source command is:
Four scenarios in which you can use the install source command are:
When a package name is not specified
When no package is specified, the command updates the latest SMUs of all installed packages.
install source [repository]
When a package name is specified
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
install source [repository] asr9k-mpls.rpm
When a package name and version number are specified
If a particular version of package needs to be installed, the complete package name must be specified; that package is installed
along with the latest SMUs of that package present in the repository.
You can upgrade to a newer version of the base software when it becomes available. To upgrade to the latest base software
version, use the
install source 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
install source command is:
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.
Default routes (0.0.0.0/0) cannot be copied onto Linux due to TPA implementation.
You can use the
install source command when:
The version number is specified
The base software (.mini) is upgraded to the specified version; all installed RPMs are upgraded to the same release version.
For example, if RPM
is the RPM installed, then is its base RPM.
Commit the configuration.
The downgrade for third-party RPMs is similar to the hostos RPMs. To downgrade a SMU, activate the lower version of the SMU.
If only one version of SMU is present, the base RPM of the SMU must be activated.
Hostos and third-party RPMs cannot be deactivated. Only activation of different versions is supported.
Downgrade Non-Hostos RPM
Deactivate the RPM to downgrade to earlier version of RPM.