Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

request system software add (Junos OS Evolved)

Syntax

Description

Install a software package on all REs in a cluster, as seen in the output of the show system nodes operational mode command. The default option is validate. We recommend that you always download the software image to /var/tmp only. For another way to validate the configuration before trying to install the software package (rather than at the same time), see request system software validate (Junos OS Evolved).

For Junos OS Evolved, the request system software add command has a built-in feature to not start the upgrade if a reboot is pending after an upgrade or rollback.

Any configuration changes you perform after inputting the request system software add command are lost when the system reboots with an upgraded version of Junos OS Evolved.

Note:

Software packages from unidentified providers cannot be loaded. To authorize providers, include the provider-id statement at the [edit system extensions provider] hierarchy level.

For information on the valid filename and URL formats, see Format for Specifying Filenames and URLs in Junos OS CLI Commands.

Options

package-name

Location from which the software package or bundle is to be installed. Junos OS Evolved does not support a remote .iso file for upgrade, so specify the pathname of a package to be installed from a local directory on the router or switch (for example, /var/tmp/package-name).

Use the file copy command to copy the software package or bundle from the remote location to the /var/tmp directory on the hard disk:

file copy scp://package-name /var/tmp

Then install the software package or bundle using the request system software add command:

request system software add /var/tmp/package-name

force

(Optional) Force the addition of the software package or bundle (ignore warnings). The force option automatically removes software versions until there is enough space for the new software install.

For Junos OS Evolved, if you are trying to reinstall an already installed application, use the force option. The force option will cause the program to remove the existing application before reinstalling it.

no-validate

(Optional) When loading a software package or bundle with a different release, suppress the default behavior of the validate option and skip the validation of the configuration. A subsequent reboot can cause the system to lose its configuration if the configuration is not compatible with the new software package. The no-validate option should only be used if you have previously issued the request system software validate operational mode command on the same target version and target configuration.

reboot

(Optional) After installing the software package, reboot the system.

The reboot command is not needed to install third-party applications on devices running Junos OS Evolved.

restart

(Optional) This option allows you to upgrade the system using an application-level restart without requiring a reboot when possible. First, the system determines how many applications need to restart (start with a new version), and then, after sending output to the CLI session, the system restarts those applications. Restarted applications re-synchronize their state from the system. You can use the request system software validate command before using the request system software add restart command to determine if you can upgrade to the new image by application restart or if the system requires a reboot.

validate (Default) When loading a software package or bundle with a different release, validate the candidate software against the current configuration of the node.

Additional Information

Before you upgrade the software on the router or replace one of the Routing Engines, when you have a known stable system, issue the request system snapshot command to back up the software, including the configuration, to the /soft directory. After you have upgraded the software or have replaced one of the Routing Engines, and are satisfied that the software packages are successfully installed and running, issue the request system snapshot command again to back up the software to the /soft directory.

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.

Before installing software on a device that has one or more custom YANG data models added to it, back up and remove the configuration data corresponding to the custom YANG data models from the active configuration. For more information see Managing YANG Packages and Configurations During a Software Upgrade or Downgrade.

Required Privilege Level

maintenance

Output Fields

When you enter this command, the system provides feedback on the status of your request.

Sample Output

request system software add restart (Junos OS Evolved for Fixed-Form Platforms)

request system software add restart (Junos OS Evolved for Fixed-Form Platforms)

request system software add restart (Junos OS Evolved for Fixed-Form Platforms)

request system software add restart (Junos OS Evolved for Chassis-based Platforms)

request system software add restart (Junos OS Evolved for Chassis-based Platforms)

request system software add

request system software add restart (Junos OS Evolved with Support for Hotfix and JSU Upgrade)

Release Information

The following options are deprecated in Junos OS Evolved Release 18.3R1: best-effort-load, delay-restart, no-copy, on-primary, (re0 | re1), set, unlink, validate, validate-on-host, and validate-on-routing-engine.