Junos OS Release Notes for Junos Fusion Provider Edge

New and Changed Features

• Release 18.1R3 New and Changed Features

• Release 18.1R2 New and Changed Features

• Release 18.1R1 New and Changed Features

Release 18.1R3 New and Changed Features

Release 18.1R2 New and Changed Features

Release 18.1R1 New and Changed Features

Hardware

• Support for QFX5110 and QFX5200 as satellite devices in Junos Fusion Provider Edge—Starting in Junos OS Release 18.1R1, you can use QFX5110-48S or QFX5200-32C switches as satellite devices in Junos Fusion Provider Edge.

  [See Satellite Device Hardware Models and Preparing the Satellite Device.]

Class of Service (CoS)

• Support for dynamic mapping of extend ports to cascade ports for hierarchical CoS (Junos Fusion Provider Edge)—Junos Fusion treats the cascade ports connecting the aggregation device to the satellite device as aggregated Ethernet ports with aggregation done automatically without configuration. By default the Junos Fusion implementation of hierarchical CoS applies the scheduler parameters across all cascade ports in scale mode. Because scale mode divides the configured shaper equally across the cascade ports, traffic drops can start before a customer reaches its committed rate for a particular flow. To avoid this problem, starting with Junos OS Release 18.1R1, you can set all cascade ports on an aggregation device to be in replicate mode and automatically target all of a customer’s traffic to a specific cascade port. To do this, simply enable target-mode at the [edit chassis satellite-management fpc fpc-number] hierarchy level.

  [See Understanding CoS on an MX Series Aggregation Device in Junos Fusion.]

Junos Fusion

• Junos Fusion Provider Edge support for Junos Node Slicing (MX960, MX2010, MX2020)—Starting in Junos OS Release 18.1R1, you can configure an aggregation device on guest network functions (GNFs), or partitions created on a router, by using Junos Node Slicing. The Junos Fusion topology is composed of an aggregation device and multiple satellite devices. An MX Series router supports a maximum of 10 GNFs, with each GNF supporting a separate aggregation device. The aggregation device on a GNF supports a maximum of 10 satellite devices. The aggregation device acts as the single point of management for all devices in a Junos Fusion topology, while the satellite devices provide interfaces that send and receive network traffic.

  For more information on Junos Node Slicing, see Junos Node Slicing Overview.

  Note

  • In a Junos Fusion Provider Edge topology that has a GNF configured as the aggregation device, you can only use EX4300 switches as satellite devices.

  • Only the following line cards support the cascade port on the aggregation device: MPC7E-MRATE, MPC7E-10G, MPC8 and MPC9.

  [See Understanding Junos Fusion Provider Edge Components.]

Changes in Behavior and Syntax

Known Behavior

• Junos Fusion

Junos Fusion

• Configuration synchronization is not triggered when you issue the rollback command on the local aggregation device (AD). PR1298747

• In Junos OS, two different input filters cannot be configured on the same interface; if two filters are configured, only the second filter (the one that was configured most recently) takes effect. Ingress mirroring on extended ports in Junos Fusion Data Center (JFDC) can only be done by using firewall filters. Considering the Junos OS filter behavior described above, in JFDC, ingress mirroring on extended ports and other firewall filter configurations cannot be done on the same port. PR1353065

• Since EVPN GR is not supported, restart of rpd will result in considerable traffic loss for EVPN traffic. The traffic should restore eventually once convergence is complete. PR1353742

• Restart of rpd will result in considerable traffic loss/duplication for EVPN traffic. The traffic should restore eventually once convergence is complete. PR1350040

Known Issues

• Junos Fusion

Junos Fusion

• During Satellite Device (SD) upgrade in Junos Fusion, there is a race condition that the Link Aggregation Control Protocol (LACP) defaulted PDU received from the peer device connected in a link aggregation group (LAG) is incorrectly sent to an aggregation device (AD) with aggregated Ethernet E-channel Identifier (ECID) instead of member ECID, which causes that LACP PDU to be received on another member in the LAG, resulting in the LAG interface flapping. PR1321575

Documentation Updates

• New Simplified Documentation Architecture

New Simplified Documentation Architecture

• With the release of Junos OS Release 18.1, Juniper is simplifying its technical documentation to make it easier for you to find information and know that you can rely on it when you find it. In the past, we organized documentation about Junos OS software features into platform-specific documents. In many cases, features are supported on multiple platforms, so you might not easily find the document you want for your platform.

  With Junos OS Release 18.1, we have eliminated the platform-specific software feature documents. For example, if you want to find documentation on OSPF, there is only one document regardless of which platform you have. Here are some of the benefits of our new simplified architecture:

  • Over time, you will see better search results when looking for Juniper documentation. You will be able to find what you want faster and be assured that is the right document.

  • If a software feature is supported on multiple platforms, you can find information about all the platforms in one place.

  • Because we have eliminated many documents that covered similar topics, you will now find one document with all the information.

  • You can know that you are always getting the most current and accurate information.

Migration, Upgrade, and Downgrade Instructions

• Basic Procedure for Upgrading an Aggregation Device

• Upgrading an Aggregation Device with Redundant Routing Engines

• Preparing the Switch for Satellite Device Conversion

• Converting a Satellite Device to a Standalone Device

• Upgrading an Aggregation Device

• Upgrade and Downgrade Support Policy for Junos OS Releases

• Downgrading from Junos OS Release 18.1

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.

The download and installation process for Junos OS Release 18.1R3 is different that for earlier Junos OS releases.

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.

    Note

    We highly recommend that you see 64-bit Junos OS software when implementing Junos Fusion Provider Edge.

    For upgrades from Junos Release 14.2 and earlier:

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

    All other upgrades:

    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 the Canada and U.S. version)

    The validate option validates the software package against the current configuration as a prerequisite for adding the software package to ensure that the router reboots successfully. This is the default behavior when the software package being added is for 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 as follows to minimize disrupting network operations:

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

Customers with EX4300 switches, use the following command:

Customers with QFX5100 switches, use the following command:

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 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. See Configuring Junos Fusion Provider Edge for detailed configuration steps for each method.

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.

Upgrading an Aggregation Device

When you upgrade an aggregation device to Junos OS Release 18.1R3, you must also upgrade your satellite device to Satellite Device Software version 3.1R1.

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.

You cannot upgrade directly from a non-EEOL release to a 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 Junos OS Release 18.1

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

For more information, see the Installation and Upgrade Guide.

Product Compatibility

• Hardware Compatibility

Hardware 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 Guide and the Interface Module Reference for the product.

To determine the features supported in a Junos Fusion, 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. See the Feature Explorer.

Hardware Compatibility Tool

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