Manage Automatic Dependency

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 install update and install upgrade . The install update command identifies and updates dependent packages. The command does not update the base package. The install upgrade command upgrades the base package.

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 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 command is:

install update source repository [rpm]

Four scenarios in which you can use the install update 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 update 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 are skipped.)

  • 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.

  • When an SMU is specified

    If an SMU is specified, that SMU is downloaded and installed, along with its dependent SMUs.

Upgrade Base Software Version

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.


Note

SMUs are not upgraded as part of this process.

The syntax of the install upgrade command is:

install upgrade source repository version version[rpm]


Note

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>