The EX2200 includes an enhanced limited lifetime hardware warranty that provides next business day advance hardware switch replacement for as long as the original purchaser owns the product. The warranty includes lifetime software updates, advanced shipping of spares within one business day, and 24x7 JTAC support for 90 days after the purchase. Help us improve your experience. Let us know what you think. Do you have time for a two-minute survey?

Perform the following steps: Prepare a TFTP server and put the corresponding image in the TFTP root directory. For example, the IP address of the TFTP server is 192.168.100.1/24 and the filename of the image is jinstall-ex-10.0R2-domestic-signed.tgz. All Juniper EX Access switches only see Fiber ports when an Optic is plugged in; they all function this way, I believe. The initial plan was to connect two racks with EX3300 - EX2200 using these modules, and later, after EX2200 replacement, move to 10GE. Directly connect the EX Series device's management port to the TFTP server, or make sure that they are in the same broadcast domain. Connect a terminal to the EX Series device's console port and power-on the switch. When Loading /boot/defaults/loader.conf is displayed, press Enter: Hit Enter to boot immediately, or space bar for command prompt.

EX Series devices are delivered with pre-installed 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 and Junos OS Evolved Installation Package Names.

Understanding Software Installation on EX Series Switches

A Juniper Networks EX Series Ethernet Switch is delivered withthe Juniper Networks Junos operating system (Junos OS) pre-installed.As new features and software fixes become available, you must upgradeyour software to use them. You can also downgrade Junos OS to a previousrelease.

This topic covers:

Juniper Ex2200 Firmware Update How To Download

Overview of the Software Installation Process

An EX Series switch is delivered with a domestic version ofJunos OS pre-installed. 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 softwarepackage to your switch or another system on your local network, thenuse either the J-Web interface or the command-line interface (CLI)to install the new software package on the switch. Finally, you rebootthe switch; it boots from the upgraded software. After a successfulupgrade, you should back up the new current configuration to a secondarydevice. You should following this procedure regardless of whetheryou are installing a domestic or controlled Junos OS package.

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

Installing Software on a Virtual Chassis

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

For ease of management, a Virtual Chassis provides flexiblemethods to upgrade software releases. You can deploy a new softwarerelease to all member switches of a Virtual Chassis or to only a particularmember switch.

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

Installing Software Using Automatic Software Download

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

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

You can use an autoinstallation process to configure the softwareon an EX2200 or EX3300 switch. You can use a configuration file thatis in either text format or XML format. If you want to use an XML-formattedfile, 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 availablein the system before downloading the software installation packageto the /var/tmp directory. Use thecommand show system storage to get details of the availablespace.

• If the space available is inadequate, use the command request system storage cleanup. Additionally, you can manuallydelete 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 Virtual Chassis or Single Routing Engine (CLI Procedure) to complete the software installation.

Note:

See the Knowledge Base for more information in regards to storage whenupgrading Junos OS on EX2300 and EX3400 switches.

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

You can use this procedure to upgrade Junos OS on a singlerouting engine in any EX Series switch, including all switches thatdo not support redundant Routing Engines. You can also use this procedureto upgrade software on all EX Series Virtual Chassis, with the exceptionof the EX8200 Virtual Chassis.

This procedure can be used to upgrade the following switchesor 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 twoRouting Engines, see Installing Software on an EX Series Switch with Redundant Routing Engines (CLI Procedure) or Upgrading Software on an EX6200 or EX8200 StandaloneSwitch 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 singleRouting Engine:

1. Download the software package.
2. (Optional) Back up the current software configurationto 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. Werecommend that you use FTP to copy the file to the /var/tmp directory.

   This step is optional because Junos OS can also be upgradedwhen the software image is stored at a remote location. These instructionsdescribe the software upgrade process for both scenarios.

4. Install the new package on the switch:
   Note:

   Include the optional member option to install the software package on only one member of a VirtualChassis:

   Note:

   To terminate the installation, do not reboot your device;instead, finish the installation and then issue the request systemsoftware deletepackage.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 deletepackage.tgz command is not available on EX2300 and EX3400switches.

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

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

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

   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).

   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 Virtual Chassis or 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 primary 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:

   Preparing the Switch for the Software Installation

   Perform the following steps before installing the software:

   Juniper Ex2200 Firmware Update How To Change

   1. Log in to the primary 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. 
         
      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 terminate 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.

   7. Reboot to start the new software:

      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.

   8. Verify that the default backup Routing Engine (shown as slot 1 in the command output) is now the primary Routing Engine:
   9. Install the new software package:
   10. Reboot the Routing Engine:

       When the reboot completes, the prompt will reappear. Wait for this prompt to reappear before proceeding to the next step.

   11. Log in to the default backup Routing Engine (slot 1) through the console port.
   12. 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.

   13. Re-enable nonstop active routing:
       Note:

       On an EX8200 Virtual Chassis, you cannot issue the show chassis firmware command on the primary external RoutingEngine. You must issue this command on each member switch.

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

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

       If the loader software version is earlier than 3.5.0 for anyFPC, you should consider upgrading the loader software for that linecard.

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

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

8. After the line card restart has completed, confirm theloader software version update:

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

9. Repeat Steps 4 through 7 to upgrade the loader softwareon the other bank of the line card.

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

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

      Install the software package onto the switch:

      where source representsthe 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 rootdrive as the only file—for example, file:///jinstall-ex-4200-9.4R1.5-domestic-signed.tgz.

   See Also

   Related Documentation