Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

request system software in-service-upgrade (Maintenance)

Syntax

Description

The in-service software upgrade (ISSU) feature allows a chassis cluster pair to be upgraded from supported Junos OS versions with a traffic impact similar to that of redundancy group failovers. Before upgrading, you must perform failovers so that all redundancy groups are active on only one device. We recommend that graceful restart for routing protocols be enabled before you initiate an ISSU.

For SRX300, SRX320, SRX340, SRX345, SRX550M, and SRX380 devices, you must use the no-sync parameter to perform an in-band cluster upgrade (ICU). This allows a chassis cluster pair to be upgraded with a minimal service disruption of approximately 30 seconds.

For SRX1500, SRX4100, and SRX4200 devices, the no-sync parameter is not supported when using ISSU to upgrade. The no-sync option specifies that the state is not synchronized from the primary node to the secondary node.

For SRX1500 devices, the no-tcp-syn-check parameter is not supported when using ISSU to upgrade.

Options

  • image_name—Specify the location and name of the software upgrade package to be installed.

  • no-copy—(Optional) Install the software upgrade package but do not save the copies of package files.

  • no-old-master-upgrade—(Optional) Do not upgrade the old primary after switchover.

    This parameter applies to SRX5400, SRX5600, and SRX5800 devices only.

  • no-sync—(Optional) Stop the flow state from synchronizing when the old secondary node has booted with a new Junos OS image.

    This parameter applies to SRX300, SRX320, SRX340, SRX345, SRX550M, and SRX380 devices only. It is required for an ICU.

  • no-tcp-syn-check—(Optional) Create a window wherein the TCP SYN check for the incoming packets is disabled. The default value for the window is 7200 seconds (2 hours).

    This parameter applies to SRX300, SRX320, SRX340, SRX345, SRX550M and SRX380 devices only.

  • no-validate—(Optional) Disable the configuration validation step at installation. The system behavior is similar to that of the request system software add command.

    This parameter applies to SRX300, SRX320, SRX340, SRX345, SRX550M and SRX380 devices only.

  • status—(Optional) 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.

    This parameter applies to SRX1500, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, and SRX5800 devices only.

  • unlink—(Optional) Remove the software package after successful installation.

Required Privilege Level

maintenance

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 status (SRX1500, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, and SRX5800)

Sample Output

request system software in-service-upgrade (SRX300, SRX320, SRX340, SRX345, SRX550M, and SRX380 Devices)

Release Information

For SRX5400, SRX5600, and SRX5800 devices, command introduced in Junos OS Release 9.6. For SRX5400 devices, the command is introduced in Junos OS Release 12.1X46-D20. For SRX300, SRX320, SRX340, and SRX345 devices, command introduced in Junos OS Release 15.1X49-D40. For SRX1500 devices, command introduced in Junos OS Release 15.1X49-D50. For SRX380 devices, command introduced in Junos OS Release 20.1R1.

Starting with Junos OS Release 15.1X49-D80, SRX4100 and SRX4200 devices support ISSU.

Starting with Junos OS Release 17.4R1, SRX4600 devices support ISSU.

SRX300 Series devices, SRX550M devices and vSRX do not support ISSU.

For SRX1500, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, and SRX5800, the status option is introduced in Junos OS Release 20.4R1.