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 (MX Series 5G Universal Routing Platforms and EX9200 Switches)

Syntax

Description

Perform a unified in-service software upgrade (unified ISSU). 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. Unified ISSU is supported only by dual Routing Engine platforms. In addition, graceful Routing Engine switchover (GRES) and nonstop active routing (NSR) must be enabled.

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-copy

(Optional) When the no-copy option is included, copies of package files are not saved on the Packet Forwarding Engine.

The no-copy option is not available for an MX Series Virtual Chassis or an EX9200 Virtual Chassis.
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 is not 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 automatically upgrades the former primary Routing Engine.

The no-old-master-upgrade option is not available for an MX Series Virtual Chassis or an EX9200 Virtual Chassis.
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.

The reboot option is accepted but ignored for an MX Series Virtual Chassis or an EX9200 Virtual Chassis. A unified ISSU in an MX Series Virtual Chassis or EX9200 Virtual Chassis always reboots all Routing Engines in the member routers or switches.
unlink

(Optional) When the unlink option is included, the package is removed from /var/home whether the installation is successful or unsuccessful.

The unlink option is not available for an MX Series Virtual Chassis or an EX9200 Virtual Chassis.

Additional Information

The following conditions apply to unified ISSUs:

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 about the status of your request.

Sample Output

request system software in-service-upgrade reboot

request system software in-service-upgrade (MX Series Virtual Chassis)

Release Information

Command introduced in Junos OS Release 11.2.

Related Documentation