Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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

Migration, Upgrade, and Downgrade Instructions

This section contains the procedure to upgrade Junos OS, and the upgrade and downgrade policies for Junos OS for Junos Fusion Provider Edge. Upgrading or downgrading Junos OS can take several hours, depending on the size and configuration of the network.

Basic Procedure for Upgrading an Aggregation Device

When upgrading or downgrading Junos OS, always use the jinstall package. Use other packages (such as the jbundle package) only when so instructed by a Juniper Networks support representative. For information about the contents of the jinstall package and details of the installation process, see the Installation and Upgrade Guide.

Note: Before upgrading, back up the file system and the currently active Junos OS configuration so that you can recover to a known, stable environment in case the upgrade is unsuccessful. Issue the following command:

user@host> request system snapshot

The installation process rebuilds the file system and completely reinstalls Junos OS. Configuration information from the previous software installation is retained, but the contents of log files might be erased. Stored files on the routing platform, such as configuration templates and shell scripts (the only exceptions are the juniper.conf and ssh files), might be removed. To preserve the stored files, copy them to another system before upgrading or downgrading the routing platform. See the Junos OS Administration Library for Routing Devices.

The download and installation process for Junos OS Release 14.2R7 is different from previous Junos OS releases.

  1. Using a Web browser, navigate to the Download Software URL on the Juniper Networks webpage:

    http://www.juniper.net/support/downloads/

  2. Log in to the Juniper Networks authentication system using the username (generally your e-mail address) and password supplied by Juniper Networks representatives.
  3. Select By Technology > Junos Platform > Junos Fusion to find the software that you want to download.
  4. Select the release number (the number of the software version that you want to download) from the Version drop-down list to the right of the page.
  5. Select the Software tab.
  6. Select the software package for the release.
  7. Review and accept the End User License Agreement.
  8. Download the software to a local host.
  9. Copy the software to the routing platform or to your internal software distribution site.
  10. Install the new jinstall package on the aggregation device.

    Note: We recommend that you upgrade all software packages out of band using the console because in-band connections are lost during the upgrade process.

    Customers in the United States and Canada, use the following commands.

    • For 64-bit software:

      Note: We highly recommend using 64-bit Junos OS software when implementing Junos Fusion.

      user@host> request system software add validate reboot source/jinstall64-14.2R7.5-domestic-signed.tgz
    • For 32-bit software:
      user@host> request system software add validate reboot source/jinstall-14.2R7.5-domestic-signed.tgz

    All other customers, use the following commands.

    • For 64-bit software:

      Note: We highly recommend using 64-bit Junos OS software when implementing Junos Fusion.

      user@host> request system software add validate reboot source/jinstall64-14.2R7.5-export-signed.tgz
    • For 32-bit software:
      user@host> request system software add validate reboot source/jinstall-14.2R7.5-export-signed.tgz

    Replace source with one of the following values:

    • /pathname—For a software package that is installed from a local directory on the router.
    • For software packages that are downloaded and installed from a remote location:

      • ftp://hostname/pathname
      • http://hostname/pathname
      • scp://hostname/pathname (available only for Canada and U.S. version)

    The validate option validates the software package against the current configuration as a prerequisite to adding the software package to ensure that the router reboots successfully. This is the default behavior when the software package being added is a different release.

    Adding the reboot command reboots the router after the upgrade is validated and installed. When the reboot is complete, the router displays the login prompt. The loading process can take 5 to 10 minutes.

    Rebooting occurs only if the upgrade is successful.

Note: After you install a Junos OS Release 14.2R7 jinstall package, you cannot issue the request system software rollback command to return to the previously installed software. Instead you must issue the request system software add validate command and specify the jinstall package that corresponds to the previously installed software.

Upgrading an Aggregation Device with Redundant Routing Engines

If the aggregation device has two Routing Engines, perform a Junos OS installation on each Routing Engine separately to minimize disrupting network operations as follows:

  1. Disable graceful Routing Engine switchover (GRES) on the master Routing Engine and save the configuration change to both Routing Engines.
  2. Install the new Junos OS release on the backup Routing Engine while keeping the currently running software version on the master Routing Engine.
  3. After making sure that the new software version is running correctly on the backup Routing Engine, switch over to the backup Routing Engine to activate the new software.
  4. Install the new software on the original master Routing Engine that is now active as the backup Routing Engine.

For the detailed procedure, see the Installation and Upgrade Guide.

Preparing the Switch for Satellite Device Conversion

Satellite devices in a Junos Fusion topology use a satellite software package that is different from the standard Junos OS software package. Before you can install the satellite software package on a satellite device, you first need to upgrade the target satellite device to an interim Junos OS software version that can be converted to satellite software. Table 2 shows a support matrix that maps Junos OS software used in aggregation devices to the compatible preconverted switch software and satellite device software.

Table 2: Aggregation Device Junos OS Software Compatibility with Satellite Software

Aggregation Device Version

Switch Version

Satellite Device Software Version

Junos OS Release 14.2R3

Junos OS Release 14.1X53-D16 or later

1.0R1

Junos OS Release 14.2R4

Junos OS Release 14.1X53-D25 or later

1.0R1-S2

Junos OS Release 14.2R5

Junos OS Release 14.1X53-D30 or later

1.0R2

Junos OS Release 14.2R6

Junos OS Release 14.1X53-D30 or later

1.0R3

Junos OS Release 14.2R7

Junos OS Release 14.1X53-D30 or later

1.0R4

Customers with EX4300 switches, use the following command:

user@host> request system software add validate reboot source/jinstall-ex-4300-14.1X53-D30.3-domestic-signed.tgz

Customers with QFX5100 switches, use the following command:

user@host> request system software add validate reboot source/jinstall-qfx-5-14.1X53-D30.3-domestic-signed.tgz

When the interim installation has completed and the switch is running a version of Junos OS that is compatible with satellite device conversion, perform the following steps:

  1. Log in to the device using the console port.
  2. Clear the device:
    [edit]
    user@satellite-device# request system zeroize

    Note: The device reboots to complete the procedure for resetting the device.

    If you are not logged in to the device using the console port connection, your connection to the device is lost after entering the request system zeroize command.

    If you lose your connection to the device, log in using the console port.

  3. (EX4300 switches only) After the reboot is complete, convert the built-in 40-Gbps QSFP+ interfaces from Virtual Chassis ports (VCPs) into network ports:
    user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port port-number

    For example, to convert all four built-in 40-Gbps QSFP+ interfaces on an EX4300-24P switch into network ports:

    user@satellite-device>request virtual-chassis vc-port delete pic-slot 1 port 0
    user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port 1
    user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port 2
    user@satellite-device> request virtual-chassis vc-port delete pic-slot 1 port 3

    This step is required for the 40-Gbps QSFP+ interfaces that will be used as uplink interfaces in a Junos Fusion topology. Built-in 40-Gbps QSFP+ interfaces on EX4300 switches are configured into VCPs by default, and the default settings are restored after the device is reset.

After this initial preparation, you can use one of three methods to convert your switches into satellite devices—autoconversion, manual conversion, and preconfiguration.

Autoconverting a Switch into a Satellite Device

Use this procedure to automatically configure a switch into a satellite device when it is cabled into the aggregation device.

You can use the autoconversion procedure to add one or more satellite devices to your Junos Fusion topology. The autoconversion procedure is especially useful when you are adding multiple satellite devices to Junos Fusion, because it allows you to easily configure the entire topology before or after cabling the satellite devices to the aggregation devices.

Before you begin:

  • Ensure that your aggregation device is running Junos OS Release 14.2R5 or later, and that the satellite devices are running Junos OS Release 14.1X53-D30 or later.

To autoconvert a switch into a satellite device:

  1. Cable a link between the aggregation device and the satellite device, if desired.

    Note: You can cable the aggregation device to the satellite device at any point in this procedure.

    When the aggregation device is cabled to the satellite device during this procedure, the process for converting a switch into a satellite device to finalize this process occurs immediately.

    If the aggregation device is not cabled to the satellite device, the process for converting a switch into a satellite device to finalize this process starts when the satellite device is cabled to the aggregation device.

  2. Log in to the aggregation device.
  3. Configure the cascade ports.

    For example, to configure interface xe-0/0/1 on the aggregation device into a cascade port:

    [edit]
    user@aggregation-device# set interfaces xe-0/0/1 cascade-port
  4. Associate an FPC slot ID with each satellite device.

    Examples:

    • To configure the FPC slot ID of the satellite device that is connected to xe-0/0/1 to 101:
      [edit]
      user@aggregation-device# set chassis satellite-management fpc 101 cascade-ports xe-0/0/1
    • To map FPC slot ID 101 to the satellite device using the serial number ABCDEFGHIJKL:
      [edit]
      user@aggregation-device# set chassis satellite-management fpc 101 serial-number ABCDEFGHIJKL
    • To map FPC slot ID to the satellite device using MAC address 12:34:56:AB:CD:EF:
      [edit]
      user@aggregation-device# set chassis satellite-management fpc 110 system-id 12:34:56:AB:CD:EF
  5. (Recommended) Configure an alias name for the satellite device:
    [edit]
    user@aggregation-device# set chassis satellite-management fpc slot-id alias alias-name

    where slot-id is the FPC slot ID of the satellite device defined in the previous step, and alias-name is the alias.

    For example, to configure the satellite device numbered 101 as qfx5100-48s-1:

    [edit]
    user@aggregation-device# set chassis satellite-management fpc 101 alias qfx5100-48s-1
  6. Configure an FPC slot ID into a software upgrade group.

    For example, to add a satellite device with FPC number 101 to an existing software group named group1, or create a software upgrade group named group1 and add a satellite device with FPC slot 101 to the group:

    [edit]
    user@aggregation-device# set chassis satellite-management upgrade-group group1 satellite 101

    If you are creating a new software upgrade group in this step, you also need to associate the group with a satellite software image. You can skip this final step if the software upgrade group has been created and an association already exists.

    Before associating a satellite software image with a satellite software group, the configuration with the satellite software upgrade group must be committed:

    [edit]
    user@satellite-device# commit synchronize

    After committing the configuration, associate a satellite software image named satellite-1.0R4.2-signed.tgz to the upgrade group named group1:

    user@aggregation-device> request system software add /var/tmp/satellite-1.0R4.2-signed.tgz upgrade-group group1
  7. Enable automatic satellite conversion:
    [edit]
    user@aggregation-device# set chassis satellite-management auto-satellite-conversion satellite slot-id

    For example, to automatically convert FPC 101 into a satellite device:

    [edit]
    user@aggregation-device# set chassis satellite-management auto-satellite-conversion satellite 101
  8. Commit the configuration:
    [edit]
    user@aggregation-device# commit

    If you want to commit the configuration to both Routing Engines:

    [edit]
    user@aggregation-device# commit synchronize

    The satellite software upgrade on the satellite device begins after this final step is completed, or after you cable the satellite device to a cascade port using automatic satellite conversion if you have not already cabled the satellite device to the aggregation device.

    After the satellite software update, the switch operates as a satellite device in the Junos Fusion topology

Manually Converting a Switch into a Satellite Device

Use this procedure to manually convert a switch into a satellite device after cabling it into the Junos Fusion topology.

This procedure should be used to convert a switch that is not currently acting as a satellite device into a satellite device. A switch might not be recognized as a satellite device for several reasons, including that the device was not previously autoconverted into a satellite device or that the switch had previously been reverted from a satellite device to a standalone switch.

Before you begin:

  • Ensure that your aggregation device is running Junos OS Release 14.2R5 or later, and that the switches that will become satellite devices are running Junos OS Release 14.1X53-D30 or later.

To manually convert a switch into a satellite device:

  1. Cable a link between the aggregation device and the satellite device.
  2. Log in to the aggregation device.
  3. Configure the link on the aggregation device into a cascade port, if you have not done so already.

    For example, to configure interface xe-0/0/1 on the aggregation device into a cascade port:

    [edit]
    user@aggregation-device# set interfaces xe-0/0/1 cascade-port
  4. Associate an FPC slot ID with the satellite device.

    Examples:

    • To configure the FPC slot ID of the satellite device that is connected to xe-0/0/1 to 101:
      [edit]
      user@aggregation-device# set chassis satellite-management fpc 101 cascade-ports xe-0/0/1
    • To map FPC slot ID 101 to the satellite device using the serial number ABCDEFGHIJKL:
      [edit]
      user@aggregation-device# set chassis satellite-management fpc 101 serial-number ABCDEFGHIJKL
    • To map FPC slot ID to the satellite device using MAC address 12:34:56:AB:CD:EF:
      [edit]
      user@aggregation-device# set chassis satellite-management fpc 110 system-id 12:34:56:AB:CD:EF
  5. Configure the interface on the aggregation device into a software upgrade group.

    For example, to add a satellite device with FPC number 101 to an existing software group named group1, or create a software upgrade group named group1 and add a satellite device configured with FPC number 101 to the group:

    [edit]
    user@aggregation-device# set chassis satellite-management upgrade-group group1 satellite 101

    If you are creating a new software upgrade group in this step, you also need to associate the group with a satellite software image. You can skip this final step if the software upgrade group has been created and an association already exists.

    Before associating a satellite software image with a satellite software group, the configuration with the satellite software upgrade group must be committed:

    [edit]
    user@satellite-device# commit synchronize

    After committing the configuration, associate a satellite software image named satellite-1.0R4.2-signed.tgz to the upgrade group named group1:

    user@aggregation-device> request system software add /var/tmp/satellite-1.0R4.2-signed.tgz upgrade-group group1
  6. Manually configure the switch into a satellite device:
    user@aggregation-device> request chassis satellite interface interface-name device-mode satellite

    For example, to manually configure the switch that is connecting the satellite device to interface xe-0/0/1 on the aggregation device into a satellite device:

    user@aggregation-device> request chassis satellite interface xe-0/0/1 device-mode satellite

    The satellite software upgrade on the satellite device begins after this final step is completed.

    After the satellite software update, the switch operates as a satellite device in the Junos Fusion topology

Configuring a Switch into a Satellite Device Before Connecting It to a Junos Fusion Topology

Use this procedure to install the satellite software onto a switch before interconnecting it into a Junos Fusion topology as a satellite device. Installing the satellite software on a switch before interconnecting it to a Junos Fusion topology allows you to more immediately deploy the switch as a satellite device by avoiding the downtime associated with the satellite software installation procedure for Junos Fusion.

Before you begin:

  • Ensure that your switch that will become a satellite device is running Junos OS Release 14.1X53-D30 or later.
  • Ensure that you have copied the satellite software onto the device that will become a satellite device.

    Note: Ensure there is sufficient space available in the /var/tmp directory to be able to copy the software to the switch (especially for EX4300 switches). If there is not enough memory available, issue the request system storage cleanup command on the device before attempting to perform the conversion.

    In satellite software release 1.0R3 and later, a satellite-ppc-release-signed.tgz package is included specifically for converting Junos OS to satellite software on an EX4300 switch to address a memory space issue. The satellite-ppc package is to be used only for configuring a standalone EX4300 switch into a satellite device before connecting it to a Junos Fusion topology.

  1. You can manually install the satellite software onto a switch by entering the following command:
    user@satellite-device> request chassis device-mode satellite URL-to-satellite-software

    For instance, to install the satellite software package satellite-1.0R4.2-signed.tgz stored in the /var/tmp/ directory on the switch:

    user@satellite-device> request chassis device-mode satellite /var/tmp/satellite-1.0R4.2-signed.tgz
    • To install satellite software onto a QFX5100 switch, use the satellite-1.0R4.2-signed.tgz satellite software package.
    • To install satellite software onto a EX4300 switch, use the satellite-ppc-1.0R4.2-signed.tgz satellite software package.
  2. The device will reboot to complete the satellite software installation.

After the satellite software is installed, follow this procedure to connect the switch into a Junos Fusion topology:

  1. Log in to the aggregation device.
  2. Configure the link on the aggregation device into a cascade port, if you have not done so already.

    For example, to configure interface xe-0/0/1 on the aggregation device into a cascade port:

    [edit]
    user@aggregation-device# set interfaces xe-0/0/1 cascade-port
  3. Configure the satellite switch into a satellite software upgrade group that is using the same version of satellite software that was manually installed onto the switch.

    This step is advisable, but not always required. Completing this step ensures that the satellite software on your device is upgraded to the version of satellite software associated with the satellite software upgrade group when the satellite device connects to the aggregation device.

  4. Commit the configuration.

    To commit the configuration to both Routing Engines:

    [edit]
    user@aggregation-device# commit synchronize

    To commit the configuration to a single Routing Engine:

    [edit]
    user@aggregation-device# commit
  5. Cable a link between the aggregation device and the satellite device.

Configuring Satellite Device Upgrade Groups

To simplify the upgrade process for multiple satellite devices, you can create a software upgrade group at the aggregation device, assign satellite devices to the group, and install the satellite software on a groupwide basis.

To create a software upgrade group and assign satellite devices to the group, include the satellite statement at the [edit chassis satellite-management upgrade-groups upgrade-group-name] hierarchy level.

To configure a software upgrade group and assign satellite devices to the group:

  1. Log in to the aggregation device.
  2. Create the software upgrade group, and add the satellite devices to the group.
    [edit]
    user@aggregation-device# set chassis satellite-management upgrade-groups upgrade-group-name satellite satellite-member-number-or-range

upgrade-group-name is the name of the upgrade group, and the satellite-member-number-or-range is the member numbers of the satellite devices that are being added to the upgrade group. If you enter an existing upgrade group name as the upgrade-group-name, you add new satellite devices to the existing software upgrade group.

For example, to create a software upgrade group named group1 that includes all satellite devices numbered 101 through 120, configure the following:

[edit]
user@aggregation-device# set chassis satellite-management upgrade-groups group1 satellite 101-120

To install, remove, or roll back a satellite software version on an upgrade group, issue the following operational mode commands:

  • request system software add upgrade-group group-name—Install the satellite software on all members of the specified upgrade group.
  • request system software delete upgrade-group group-name—Remove the satellite software association from the specified upgrade group.
  • request system software rollback upgrade-group group-name—Associate an upgrade group with a previous version of satellite software.

Customers installing satellite software on EX4300 and QFX5100 switches referenced in a software upgrade group, use the following command:

user@aggregation-device> request system software add upgrade-group group-name source/satellite-1.0R4.2-signed.tgz

A copy of the satellite software is saved on the aggregation device. When you add a satellite device to an upgrade group that is not running the same satellite software version, the new satellite device is automatically updated to the version of satellite software that is associated with the upgrade group.

You can issue the show chassis satellite software command to see which software images are stored on the aggregation device and which upgrade groups are associated with the software images.

Converting a Satellite Device to a Standalone Device

In the event that you need to convert a satellite device to a standalone device, you will need to install a new Junos OS software package on the satellite device and remove it from the Junos Fusion topology.

Note: If the satellite device is a QFX5100 switch, you need to install a PXE version of Junos OS. The PXE version of Junos OS is the software that includes pxe in the Junos OS package name when it is downloaded from the Software Center—for example, the PXE image for Junos OS Release 14.1X53-D30 is named install-media-pxe-qfx-5-14.1X53-D30.3.tgz. If the satellite device is an EX4300 switch, you install a standard jinstall-ex-4300 version of Junos OS.

The following steps explain how to download software, remove the satellite device from Junos Fusion, and install the Junos OS software image on the satellite device so that the device can operate as a standalone device.

  1. Using a Web browser, navigate to the Junos OS software download URL on the Juniper Networks webpage:

    http://www.juniper.net/support/downloads

  2. Log in to the Juniper Networks authentication system using the username (generally your e-mail address) and password supplied by Juniper Networks representatives.
  3. Select By Technology > Junos Platform > Junos Fusion from the drop-down list and select the switch platform series and model for your satellite device.
  4. Select the Junos OS Release 14.1X53-D30 software image for your platform.
  5. Review and accept the End User License Agreement.
  6. Download the software to a local host.
  7. Copy the software to the routing platform or to your internal software distribution site.
  8. Remove the satellite device from the automatic satellite conversion configuration.

    If automatic satellite conversion is enabled for the satellite device’s member number, remove the member number from the automatic satellite conversion configuration. The satellite device’s member number is the same as the FPC slot ID. You can check the automatic satellite conversion configuration by entering the show command at the [edit chassis satellite-management auto-satellite-conversion] hierarchy level.

    [edit]
    user@aggregation-device# delete chassis satellite-management auto-satellite-conversion satellite member-number

    For example, to remove member number 101 from Junos Fusion:

    [edit]
    user@aggregation-device# delete chassis satellite-management auto-satellite-conversion satellite 101
  9. Commit the configuration.

    To commit the configuration to both Routing Engines:

    [edit]
    user@aggregation-device# commit synchronize

    Otherwise, commit the configuration to a single Routing Engine:

    [edit]
    user@aggregation-device# commit
  10. Install the Junos OS software on the satellite device to convert the device to a standalone device.
    [edit]
    user@aggregation-device> request chassis satellite install URL-to-software-package fpc-slot member-number

    For example, to install a PXE software package stored in the /var/tmp directory on the aggregation device onto a QFX5100 switch acting as the satellite device using FPC slot 101:

    [edit]
    user@aggregation-device> request chassis satellite install /var/tmp/install-media-pxe-qfx-5-14.1X53-D30.3.tgz fpc-slot 101

    For example, to install a software package stored in the var/tmp directory on the aggregation device onto an EX4300 switch acting as the satellite device using FPC slot 101:

    [edit]
    user@aggregation-device> request chassis satellite install /var/tmp/jinstall-ex-4300-14.1X53-D30.3-domestic-signed.tgz fpc-slot 101

    The satellite device stops participating in the Junos Fusion topology once the software installation starts. The software upgrade starts after this command is entered.

  11. Wait for the reboot that accompanies the software installation to complete.
  12. When you are prompted to log back into your device, uncable the device from the Junos Fusion topology. See Removing a Transceiver from a QFX Series Device or Removing a Transceiver, as needed. Your device has been removed from Junos Fusion.

    Note: The device uses a factory default configuration after the Junos OS installation is complete.

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 on EEOL releases and to review a list of EEOL releases, see http://www.juniper.net/support/eol/junos.html

Downgrading from Release 14.2

To downgrade from Release 14.2 to another supported release, follow the procedure for upgrading, but replace the 14.2 jinstall package with one that corresponds to the appropriate release.

Note: You cannot downgrade more than three releases. For example, if your routing platform is running Junos OS Release 11.4, you can downgrade the software to Release 10.4 directly, but not to Release 10.3 or earlier; as a workaround, you can first downgrade to Release 10.4 and then downgrade to Release 10.3.

For more information, see the Installation and Upgrade Guide.

Related Documentation

Modified: 2017-02-20