Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

ON THIS PAGE

Junos OS Release Notes for Junos Fusion Enterprise

 

These release notes accompany Junos OS Release 17.3R3 for Junos Fusion Enterprise. Junos Fusion Enterprise is a Junos Fusion that uses EX9200 switches in the aggregation device role. These release notes describe new and changed features, limitations, and known problems in the hardware and software.

Note

For a complete list of all hardware and software requirements for a Junos Fusion Enterprise, including which Juniper Networks devices can function as satellite devices, see Understanding Junos Fusion Enterprise Software and Hardware Requirements .

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

This section describes the new features and enhancements to existing features in Junos OS Release 17.3R3 for Junos Fusion Enterprise.

Note

For more information about the Junos Fusion Enterprise features, see the Junos Fusion Enterprise User Guide.

Junos Fusion Enterprise

  • Satellite device support (Junos Fusion Enterprise)—Starting with Junos OS Release 17.3R1, you can configure QFX5100-48T and QFX5100-48S switches as satellite devices in a Junos Fusion Enterprise topology. The satellite device in a Junos Fusion topology is managed and configured by the aggregation device. Junos Fusion Enterprise uses EX9200 switches in the aggregation device role.

    [See Junos Fusion Enterprise Overview.]

  • LAG to single satellite device (Junos Fusion Enterprise)—Starting in Junos OS Release 17.3R1, you can configure LAGs in a Junos Fusion Enterprise using extended port member links to increase uplink bandwidth and high availability for endpoint devices connected to a satellite device. The member links of the LAG must be on the same satellite device. The LAG can be configured to use LACP, which automates the addition and deletion of individual links to the LAG and can also prevent communication failures by detecting misconfigurations within a LAG.

    [See Configuring Link Aggregation on Satellite Devices in a Junos Fusion Enterprise.]

Changes in Behavior and Syntax

This section lists the changes in behavior of Junos OS features and changes in the syntax of Junos OS statements and commands in Junos OS Release 17.3R3 for Junos Fusion Enterprise.

Junos Fusion Enterprise

  • For the request chassis satellite beacon operational command, the slot-id option has been changed to fpc-slot. This change was made to support enabling beacon functionality for individual FPCs. PR1272956

Known Behavior

This section lists known behavior, system maximums, and limitations in hardware and software in Junos OS Release 17.3R3 for Junos Fusion Enterprise.

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

Junos Fusion Enterprise

  • In a Junos Fusion Enterprise topology with dual aggregation devices, firewall statistics are not synced across the aggregation devices. PR1105612

  • In a Junos Fusion Enterprise, the show ethernet-switching table command takes a few minutes to show entries when received on an extended port with MAC count set to 150K. PR1117567

  • In a Junos Fusion Enterprise, to use a non-default port as a clustering port in a clustering port policy, the policy must include at least one port that is a default uplink/clustering port for that platform. PR1241808

  • In a Junos Fusion Enterprise, the satellite device link goes down with autonegotiation enabled when the link partner speed is 100 Mbps. PR1272107

  • In a Junos Fusion Enterprise, Auto_MDIX and EEE are not supported on the QFX5100 as a satellite device. The configuration commit succeeds on ge- ports but the features are not enabled. PR1279928

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 17.3R3 for Junos Fusion Enterprise.

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

Junos Fusion Enterprise

  • On a Junos Fusion, when using LLDP, the "Power via MDI" and "Extended Power via MDI" TLVs are not transmitted. PR1105217

  • On a Junos Fusion, the tcpdump command does not capture packets on satellite devices. PR1125568

  • On a Junos Fusion Enterprise, Link Layer Discovery Protocol-Media Endpoint Discovery (LLDP-MED) fast start does not work. PR1171899

  • On a Junos Fusion Enterprise, when the satellite devices of a cluster are rebooted, the output of the CLI command show chassis satellite shows the port state of the cascade ports as "Present". PR1175834

Resolved Issues

This section lists the issues fixed in the Junos OS main release and the maintenance releases for Junos Fusion Enterprise.

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

Resolved Issues: 17.3R3

Junos Fusion Enterprise

  • Mirrored packets are dropped if analyzer output extended port is reachable through the ICL link. PR1211123

  • In a Junos Fusion environment, the satellite device displays U-boot on the LCD screen. PR1304784

  • Packet loss of 2-3 seconds is seen every 5 minutes on a Junos Fusion. PR1320254

  • An scpd core file might be seen on an aggregation device when a dynamic ACL on an 802.1X-enabled port is installed on a single-homed satellite device. PR1328247

  • DHCP security binding entries are not synced after the FPC goes offline and then online. PR1332828

  • This PR is an 802.1X re-authentication issue. PR1345365

Resolved Issues: 17.3R2

Junos Fusion Enterprise

  • While applying a loopback filter on aggregation devices in a Junos Fusion Enterprise, Callback Control Protocol (CBCP) packets might be filtered, which might cause CBCP sessions to be dropped and one of the satellite devices in a redundant pair to be in the SplitBrainDn state.

    PR1183680

  • Request chassis satellite beacon functionality to specific satellite device (SD) is not working, causing all the SDs to enable the beacon LED. PR1272956

  • VRRP has a split brain in a dual autodiscovery Junos Fusion. PR1293030

  • On a dual aggregation device Fusion setup, PoE is not working on one of the satellite devices in a satellite cluster. PR1295556

  • On a Junos Fusion Enterprise with dual aggregation devices (ADs), if you apply Routing Engine loopback filters and bring down the cascade port on one of the ADs, the satellite device (SD) on the AD where the cascade port is down goes to ProvSessDown due to a TCP session drop over the ICL interface. As a workaround, add additional filters to bypass the ICL traffic for the ICL interface's IP address. PR1275290

  • An aggregation device without a cascade port cannot reach hosts over an ICL link if they are authenticated by 802.1X in a different VLAN than the default (manually assigned) VLAN. PR1298880

  • The 802.1X authentication fails on a Junos Fusion setup. PR1299532

  • The 802.1X authentication might crash in a Junos Fusion setup with dual aggregation devices. PR1303909

  • All the 802.1X authentication sessions are removed when the auto-ICCP link is disabled. PR1307588

  • LACP aggregated Ethernet interfaces go to a DOWN state when performing commit synchronize. PR 1314561

Resolved Issues: 17.3R1

Junos Fusion Enterprise

  • On a Junos Fusion Enterprise, an upgrade group's association with a satellite software version is removed if the chassis satellite-management redundancy-groups configuration is deleted. PR1267370

  • On a Junos Fusion Enterprise, traffic shaping is not supported on the extended ports. PR1268084

  • When a race condition results in a dynamic VLAN assignment, the MAC-based VLAN (MBV) entry might not get created on the peer aggregation device. This situation can result in traffic loss when it flows through the peer AD. PR1282828

Documentation Updates

There are no errata or changes in Junos OS Release 17.3R3 for Junos Fusion Enterprise documentation.

Migration, Upgrade, and Downgrade Instructions

This section contains the procedure to upgrade or downgrade Junos OS and satellite software for a Junos Fusion Enterprise. Upgrading or downgrading Junos OS and satellite software might take several hours, depending on the size and configuration of the Junos Fusion Enterprise topology.

Basic Procedure for Upgrading Junos OS on an Aggregation Device

When upgrading or downgrading Junos OS for an aggregation device, always use the junos-install 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 junos-install 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 Release 17.3R1:

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

    https://support.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 on 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 junos-install 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, replacing n with the spin number.

    user@host> request system software add validate reboot source/junos-install-ex92xx-x86-64-17.3R1.n.tgz

    All other customers, use the following commands, replacing n with the spin number.

    user@host> request system software add validate reboot source/junos-install-ex92xx-x86-64-17.3R1.n-limited.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 might take 5 to 10 minutes.

    Rebooting occurs only if the upgrade is successful.

Note

To upgrade from Junos OS 17.1 to 17.3R1, use the procedure for upgrading from Junos OS 17.1 to 17.2, as documented in the Release Notes for Junos Fusion Enterprise, Junos OS Release 17.2.

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

There are multiple methods to upgrade or downgrade satellite software in your Junos Fusion Enterprise. See Configuring or Expanding a Junos Fusion Enterprise.

For satellite device hardware and software requirements, see Understanding Junos Fusion Enterprise Software and Hardware Requirements.

Use the following command to install Junos OS on a switch before converting it into a satellite device:

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

For EX4300 switches running Junos OS Release 17.2R1, QFX5100 switches running Junos OS Release 14.1X53-D43 or EX2300 and EX3400 switches running Junos OS Release 15.1X53-D55.5, the following conditions must be met before the Junos switch can be converted to a satellite device when the action is initiated from the aggregation device:

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

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

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:


    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 you enter the request system zeroize command.

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

  3. (EX3400 and 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 EX3400 and 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, or preconfiguration. See Configuring or Expanding a Junos Fusion Enterprise for detailed configuration steps for each method.

Converting a Satellite Device to a Standalone Switch

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 the satellite device from the Junos Fusion topology.

The following steps explain how to convert a satellite device that is participating in a Junos Fusion to a standalone device running Junos OS. If you have a standalone switch that is not part of a Junos Fusion but is running satellite software, and you want the switch to run Junos OS software, see Installing Junos OS Software on a Standalone Device Running Satellite Software.

Note

Conversion of EX2300 and EX3400 switches from satellite devices to standalone devices cannot be initiated from the aggregation device. To install Junos OS software on an EX2300 or EX3400 switch acting as a satellite device, see Installing Junos OS Software on a Standalone Device Running Satellite Software.

The following steps explain how to download software, remove the satellite device from the 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:

    https://support.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 menu and select the switch platform series and model for your satellite device.
  4. Select the software image for your platform, using the following guidelines:

    • If the satellite device is a EX4300 switch, you install a standard, signed jinstall version of Junos OS.

    • If the satellite device is a QFX5100 switch that can be converted to a standalone device, you must install a Preboot eXecution Environment (PXE) version of Junos OS. The PXE version of Junos OS software supports the same feature set as the other Junos OS software packages for a release, but is specially engineered to install Junos OS onto a device running satellite software. The PXE Junos OS package name uses the format install-media-pxe-qfx-5-version-domestic-signed.tgz.

  5. Review and accept the End User License Agreement.
  6. Download the software to a local host.

    Copy the software to the routing platform or to your internal software distribution site.

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

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

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

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

    You can check the automatic satellite conversion configuration by entering the show command at the [edit chassis satellite-management auto-satellite-conversion] hierarchy level.

  8. 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
  9. Install Junos OS 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 software package stored in the /var/tmp directory on the aggregation device onto a switch acting as the satellite device using FPC slot 102:

    [edit]
    user@aggregation-device> request chassis satellite install /var/tmp/package-name fpc-slot 102

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

  10. Wait for the reboot that accompanies the software installation to complete.
  11. When you are prompted to log back in to your device, uncable the device from the Junos Fusion topology. See or Remove a Transceiver. Your device is removed from the 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 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 on EEOL releases and to review a list of EEOL releases, see https://support.juniper.net/support/eol/software/junos/

Downgrading from Release 17.3

Junos Fusion Enterprise is first supported in Junos OS Release 16.1, although you can downgrade a standalone EX9200 switch to earlier Junos OS releases.

Note

You cannot downgrade more than three releases.

To downgrade a Junos Fusion Enterprise, follow the procedure for upgrading, but replace the 17.2 junos-install package with one that corresponds to the appropriate release.

Note

We recommend that you do not downgrade the aggregation device from 17.3R1 to 17.2 if there are cluster satellite devices in the setup.

For more information, see the Installation and Upgrade Guide.

Product Compatibility

Hardware and Software Compatibility

For a complete list of all hardware and software requirements for a Junos Fusion Enterprise, including which Juniper Networks devices function as satellite devices, see Understanding Junos Fusion Enterprise Software and Hardware Requirements in the Junos Fusion Enterprise User Guide.

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/

Hardware Compatibility Tool

For a hardware compatibility matrix for optical interfaces and transceivers supported across all platforms, see the Hardware Compatibility tool.