System Setup and Software Installation Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.0.x
Bias-Free Language
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.
Figure 1. Flow for
Installation (base software, RPMs and SMUs)
Until this release, you download 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 . Then, you manually identified 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 commands to identify and install dependent RPMs automatically.
The new commands are
and install upgrade. The
command identifies and updates dependent packages. The command does not update the base package. The install upgrade command upgrades the base package.
Note
Cisco IOS XR Version 6.0.2 and later does not provide 3rd-party and host package SMUs as part of automatic dependency management
(
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
SMUs
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
command. When the
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
command is:
repository[rpm]
Four scenarios in which you can use the
command are:
When a package name is not specified
When no package is specified, the command updates the latest SMUs of all installed packages.
[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
are skipped.)
[repository] ncs5k-mcast.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.
[repository] ncs5k-mcast-1.0.0.1-r611.x86_64.rpm
When an SMU is specified
If an SMU is specified, that SMU is downloaded and installed, along with its dependent SMUs.
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.
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 install upgrade 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.
install upgrade source[repository] version <release-number>
The version number for an RPM
is specified
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
specified.
install upgrade source[repository] version <release-number> ncs5k-mcast-1.0.0.0-<release-number>.x86_64.rpm
Downgrade an
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 command is: install activate[rpm]force
For example, to add and activate an RPM of a lower version, use the following steps.
Feedback