request system software add (Junos OS Evolved)

Syntax

Description

Install a software package on all Routing Engines 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.

After you add a new software image, you must reboot the system to run the new software. If you have added the software image but have not yet rebooted, you can issue the request system software delete package-name command to remove the newly added package and cancel the installation.

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.

You can use the request system software add restart command to perform a unified in-service software upgrade (ISSU), which upgrades to a more recent version of Junos OS Evolved with minimal disruption of the control plane and data plane traffic.

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/tmpThen 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-confirm	(Optional) Starting from Junos OS Evolved Release 22.4R3, you can use this option to suppress the prompt that asks you to enter `yes` or `no` before starting a unified ISSU. The upgrade will start without confirmation, but if there is any error that can impact traffic, then the upgrade is automatically cancelled.
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. Starting in Junos OS Evolved 23.4R1, when using the `reboot` option, the Layer 2 applications `l2ald`, `l2ald-agent`, `l2cpd`, and `l2cpd-agent` are initialized and started only if any of the following configuration hierarchy levels contain any configuration statements: `[edit interface interface-name unit number family ethernet-switching]` `[edit vlans]` `[edit routing-instance instance-name instance-type virtual-switch]` `[edit routing-instance instance-name instance-type mac-vrf]` `[edit protocols l2-learning]` Additionally, `l2cpd`, and `l2cpd-agent` are initialized and started if the `[edit protocols lldp]` hierarchy level contains any configuration statements. As a result of this change, if your configuration already contains these configuration statements and you then delete all of the above configuration statements, these Layer 2 applications stop running.
restart	(Optional) Starting from Junos OS Evolved Release 22.1R1, you can use this option to perform a unified ISSU. For more details, see request system software add restart, Note: This is applicable only for QFX5220-CD switches.
validate	(Default) When loading a software package or bundle with a different release, validate the candidate software against the current configuration of the node.

Back Up the Software First

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.

Migrate to GPT Disk Partitioning

Starting in Junos OS Evolved Release 24.2R1, we support migrating to GUID Partition Table (GPT) disk partitioning. GPT is the native disk partitioning scheme used by UEFI BIOSes. GPT is similar to the Master Boot Record (MBR) disk partitioning scheme used by traditional BIOSes. All Junos OS Evolved platforms support GPT natively. However, we default to MBR disk partitioning because Junos OS Evolved was originally ported to systems that used traditional BIOSes.

When you use this command to install a release that supports GPT disk partitioning, you can:

For new installations, change the default partition scheme for both the primary and secondary disks to GPT immediately (for example, scratch installations to empty disks).
For existing installations, migrate to GPT disk partitioning for both the primary and secondary disks after a reboot of the system.

For more details about this feature, see Migrate to GPT Disk Partitioning.

Unsupported Configurations

Starting in Junos OS Evolved Release 23.4R1, the system accepts unsupported configurations silently, and ignores unsupported configurations during commit. Downgrading to a Junos OS Evolved release prior to 23.2R1 will fail if an unsupported configuration is present on the device. Remove any unsupported configurations to downgrade successfully.

YANG Data Models

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.

Required Privilege Level

maintenance

Output Fields

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

Sample Output