Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Junos OS Release Notes for Junos Fusion Provider Edge

 

These release notes accompany Junos OS Release 16.1R7 for the Junos Fusion Provider Edge. 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

This section describes the new features and enhancements to existing features in the Junos OS main release and the maintenance releases for Junos Fusion Provider Edge.

Release 16.1R7 New and Changed Features

  • There are no new features or enhancements to existing features for Junos Fusion Provider Edge in Junos OS Release 16.1R7.

Release 16.1R6 New and Changed Features

  • There are no new features or enhancements to existing features for Junos Fusion Provider Edge in Junos OS Release 16.1R6.

Release 16.1R5 New and Changed Features

  • There are no new features or enhancements to existing features for Junos Fusion Provider Edge in Junos OS Release 16.1R5.

Release 16.1R4 New and Changed Features

Junos Fusion

  • Support for selective VLAN local switching—Starting in Junos OS Release 16.1R4, Junos Fusion Provider Edge supports local switching on a service level. When you configure selective VLAN local switching on satellite devices, the other VLANs will continue to follow the default forwarding behavior. Use the selective-vlan-switching option for the routing instance at the [edit forwarding-options satellite fpc slot] hierarchy level to enable selective VLAN local switching for a particular satellite device.

  • Support for an ingress policer—Starting in Junos OS Release 16.1R4, Junos Fusion Provider Edge supports the use of an ingress policer to filter incoming traffic at the extended port level. This feature supports a two-color policer that allows you to limit the traffic that is received on an interface. You can configure the Layer 2 ingress policer by using the input-policer statement at the [edit interfaces interface-name layer2-policer] hierarchy level.

Release 16.1R3 New and Changed Features

  • There are no new features or enhancements to existing features for Junos Fusion Provider Edge in Junos OS Release 16.1R3.

Release 16.1R2 New and Changed Features

  • There are no new features or enhancements to existing features for Junos Fusion Provider Edge in Junos OS Release 16.1R2.

Release 16.1R1 New and Changed Features

Hardware

  • Additional MPC support—Starting with Junos OS Release 16.1R1, the following Modular Port Concentrators (MPCs) are supported on the MX Series routers:

    • MPC7E

    • MPC8E

    • MPC9E

Multicast

  • Egress Multicast Replication—Starting with Junos OS Release 16.1, you can enable egress multicast replication to optimize multicast traffic in a Junos Fusion. In egress multicast replication, multicast traffic is replicated on satellite devices, rather than on the aggregation device. If you have a large number of multicast receivers or high multicast bandwidth traffic, enabling egress multicast replication reduces the traffic on cascade port interfaces and reduces the load on the aggregation device. This can reduce the latency and jitter in packet delivery, decrease the number of problems associated with oversubscription, and prevent a traffic storm caused by flooding of unknown unicast packets to all interfaces.

    This feature is disabled by default. To enable egress multicast replication, use the local-replication statement in the the [edit forwarding-options satellite] hierarchy level. When you enable this feature, local replication is enabled on all satellite devices that are connected to the aggregation device. You cannot enable local replication for just a few selected satellite devices, specific bridge domains, or specific route prefixes.

    Egress multicast replication does not take effect with the following features (Junos Fusion replicates multicast traffic on the aggregation device and other multicast traffic will continue to be replicated on satellite devices):

    • Multicast support on pure layer 3 extended ports

    • MLD snooping on an IPv6 network

    Egress multicast replication is incompatible with the following features (the feature will not work together with egress multicast replication and you must choose either to enable egress multicast replication or to use the feature):

    • VLAN tag manipulations, such as VLAN tag translations, VLAN tag stacking, and VLAN per port policies. This can result in dropped packets caused by unexpected VLAN tags.

    • Multicast support for the extended ports on the edge side of Pseudowire connections in VPLS networks.

    • Multicast support for the extended ports on the edge side of EVPNs.

    • Multicast VPN deployments.

    • MPLS/BGP VPN deployments.

    • Features that perform egress actions on individual extended ports, such as egress local-port mirroring.

    Use the following new operational commands to display information related to this feature:

    • show bridge flood next-hops satellite

    • show bridge flood next-hops satellite nexthop-id nexthop-identifier

    • show bridge flood satellite

    • show bridge flood satellite bridge-domain-name domain-name

    • show bridge satellite device

    • show multicast ecid-mapping satellite

    • show multicast next-hops satellite

    • show multicast snooping next-hops satellite nexthop-id nexthop-identifier

    • show multicast snooping route satellite

    • show multicast snooping route satellite bridge-domain-name domain-name

    • show multicast snooping route satellite group group-id

    • show multicast statistics satellite

    • show multicast summary satellite

Changes in Behavior and Syntax

There are no changes in behavior of Junos OS features and changes in the syntax of Junos OS statements and commands in Junos OS Release 16.1R7 for Junos Fusion Provider Edge.

Known Behavior

There are no known behaviors, system maximums, and limitations in hardware and software in Junos OS Release 16.1R7 for Junos Fusion Provider Edge.

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

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 16.1R7 for Junos Fusion Provider Edge.

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

Junos Fusion

  • On a Junos Fusion topology, if you issue the request support information operational mode command, the logs do not include satellite device information. PR1220575

  • The operation to add a physical port with CoS configuration to an aggregated Ethernet bundle should be done as a two-step commit process. First, remove the CoS configuration from the physical port and commit the configuration. Then, add the physical port to the aggregated Ethernet bundle and commit again. Same holds true for the other way around that is, when removing a port from the bundle and applying CoS configuration. Not following this guideline might result in incorrect CoS behavior on the physical interface and the aggregated Ethernet link.PR1334018

Resolved Issues

This section lists the issues fixed in the Junos OS main release and the maintenance releases. The identifier following the description is the tracking number in the Juniper Networks Problem Report (PR) tracking system.

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

Resolved Issues: 16.1R7

Junos Fusion

  • The show interfaces diagnostics optics satellite command output is broken in Junos OS Releases 16.1 and 17.1. Engineering fixed the same in this PR. PR1327876

Resolved Issues: 16.1R6

Junos Fusion Satellite Software

  • Junos OS Fusion is not supported with any MX Series platform as aggregation device on Junos OS Release 16.2R1. PR1231227

Resolved Issues: 16.1R5

Junos Fusion

  • Before this issue gets fixed, in Junos Fusion setup, aggregation device will always stamp ingress ECID if ingress and egress satellite device is same. The transit unicast traffic would be discarded on satellite device when they pass through different logical interfaces (IFL) of the same extended port because ingress ECID is equal to egress ECID and due to split-horizon check on satellite device. This issue only impact unicast traffic but not impact multicast/broadcast traffic. PR1264900

Resolved Issues: 16.1R4

General Routing

  • On a Junos Fusion Provider Edge topology, if there are power failures or the power is not connected to a power supply on a satellite device, the "jnxPowerSupplyFailure" traps are not generated by the aggregation device. For example, if there are two Power Entry Modules (PEMs) inserted on the satellite device and one PEM is not powered on, the aggregation device does not generate a trap for the PEM without power. PR1140097

Resolved Issues: 16.1R3

Junos Fusion

  • On a Junos Fusion topology, some race conditions occur, such as a satellite route being deleted followed quickly by the reuse of the same route. This may cause the SCPD process to crash.PR1200120

Resolved Issues:16.1R2

Junos Fusion

  • On a Junos Fusion topology, MX Series routers send an extra VLAN tag for routing engine (RE) packets on the extended ports with dual vlan-tag family inet option configured. PR1184850

  • On a Junos Fusion topology, the transit traffic that is received from the LAG of the extended ports is still forwarded even when the minimum-link condition has not been met. PR1188482

  • On a Junos Fusion topology, when you issue the request chassis satellite shell command and the output generates more than 24 kilobytes of data, the satellite discovery and provisioning process (SDPD) might stop operating. PR1188712

  • On a Junos Fusion topology, the SNMP monitoring tool does not receive any interface statistics for the extension ports on the satellite device when there is traffic on the extension ports and connectivity between the mib2d (Management Information Base II Daemon) process and the spmd (Satellite Platform Management Daemon) process is lost. PR1190655

  • On a Junos Fusion topology, you cannot specify the fpc-slot option with the show chassis environment satellite command.PR1199787

Junos Fusion

  • On a Junos Fusion topology, when forwarding-options satellite local-replication is enabled and multicast traffic is being forwarded by the satellite devices, some configuration changes and hardware events may result in dropped multicast traffic. PR1139592

Documentation Updates

There are no errata or changes in Junos OS Release 16.1R7 for Junos Fusion Provider Edge 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 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:

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 16.1R1 is different from previous 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.

    All customers except the customers in the Eurasian Customs Union (currently consists of Armenia, Belarus, Kazakhstan, Kyrgyzstan, and Russia) can use the following package:

    • For MX5, MX10, MX104, MX40, and MX80:

      user@host> request system software add no-validate reboot source/jinstall-ppc-16.1R7.7-signed.tgz
    • For MX240, MX480, MX960, MX2010, and MX2020 (32-bit Routing Engine version):

      user@host> request system software add no-validate reboot source/junos-install-mx-x86-32-16.1R7.7-signed.tgz
    • For MX240, MX480, MX960, MX2010, and MX2020 (64-bit Routing Engine version):

      user@host> request system software add no-validate reboot source/junos-install-mx-x86-64-16.1R7.7-signed.tgz

      For VM Host 64-bit:

      user@host> request vhhost software add no-validate rebootsource/junos-vmhost-install-mx-x86-64-16.1R7.7.tgz

      For VM Host Net 64-bit:

      user@host> request vhhost software add no-validate rebootsource/junos-vmhost-install-net-mx-x86-64-16.1R7.7.tgz

    Customers in the Eurasian Customs Union (currently consists of Armenia, Belarus, Kazakhstan, Kyrgyzstan, and Russia) can use the following package (limited encryption Junos package):

    • For MX5, MX10, MX104, MX40, and MX80:

      user@host> request system software add no-validate reboot source/jinstall-ppc-16.1R7.7-limited-signed.tgz
    • For MX240, MX480, MX960, MX2010, and MX2020 (32-bit Routing Engine version):

      user@host> request system software add no-validate reboot source/junos-install-mx-x86-32-16.1R7.7-limited.tgz
    • For MX240, MX480, MX960, MX2010, and MX2020 (64-bit Routing Engine version):

      user@host> request system software add no-validate reboot source/junos-install-mx-x86-64-16.1R7.7-limited.tgz

      For VM Host 64-bit:

      user@host> request vhhost software add no-validate rebootsource/junos-vmhost-install-mx-x86-64-16.1R7.7-limited.tgz

      For VM Host Net 64-bit:

      user@host> request vhhost software add no-validate rebootsource/junos-vmhost-install-net-mx-x86-64-16.1R7.7-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

    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 16.1R7 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

There are multiple methods to upgrade or downgrade satellite software in your Junos Fusion Provider Edge. See Configuring Junos Fusion Provider Edge.

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

A satellite device must be running Junos OS Release 14.1X53-D35 or later before it can be converted into a satellite device, in any context.

Use the following command to install Junos OS Release 14.1X53-D40 onto a switch before converting it into a satellite device:

user@host> request system software add validate reboot source/jinstall-ex-4300-14.1X53-D40.8-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. See Configuring Junos Fusion Provider Edge for detailed configuration steps for each option.

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.

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://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 pull-down menu and select the switch platform series and model for your satellite device.
  4. Select the Junos OS Release 14.1X53-D35 software image for your platform.
  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. 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 the Junos Fusion:

    [edit]
    user@aggregation-device# delete chassis satellite-management auto-satellite-conversion satellite 101
  8. 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
  9. 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 software package stored in the /var/tmp directory on the aggregation device onto an EX4300 switch acting as the satellite device using FPC slot 102:

    [edit]
    user@aggregation-device> request chassis satellite install /var/tmp/jinstall-ex-4300-14.1X53-D35.3-domestic-signed.tgz 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. SeeRemoving a Transceiver from a QFX Series Device or Removing a Transceiver, as needed. Your device has been removed from the Junos Fusion. Note

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

Upgrading an Aggregation Device from Junos OS Release 14.2

When you upgrade an aggregation device from Junos OS Release 14.2 to Junos OS Release 16.1R7, you must also upgrade your satellite device to Satellite Device Software Version 2.0R1.

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 from Junos OS Release 15.1 to Release 16.2. 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 16.1

To downgrade from Release 16.1 to another supported release, follow the procedure for upgrading, but replace the16.1 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 Software 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 Provider Edge 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/.