Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Upgrading Junos OS Software in an EX9200 Virtual Chassis

 

You can upgrade the Junos OS in an EX9200 Virtual Chassis by installing Junos OS software onto each Routing Engine in the Virtual Chassis, and rebooting each Routing Engine individually to complete the installation. Both member switches in the EX9200 Virtual Chassis must have dual Routing Engines installed.

Note

Make sure all four Routing Engines in the Virtual Chassis (both Routing Engines in the primary switch and both Routing Engines in the backup switch) are running the same version of Junos OS software.

Caution

Support for EX9200 Virtual Chassis was phased out as of Junos OS Release 17.1R1, so do not upgrade an EX9200 Virtual Chassis to Junos OS Release 17.1R1 and beyond. For deployments with EX9200 switches, we recommend planning or moving to MC-LAG or Junos Fusion Enterprise architectures instead of using a Virtual Chassis.

To upgrade Junos OS software in an EX9200 Virtual Chassis:

  1. Download the Junos OS software package to the primary Routing Engine on the primary switch in the Virtual Chassis (VC-P).

    See Downloading Software.

  2. Disable nonstop active routing (NSR) from the primary Routing Engine on the primary switch in the Virtual Chassis (VC-P):
    user@switch# deactivate nonstop-routing
  3. Disable graceful Routing Engine switchover (GRES) from the primary Routing Engine on the primary switch in the Virtual Chassis (VC-P):
    user@switch# deactivate graceful-switchover
  4. Commit the configuration.
  5. Exit CLI configuration mode.
    user@switch# exit
  6. Install the Junos OS software package onto each Routing Engine in the Virtual Chassis:
    user@switch> request system software add package-name

    On a properly formed Virtual Chassis, entering the request system software add package-name from the primary Routing Engine on the primary switch in the Virtual Chassis (VC-P) propagates the Junos OS software package to all four Routing Engines in the Virtual Chassis.

  7. Enter CLI configuration mode, and re-enable GRES:
    user@switch> configure
    user@switch# edit chassis redundancy
    user@switch# activate graceful-switchover
  8. Re-enable NSR:
    user@switch# activate nonstop-routing
  9. Commit the configuration on the primary Routing Engine on the primary switch in the Virtual Chassis (VC-P).
  10. Reboot all Routing Engines in the Virtual Chassis by entering the request system reboot command with no options from the primary Routing Engine on the primary switch in the Virtual Chassis (VC-P):
    user@switch> request system reboot

    This command reboots all Routing Engines and line cards in both member switches. The Routing Engines run the updated version of Junos OS software after the reboot is complete.

    A traffic disruption occurs until all line cards return online and the Virtual Chassis reforms.