Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    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
    • EX3200 switch
    • EX3300 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 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 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:
      user@switch> request system software add package

      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:

      user@switch> request system software add source member member-id reboot

      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.

    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:
      user@switch> show version
    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:
      user@switch> request system snapshot slice alternate

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

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

      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.

    Published: 2014-04-23