Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Installing Software on Routing Devices

 

Routing devices are delivered with Junos OS preinstalled on them. As new features and software fixes become available, you must upgrade Junos OS to use them. You can install software on single and redundant routing engines.

Installing the Software Package on a Device with a Single Routing Engine

With the exception of installing software for Junos OS Evolved, before you install a new software release on a device, you should back up the current system.

In the case of Junos OS Evolved, there is no need to back up the system, and there is no request system snapshot command. Multiple releases of the software can be installed on the device simultaneously. When a new release is installed, if there is no space, the least recently installed release is removed.

For more information on backing up Junos OS, see Backing Up the Existing Installation on Routers.

To upgrade the software on a router or switch:

  1. Install the new software package using the request system software add command:

    The variable installation-package is the name of the installation package. Specify the absolute path on the local disk, for example, for Junos OS Evolved, /var/tmp/junos-linux-install-ptx.iso. For package name prefixes, see Junos OS Installation Packages Prefixes.

    Note

    (Does not apply to Junos OS Evolved) To install multiple software packages at one time, you can use the request system software add set command. For more information on this command, see the set option in request system software add.

    Warning

    Do not include the re0 | re1 option when you install a package using the request system software add command, if the Routing Engine on which the package is located and the Routing Engine on which you want to install the package are the same. In such cases, the package gets deleted after a successful upgrade.

  2. Reboot the device to start the new software:
    • To reboot using Junos OS Evolved, use the request system shutdown reboot command.

    • To reboot using Junos OS, use the request system reboot command.

    Note

    You must reboot the device to load the new software release on the device.

    To abort the installation, do not reboot the device. Instead, finish the installation and then issue the request system software delete package-name command. This is your last chance to stop the installation.

    The software is loaded when you reboot the system. Installation can take between 5 and 10 minutes. The device then reboots from the boot device on which the software was just installed. When the reboot is complete, the device displays the login prompt.

    While the software is being upgraded, the Routing Engine on which you are performing the installation does not route traffic.

  3. Log in and verify the release of the software installed:
    • To verify release for installation of a Junos OS Evolved release, use the request system software list command.

    • To verify release for installation of a Junos OS release, use the show version command.

  4. (Does not apply to Junos OS Evolved.) After you have upgraded or downgraded the software and are satisfied that the new software is successfully running, issue the request system snapshot command to back up the new software.

Installing the Software Package on a Device with Redundant Routing Engines

If the device has two Routing Engines, perform a Junos OS installation on each Routing Engine separately to minimize disruption to network operation.

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. For detailed procedures, see the following subsections:

  1. Preparing the Device for the Installation

  2. Installing Software on the Backup Routing Engine

  3. Installing Software on the Remaining Routing Engine

  4. Finalizing the Installation

Preparing the Device for the Installation

Determine if this is the best procedure for upgrading your device:

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 deactivate GRES (if it is enabled). 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 ensure GRES and NSR are disabled:

  1. Log in to the primary Routing Engine’s console.

    For more information about logging in to the Routing Engine through the console port, see the specific hardware guide for your device.

  2. From the CLI operational prompt, enter configuration mode:

  3. Disable nonstop active routing (NSR) (supported on switches running Junos OS Release 10.4 or later):

  4. Disable nonstop-bridging if it is enabled:

  5. Disable Routing Engine redundancy if enabled:

  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:

Installing Software on the Backup Routing Engine

After the device has been prepared, 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. This enables the primary Routing Engine to continue operations, minimizing disruption to your network.

Before you start this procedure, decide which software package you need and download it to the /var/tmp directory of the primary Routing Engine. For information on which packages to use for which upgrades, see Junos OS Installation Package Names.

To install software on the backup Routing Engine:

  1. Log in to the console port on the current primary Routing Engine in slot 0.

  2. Install the new software package on the backup Routing Engine (re1) using the request system software add command:

    Installation and validation take about 15 minutes.

    Warning

    Do not include the re0 or re1 option when you install a package using the request system software add command if the Routing Engine on which the package is located and the Routing Engine on which you want to install the package are the same. In such cases, the package gets deleted after a successful upgrade.

    For M Series, MX Series, and T Series routers running Junos OS Release 12.2 and later, you can use the request system software add set command to install multiple software packages at the same time:

    For more information about the request system software add set command, see request system software add or the CLI Explorer.

  3. Reboot the backup Routing Engine to start the new software:

    You must reboot the device to load the new installation of Junos OS on the device. You can combine steps 2 and 3 by adding reboot to the request system software add command. But if you do the steps separately, make sure you reboot the Routing Engine you just added system software to.

    Note

    To abort the installation, do not reboot your device. Instead, finish the installation and then issue the request system software delete software-package-name command. This is your last chance to stop the installation.

    All the software is loaded when you reboot the device. Installation can take between 5 and 10 minutes. The device then reboots from the boot device on which the software was just installed. When the reboot is complete, the device displays the login prompt.

    While the software is being upgraded, the Routing Engine on which you are performing the installation is not routing traffic.

  4. Issue the show version invoke-on other-routing-engine command to verify the new software is installed.

  5. (Optional) Add the jweb package using the request system software add command. Before you can add this package, you must first download the software as you did the installation package. For more information about downloading the jweb package, see Downloading Software.

    The jweb installation module adds a router management graphical user interface that you can use to view and configure your router.

Installing Software on the Remaining Routing Engine

Once the software is installed on the backup Routing Engine, you are ready to switch routing control to the backup Routing Engine, and then upgrade or downgrade the software on the remaining Routing Engine in slot 0.

To install software on the primary Routing Engine:

  1. Transfer routing control from the primary to the backup Routing Engine:

    For more information about the request chassis routing-engine master command, see the CLI Explorer.

  2. Verify that the Routing Engine in slot 1 is now the primary Routing Engine:

  3. Install the new software package on the Routing Enigne in slot 0 using the request system software add command:

    Installation and validation take about 15 minutes.

    Warning

    Do not include the re0 or re1 option when you install a package using the request system software add command if the Routing Engine on which the package is located and the Routing Engine on which you want to install the package are the same. In such cases, the package gets deleted after a successful upgrade.

    For M Series, MX Series, and T Series routers running Junos OS Release 12.2 and later, you can use the request system software add set command to install multiple software packages at the same time:

    For more information about the request system software add set command, see request system software add or the CLI Explorer.

  4. Reboot the Routing Engine using the request system reboot command:

    You must reboot the device to load the new installation of Junos OS on the device. You can combine steps 3 and 4 by adding reboot to the request system software add command. But if you do the steps separately, make sure you reboot the Routing Engine you just added system software to.

    Note

    To abort the installation, do not reboot your device. Instead, finish the installation and then issue the request system software delete software-package-name command. This is your last chance to stop the installation.

    The software is loaded when you reboot the system. Installation can take between 5 and 10 minutes. The device then reboots from the boot device on which the software was just installed. When the reboot is complete, the device displays the login prompt.

    While the software is being upgraded, the Routing Engine on which you are performing the installation does not route traffic.

  5. Log in to the current backup Routing Engine (slot 0) and issue the show version command to verify the version of the software installed.

  6. (Optional) Add the jweb package using the request system software add command. Before you can add this package, you must first download the software as you did the installation package. For more information about downloading the jweb package, see Downloading Software.

    The jweb installation module adds a router management graphical user interface that you can use to view and configure your router.

Finalizing the Installation

Once the software is installed on both Routing Engines, you return the router back to its original configuration and back up the new installation.

To finalize the redundant Routing Engines upgrade:

  1. Restore the configuration that existed before you started this procedure (from Preparing the Device for the Installation):

    Note

    The number on the rollback command should match the number of commits you did in preparing the router for the installation. For example, if you did a separate commit for disabling Routing Engine redundancy and disabling nonstop-bridging, you need to use rollback 2 in this step.

  2. Save the configuration change on both Routing Engines:

  3. Transfer routing control back to the original primary Routing Engine in slot 0:

    For more information about the request chassis routing-engine master command, see the CLI Explorer.

  4. Verify that the Routing Engine (slot 0) is indeed the primary Routing Engine:

  5. After you have installed the new software and are satisfied that it is successfully running, back up the new software on both primary and backup Routing Engines.

    The root file system is backed up to /altroot, and /config is backed up to /altconfig. The root and /config file systems are on the router’ s CompactFlash card, and the /altroot and /altconfig file systems are on the router’ s hard disk or solid-state drive (SSD).

    For more information about the request system snapshot command, see the CLI Explorer .

    Note

    After you issue the request system snapshot command, you cannot return to the previous version of the software because the running copy and backup copy of the software are identical.