request system software add

Syntax

Syntax (TX Matrix Router)

Syntax (TX Matrix Plus Router)

Release Information

Command introduced before JUNOS Release 7.4.

best-effort-load and unlink options added in JUNOS Release 7.4.

sfc option introduced for the TX Matrix Plus router in JUNOS Release 9.6.

Description

Install a software package or bundle on the router.

Options

package-name — Location from which the software package or bundle is to be installed. For example:

• /var/tmp/package-name—For a software package or bundle that is being installed from a local directory on the router.
• protocol://hostname/pathname/package-name—For a software package or bundle that is to be downloaded and installed from a remote location. Replace protocol with one of the following:
  • ftp—File Transfer Protocol.
    Use ftp://hostname/pathname/package-name. To specify authentication credentials, use ftp://<username>:<password>@hostname/pathname/package-name. To have the system prompt you for the password, specify prompt in place of the password. If a password is required, and you do not specify the password or prompt, an error message is displayed.
  • http—Hypertext Transfer Protocol.
    Use http://hostname/pathname/package-name. To specify authentication credentials, use http://<username>:<password>@hostname/pathname/package-name. If a password is required and you omit it, you are prompted for it.
  • scp—Secure copy (available only for Canada and U.S. version).
    Use scp://hostname/pathname/package-name. To specify authentication credentials, use scp://<username>:<password>@hostname/pathname/package-name.

The pathname in the protocol is the relative path to the user's home directory on the remote system and not the root directory. On a J Series Services Router, when you install the software from a remote location, the package is removed at the earliest opportunity in order to make room for the installation to be completed. If you copy the software to a local directory on the router and then install the new package, use the unlink option to achieve the same effect and allow the installation to be completed.

best-effort-load — (Optional) Activate a partial load and treat parsing errors as warnings instead of errors.

delay-restart — (Optional) Install software package or bundle, but do not restart software processes.

force — (Optional) Force the addition of the software package or bundle (ignore warnings).

lcc number — (TX Matrix and TX Matrix Plus routers only) (Optional) In a routing matrix based on the TX Matrix router, install a software package or bundle on a T640 router (or line-card chassis) that is connected to the TX Matrix router. In a routing matrix based on the TX Matrix Plus router, install a software package or bundle on a T1600 router (or line-card chassis) that is connected to the TX Matrix Plus router. Replace number with a value from 0 through 3.

scc — (TX Matrix routers only) (Optional) Install a software package or bundle on a Routing Engine on a TX Matrix router (or switch-card chassis).

sfc number — (TX Matrix Plus routers only) (Optional) Install a software package or bundle on a Routing Engine on a TX Matrix Plus router (or switch-fabric chassis). Replace number with 0.

no-copy — (Optional) Install a software package or bundle, but do not save copies of package or bundle files.

no-validate — (Optional) When loading a software package or bundle with a different release, suppress the default behavior of the validate option.

re0 | re1 — (TX Matrix and TX Matrix Plus routers only) (Optional) Load a software package or bundle on a particular Routing Engine.

reboot — (Optional) After adding the software package or bundle, reboot the system.

unlink — (Optional) On J Series Services Routers, this option ensures that the software package is removed at the earliest opportunity in order to make room for the installation to be completed. On M Series and T Series routers, use the unlink option to remove the software package from this directory after a successful upgrade is completed.

validate — (Optional) Validate the software package or bundle against the current configuration as a prerequisite to adding the software package or bundle. This is the default behavior when the software package or bundle being added is a different release.

Additional Information

Before upgrading the software on the router, when you have a known stable system, issue the request system snapshot command to back up the software, including the configuration, to the /altroot and /altconfig file systems. After you have upgraded the software on the router and are satisfied that the new package or bundle is successfully installed and running, issue the request system snapshot command again to back up the new software to the /altroot and /altconfig file systems.

After you run the request system snapshot command, you cannot return to the previous version of the software, because the running and backup copies of the software are identical.

If you are upgrading more than one package at the same time, delete the operating system package, jkernel, last. Add the operating system package, jkernel, first and the routing software package, jroute, last. If you are upgrading all packages at once, delete and add them in the following order:

By default, when you issue the request system software add package-name command on a TX Matrix master Routing Engine, all the T640 master Routing Engines that are connected to it are upgraded to the same version of software. If you issue the same command on the TX Matrix backup Routing Engine, all the T640 backup Routing Engines that are connected to it are upgraded to the same version of software.

Likewise, when you issue the request system software add package-name command on a TX Matrix Plus master Routing Engine, all the T1600 master Routing Engines that are connected to it are upgraded to the same version of software. If you issue the same command on the TX Matrix Plus backup Routing Engine, all the T1600 backup Routing Engines that are connected to it are upgraded to the same version of software.

Required Privilege Level

maintenance

Related Topics

request system software delete
request system software rollback
request system storage cleanup

List of Sample Output

Output Fields

When you enter this command, you are provided feedback on the status of your request.

Sample Output

Checking compatibility with configuration
Initializing...
Using jbase-7.1R2.2
Using /var/tmp/jinstall-7.2R1.7-domestic-signed.tgz
Verified jinstall-7.2R1.7-domestic.tgz signed by PackageProduction_7_2_0
Using /var/validate/tmp/jinstall-signed/jinstall-7.2R1.7-domestic.tgz
Using /var/validate/tmp/jinstall/jbundle-7.2R1.7-domestic.tgz
Checking jbundle requirements on /
Using /var/validate/tmp/jbundle/jbase-7.2R1.7.tgz
Using /var/validate/tmp/jbundle/jkernel-7.2R1.7.tgz
Using /var/validate/tmp/jbundle/jcrypto-7.2R1.7.tgz
Using /var/validate/tmp/jbundle/jpfe-7.2R1.7.tgz
Using /var/validate/tmp/jbundle/jdocs-7.2R1.7.tgz
Using /var/validate/tmp/jbundle/jroute-7.2R1.7.tgz
Validating against /config/juniper.conf.gz
mgd: commit complete
Validation succeeded
Validating against /config/rescue.conf.gz
mgd: commit complete
Validation succeeded
Installing package '/var/tmp/jinstall-7.2R1.7-domestic-signed.tgz' ...
Verified jinstall-7.2R1.7-domestic.tgz signed by PackageProduction_7_2_0
Adding jinstall...

WARNING:     This package will load JUNOS 7.2R1.7 software.
WARNING:     It will save JUNOS configuration files, and SSH keys
WARNING:     (if configured), but erase all other files and information
WARNING:     stored on this machine.  It will attempt to preserve dumps
WARNING:     and log files, but this can not be guaranteed.  This is the
WARNING:     pre-installation stage and all the software is loaded when
WARNING:     you reboot the system.

Saving the config files ...
Installing the bootstrap installer ...

WARNING:     A REBOOT IS REQUIRED TO LOAD THIS SOFTWARE CORRECTLY. Use the
WARNING:     'request system reboot' command when software installation is
WARNING:     complete. To abort the installation, do not reboot your system,
WARNING:     instead use the 'request system software delete jinstall'
WARNING:     command as soon as this operation completes.

Saving package file in /var/sw/pkg/jinstall-7.2R1.7-domestic-signed.tgz ...
Saving state for rollback ...