request system software in-service-upgrade

Syntax

request system software in-service-upgrade image_name <no-old-master-upgrade>

Release Information

Command introduced in Release 9.6 of Junos OS.

Description

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

Options

image_name—This is the location and name of the software upgrade package to be installed.

no-old-master-upgrade—(optional) This switch leaves the current master device in a nonupgraded state, which is a precaution against service failure. This option allows routing control to be quickly returned to the old master device if the newly upgraded device does not operate correctly.

Use of the no-old-master-upgrade option will require you to run a standard upgrade on the old master device after the ISSU is completed on the backup device.

Note: We recommend that in running this command, you include reboot at the end of the command sequence. If reboot is not included in the command, you will need to manually reboot each device as the ISSU completes updating the software image.

Required Privilege Level

maintenance

List of Sample Output

request system software in-service-upgrade reboot

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

user@host> request
system software in-service-upgrade /var/tmp/junos-srx3000–9.6R1.13-domestic.tgz
reboot

Chassis ISSU Started
node0:
--------------------------------------------------------------------------
Chassis ISSU Started
ISSU: Validating Image
Initiating in-service-upgrade

node0:
--------------------------------------------------------------------------
Initiating in-service-upgrade
Checking compatibility with configuration
Initializing...
Using /var/tmp/junos-srx3000-9.6R1.13-domestic.tgz
Checking junos requirements on /
Available space: 229192 require: 4102
Verified SHA1 checksum of issu-indb.tgz
Verified junos-boot-srx3000-9.6R1.13.tgz signed by PackageDevelopment_9_6_0
Verified junos-srx3000-9.6R1.13-domestic signed by PackageDevelopment_9_6_0
Hardware Database regeneration succeeded
Validating against /config/juniper.conf.gz
mgd: commit complete
Validation succeeded

Pushing bundle to node0
Installing package '/var/tmp/junos-srx3000-9.6R1.13-domestic.tgz' ...
Verified SHA1 checksum of issu-indb.tgz
Verified junos-boot-srx3000-9.6R1.13.tgz signed by PackageDevelopment_9_6_0
Verified junos-srx3000-9.6R1.13-domestic signed by PackageDevelopment_9_6_0
Available space: 391052 require: 175814
Verified SHA1 checksum of issu-indb.tgz
Verified junos-boot-srx3000-9.6R1.13.tgz signed by PackageDevelopment_9_6_0
Verified junos-srx3000-9.6R1.13-domestic signed by PackageDevelopment_9_6_0
JUNOS 9.6R1.13 will become active at next reboot
WARNING: A reboot is required to load this software correctly
WARNING:     Use the 'request system reboot' command
WARNING:         when software installation is complete
Saving package file in /var/sw/pkg/junos-9.6R1.13.tgz ...
Saving state for rollback ...
Finished upgrading secondary node node0
Rebooting Secondary Node

node0:
--------------------------------------------------------------------------
Shutdown NOW!
[pid 1365]
ISSU: Backup RE Prepare Done
Waiting for node0 to reboot.

node0 booted up.
Waiting for node0 to become secondary

node0 became secondary.