Supported Platforms
Related Documentation
- EX Series, QFX Series standalone switches
- request system software nonstop-upgrade
- show chassis nonstop-upgrade
- Configuring Graceful Routing Engine Switchover in a Virtual Chassis (CLI Procedure)
- Understanding Nonstop Software Upgrade on a Virtual Chassis Fabric
- Configuring Nonstop Bridging on Switches (CLI Procedure)
- Example: Configuring Nonstop Active Routing on Switches
- EX Series
- Example: Configuring Line-Card Upgrade Groups for Nonstop Software Upgrade on EX Series Switches
- Understanding Resilient Dual-Root Partitions on Switches
Upgrading Software on a Virtual Chassis Fabric Using Nonstop Software Upgrade
Nonstop software upgrade (NSSU) enables you to upgrade the software running on all member switches on a Virtual Chassis Fabric with minimal network traffic disruption during the upgrade. A Virtual Chassis Fabric can contain 32 members—up to 2 members can be in the routing engine role, and up to 30 line cards can be configured in the line card role. You can upgrade software for a fixed configuration of switches or for a mixed mode of switches in a Virtual Chassis Fabric.
This topic covers:
Preparing the Switch for Software Installation
Before you begin software installation using NSSU:
- Ensure that the Virtual Chassis Fabric is configured correctly
to support NSSU. Verify that:
- The Virtual Chassis Fabric members are connected in a spine and leaf topology. A spine and leaf topology prevents the Virtual Chassis from splitting during an NSSU. Each leaf device must be connected to both spine devices.
- The Virtual Chassis Fabric must be preprovisioned so that the line card role has been explicitly assigned to member switches acting in a line card role, and that the routing engine role has been explicitly assigned to member switches acting in a routing engine role. During an NSSU, the Virtual Chassis Fabric members must maintain their roles—the master and backup must maintain their master and backup roles (although mastership will change), the member switches must remain their routing engine roles, and the remaining switches must maintain their line card roles.
- Only two pre-provisioned members in the routing engine role are supported. If more than two routing engines are configured, a warning will be issued, and NSSU will stop.
- A two-member Virtual Chassis has no-split-detection configured so that the Virtual Chassis Fabric does not split when an NSSU upgrades a member.
- Verify that the members are running the same version of
the software: user@switch> show version
If you are going to perform an NSSU on a fixed configuration of switches or a mixed mode configuration of switches that are not running the same version of the software, use the request system software nonstop-upgrade <set [package-name package-name]> reboot command to upgrade the software on the inconsistent members.
Note: This command can require up to three software images depending on devices configured in the Virtual Chassis Fabric.
For example:
user@switch> request system software nonstop-upgrade add set [jinstall-qfx5100.tgz jinstall-qfx3500.tgz jinsall-ex-4300.tgz] reboot - Ensure that graceful
Routing Engine switchover (GRES) is enabled. To verify that they are
enabled, you need to check only the state of nonstop active routing—if
nonstop active routing is enabled, then graceful Routing Engine switchover
is enabled.
To verify that nonstop active routing is enabled:
user@switch> show task replication Stateful Replication: Enabled RE mode: Master Protocol Synchronization Status OSPF Complete BGP Complete PIM Complete
If nonstop active routing is not enabled (Stateful Replication is Disabled), seeExample: Configuring Nonstop Active Routing on Switches for information on how to enable it.
- Enable nonstop bridging (NSB). Enabling NSB ensures that all NSB-supported Layer 2 protocols operate seamlessly during the Routing Engine switchover that is part of the NSSU.
- (Optional) Back up the system software—Junos OS, the active configuration, and log files—on each member to an external storage device with the request system snapshot command.
Upgrading the Software Using NSSU
This procedure describes how to upgrade the software running on all Virtual Chassis Fabric members using NSSU. When the upgrade completes, all members are running the new version of the software. Because a graceful Routing Engine switchover occurs during the upgrade, the original Virtual Chassis Fabric backup is the new master.
![]() | Note: Junos OS software images with enhanced automation are only supported on a non-mixed Virtual Chassis Fabric with QFX5100 switches. Also, performing an NSSU from a standard Junos OS software image to a Junos OS software image with enhanced automation or from a Junos OS software image with enhanced automation to a standard Junos OS software image is not supported. |
To upgrade all members using NSSU:
- Download the software package by following the procedure in the Downloading Software Files with a Browser section in Upgrading Software and Downloading Software Packages from Juniper Networks. If you are upgrading the software running on a mixed mode Virtual Chassis Fabric, download the software packages for each switch type.
- Copy the software package or packages to the Virtual Chassis Fabric. We recommend that you copy the file to the /var/tmp directory on the master.
- Log in to the Virtual Chassis Fabric using the console connection of the master or the virtual management Ethernet (VME) interface. Without the console connection, you will not be able to view any CLI output during an NSSU reboot. The console connection enables you to view CLI output during an NSSU reboot and monitor the progress of the master switch reboot.
- Start the NSSU:
- To perform an NSSU on a fixed configuration of switches
(QFX3500/QFX3600, QFX5100, or EX4300 switches), enter:
user@switch> request system software nonstop-upgrade /var/tmp/package-name.tgz
where package-name.tgz is, for example, jinstall-qfx5100.tgz.
- To perform an NSSU on a mixed mode configuration of switches
(QFX3500/QFX3600, QFX5100, or EX4300 switches), enter:
user@switch> request system software nonstop-upgrade set [package-name package-name package-name]
where [package-name.tgz package-name.tgz package-name.tgz is, for example, [jinstall-qfx5100.tgz jinstall-qfx3500.tgz jinsall-ex-4300.tgz].
The switch displays status messages similar to the following messages as the upgrade executes:
switch# request system software nonstop-upgrade [ jinstall-qfx-3-mixed_vc-1-domestic.tgz jinstall-qfx-5-mixed_vc-1-domestic-img.tgz jinstall-ex-4300-mixed_vc-1-domestic.tgz ]
Chassis ISSU Check Done ISSU: Validating Image ISSU: Preparing Backup RE Installing image on other FPC's along with the backup Retrieving software images. This process can take several minutes. Please be patient.. Retrieving version and model information from /var/tmp/jinstall-qfx-3-mixed_vc-1-domestic.tgz Retrieving version and model information from /var/tmp/jinstall-qfx-5-mixed_vc-1-domestic-img.tgz Retrieving version and model information from /var/tmp/jinstall-ex-4300-mixed_vc-1-domestic.tgz Starting with package /var/tmp/jinstall-qfx-3-mixed_vc-1-domestic.tgz Download done for package /var/tmp/jinstall-qfx-3-mixed_vc-1-domestic.tgz Pushing bundle to fpc5 WARNING: The software that is being installed has limited support. WARNING: Run 'file show /etc/notices/unsupported.txt' for details. Setting up /var/shared/v for validation ... Checking compatibility with configuration Initializing... Using jbase-qfx-mixed_vc Using /var/tmp/jinstall-qfx-3-mixed_vc-1-domestic.tgz Using jbundle-qfx-3-mixed_vc-1-domestic.tgz Using jkernel-qfx-3-mixed_vc Using jroute-qfx-3-mixed_vc Using jcrypto-qfx-mixed_vc Using jswitch-qfx-3-mixed_vc Hardware Database regeneration succeeded Validating against /config/juniper.conf.gz mgd: commit complete Validation succeeded fpc5 WARNING: The software that is being installed has limited support. WARNING: Run 'file show /etc/notices/unsupported.txt' for details. Image name: /var/tmp/jinstall-qfx-3-mixed_vc-1-domestic.tgz Package name: jinstall-qfx-3 Junos revision: mixed_vc-1 ==> STEP #1 of 20: Creating temporary file system <== *** Fri Apr 4 16:28:23 PDT 2014 *** ==> STEP #2 of 20: Determining installation source <== *** Fri Apr 4 16:28:23 PDT 2014 *** Interactive installation: yes Boot media formatting option: disabled Installing packages from internal drive da0 Packages will be installed to da0, media size: 8G ==> STEP #3 of 20: Processing format options <== *** Fri Apr 4 16:28:24 PDT 2014 *** Formatting of boot media is not supported in this form of installation ==> STEP #4 of 20: Determining installation slice <== *** Fri Apr 4 16:28:24 PDT 2014 *** Physmem correction sectors: 0 Dump partition sectors: 4161792 package: INFO: Dump partition da0s3b size sufficient for kernel dumps. package: INFO: da0s3b will be retained as dump partition. ==> STEP #5 of 20: Creating and labeling new slices <== *** Fri Apr 4 16:28:25 PDT 2014 *** Primary partition - /: /dev/da0s1a, /var: /dev/da0s1f Shared partition - /var/tmp: /dev/da0s3d, /config: /dev/da0s3e, /var/shared: /dev/da0s3f, recovery: /dev/da0s3a, /var/rundb: /dev/da0s3g Checking integrity on da0s3 ==> STEP #6 of 20: Create and mount new file system <== *** Fri Apr 4 16:28:25 PDT 2014 *** /dev/da0s1a: 464.0MB (950192 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 116.00MB, 7424 blks, 14848 inodes. super-block backups (for fsck -b #) at: 32, 237600, 475168, 712736 tunefs: soft updates set /dev/da0s1f: 249.8MB (511656 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 62.47MB, 3998 blks, 8064 inodes. super-block backups (for fsck -b #) at: 32, 127968, 255904, 383840 tunefs: soft updates remains unchanged as disabled Size of staging area: 1006M Staging area setup in /instrootmnt/var/tmp ... ==> STEP #7 of 20: Getting OS bundles <== *** Fri Apr 4 16:28:35 PDT 2014 *** ==> STEP #8 of 20: Updating recovery media <== *** Fri Apr 4 16:28:35 PDT 2014 *** System recovery media update option is disabled - skipping set update_recovery_on_install="YES" in /etc/rc.conf.platform ==> STEP #9 of 20: Extracting incoming image <== *** Fri Apr 4 16:28:35 PDT 2014 *** install bundle source /var/tmp:jinstall-qfx-3-mixed_vc-1-domestic.tgz Enabling platform watchdog Starting pkg_add on /var/tmp/tmp - Fri Apr 4 16:29:09 PDT 2014 WARNING: The software that is being installed has limited support. WARNING: Run 'file show /etc/notices/unsupported.txt' for details. Completed pkg_add - Fri Apr 4 16:29:37 PDT 2014 Enabling platform watchdog ==> STEP #10 of 20: Unpacking OS packages <== *** Fri Apr 4 16:29:37 PDT 2014 *** Enabling platform watchdog ==> STEP #11 of 20: Mounting jbase package <== *** Fri Apr 4 16:29:39 PDT 2014 *** Mounted jbase package on /dev/md17... ==> STEP #12 of 20: Creating base OS symbolic links <== *** Fri Apr 4 16:29:54 PDT 2014 *** ==> STEP #13 of 20: Creating fstab <== *** Fri Apr 4 16:30:49 PDT 2014 *** ==> STEP #14 of 20: Creating new system files <== *** Fri Apr 4 16:30:49 PDT 2014 *** ==> STEP #15 of 20: Adding jbundle package <== *** Fri Apr 4 16:30:49 PDT 2014 *** Checking package integrity... Verified SHA1 checksum of jbase-qfx-mixed_vc-1.tgz Verified SHA1 checksum of jboot-qfx-mixed_vc-1.tgz Verified SHA1 checksum of jcrypto-qfx-mixed_vc-1.tgz Verified SHA1 checksum of jdocs-qfx-mixed_vc-1.tgz Verified SHA1 checksum of jkernel-qfx-3-mixed_vc-1.tgz Verified SHA1 checksum of jpfe-qfx-3-mixed_vc-1.tgz Verified SHA1 checksum of jroute-qfx-3-mixed_vc-1.tgz Verified SHA1 checksum of jswitch-qfx-3-mixed_vc-1.tgz Verified SHA1 checksum of py-base-xlr-mixed_vc-1.tgz Running requirements check first for jbundle-qfx-3-mixed_vc-1-domestic... Setting up alternate devfs for installation WARNING: The software that is being installed has limited support. WARNING: Run 'file show /etc/notices/unsupported.txt' for details. Running pre-install for jbundle-qfx-3-mixed_vc-1-domestic... Installing jbundle-qfx-3-mixed_vc-1-domestic in /var/tmp/tmp/pa8070.50/jbundle-qfx-3-mixed_vc-1-domestic.x8070... Running post-install for jbundle-qfx-3-mixed_vc-1-domestic... Adding jkernel-qfx-3... Registering jkernel as unsupported Adding jcrypto-qfx... Registering jcrypto as unsupported Adding jdocs-qfx... Registering jdocs as unsupported Adding jswitch-qfx-3... Registering jswitch as unsupported Adding jpfe-qfx-3... Registering jpfe as unsupported Adding jroute-qfx-3... Registering jroute as unsupported Adding py-base-xlr... Registering py-base-xlr as unsupported Setting up shared filesystem (/dev/da0s3f) ... ==> STEP #16 of 20: Backing up system data <== *** Fri Apr 4 16:33:18 PDT 2014 *** Backup configuration file: /config/install_backup.conf Files to be backed up: /var/db/scripts /var/home /root Backup file saved at /var/tmp/install_backup.tar Restoring system backed up data on new partition - Fri Apr 4 16:33:18 PDT 2014 Done - Fri Apr 4 16:33:19 PDT 2014 ==> STEP #17 of 20: Setting up shared partition data <== *** Fri Apr 4 16:33:19 PDT 2014 *** Creating directories in /dev/da0s3f ==> STEP #18 of 20: Checking package sanity in installation <== *** Fri Apr 4 16:33:19 PDT 2014 *** ==> STEP #19 of 20: Unmounting and cleaning up temporary file systems <== *** Fri Apr 4 16:33:19 PDT 2014 *** tunefs: soft updates remains unchanged as disabled tunefs: soft updates cleared Enabling platform watchdog ==> STEP #20 of 20: Setting da0s1 as new active partition <== *** Fri Apr 4 16:33:26 PDT 2014 *** WARNING: NOTE: A reboot is required to start using the new software WARNING: Use the 'request system reboot' command when ready Installation log saved at /var/sw/install-04042014162823.log Starting with package /var/tmp/jinstall-ex-4300-mixed_vc-1-domestic.tgz Download done for package /var/tmp/jinstall-ex-4300-mixed_vc-1-domestic.tgz Pushing bundle to fpc2 WARNING: The software that is being installed has limited support. WARNING: Run 'file show /etc/notices/unsupported.txt' for details. fpc2 WARNING: The software that is being installed has limited support. WARNING: Run 'file show /etc/notices/unsupported.txt' for details. WARNING: A reboot is required to install the software WARNING: Use the 'request system reboot' command immediately Starting with package /var/tmp/jinstall-qfx-5-mixed_vc-1-domestic-img.tgz Download done for package /var/tmp/jinstall-qfx-5-mixed_vc-1-domestic-img.tgz Pushing bundle to fpc1 Pushing bundle to fpc4 WARNING: The software that is being installed has limited support. WARNING: Run 'file show /etc/notices/unsupported.txt' for details. WARNING: The software that is being installed has limited support. WARNING: Run 'file show /etc/notices/unsupported.txt' for details. fpc1 WARNING: The software that is being installed has limited support. WARNING: Run 'file show /etc/notices/unsupported.txt' for details. Image name: /var/tmp/jinstall-qfx-5-mixed_vc-1-domestic-img.tgz Package name: jinstall-qfx-5-img Junos revision: mixed_vc-1 NOTE: A reboot is required to install the software Use the 'request system reboot' command immediately fpc4 WARNING: The software that is being installed has limited support. WARNING: Run 'file show /etc/notices/unsupported.txt' for details. Image name: /var/tmp/jinstall-qfx-5-mixed_vc-1-domestic-img.tgz Package name: jinstall-qfx-5-img Junos revision: mixed_vc-1 NOTE: A reboot is required to install the software Use the 'request system reboot' command immediately Backup upgrade done Rebooting Backup RE Rebooting fpc1 ISSU: Backup RE Prepare Done Waiting for Backup RE reboot GRES operational Initiating Chassis In-Service-Upgrade Chassis ISSU Started ISSU: Preparing Daemons ISSU: Daemons Ready for ISSU ISSU: Starting Upgrade for FRUs . . . . . . FPC 2 is undergoing a software upgrade . . . . . . . . . . . . . . . . . . . . . . . . . FPC 2 has come up after a software upgrade . . . . . . FPC 4 is undergoing a software upgrade . . . . . FPC 4 has come up after a software upgrade . . . . . . . . FPC 5 is undergoing a software upgrade . . . . . . . . . . . FPC 5 has come up after a software upgrade . . . . ISSU: Preparing for Switchover ISSU: Ready for Switchover Checking In-Service-Upgrade status Item Status Reason FPC 0 Online FPC 1 Online (ISSU) FPC 2 Online (ISSU) FPC 4 Online (ISSU) FPC 5 Online (ISSU) Going to install image on master WARNING: The software that is being installed has limited support. WARNING: Run 'file show /etc/notices/unsupported.txt' for details. Image name: /var/tmp/jinstall-qfx-5-mixed_vc-1-domestic-img.tgz Package name: jinstall-qfx-5-img Junos revision: mixed_vc-1 Going to install image on master WARNING: The software that is being installed has limited support. WARNING: Run 'file show /etc/notices/unsupported.txt' for details. Image name: /var/tmp/jinstall-qfx-5-mixed_vc-1-domestic-img.tgz Package name: jinstall-qfx-5-img Junos revision: mixed_vc-1 NOTE: A reboot is required to install the software Use the 'request system reboot' command immediately failover links Rebooting Old master ISSU: IDLE *** FINAL System shutdown message from root@vcf *** System going down IMMEDIATELY Shutdown NOW! [pid 5290]
- To perform an NSSU on a fixed configuration of switches
(QFX3500/QFX3600, QFX5100, or EX4300 switches), enter:
- Log in after the reboot of the original master switch
completes. To verify that the software on all Routing Engines in the
Virtual Chassis Fabric members has been upgraded, enter the following
command:user@switch> show version
Related Documentation
- EX Series, QFX Series standalone switches
- request system software nonstop-upgrade
- show chassis nonstop-upgrade
- Configuring Graceful Routing Engine Switchover in a Virtual Chassis (CLI Procedure)
- Understanding Nonstop Software Upgrade on a Virtual Chassis Fabric
- Configuring Nonstop Bridging on Switches (CLI Procedure)
- Example: Configuring Nonstop Active Routing on Switches
- EX Series
- Example: Configuring Line-Card Upgrade Groups for Nonstop Software Upgrade on EX Series Switches
- Understanding Resilient Dual-Root Partitions on Switches
Modified: 2015-10-22
Supported Platforms
Related Documentation
- EX Series, QFX Series standalone switches
- request system software nonstop-upgrade
- show chassis nonstop-upgrade
- Configuring Graceful Routing Engine Switchover in a Virtual Chassis (CLI Procedure)
- Understanding Nonstop Software Upgrade on a Virtual Chassis Fabric
- Configuring Nonstop Bridging on Switches (CLI Procedure)
- Example: Configuring Nonstop Active Routing on Switches
- EX Series
- Example: Configuring Line-Card Upgrade Groups for Nonstop Software Upgrade on EX Series Switches
- Understanding Resilient Dual-Root Partitions on Switches