Installing Software on EX Series Switches

 

EX Series devices are delivered with preinstalled Junos operating system (Junos OS). Before you start this procedure, decide which software package you need and download it. For information on which packages to use for which upgrades, see Junos OS Installation Package Names.

Understanding Software Installation on EX Series Switches

A Juniper Networks EX Series Ethernet Switch is delivered with the Juniper Networks Junos operating system (Junos OS) preinstalled. As new features and software fixes become available, you must upgrade your software to use them. You can also downgrade Junos OS to a previous release.

This topic covers:

Overview of the Software Installation Process

An EX Series switch is delivered with a domestic version of Junos OS preinstalled. When you connect power to the switch, it starts (boots) from the installed software.

You upgrade Junos OS on an EX Series switch by copying a software package to your switch or another system on your local network, then use either the J-Web interface or the command-line interface (CLI) to install the new software package on the switch. Finally, you reboot the switch; it boots from the upgraded software. After a successful upgrade, you should back up the new current configuration to a secondary device. You should following this procedure regardless of whether you are installing a domestic or controlled Junos OS package.

During a successful upgrade, the upgrade package removes all files from /var/tmp and completely reinstalls the existing software. It retains configuration files, and similar information, such as secure shell and host keys, from the previous version. The previous software package is preserved in a separate disk partition, and you can manually revert back to it if necessary. If the software installation fails for any reason, such as loss of power during the installation process, the system returns to the originally active installation when you reboot.

Installing Software on a Virtual Chassis

You can connect individual EX Series switches together to form one unit and manage the unit as a single device, called a Virtual Chassis. The Virtual Chassis operates as a single network entity composed of member switches. Each member switch in a Virtual Chassis must be running the same version of Junos OS.

For ease of management, a Virtual Chassis provides flexible methods to upgrade software releases. You can deploy a new software release to all member switches of a Virtual Chassis or to only a particular member switch.

You can also upgrade the software on a Virtual Chassis using nonstop software upgrade (NSSU). NSSU takes advantage of graceful Routing Engine switchover (GRES) and nonstop active routing (NSR) to ensure no disruption to the control plane during the upgrade. You can minimize disruption to network traffic by defining link aggregation groups (LAGs) such that the member links of each LAG reside on different line cards or on different members . During an NSSU, the line cards and Virtual Chassis members are upgraded one at a time, so that traffic continues to flow through the other line cards or members while that line card or member is being upgraded.

Installing Software Using Automatic Software Download

The automatic software download feature uses the DHCP message exchange process to download and install software packages. Users can define a path to a software package on the DHCP server, and then the DHCP server communicates this path to EX Series switches acting as DHCP clients as part of the DHCP message exchange process. The DHCP clients that have been configured for automatic software download receive these messages and, when the software package name in the DHCP server message is different from that of the software package that booted the DHCP client switch, download and install the software package. See Upgrading Software by Using Automatic Software Download for Switches.

Autoinstalling a Configuration File on an EX2200 or EX3300 Switch from a Disk-on-Key USB Memory Stick

You can use an autoinstallation process to configure the software on an EX2200 or EX3300 switch. You can use a configuration file that is in either text format or XML format. If you want to use an XML-formatted file, you use a Junos Space platform to create the configuration file. You place the configuration file on a Disk-on-Key USB memory stick.

Installing Software on an EX2300 or EX3400 Switch

Before installing software on an EX2300 or EX3400 switch:

  • Ensure that at least 620 MB of disk space is available in the system before downloading the software installation package to the /var/tmp directory. Use the command show system storage to get details of the available space.

  • If the space available is inadequate, use the command request system storage cleanup. Additionally, you can manually delete any other log or unwanted files from the /var/tmp or /var/log directories.

You can now follow the procedure in Installing Software on an EX Series Switch with a Single Routing Engine (CLI Procedure) to complete the software installation.

Installing Software on an EX Series Switch with a Single Routing Engine (CLI Procedure)

You can use this procedure to upgrade Junos OS on a single routing engine in any EX Series switch, including all switches that do not support redundant Routing Engines. You can also use this procedure to upgrade software on all EX Series Virtual Chassis, with the exception of the EX8200 Virtual Chassis.

This procedure can be used to upgrade the following switches or Virtual Chassis:

  • EX2200 switch

  • EX2300 switch

  • EX3200 switch

  • EX3300 switch

  • EX3400 switch

  • EX4200 switch

  • EX4300 switch

  • EX4500 switch

  • EX4550 switch

  • EX6200 switch (single Routing Engine upgrade only)

  • EX8200 switch (single Routing Engine upgrade only)

  • All Virtual Chassis except EX8200 Virtual Chassis

To upgrade software on an EX6200 or EX8200 switch running two Routing Engines, see Installing Software on an EX Series Switch with Redundant Routing Engines (CLI Procedure) or Upgrading Software on an EX6200 or EX8200 Standalone Switch Using Nonstop Software Upgrade (CLI Procedure).

To upgrade software on an EX8200 Virtual Chassis, see Installing Software for All Devices in an EX8200 Virtual Chassis.

To install software upgrades on a switch with a single Routing Engine:

  1. Download the software package.
  2. (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.
  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 Junos OS can also be upgraded when the software image is stored at a remote location. These instructions describe the software upgrade process for both scenarios.

  4. Install the new package on the switch:

    Replace package with one of the following paths:

    • For a software package in a local directory on the switch—/var/tmp/package.tgz.

    • For a software package on a remote server:

      • ftp://hostname/pathname/package.tgz

      • http://hostname/pathname/package.tgz

    where package.tgz is, for example, jinstall-ex-4200-9.4R1.8-domestic-signed.tgz.

    Include the optional member option to install the software package on only one member of an EX4200 Virtual Chassis:

    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, for example, jinstall-ex-4200-10.2R1.8-domestic-signed.tgz. This is your last chance to stop the installation.

    The request system software delete package.tgz command is not available on EX2300 and EX3400 switches.

  5. Reboot to start the new software:
  6. After the reboot has completed, log in and verify that the new version of the software is properly installed:
  7. To ensure that the resilient dual-root partitions feature operates correctly, execute the following command to copy the new Junos OS image into the alternate root partition:

    To update the alternate root partitions on all members of a Virtual Chassis, use this command:

    Resilient dual-root partitions allow the switch to boot transparently from the alternate root partition if the system fails to boot from the primary root partition.

    Note

    EX2300 and EX3400 switches have two volumes: JUNOS volume and OAM (recovery) volume. To store a snapshot (non-recovery) on JUNOS volume, use the command request system snapshot. To create snapshot (recovery) on the OAM volume, use the command request system snapshot recovery.

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

You can install software on a switch with redundant Routing Engines in one of two ways:

  • Perform an NSSU—An NSSU upgrades both Routing Engines with a single command and with a minimum of network disruption. An NSSU takes advantage of GRES and NSR to ensure no disruption to the control plane. You can minimize disruption to network traffic by defining LAGs such that the member links of each LAG reside on different line cards. The line cards are upgraded one at a time, so that traffic continues to flow through the other line cards while a line card is being upgraded.

    You cannot use NSSU to downgrade the software running on a switch.

    For more information about NSSU, see Understanding Nonstop Software Upgrade on EX Series Switches.

  • Upgrade each Routing Engine manually—You can perform a Junos OS installation on each Routing Engine separately, starting with the backup Routing Engine. You can use this procedure to downgrade the software running on a switch.

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.4R3 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 EX6200 or 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

Perform the following steps before installing the software:

  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:

      You will see:
    2. Enter configuration mode:

      You will see:
  3. Disable nonstop active routing (NSR) (supported on switches running Junos OS Release 10.4 or later):
  4. Disable nonstop bridging:
  5. Disable graceful Routing Engine switchover (GRES):
  6. Save the configuration change on both Routing Engines:
    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.

  7. Exit the CLI configuration mode:

  8. (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

After you have prepared the switch for software installation, install the software on the backup Routing Engine. During the installation, the master Routing Engine continues operations, minimizing the disruption to network traffic.

  1. Download the software.
  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:

    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:

    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:

Installing Software on the Default Master Routing Engine

To transfer control to the backup Routing Engine and then upgrade or downgrade the master Routing Engine software:

  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.

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

    You will see:

  4. Install the new software package:

  5. Reboot the Routing Engine:

    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:

    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:
    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:
  10. To ensure that the resilient dual-root partitions feature operates correctly, execute the following command to copy the new Junos OS image into the alternate root partition on each Routing Engine:

    Resilient dual-root partitions allow the switch to boot transparently from the alternate root partition if the system fails to boot from the primary root partition.

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)

The switch can maintain normal operations with the Routing Engine in slot 1 acting as the master Routing Engine after the software upgrade, so only perform this task if you want to return routing control to the default master Routing Engine in slot 0.

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

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

    You will see:

Upgrading the Loader Software on the Line Cards in a Standalone EX8200 Switch or an EX8200 Virtual Chassis

You are almost never required to upgrade the loader software on the line cards in an EX8200 switch.

Upgrading the loader software version for a line card is not a requirement to complete any software upgrade. In rare cases, a line card might go offline immediately after a software upgrade because the loader software version on the line card requires an upgrade to become compatible with the upgraded Junos OS. You can upgrade the loader software on the line cards as a best practice to avoid this problem and other less severe issues.

The loader software on any line card in an EX8200 switch is updated using the same loader software package that upgrades the EX8200 Routing Engine loader software. The line card software loader contains two banks, each with a single loader software version. This procedure is used to upgrade the loader software for both banks of a line card in a standalone EX8200 switch or an EX8200 Virtual Chassis.

To upgrade the loader software on the line cards in a standalone EX8200 switch or an EX8200 Virtual Chassis:

Note

If you are upgrading Junos OS, the Routing Engine loader software, and the line card loader software, we recommend that you upgrade in this order: Junos OS, line card loader software, Routing Engine loader software.

  1. Determine the version of the loader software for the line cards:
    user@switch> show chassis firmware
    Note

    On an EX8200 Virtual Chassis, you cannot execute the show chassis firmware command on the master external Routing Engine. You must execute this command on each member switch.

    1. From the master external Routing Engine, start a shell session on the member switch, for example:
    2. Enter the CLI and execute the show chassis firmware command.
    3. Repeat these steps for the other member switch.

    The loader software version appears after the timestamp (see the Version column in the output) for each component. For example, In the example given in this step, look at the first FPC listed (FPC 6). Ignore the U-Boot version number (1.1.6) and find the loader software version number (2.3.0) after the timestamp (U-Boot 1.1.6 (Jan 13 2009 - 06:55:22). The U-Boot version number has nothing to do with the loader software version that you need to determine.

    If the loader software version is earlier than 3.5.0 for any FPC, you should consider upgrading the loader software for that line card.

  2. Download the loader software package from the Juniper Networks Download page (https://support-www.juniper.net/support/downloads/) and place the software package on an internal software distribution site or in a local directory on the switch. We recommend using /var/tmp as the local directory on the switch.Note

    To obtain the loader software package, see the Download Software page at https://support-www.juniper.net/support/downloads/. Select the OS type and the release. Then find and click the download image.

    A login screen appears.

  3. Log in with you user name and password.
  4. Disable graceful Routing Engine switchover (GRES) and nonstop active routing (NSR), if enabled. Commit the configuration:
  5. Install the loader package:

    Replace package with one of the following paths:

    • For a software package in the /var/tmp directory on the switch or external Routing Engine—/var/tmp/package.tgz.

    • For a software package on a remote server:

      • ftp://hostname/pathname/package.tgz

      • http://hostname/pathname/package.tgz

      In the above options, package.tgz might be, for example, jloader-ex-8200-11.3build-signed.tgz.

  6. Upgrade the loader software.
    • To upgrade the loader software for a line card on a standalone EX8200 switch:

      user@switch> request system firmware upgrade fpc slot slot-number
    • To upgrade the loader software for a line card on an EX8200 member switch in an EX8200 Virtual Chassis:

      user@switch> request system firmware upgrade fpc slot slot-number member member-id
  7. Confirm the loader software upgrade:
    user@switch> show system firmware

    The status is UPGRADED SUCCESSFULLY if the boot loader version update process is complete.

    The status is PROGRAMMING if the boot loader version update process is still in progress.

    Do not proceed to the next step until the show system firmware output confirms that the loader software upgrade is complete.

  8. Restart the line card.
    • To restart a line card on a standalone EX8200 switch:

      user@switch> request chassis fpc restart slot slot-number
    • To restart a line card on an EX8200 member switch in an EX8200 Virtual Chassis:

      user@switch> request chassis fpc restart slot slot-number member member-id
      Note

      You can monitor the status of the line card restart by using the show chassis fpc command.

  9. After the line card restart has completed, confirm the loader software version update:
    user@switch> show chassis firmware

    The current version has updated to 3.5.0. You have upgraded the loader software for one bank of the line card.

  10. Repeat Steps 4 through 7 to upgrade the loader software on the other bank of the line card.Note

    A bank switchover occurs automatically as part of the line card restart. Repeating Steps 3 through 6 updates the loader software on the other bank.

  11. Repeat Steps 4 through 8 for all other line cards that require a line card loader version upgrade.

Booting an EX Series Switch Using a Software Package Stored on a USB Flash Drive

There are two methods of getting Junos OS stored on a USB flash drive before using the software to boot the switch. You can pre-install the software onto the USB flash drive before inserting the USB flash drive into the USB port, or you can use the system snapshot feature to copy files from internal switch memory to the USB flash drive.

To move files into USB flash memory by using a system snapshot and use those files to boot the switch, see Creating a Snapshot and Using It to Boot an EX Series Switch. We recommend that you use this method to boot the switch from a USB flash drive if your switch is running properly.

If you need to pre-install the software onto the USB flash drive, you can use the method described in this topic. Pre-installing Junos OS onto a USB flash drive to boot the switch can be done at any time and is particularly useful when the switch boots to the loader prompt because the switch cannot locate the Junos OS in internal flash memory.

Ensure that you have the following tools and parts available to boot the switch from a USB flash drive:

  • A USB flash drive that meets the EX Series switch USB port specifications. See USB Port Specifications for an EX Series Switch.

  • A computer or other device that you can use to download the software package from the Internet and copy it to the USB flash drive.

To download a Junos OS package onto a USB flash drive before inserting the USB flash drive:

  1. Download the Junos OS package that you want to place onto the EX Series switch from the Internet onto the USB flash drive by using your computer or other device.
  2. Remove the USB flash drive from the computer or other device.
  3. Insert the USB flash drive into the USB port on the switch.
  4. This step can be performed only when the prompt for the loader script (loader>) is displayed. The loader script starts when the Junos OS loads but the CLI is not working for any reason or if the switch has no software installed.

    Install the software package onto the switch:

    where source represents the name and location of the Junos OS package on the USB flash drive. The Junos OS package on a flash drive is commonly stored in the root drive as the only file—for example, file://jinstall-ex-4200-9.4R1.5-domestic-signed.tgz.