Navigation
request system software in-service-upgrade (Branch SRX Series Devices)
Table of Contents
Guide That Contains This Content
[+] Expand All
[-] Collapse All
Supported Platforms
request system software in-service-upgrade (Maintenance)
Syntax
request system software in-service-upgrade image_name <no-copy><no-sync><no-tcp-syn-check><no-validate><reboot><unlink>
Release Information
For SRX1400, SRX3400, SRX3600, SRX5400, SRX5600, and SRX5800 devices, command introduced in Junos OS Release 9.6 and support for reboot as a required parameter added in Junos OS Release 11.2R2. For SRX100, SRX210, SRX220, SRX240, and SRX650 devices, command introduced in Junos OS Release 11.2R2.
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 should 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 SRX100, SRX210, SRX220, SRX240, and SRX650 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.
Options
- image_name—Location and name of the software upgrade package to be installed.
- no-copy—(Optional) Installs the software upgrade package but does not save the copies of package files.
- no-sync—Stops the flow state from synchronizing
when the old secondary node has booted with a new Junos OS image.
This parameter applies to SRX100, SRX210, SRX220, SRX240, and SRX650 devices only. It is required for an ICU.
- no-tcp-syn-check—(Optional) Creates 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 SRX100, SRX210, SRX220, SRX240, and SRX650 devices only.
- no-validate—(Optional) Disables the configuration
validation step at installation. The system behavior is similar to
that of the request system software add command.
This parameter applies to SRX100, SRX210, SRX220, SRX240, and SRX650 devices only.
- reboot—Reboots each device in the chassis
cluster pair after installation is completed.
This parameter applies to SRX1400, SRX3400, SRX3600, SRX5400, SRX5600, and SRX5800 devices only. It is required for an ISSU. (The devices in a cluster are automatically rebooted following an ICU.)
- unlink—(Optional) Removes the software package after successful installation.
Required Privilege Level
maintenance
List of Sample Output
request system software in-service-upgrade (High-End SRX Series Devices)request system software in-service-upgrade (Branch SRX Series Devices)
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 (High-End SRX Series Devices)
user@host> request
system software in-service-upgrade /var/tmp/junos-srx1k3k-11.2R2.5-domestic.tgz
no-copy reboot Chassis ISSU Started node0: -------------------------------------------------------------------------- Chassis ISSU Started ISSU: Validating Image Inititating in-service-upgrade node0: -------------------------------------------------------------------------- Inititating in-service-upgrade Checking compatibility with configuration mgd: commit complete Validation succeeded ISSU: Preparing Backup RE Finished upgrading secondary node node0 Rebooting Secondary Node node0: -------------------------------------------------------------------------- Shutdown NOW! [pid 3257] ISSU: Backup RE Prepare Done Waiting for node0 to reboot. node0 booted up. Waiting for node0 to become secondary node0 became secondary. Waiting for node0 to be ready for failover ISSU: Preparing Daemons Secondary node0 ready for failover. Failing over all redundancy-groups to node0 ISSU: Preparing for Switchover Initiated failover for all the redundancy groups to node1 Waiting for node0 take over all redundancy groups Exiting in-service-upgrade window node0: -------------------------------------------------------------------------- Exiting in-service-upgrade window Exiting in-service-upgrade window Chassis ISSU Aborted node0: -------------------------------------------------------------------------- Chassis ISSU Ended ISSU completed successfully, rebooting... Shutdown NOW! [pid 4294]
Sample Output
request system software in-service-upgrade (Branch SRX Series Devices)
user@host> request
system software in-service-upgrade /var/tmp/junos-srxsme-11.2R2.2-domestic.tgz
no-sync ISSU: Validating package
WARNING: in-service-upgrade shall reboot both the nodes
in your cluster. Please ignore any subsequent
reboot request message
ISSU: start downloading software package on secondary node
Pushing bundle to node1
NOTICE: Validating configuration against junos-srxsme-11.2R2.2-domestic.tgz.
NOTICE: Use the 'no-validate' option to skip this if desired.
Formatting alternate root (/dev/ad0s1a)...
/dev/ad0s1a: 630.5MB (1291228 sectors) block size 16384, fragment size 2048
using 4 cylinder groups of 157.62MB, 10088 blks, 20224 inodes.
super-block backups (for fsck -b #) at:
32, 322848, 645664, 968480
Checking compatibility with configuration
Initializing...
Verified manifest signed by PackageProduction_11_2_0
Verified junos-11.2R2.2-domestic signed by PackageProduction_11_2_0
Using junos-11.2R2.2-domestic from /altroot/cf/packages/install-tmp/junos-11.2R2.2-domestic
Copying package ...
Saving boot file package in /var/sw/pkg/junos-boot-srxsme-11.2R2.2.tgz
Verified manifest signed by PackageProduction_11_2_0
Hardware Database regeneration succeeded
Validating against /config/juniper.conf.gz
cp: /cf/var/validate/chroot/var/etc/resolv.conf and /etc/resolv.conf are identical (not copied).
cp: /cf/var/validate/chroot/var/etc/hosts and /etc/hosts are identical (not copied).
mgd: commit complete
Validation succeeded
Installing package '/altroot/cf/packages/install-tmp/junos-11.2R2.2-domestic' ...
Verified junos-boot-srxsme-11.2R2.2.tgz signed by PackageProduction_11_2_0
Verified junos-srxsme-11.2R2.2-domestic signed by PackageProduction_11_2_0
Saving boot file package in /var/sw/pkg/junos-boot-srxsme-11.2R2.2.tgz
JUNOS 11.2R2.2 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 state for rollback ...
ISSU: finished upgrading on secondary node node1
ISSU: start upgrading software package on primary node
NOTICE: Validating configuration against junos-srxsme-11.2R2.2-domestic.tgz.
NOTICE: Use the 'no-validate' option to skip this if desired.
Formatting alternate root (/dev/ad0s1a)...
/dev/ad0s1a: 630.9MB (1292176 sectors) block size 16384, fragment size 2048
using 4 cylinder groups of 157.75MB, 10096 blks, 20224 inodes.
super-block backups (for fsck -b #) at:
32, 323104, 646176, 969248
Checking compatibility with configuration
Initializing...
Verified manifest signed by PackageProduction_11_2_0
Verified junos-11.2R2.2-domestic signed by PackageProduction_11_2_0
Using junos-11.2R2.2-domestic from /altroot/cf/packages/install-tmp/junos-11.2R2.2-domestic
Copying package ...
Saving boot file package in /var/sw/pkg/junos-boot-srxsme-11.2R2.2.tgz
Verified manifest signed by PackageProduction_11_2_0
Hardware Database regeneration succeeded
Validating against /config/juniper.conf.gz
cp: /cf/var/validate/chroot/var/etc/resolv.conf and /etc/resolv.conf are identical (not copied).
cp: /cf/var/validate/chroot/var/etc/hosts and /etc/hosts are identical (not copied).
mgd: commit complete
Validation succeeded
Installing package '/altroot/cf/packages/install-tmp/junos-11.2R2.2-domestic' ...
Verified junos-boot-srxsme-11.2R2.2.tgz signed by PackageProduction_11_2_0
Verified junos-srxsme-11.2R2.2-domestic signed by PackageProduction_11_2_0
Saving boot file package in /var/sw/pkg/junos-boot-srxsme-11.2R2.2.tgz
JUNOS 11.2R2.2 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 state for rollback ...
ISSU: failover all redundancy-groups 1...n to primary node
node0:
--------------------------------------------------------------------------
Successfully reset all redundancy-groups priority back to configured ones.
Redundancy-groups-0 will not be reset and the primaryship remains unchanged.
node1:
--------------------------------------------------------------------------
Successfully reset all redundancy-groups priority back to configured ones.
Redundancy-groups-0 will not be reset and the primaryship remains unchanged.
node0:
--------------------------------------------------------------------------
Initiated manual failover for all redundancy-groups to node0
Redundancy-groups-0 will not failover and the primaryship remains unchanged.
ISSU: rebooting Secondary Node
node1:
--------------------------------------------------------------------------
Shutdown NOW!
[pid 7023]
ISSU: Waiting for secondary node node1 to reboot.
ISSU: node 1 went down
ISSU: Waiting for node 1 to come up
ISSU: node 1 came up
ISSU: secondary node node1 booted up.
Shutdown NOW!
[pid 45056]
