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.4R2 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 the Junos OS main release and the maintenance releases for Junos Fusion Enterprise.

Note

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

Release 17.4R2 New and Changed Features

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

Release 17.4R1 New and Changed Features

  • Cascade port support on EX9200 line cards (Junos Fusion Enterprise)—Starting with Junos OS Release 17.4R1, interfaces on the following EX9200 line cards can be converted to cascade ports in a Junos Fusion Enterprise topology:

    • EX9200-12QS

    • EX9200-40XS

    • EX9200-40F

    • EX9200-40F-M

    In a Junos Fusion Enterprise topology, the EX9200 switch acts as the aggregation device. A cascade port is a port on the aggregation device that sends and receives control and network traffic from an attached satellite device.

    [See Understanding Junos Fusion Enterprise Software and Hardware Requirements.]

  • Aggregation device support on EX9200 with EX9200-RE2 Routing Engine (Junos Fusion Enterprise)—Starting with Junos OS Release 17.4, EX9200 switches with the EX9200-RE2 Routing Engine module are supported as aggregation devices in a Junos Fusion Enterprise. The EX9200-RE2 module supports virtual machine (VM) architecture in an EX9200 switch.

    [See Understanding Junos Fusion Enterprise Software and Hardware Requirements.]

  • EVPN-MPLS interworking with Junos Fusion Enterprise (EX9200 switches)—Starting with Junos OS Release 17.4R1, you can use Ethernet VPN (EVPN) to extend your Junos Fusion Enterprise over an MPLS network to a geographically distributed campus or enterprise network.

    The EVPN-MPLS interworking feature offers the following benefits:

    • Ability to use separate virtual routing and forwarding (VRF) instances to control inter-VLAN routing.

    • VLAN translation.

    • Default Layer 3 virtual gateway support, which eliminates the need to run such protocols as Virtual Router Redundancy Protocol (VRRP).

    • Load balancing to better utilize both links when using EVPN multihoming.

    • The use of EVPN type 2 advertisement routes (MAC+IP) reduces the need for flooding domains with ARP packets.

    [See Understanding EVPN-MPLS Interworking with Junos Fusion Enterprise and MC-LAG.]

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

  • 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 Enterprise, when you issue the show ethernet-switching table CLI command, it takes a few minutes to show entries when an extended port receives with the MAC count set to 150K. PR1117567

  • 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

  • On a Junos Fusion Enterprise, in order 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

Known Issues

There are no known issues in hardware and software in Junos OS Release 17.4R2 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

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

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

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

  • In a Junos Fusion, a packet loss of 2-3 seconds is seen every 5 minutes. PR1320254

  • On Junos Fusion Enterprise, an SCPD core might be seen on an aggregation device when DACL on 802.1X-enabled port is installed on a single-homed satellite device. PR1328247

  • On Junos Fusion Enterprise, DHCP security binding entries are not synced after the FPC goes offline and comes back online. PR1332828

  • Issue with 802.1X re-authentication. PR1345365

  • A satellite device does not recover PoE after the device is offline for more than 10 minutes and rejoins the aggregation device. PR1356478

  • The Junos Fusion satellite device reboots after an automatic PoE firmware upgrade. PR1359065

  • The ppm-lite process might generate a core file on the Junos Fusion satellite devices. PR1364265

Resolved Issues: 17.4R1

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

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

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

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

  • The 802.1X authentication might fail in a Junos Fusion setup. PR1299532

  • IPv6 multicast is not forwarded over an MC-LAG ICL interface until the interface is toggled. PR1301698

  • The l2ald process generates a core file with no apparent trigger. PR1302344

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

  • The dot1x process might generate a core file in a Junos Fusion setup with dual aggregation devices.PR1303909

  • LACP aggregated Ethernet interfaces go to down state when performing commit synchronize. PR1314561

Documentation Updates

There are no errata or changes in Junos OS Release 17.4R2 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.4R2:

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

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

    All other customers, use the following commands, where n is the spin number:

    user@host> request system software add validate 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 might take 5 to 10 minutes.

    Rebooting occurs only if the upgrade is successful.

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

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.

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

    If you lose 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, 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 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 17.1, 17.2, and 17.3 are EEOL releases. You can upgrade from Junos OS Release 17.1 to Release 17.2 or from Junos OS Release 17.1 to Release 17.3. 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://www.juniper.net/support/eol/junos.html

Downgrading from Release 17.4

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.

For more information, see the Installation and Upgrade Guide.

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

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