Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

request system software in-service-upgrade

Syntax

Syntax

Syntax (QFX Series)

Description

Perform a unified in-service software upgrade (ISSU). A unified ISSU enables you to upgrade from one Junos OS release to another with no disruption on the control plane and with minimal disruption of traffic.

On QFX5100 and QFX5200 switches, enable nonstop active routing (NSR) and nonstop bridging (NSB).

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

    • http—Hypertext Transfer Protocol

    • scp—Secure copy (available only for Canada and U.S. version)
no-old-master-upgrade

(Optional) When the no-old-master-upgrade option is included, after the backup Routing Engine is rebooted with the new software package and a switchover occurs to make it the new primary Routing Engine, the former primary (new backup) Routing Engine will not be upgraded to the new software. In this case, you must manually upgrade the former primary (new backup) Routing Engine. If you do not include the no-old-master-upgrade option, the system will automatically upgrade the former primary Routing Engine.

Note:

This option is not available on QFX5100 and QFX5200 switches.
reboot

(Optional) When the reboot option is included, the former primary (new backup) Routing Engine is automatically rebooted after being upgraded to the new software. When the reboot option is not included, you must manually reboot the former primary (new backup) Routing Engine using the request system reboot command.

Note:

This option is not available on the QFX Series switches.
status

(Optional) Starting in Junos OS Release 19.4R1, use this option to display the status of a unified ISSU during the upgrade. You will need to run this command on the Routing Engine where the ISSU was triggered to display the correct ISSU log file.

Note:

This option is only available on MX240, MX480, MX960, MX2010, MX2020, PTX3000, and PTX5000 routers.
enhanced-mode

(Optional) Starting in Junos OS Release 20.1R1, runs unified ISSU in enhanced mode, a mode of ISSU that eliminates packet loss during the unified ISSU process.

Note:

This option is only available on MPC8E, and MPC9E line cards. Support for MPC11E line cards is provided from Junos OS Release 21.4R1 onwards.
no-validate

(Optional) Starting in Junos OS Release 20.4R2, skip the validation step of the unified ISSU process.
handle-incompatible-config

(Optional) Starting in Junos OS Release 22.1R1, automatically deactivate the incompatible configurations at the start of an ISSU and reactivate them once the ISSU is completed. If the ISSU is aborted, the deactivated configurations are automatically reactivated. This is currently applicable only to clock synchronization configurations for Precision Time Protocol (PTP) and Synchronous Ethernet.

Note:

This option is available only for the MX960, MX10003, MX10008, MX10016, MX2010, and MX2020 routers.

Additional Information

The following conditions apply to unified ISSUs:

  • Unified ISSU is not supported on every platform. For a list of supported platforms, see Unified ISSU System Requirements.

  • Unsupported PICs are restarted during a unified ISSU on certain routing devices. For information about supported PICs, see the Junos OS High Availability User Guide.

  • Unsupported protocols will experience packet loss during a unified ISSU. For information about supported protocols, see the Junos OS High Availability User Guide.

  • During a unified ISSU, you cannot bring any PICs online or offline on certain routing devices.

  • The no-validate option is required when upgrading to Junos OS Releases 21.2R1 or 22.1R1. If you are upgrading from a release prior to Junos OS Release 20.4R2, then you will need to upgrade to a release that supports the no-validate option before using unified ISSU to upgrade to Junos OS Releases 21.2R1 or 22.1R1.

For more information, see the Junos OS High Availability User Guide.

Required Privilege Level

view

Output Fields

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

Sample Output

request system software in-service-upgrade reboot

request system software in-service-upgrade reboot (TX Matrix Plus Router)

request system software in-service-upgrade (QFX5100 Switch)

request system software in-service-upgrade status

request system software in-service-upgrade enhanced-mode

Release Information

Command introduced in Junos OS Release 9.0.

status option introduced in Junos OS Release 19.4R1 for MX240, MX480, MX960, MX2010, MX2020, PTX3000, and PTX5000 routers.

handle-incompatible-config option introduced in Junos OS Release 22.1R1 for MX960, MX10003, MX10008, MX10016, MX2010, and MX2020 routers.

Related Documentation