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 for enterprise

 

These release notes accompany Junos OS Release 19.1R3 for Junos fusion for enterprise. Junos fusion for 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 for enterprise, including which Juniper Networks devices can function as satellite devices, see Understanding Junos fusion for 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.

What’s New

Learn about new features introduced in the Junos OS main and maintenance releases for Junos fusion for enterprise.

Note

For more information about the Junos fusion for enterprise features, see the Junos fusion for enterprise User Guide.

Release 19.1R3 New and Changed Features

There are no new or changed features in Junos OS Release 19.1R3 for Junos fusion for enterprise.

Release 19.1R2 New and Changed Features

There are no new or changed features in Junos OS Release 19.1R2 for Junos fusion for enterprise.

Release 19.1R1 New and Changed Features

Authentication, Authorization and Accounting (AAA) (RADIUS)

  • Support for SFTP global disablement (Junos fusion for enterprise)—Starting in Junos OS Release 19.1R1, we have globally disabled incoming SSH File Transfer Protocol (SFTP) connections by default. You can enable incoming SFTP connections globally by configuring the sftp-server statement at the [edit system services ssh] hierarchy level. In releases before Junos OS Release 19.1R1, the incoming SFTP connections are globally enabled by default.

    [See Configuring sftp-server.]

What's Changed

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 19.1R3 for Junos fusion for enterprise.

Known Limitations

This section lists known behavior, system maximums, and limitations in hardware and software in Junos OS Release 18.4R1 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 for enterprise

  • When using an EX9200 switch as the aggregation device (AD), you might see the error "jnh_dot1br_ktree_entry_create(1098): Entry Already Exists" continuously. This is caused by EX2300 satellite devices (SDs) having duplicate ECID values for the cluster/extended ports across members of the same cluster devices. PR1408947

Open Issues

This section lists the known issues in hardware and software in Junos OS Release 19.1R3 for Junos fusion for 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 for enterprise

  • The sdpd process generates a core file at vfpc_all_eports_deletion_complete vfpc_dampen_fpc_timer_expiry on the following triggers:

    • Deleting and adding the same satellite device with some attribute change in a single commit.

    • Interchange of slot ID between two satellite devices in a single commit.

    As a workaround, instead of making these satellite device configuration changes in a single commit, break it into multiple commits. PR1454335

  • On a Junos fusion system, intermediate traffic drop might be seen between the aggregation and satellite device when SFlow is enabled on the ingress interface. When SFlow is enabled, the original packet is corrupted for those packets which hit the SFlow filter. This is because the packets egressing the aggregation device are short of 4 bytes of FCS 2 bytes of data. Normal data packets are 128 bytes (4 bytes for FCS, 14 bytes for Ethernet header, 20 bytes for IP header and 90 bytes for data). The corrupted packets are 122 bytes (14 bytes for Ethernet header, 20 bytes for IP header, and 88 bytes for data). PR1450373

  • In a Junos Fusion scenario with the EX4300 switch acting as the satellite device, the temperature sensor alarms and logs might be seen due to an incorrect reading about 2-3 degrees lower than expected. There is no CLI command to clear the alarm and logs. PR1466324

Resolved Issues

Learn which issues were resolved in the Junos OS main and maintenance releases for Junos fusion for 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: Release 19.1R3

  • There is an inconsistency in the loop detect feature on newly provisioned satellite devices. PR1460209

  • The dpd process might generate a core file on satellite devices in Junos fusion for enterprise. PR1460607

Resolved Issues: Release 19.1R2

  • Traffic might be dropped in Junos fusion for enterprise scenario with dual aggregation devices. PR1417139

  • The 1-gigabit SFP transceiver in the 10-Gigabit Ethernet upstream port on EX3400 and EX4300 satellite devices might not come up. PR1420343

  • The loop-detect feature does not work in Junos fusion for enterprise. PR1426757

  • Reachability issue of the host connected to the satellite device might be affected in Junos fusion for enterprise environment with EX9200 series devices as aggregation devices. PR1447873

Resolved Issues: Release 19.1R1

  • PoE-over-LLDP negotiation is not supported on a Junos fusion for enterprise setup. PR1366106

  • An error peer_daemon: bad daemon: scpd is seen on an EX9251 switch running Junos OS Releases 18.1R1 and 18.1R2. PR1369646

  • Cannot log in to satellite device cluster although it is recognized by the aggregation device properly. PR1395570

  • The l2ald process might generate a core file when persistent MAC addresses are cleared from the switching table. PR1409403

  • VoIP-enabled extended ports (on satellite devices) do not adjust MTU in Junos fusion for enterprise. PR1411179

Documentation Updates

There are no errata or changes in Junos OS Release 19.1R3 for documentation for Junos fusion for enterprise.

Migration, Upgrade, and Downgrade Instructions

This section contains the procedure to upgrade or downgrade Junos OS and satellite software for a Junos fusion for enterprise. Upgrading or downgrading Junos OS and satellite software might take several hours, depending on the size and configuration of the Junos fusion for 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:

  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 commands, where n is the spin number.

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

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

    user@host> request system software add validate reboot source/junos-install-ex92xx-x86-64-18.3B1.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.

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 for enterprise. See Configuring or Expanding a Junos fusion for enterprise.

For satellite device hardware and software requirements, see Understanding Junos fusion for 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 Junos 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 running Junos OS can be converted only to SNOS 3.1 and later.

  • Either the switch must be set to factory-default configuration by 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 for enterprise for detailed configuration steps for each method.

Converting a Satellite Device to a Standalone Switch

If you need to convert a satellite device to a standalone device, you must 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.

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

Junos fusion for 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 for enterprise from Junos OS Release 18.3R1, follow the procedure for upgrading, but replace the 18.3 junos-install package with one that corresponds to the appropriate release.