Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

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.

Note:

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:

    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:

    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:

  1. 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.

  2. Copy the software package to the switch. We recommend that you use FTP to copy the file to the /var/tmp directory.

  3. 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.

  4. Install the new software package:

    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:

    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.

  5. 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:

  6. Verify that the line cards that were online before the upgrade are online after the upgrade by entering the show chassis nonstop-upgrade command:

Related Documentation