Installing Software on an EX Series Switch with Redundant Routing Engines (CLI Procedure)

For an EX6200 switch or an EX8200 switch with redundant Routing Engines, you can minimize disruption to network operation during a Junos OS upgrade by upgrading the Routing Engines separately, starting with the backup Routing Engine.

Note: If your EX8200 switch is running Junos OS Release 10.4 or later, you can upgrade the software packages on both Routing Engines with a single command and with minimal network disruption by using nonstop software upgrade (NSSU) instead of this procedure. See Upgrading Software on an EX8200 Standalone Switch Using Nonstop Software Upgrade (CLI Procedure).

Warning: If graceful routing engine switchover (GRES) or nonstop active routing (NSR) is enabled when you initiate a software installation, the software does not install properly. Make sure you disable GRES before you begin the software installation by using the deactivate chassis redundancy graceful-switchover command in configuration mode. If GRES is enabled, it will be removed with the redundancy command. By default, NSR is disabled. If NSR is enabled, remove the nonstop-routing statement from the [edit routing-options] hierarchy level to disable it.

To upgrade the software package on an EX6200 switch or an EX8200 switch with one installed Routing Engine, see Installing Software on an EX Series Switch with a Single Routing Engine (CLI Procedure).

To upgrade redundant Routing Engines, you first install the new Junos OS release on the backup Routing Engine while keeping the currently running software version on the master Routing Engine. After making sure that the new software version is running correctly on the backup Routing Engine, you switch device control to the backup Routing Engine. Finally, you install the new software on the new backup Routing Engine.

To upgrade Junos OS on the switch, perform the following tasks:

1. Preparing the Switch for the Software Installation
2. Installing Software on the Backup Routing Engine
3. Installing Software on the Default Master Routing Engine
4. Returning Routing Control to the Default Master Routing Engine (Optional)

Preparing the Switch for the Software Installation

1. Log in to the master Routing Engine’s console.

   For information on logging in to the Routing Engine through the console port, see Connecting and Configuring an EX Series Switch (CLI Procedure).

2. Enter the Junos OS CLI configuration mode:

   1. Start the CLI from the shell prompt:

      user@switch:RE% cli

      You will see:

      {master}
      user@switch>

   2. Enter configuration mode:

      user@switch> configure
        
      

      You will see:

      {master}[edit]
      user@switch#

3. Disable nonstop active routing (NSR) (supported on switches running Junos OS Release 10.4 or later):

   {master}[edit]
   user@switch# delete routing-options nonstop-routing

4. Disable graceful Routing Engine switchover (GRES):

   {master}[edit]
   user@switch# deactivate chassis redundancy graceful-switchover
   

5. Save the configuration change on both Routing Engines:

   {master}[edit]
   user@switch# commit synchronize

   Note: To ensure the most recent configuration changes are committed before the software upgrade, perform this step even if nonstop active routing and graceful Routing Engine switchover were previously disabled.

6. Exit the CLI configuration mode:

   [edit]
   user@switch# exit

7. (Optional) Back up the current software configuration to a second storage option. See the Junos OS Installation and Upgrade Guide for instructions on performing this task.

Installing Software on the Backup Routing Engine

1. Download the software by following the procedures in Downloading Software Packages from Juniper Networks.
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 console of the backup Routing Engine.

4. Install the new software package:

   user@switch> request system software add  /var/tmp/package.tgz

   where package.tgz is, for example, jinstall-ex-8200-10.2R1.8-domestic-signed.tgz.

   Note: To abort the installation, do not reboot your device; instead, finish the installation and then issue the request system software delete package.tgz command, where package.tgz is, for example, jinstall-ex-8200-10.2R1.8-domestic-signed.tgz. This is your last chance to stop the installation.

5. Reboot to start the new software:

   user@switch> request system reboot
   Reboot the system? [yes, no] (no) yes

   Note: You must reboot the switch to load the new installation of the Junos OS.

6. After the reboot has completed, log in and verify the new version of the software is properly installed:

   user@switch> show version

Installing Software on the Default Master Routing Engine

1. Log in to the master Routing Engine console port.
2. Transfer control to the backup Routing Engine:

   Caution: Because graceful Routing Engine switchover is disabled, this switchover causes all line cards in the switch to reload. All network traffic passing through these line cards is lost during the line card reloads.

   user@switch> request chassis routing-engine master switch

3. Verify that the default backup Routing Engine (shown as slot 1 in the command output) is now the master Routing Engine:

   user@switch> show chassis routing-engine
   

   You will see:

   
   Routing Engine status:
     Slot 0:
       Current state                  Backup
       Election priority              Master (default)
   
   Routing Engine status:
     Slot 1:
       Current state                  Master
       Election priority              Backup (default)

4. Install the new software package:

   user@switch> request system software add package.tgz

5. Reboot the Routing Engine:

   user@switch> request system reboot
   Reboot the system? [yes, no] (no) yes

   When the reboot completes, the prompt will reappear. Wait for this prompt to reappear before proceeding to the next step.
6. Log in to the default backup Routing Engine (slot 1) through the console port.
7. Re-enable graceful Routing Engine switchover:

   [edit]
   user@switch# activate chassis redundancy graceful-switchover
   

   Re-enabling graceful Routing Engine switchover allows any future Routing Engine switchovers to occur without loss of any network traffic.

8. Re-enable nonstop active routing:

   [edit]
   user@switch# set routing-options nonstop-routing
   

   Note: Automatic commit synchronization is a requirement for nonstop active routing. If you have not yet enabled it, do so with the set system commit synchronize command.

9. Save the configuration change:

   [edit]
   user@switch# commit synchronize
   

10. Log in and verify the version of the software installed.

If you want to return routing control to the Routing Engine that was the master Routing Engine at the beginning of the procedure (the default master Routing Engine), perform the next task.

Returning Routing Control to the Default Master Routing Engine (Optional)

1. Transfer routing control back to the default master Routing Engine:

   user@switch> request chassis routing-engine master switch
   

2. Verify that the default master Routing Engine (slot 0) is indeed the master Routing Engine:

   user@switch> show chassis routing-engine
   

   You will see:

   
   Routing Engine status:
     Slot 0:
       Current state                  Master
       Election priority              Master (default)
   
   Routing Engine status:
     Slot 1:
       Current state                  Backup
       Election priority              Backup (default)