Junos OS Release Notes for Junos Fusion Data Center

 

These release notes accompany Junos OS Release 17.4R2 for the Junos Fusion Data Center. They describe new and changed features, limitations, and known and resolved problems in the hardware and software.

You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located at https://www.juniper.net/documentation/product/en_US/junos-os.

New and Changed Features

There are no new features in Junos OS Release 17.4R2 for Junos Fusion Data Center.

Changes in Behavior and Syntax

There are no changes in behavior and syntax for Junos Fusion Data Center in Junos OS Release 17.4R2.

Known Behavior

This section lists known behavior, system maximums, and limitations in hardware and software in Junos OS Release 17.4R2 for Junos Fusion Data Center.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Junos Fusion Data Center

  • The license installed will not be deleted, unless it is explicitly deleted using the request command. After disabling the cascade port, the license count will be marked as zero only after the satellite information is purged from the neighbor database. Previously, this satellite neighbor information persisted only for 8 minutes; now, neighbor information is being held for 8 hours. This time delay is introduced to avoid repeating the initial recognition of the satellite device for interface-down events. As a workaround, delete the FPC instance for the satellite device to see the license removed for the corresponding satellite device. PR1294951

Known Issues

There are no known issues in hardware and software in Junos OS Release 17.4R2 for Junos Fusion Data Center.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Resolved Issues

This section lists the issues fixed in the Junos OS Release 17.4R2 for Junos Fusion Data Center.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Resolved Issues: Junos OS Release 17.4R2

  • The LAG interface might flap if rebooting aggregation device. PR1315879

  • Duplicated packets might be received on the multicast downstream devices and multicast receivers. PR1316499

  • The aggregate device might show a plus sign on the ICL link for a satellite device. PR1335373

  • Aggregation device failure (power off) in a Junos Fusion Data Center causes complete or partial traffic loss for an extended period. PR1352167

Resolved Issues: Junos OS Release 17.4R1

There are no resolved issues in Junos OS Release 17.4R1 for Junos Fusion Data Center.

Documentation Updates

This section lists the errata or changes in Junos OS Release 17.4R2 for Junos Fusion Data Center documentation.

  • There are no errata and changes in the current Junos Fusion Data Center documentation.

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 Data Center. 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:

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.

To download and install Junos OS:

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

    https://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 command:

    user@host> request system software add reboot source/package-name

    All other customers, use the following command:

    user@host> request system software add reboot source/package-name

    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.

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. For satellite device hardware and software requirements, see Junos Fusion Hardware and Software Compatibility Matrices.

Note

The following conditions must be met before a standalone switch that is running Junos OS Release 14.1X53-D43 can be converted to a satellite device when the action is initiated from the aggregation device:

  • The switch can only be converted to SNOS 3.1 and higher.

  • The switch must be either set to factory-default configuration using the request system zeroize command, or the following command must be included in the configuration: set chassis auto-satellite-conversion.

Customers with EX4300 switches, use the following command:

user@host> request system software add validate reboot source/package-name

Customers with QFX5100 switches, use the following command, replacing n with the spin number:

user@host> request system software add reboot source/package-name

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:

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

    After committing the configuration, associate a satellite software image to the upgrade group:

    user@aggregation-device> request system software add /var/tmp/package-name upgrade-group group-name
    Note

    Before issuing request system software add /var/tmp/package-name upgrade-group group-name, you must issue a one-time command to expand the storage capacity. Use the request system storage user-disk expand command to increase the size of /user partition.

  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

    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:

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 group-name 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

    After committing the configuration, associate a satellite software image to the upgrade group:

    user@aggregation-device> request system software add /var/tmp/package-name upgrade-group group-name
    Note

    Before issuing request system software add /var/tmp/package-name upgrade-group group-name, you must issue a one-time command to expand the storage capacity. Use the request system storage user-disk expand command to increase the size of /user partition.

  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 a compatible conversion release of Junos OS. See Junos Fusion Hardware and Software Compatibility Matrices.

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

  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-3.1R1.n-signed.tgz stored in the /var/tmp/ directory on the switch, where n is the spin number:

    user@satellite-device> request chassis device-mode satellite /var/tmp/satellite-3.1R1.n-signed.tgz
    • To install satellite software onto a QFX5100 switch, use the satellite-3.1R1.n-signed.tgz satellite software package.

    • To install satellite software onto a EX4300 switch, use the satellite-ppc-3.1R1.n-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.
    [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/package-name
Note

Before issuing request system software add upgrade-group group-name, you must issue a one-time command to expand the storage capacity. Use the request system storage user-disk expand command to increase the size of /user partition.

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. For more information, see Converting a Satellite Device to a Standalone Device.

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 14.1, 14.2, 15.1, and 16.1 are EEOL releases. You can upgrade from Junos OS Release 14.1 to Release 15.1 or even from Junos OS Release 14.1 to Release 16.1. However, you cannot upgrade directly from a non-EEOL release that is more than three releases ahead or behind.

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

Downgrading from Release 17.4

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

Note

You cannot downgrade more than three releases.

For more information, see the Installation and Upgrade Guide.

Product Compatibility

Hardware Compatibility

To obtain information about the components that are supported on the devices, and special compatibility guidelines with the release, see the Hardware Guides for the devices used in your Junos Fusion Data Center topology.

To determine the features supported on Junos Fusion devices, use the Juniper Networks Feature Explorer, a Web-based application that helps you to explore and compare Junos OS feature information to find the right software release and hardware platform for your network. Find Feature Explorer at: https://pathfinder.juniper.net/feature-explorer/