Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

request system software nonstop-upgrade

 

Syntax

Release Information

Command introduced in Junos OS Release 10.4 for EX Series switches.

Option set [package-name package-name] added in Junos OS Release 12.1 for EX Series switches.

Command introduced in Junos OS Release 13.2X50-D20 for the QFX Series.

Command introduced in Junos OS Release 15.1X53-D55 for EX3400 switches.

Command introduced in Junos OS Release 19.3R1 for EX4650 and QFX5120 switches.

Description

Perform a nonstop software upgrade (NSSU) on a switch with redundant Routing Engines or on a Virtual Chassis or Virtual Chassis Fabric (VCF). The behavior of this command depends on the type of switch, Virtual Chassis, or VCF where you run it, as follows:

  • When you run this command on any of the following Virtual Chassis or VCF configurations, NSSU upgrades all members of the Virtual Chassis:

    • EX3300, EX3400, EX4200, EX4300, EX4500, EX4550, EX4600. or EX4650 Virtual Chassis

    • Mixed Virtual Chassis composed of any combination of EX4200, EX4500, and EX4550 switches, or EX4300 and EX4600 switches

    • QFX3500 and QFX3600 Virtual Chassis

    • QFX5100 Virtual Chassis

    • QFX5120-48Y Virtual Chassis

    • Fixed configuration of switches in a VCF (QFX3500/QFX3600 and QFX5100 switches)

    • Mixed VCF composed of any combination of QFX3500/QFX3600, QFX5100, and EX4300 switches

    The original Virtual Chassis or VCF backup becomes the master. The new master automatically upgrades and reboots the original master, which then rejoins the Virtual Chassis or VCF as the backup.

  • When you run this command on an EX6200 or EX8200 switch, NSSU upgrades both the backup and master Routing Engines. The original backup Routing Engine becomes the new master at the end of the upgrade.

    • On an EX6200 switch, NSSU automatically reboots the original master Routing Engine.

    • On an EX8200 switch, NSSU does not automatically reboot the original master Routing Engine unless you specify the reboot option.

  • When you run this command on an EX8200 Virtual Chassis, NSSU upgrades all master and backup Routing Engines in the Virtual Chassis, including the external Routing Engines. The original backup Routing Engines become the new master Routing Engines. NSSU does not automatically reboot the original master Routing Engines unless you specify the reboot option.

This command has the following requirements:

  • All Virtual Chassis members, VCF members, and all Routing Engines must be running the same Junos OS release.

  • Graceful Routing Engine switchover (GRES) must be enabled.

  • Nonstop active routing (NSR) must be enabled.

    Note

    Although not required, we recommend you enable nonstop bridging (NSB). NSB ensures that all NSB-supported Layer 2 protocols operate seamlessly during the Routing Engine switchover during NSSU. See Configuring Nonstop Bridging on EX Series Switches (CLI Procedure).

  • You must run the command from the master Routing Engine on a standalone switch or from the master on a Virtual Chassis.

  • For minimal traffic disruption, you must define link aggregation groups (LAGs) such that the member links reside on:

    • Different Virtual Chassis members for EX3300, EX3400, EX4200, EX4300, EX4500, EX4550, EX4600, EX4650, QFX3500, QFX3600, QFX5100, and QFX5120 Virtual Chassis, mixed Virtual Chassis, or VCF.

    • Different line cards for EX6200 and EX8200 switches and EX8200 Virtual Chassis.

  • For EX3300, EX3400, EX4200, EX4300, EX4500, EX4550, EX4600, EX4650, QFX3500 QFX3600, QFX5100, and QFX5120 Virtual Chassis, and mixed Virtual Chassis:

    • The Virtual Chassis members must be connected in a ring topology. A ring topology prevents the Virtual Chassis from splitting during an NSSU.

    • The Virtual Chassis master and backup must be adjacent to each other in the ring topology. With adjacent placement, the master and backup are always in sync while the switches in line-card roles are rebooting.

    • The Virtual Chassis must be preprovisioned so the line-card role is explicitly assigned to member switches acting in a line-card role. During an NSSU, the master and backup member switches must maintain their Routing Engine roles (although mastership switches to the backup), and the remaining switches must maintain their line-card roles.

    • You must configure no-split-detection in a two-member Virtual Chassis so the Virtual Chassis doesn’t split during NSSU.

  • For Virtual Chassis Fabric:

    • You can only have two members preprovisioned in the Routing Engine role. If more than two Routing Engines are configured, NSSU issues a warning message and the NSSU process stops.

    • The VCF members should be connected in a spine and leaf topology. A spine and leaf topology prevents the VCF from splitting during NSSU. Each leaf device must be connected to both spine devices.

    • The VCF must be preprovisioned so that the line-card role has been explicitly assigned to member switches acting in a line-card role, and likewise the Routing Engine role has been explicitly assigned to the member switches acting in a Routing Engine role. During an NSSU, the master and backup member switches must maintain their Routing Engine roles (although mastership switches to the backup), and the remaining switches must maintain their line-card roles.

    • You must configure no-split-detection in a two-member VCF so the VCF does not split during NSSU.

Options

package-nameLocation of the software package or bundle to be installed. For example:
  • /var/tmp/package-name—For a software package or bundle installed from a local directory on the switch.

  • protocol://hostname/pathname/package-name—For a software package or bundle 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.

      The command displays an error message If a password is required and you do not specify the password or prompt.

    • http—Hypertext Transfer Protocol.

      Use http://hostname/pathname/package-name.

      To specify authentication credentials, use http://<username>:<password>@hostname/pathname/package-name.

      The command prompts you for a password if one is required and you didn’t include 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.

Note

The pathname in the protocol is the relative path to the user home directory on the remote system and not the root directory.

set [package-name package-name](Mixed Virtual Chassis only) Locations of the different installation packages required by the different types of member switches. These packages must be for the same Junos OS release. See this command’s package-name option for information about how to specify the installation packages.
force-host(Optional) Force adding the host software package or bundle (and ignore warnings) on EX4650, QFX5100, or QFX5120 devices.
no-copy(Optional) Install a software package or bundle, but do not save copies of the package or bundle files.
no-old-master-upgrade(Optional) (EX8200 switches only) Upgrade the backup Routing Engine only. After the upgrade completes, the original master Routing Engine becomes the backup Routing Engine and continues running the previous software version.
reboot(Optional) (EX8200 switches and EX8200 Virtual Chassis only) When you include the reboot option, NSSU automatically reboots the original master (new backup) Routing Engine after being upgraded to the new software. When you omit the reboot option, you must manually reboot the original master (new backup) Routing Engine using the request system reboot command.
Note

If you do not use the reboot option on an EX8200 Virtual Chassis, you must establish a connection to the console port on the Switch Fabric and Routing Engine (SRE) module or Routing Engine (RE) module to manually reboot the backup Routing Engines.

unlink(Optional) Remove the software package after a successful upgrade.

Required Privilege Level

maintenance

List of Sample Output

request system software nonstop-upgrade (EX4200 Virtual Chassis)

request system software nonstop-upgrade (EX6200 Switch)

request system software nonstop-upgrade reboot (EX8200 Switch)

request system software nonstop-upgrade no-old-master-upgrade (EX8200 Switch)

request system software nonstop-upgrade reboot (EX8200 Virtual Chassis)

Output Fields

This command reports feedback on the status of the request. Some functions are shared between NSSU and the in-service software upgrade (ISSU) feature, so you might see what appear to be ISSU messages as well as NSSU messages in the output from this command.

Sample Output

request system software nonstop-upgrade (EX4200 Virtual Chassis)

request system software nonstop-upgrade (EX6200 Switch)

request system software nonstop-upgrade reboot (EX8200 Switch)

request system software nonstop-upgrade no-old-master-upgrade (EX8200 Switch)

request system software nonstop-upgrade reboot (EX8200 Virtual Chassis)