- play_arrow Overview
- play_arrow Configuring Switching Control Board Redundancy
- play_arrow Configuring Bidirectional Forwarding Detection (BFD)
- play_arrow Configuring Routing Engine Redundancy
- play_arrow Configuring Load Balancing
- play_arrow Configuring Graceful Routing Engine Switchover (GRES)
- play_arrow Configuring Ethernet Ring Protection Switching
- play_arrow Configuring Nonstop Bridging
- play_arrow Configuring Nonstop Active Routing (NSR)
- play_arrow Configuring Graceful Restart
- play_arrow Power Management Overview
- play_arrow Configuring Virtual Router Redundancy Protocol (VRRP)
- play_arrow Performing Unified In-Service Software Upgrade (ISSU)
- play_arrow Performing Nonstop Software Upgrade (NSSU)
- play_arrow Multinode High Availability
- Multinode High Availability
- Prepare Your Environment for Multinode High Availability Deployment
- Multinode High Availability Services
- IPsec VPN Support in Multinode High Availability
- Asymmetric Traffic Flow Support in Multinode High Availability
- Example: Configure Multinode High Availability in a Layer 3 Network
- Example: Configure Multinode High Availability in a Default Gateway Deployment
- Example: Configure Multinode High Availability in a Hybrid Deployment
- Example: Configure IPSec VPN in Active-Active Multinode High Availability in a Layer 3 Network
- Example: Configure Multinode High Availability with Junos OS Configuration Groups
- Software Upgrade in Multinode High Availability
- Insert Additional SRX5K-SPC3 in a Multinode High Availability Setup
- Multinode High Availability Support for vSRX Virtual Firewall Instances
- Multinode High Availability in AWS Deployments
- Multinode High Availability in Azure Cloud
- Multinode High Availability in Google Cloud Platform
- Multinode High Availability Monitoring Options
- play_arrow Verification Tasks
- play_arrow Troubleshooting
- play_arrow Knowledge Base
Upgrading Software on an EX8200 Virtual Chassis Using Nonstop Software Upgrade (CLI Procedure)
You can use nonstop software upgrade (NSSU) to upgrade the software on an EX8200 Virtual Chassis. NSSU upgrades the software running on all Routing Engines with minimal traffic disruption during the upgrade. NSSU is supported on EX8200 Virtual Chassis with redundant XRE200 External Routing Engines running Junos OS Release 11.1 or later.
NSSU upgrades all Routing Engines on all members of the Virtual Chassis and on the XRE200 External Routing Engines. Using NSSU, you cannot choose to upgrade the backup Routing Engines only, nor can you choose to upgrade a specific member of the Virtual Chassis. If you need to upgrade a specific member of the Virtual Chassis, see Installing Software for a Single Device in an EX8200 Virtual Chassis.
This topic covers:
Preparing the Switch for Software Installation
Before you begin software installation using NSSU:
(Optional) Configure line-card upgrade groups as described in Configuring Line-Card Upgrade Groups for Nonstop Software Upgrade. By default, NSSU upgrades line cards one at a time, starting with the line card in slot 0 of member 0. This permits aggregated Ethernet links that have members on different line cards remain up through the upgrade process. Configuring line-card upgrade groups reduces the time an upgrade takes because the line cards in each upgrade group are upgraded at the same time rather than sequentially.
Verify that the members are running the same version of the software:
content_copy zoom_out_map{master:8} user@external-routing-engine> show version all-members
If the Virtual Chassis members are not running the same version of the software, use the
request system software add
command to upgrade the software on the inconsistent members. For instructions, see Installing Software for a Single Device in an EX8200 Virtual Chassis.Ensure that nonstop active routing (NSR) and graceful Routing Engine switchover (GRES) are 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:
content_copy zoom_out_map{master:8} user@switch> show task replication Stateful Replication: Enabled RE mode: Master Protocol Synchronization Status PIM Complete
If nonstop active routing is not enabled (Stateful Replication is Disabled), see Configuring Nonstop Active Routing on Switches for information on how to enable it.
Upgrading the Software Using NSSU
This procedure describes how to upgrade the software running on all Routing Engines using NSSU. When the upgrade completes, all Routing Engines are running the new version of the software. The backup external Routing Engine is now the primary external Routing Engine, and the internal backup Routing Engines in the member switches are now the internal primary Routing Engines in those member switches.
To upgrade all Routing Engines using NSSU:
Download the software package for the XRE200 External Routing Engine by following one of the procedures in Downloading Software. The name of the software package for the XRE200 External Routing Engine contains the term xre200.
Copy the software package to the switch. We recommend that you use FTP to copy the file to the /var/tmp directory.
Log in to the primary external Routing Engine using the console connection. You can perform an NSSU from the management interface, but a console connection allows you to monitor the progress of the primary Routing Engine reboot.
Install the new software package:
content_copy zoom_out_map{master:8} user@external-routing-engine> request system software nonstop-upgrade reboot /var/tmp/package-name-m.nZx-distribution.tgz
where package-name-m.nZx-distribution.tgz is, for example, jinstall-ex-xre200-11.1R2.5-domestic-signed.tgz.
Note:You can omit reboot option. When you include the reboot option, NSSU automatically reboots the original primary Routing Engines after the new image has been installed on them. If you omit the reboot option, you must manually reboot the original primary Routing Engines (now the backup Routing Engines) to complete the upgrade. To perform the reboot, you must establish a connection to the console port on the Switch Fabric and Routing Engine (SRE) module or Routing Engine (RE) module.
The switch displays status messages similar to the following messages as the upgrade executes:
content_copy zoom_out_mapChassis ISSU Check Done ISSU: Validating Image ISSU: Preparing LCC Backup REs ISSU: Preparing Backup RE Pushing bundle /var/tmp/jinstall-ex-xre200-11.1-20110208.0-domestic-signed.tgz to member9 member9: -------------------------------------------------------------------------- WARNING: A reboot is required to install the software WARNING: Use the 'request system reboot' command immediately VC Backup upgrade done Rebooting VC Backup RE Rebooting member9 ISSU: Backup RE Prepare Done Waiting for VC Backup RE reboot Pushing bundle to member0-backup Pushing bundle to member1-backup WARNING: A reboot is required to install the software WARNING: Use the 'request system reboot' command immediately WARNING: A reboot is required to install the software WARNING: Use the 'request system reboot' command immediately Rebooting member0-backup Rebooting LCC [member0-backup] Rebooting member1-backup Rebooting LCC [member1-backup] ISSU: LCC Backup REs Prepare Done GRES operational Initiating Chassis Nonstop-Software-Upgrade Chassis ISSU Started ISSU: Preparing Daemons ISSU: Daemons Ready for ISSU ISSU: Starting Upgrade for FRUs ISSU: Preparing for Switchover ISSU: Ready for Switchover Checking Nonstop-Upgrade status member0: -------------------------------------------------------------------------- Item Status Reason FPC 0 Online (ISSU) FPC 1 Online (ISSU) FPC 2 Online (ISSU) FPC 5 Online (ISSU) member1: -------------------------------------------------------------------------- Item Status Reason FPC 0 Online (ISSU) FPC 1 Online (ISSU) FPC 2 Online (ISSU) FPC 5 Online (ISSU) member0: -------------------------------------------------------------------------- Item Status Reason FPC 0 Online (ISSU) FPC 1 Online (ISSU) FPC 2 Online (ISSU) FPC 5 Online (ISSU) member1: -------------------------------------------------------------------------- Item Status Reason FPC 0 Online (ISSU) FPC 1 Online (ISSU) FPC 2 Online (ISSU) FPC 5 Online (ISSU) ISSU: Upgrading Old Master RE Pushing bundle /var/tmp/incoming-package-8200.tgz to member0-master Pushing bundle /var/tmp/incoming-package-8200.tgz to member1-master ISSU: RE switchover Done WARNING: A reboot is required to install the software WARNING: Use the 'request system reboot' command immediately ISSU: Old Master Upgrade Done ISSU: IDLE *** FINAL System shutdown message from root@ *** System going down IMMEDIATELY Shutdown NOW!
Note:If you omit the reboot option in this step, you must complete the upgrade by separately rebooting the original primary Routing Engine on each Virtual Chassis member and the original primary external Routing Engine. To reboot the original primary Routing Engine on a Virtual Chassis member, you must establish a connection to the console port on the Switch Fabric and Routing Engine (SRE) module or Routing Engine (RE) module.
Log in after the reboot completes. To verify that the software on all Routing Engines in the Virtual Chassis members has been upgraded, enter the following command:
content_copy zoom_out_map{backup:8} user@external-routing-engine> show version all-members
Verify that the line cards that were online before the upgrade are online after the upgrade by entering the
show chassis nonstop-upgrade
command:content_copy zoom_out_map{backup:8} user@external-routing-engine> show chassis nonstop-upgrade member0: -------------------------------------------------------------------------- Item Status Reason FPC 0 Online FPC 1 Online FPC 2 Online FPC 5 Online member1: -------------------------------------------------------------------------- Item Status Reason FPC 0 Online FPC 1 Online FPC 2 Online FPC 5 Online