Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

No index entries found.

Upgrade and Downgrade Instructions for Junos OS Release 12.3 for EX Series Switches

This section discusses the following topics:

Upgrade and Downgrade Support Policy for Junos OS Releases

Support for upgrades and downgrades that span more than three Junos OS releases at a time is not provided, except for releases that are designated as Extended End-of-Life (EEOL) releases. EEOL releases provide direct upgrade and downgrade paths—you can upgrade directly from one EEOL release to the next EEOL release even though EEOL releases generally occur in increments beyond three releases.

You can upgrade or downgrade to the EEOL release that occurs directly before or after the currently installed EEOL release, or to two EEOL releases before or after. For example, Junos OS Releases 10.0, 10.4, and 11.4 are EEOL releases. You can upgrade from Junos OS Release 10.0 to Release 10.4 or even from Junos OS Release 10.0 to Release 11.4. However, you cannot upgrade directly from a non-EEOL release that is more than three releases ahead or behind. For example, you cannot directly upgrade from Junos OS Release 10.3 (a non-EEOL release) to Junos OS Release 11.4 or directly downgrade from Junos OS Release 11.4 to Junos OS Release 10.3.

To upgrade or downgrade from a non-EEOL release to a release more than three releases before or after, first upgrade to the next EEOL release and then upgrade or downgrade from that EEOL release to your target release.

For more information about EEOL releases and to review a list of EEOL releases, see http://www.juniper.net/support/eol/junos.html.

Upgrading EX Series Switches Using NSSU

You can use nonstop software upgrade (NSSU) to upgrade Junos OS releases on standalone EX6200 and EX8200 switches with dual Routing Engines and on EX3300, EX4200, EX4500, EX4550, and EX8200 Virtual Chassis. NSSU enables you to upgrade the software with a single command and minimal disruption to network traffic.

To optimize the quality and reliability of NSSU across multiple EX Series platforms and Junos OS releases, starting with Junos OS Release 12.3R6, NSSU support is limited to specific release combinations using the following guidelines:

  • NSSU support is limited to N-1 to N and N to N+1 major release versions, where N represents a major release version such as 12.1, 12.2, or 12.3.
    For example, NSSU from Release 11.4 to Release 12.2 is supported. NSSU from Release 11.x to Release 13.x is not supported.
  • NSSU support is limited to N.3 and N.6 minor release versions.
    For example, NSSU from Release 11.4R11 to Releases 12.1R3, 12.1R6, 12.2R3, 12.2R6, 12.3R3, and 12.3R6 is supported.
  • Additional NSSU support for EEOL releases is provided within the same major release version and is limited to two consecutive prior minor releases.
    For example, NSSU from Release 11.4R9 or 11.4R10 to Release 11.4R11 is supported.

For details on the supported Junos OS release combinations for upgrading EX Series switches using NSSU, see the tables in Junos OS Release Support for Upgrading EX Series Switches Using NSSU.

For details on NSSU, including procedures, see Understanding Nonstop Software Upgrade on EX Series Switches.

Note: On a Virtual Chassis, you can use NSSU to upgrade from a domestic version of Junos OS to a controlled (MACsec) version of Junos OS. You cannot, however, use NSSU to upgrade from the controlled version of Junos OS to a domestic version of Junos OS.

Note: On an EX8200 Virtual Chassis, an NSSU operation can be performed only if you have configured the XRE200 External Routing Engine member ID to be 8 or 9.

Note: Do not use NSSU to upgrade the software on an EX8200 switch from Junos OS Release 10.4 if you have configured the IGMP, MLD, or PIM protocols on the switch. If you attempt to use NSSU, your switch might be left in a nonfunctional state from which it is difficult to recover. If you have these multicast protocols configured, upgrade the software on the EX8200 switch from Junos OS Release 10.4 by following the instructions in Installing Software on an EX Series Switch with Redundant Routing Engines (CLI Procedure). This issue does not apply to upgrades from Junos OS Release 11.1 or later.

Note: If you are using NSSU to upgrade the software on an EX8200 switch from Junos OS Release 10.4 and sFlow technology is enabled, disable sFlow technology before you perform the upgrade using NSSU. After the upgrade is complete, you can reenable sFlow technology. If you do not disable sFlow technology before you perform the upgrade with NSSU, sFlow technology does not work properly. This issue does not affect upgrades from Junos OS Release 11.2 or later.

Upgrading to Junos OS Release 12.1R2 or Later with Existing VSTP Configurations

If you are upgrading to Junos OS Release 12.1R2 or later from Release 12.1R1 or earlier, ensure that any VSTP configurations on the switch meet the following guidelines. If the VSTP configurations do not meet these guidelines and you run the upgrade, the upgrade fails and you have to connect the console, change the invalid VSTP configurations, and commit the changed configurations through the console. Guidelines for VSTP configurations are:

  • If you have specified physical interfaces for VSTP-configured VLANs, ensure that those interfaces are members of the VLANs specified in the VSTP configuration. If the VSTP configuration specifies vlan all, then the interfaces configured at the [edit protocols vstp vlan all] hierarchy level must be members of all VLANs.
  • If the interfaces are not members of the VLANs in the VSTP configurations but are already added to the VSTP configurations, remove them from those configurations, add them to the VLANs, and then add them back to the VSTP configurations.

[This issue is being tracked by PR/736488 in our bug database.]

Upgrading from Junos OS Release 10.4R3 or Later

This section contains the procedure for upgrading from Junos OS Release 10.4R3 or later to Junos OS Release 12.2. You can use this procedure to upgrade Junos OS on a standalone EX Series switch with a single Routing Engine and to upgrade all members of a Virtual Chassis or a single member of a Virtual Chassis.

To upgrade Junos OS on an EX6200 or EX8200 switch with dual Routing Engines, see Installing Software on an EX Series Switch with Redundant Routing Engines (CLI Procedure).

On switches with dual Routing Engines or on Virtual Chassis, you might also be able to use nonstop software upgrade (NSSU) to upgrade Junos OS. See Upgrading EX Series Switches Using NSSU for more information.

To upgrade Junos OS on a switch with a single Routing Engine or on a Virtual Chassis:

  1. Download the software package as described in Downloading Software Packages from Juniper Networks.
  2. (Optional) Back up the current software configuration to a second storage option. See the Junos OS Installation and Upgrade Guide for instructions.
  3. (Optional) Copy the software package to the switch. We recommend that you use FTP to copy the file to the /var/tmp directory.

    This step is optional because you can also upgrade Junos OS using a software image that is stored at a remote location.

  4. Install the new software package on the switch:
    user@switch> request system software add package

    Replace package with one of the following paths:

    • /var/tmp/package.tgz—For a software package in a local directory on the switch
    • ftp://hostname/pathname/package.tgz or http://hostname/pathname/package.tgz—For a software package on a remote server

    package.tgz is the name of the package; for example, jinstall-ex-4200-11.4R1.8-domestic-signed.tgz.

    To install software packages on all switches in a mixed EX4200 and EX4500 Virtual Chassis, use the set option to specify both the EX4200 package and the EX4500 package:

    user@switch> request system software add set [package package]

    To install the software package on only one member of a Virtual Chassis, include the member option:

    user@switch> request system software add package member member-id 

    Other members of the Virtual Chassis are not affected. To install the software on all members of the Virtual Chassis, do not include the member option.

    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 the name of the package; for example, jinstall-ex-8200-11.4R1.8-domestic-signed.tgz. This is the last chance to stop the installation.

  5. Reboot the switch to start the new software:
    user@switch> request system reboot

    To reboot only a single member in a Virtual Chassis, include the member option:

    user@switch> request system reboot member
  6. After the reboot has finished, log in and verify that the new version of the software is properly installed:
    user@switch> show version
  7. Once you have verified that the new Junos OS version is working properly, copy the version to the alternate slice to ensure that if the system automatically boots from the backup partition, it uses the same Junos OS version:
    user@switch> request system snapshot slice alternate

    To update the alternate root partitions on all members of a Virtual Chassis, include the all-members option:

    user@switch> request system snapshot slice alternate all-members

Upgrading from Junos OS Release 10.4R2 or Earlier

To upgrade to Junos OS Release 12.3 from Junos OS Release 10.4R2 or earlier, first upgrade to Junos OS Release 11.4 by following the instructions in the Junos OS Release 11.4 release notes. See Upgrading from Junos OS Release 10.4R2 or Earlier or Upgrading from Junos OS Release 10.4R3 or Later in the Junos OS 11.4 Release Notes PDF Document.

Related Documentation

Modified: 2016-06-09