Performing an In-Service Software Upgrade (ISSU) with Non-Stop Routing
You can use an in-service software upgrade with non-stop routing to upgrade the software running on the switch with minimal traffic disruption during the upgrade.
Starting with Junos OS Release 18.2R1 on the QFX5200 switch, we recommend that you wait at least five minutes between in-service software upgrades.
Starting with Junos OS Release 17.1R1, on QFX5100 and EX4600 switches, you cannot perform an ISSU from a Junos OS Release earlier than 17.1R1 to Junos OS Release 17.1R1.
This topic covers:
Preparing the Switch for Software Installation
Before you begin software installation using ISSU:
Before you perform an in-service software upgrade, if
applicable, remove the set system internet-options no-tcp-reset
drop-all-tcp command from the configuration, otherwise the upgrade
will fail and an error message will be displayed.
NSB and non-stop routing enable NSB-supported Layer 2 protocols to synchronize protocol information between the primary and backup Routing Engines.
Enable non-stop routing. See Configuring Nonstop Active Routing on Switchesfor information on how to enable it.
Enable nonstop bridging (NSB). See Configuring Nonstop Bridging on Switches (CLI Procedure) for information on how to enable it.
Configure the Bidirectional Forwarding Detection Protocol (BFD) timeout to be more than one second, otherwise you will receive an error.
Upgrading the Software Using ISSU
This procedure describes how to upgrade the software running on a standalone switch:
If the Host OS software needs to be updated, you cannot perform an ISSU. Instead, perform a standard software upgrade.
To upgrade the switch using ISSU:
Download the software package by following the procedure in the Downloading Software Files with a Browser section in Installing Software Packages on QFX Series Devices.
Copy the software package or packages to the switch. We recommend that you copy the file to the
/var/tmpdirectory.Log in to the console connection. Using a console connection allows you to monitor the progress of the upgrade.
Start the ISSU:
On the switch, enter:
user@switch> request system software in-service-upgrade /var/tmp/package-name.tgz
where
package-name.tgzis, for example,jinstall-host-qfx-5e-18.1R1-secured-signed.tgz.
Note:During the upgrade, you will not be able to access the Junos OS CLI.
The switch displays status messages similar to the following messages as the upgrade executes:
ISSU: Validating Image PRE ISSU CHECK: --------------- PFE Status : Online Member Id zero : Valid VC not in mixed or fabric mode : Valid Member is single node vc : Valid BFD minimum-interval check done : Valid GRES enabled : Valid GR enabled : Valid drop-all-tcp not configured : Valid Ready for ISSU : Valid warning: Do NOT use /user during ISSU. Changes to /user during ISSU may get lost! Pushing Junos image package to the host... Installing /var/tmp/install-media-qfx-5e-junos-2018-secure.tgz Extracting the package ... total 1110328 -rw-r--r-- 1 18735 758 237044439 Oct 26 05:11 jinstall-qfx-5e-junos-2018-secure-linux.tgz -rw-r--r-- 1 18735 758 899918118 Oct 26 05:11 jinstall-qfx-5e-junos-2018-secure-app.tgz ============================================ Current Host kernel version : 3.14.52-rt50-WR7.0.0.9_ovp Package Host kernel version : 3.14.52-rt50-WR7.0.0.9_ovp Current Host version : 3.0.7 Package Host version : 3.0.7 Min host version required for applications: 3.0.7 Min host version required for in-service-upgrade: 3.0.7 ============================================ Setting up Junos host applications for in-service-upgrade ... ------------------------------------------------ Running Junos application installer for in-service-upgrade ------------------------------------------------ ------------------------------- Installing /var/sw/applications/qfx-5e-flex-2018.tgz ------------------------------- pkg_install_rpms: qfx-5e-base-1.0-0-2018.x86_64.rpm Installing qfx-5e-control-plane-flex-1.0-0-2018.x86_64.rpm ... ======================================== Loading cache... Updating cache... ######################################## [100%] Committing transaction... Preparing... ######################################## [ 0%] 1:Installing qfx-5e-contro.. ######################################## [100%] Output from qfx-5e-control-plane-flex-1.0-0@x86_64: ------------------------------- Installing JUNOS image: jinstall-jcp-i386-flex-18.12018.img.gz ------------------------------- Extracting jinstall-jcp-i386-flex-18.12018.img.gz to /recovery/junos/jinstall-jcp-i386-flex-18.12018-2018.img Prepare host for virtfs... Integrity check passed for hash-control-plane.md5. Installing packages (1): qfx-5e-control-plane-flex-1.0-0@x86_64 812.9MB of package files are needed. 821.5MB will be used. Saving cache... ======================================== Application installed. Waiting to sync newly setup VM disk VM ready after 200 seconds [Oct 26 05:19:22]:ISSU: Preparing Backup RE Prepare for ISSU [Oct 26 05:19:27]:ISSU: Backup RE Prepare Done Spawning the backup RE Spawn backup RE, index 0 successful Starting secondary dataplane Second dataplane container started GRES in progress Waiting for backup RE switchover ready GRES operational Copying home directories Copying home directories successful Initiating Chassis In-Service-Upgrade Chassis ISSU Started [Oct 26 05:28:33]:ISSU: Preparing Daemons [Oct 26 05:28:39]:ISSU: Daemons Ready for ISSU [Oct 26 05:28:43]:ISSU: Starting Upgrade for FRUs [Oct 26 05:28:54]:ISSU: FPC Warm Booting [Oct 26 05:29:59]:ISSU: FPC Warm Booted [Oct 26 05:30:10]:ISSU: Preparing for Switchover [Oct 26 05:30:14]:ISSU: Ready for Switchover Checking In-Service-Upgrade status Item Status Reason FPC 0 Online (ISSU) Send ISSU done to chassisd on backup RE Chassis ISSU Completed Removing dcpfe1 eth1 128.0.0.16 IP Bringing down bme01 Post Chassis ISSU processing done [Oct 26 05:30:17]:ISSU: IDLE Stopping primary dataplane Clearing ISSU states Console and management sessions will be disconnected. Please login again.
Note:If the ISSU process stops, you can look at the CLI output when you issue the
request system software in-service-upgradecommand to diagnose the problem. You can also look at syslog files for more information.Log in after the reboot of the switch completes. To verify that the software has been upgraded, enter the following command:
user@switch>
show version