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 NFX Series

 

These release notes accompany Junos OS Release 20.3R3 for the NFX Series Network Services Platforms. 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.

What’s New

Learn about new features introduced in the Junos OS main and maintenance releases for NFX Series.

Note

For information about NFX product compatibility, see NFX Product Compatibility.

What’s New in Release 20.3R3

There are no new features or enhancements to existing features for NFX Series devices in Junos OS Release 20.3R3.

What’s New in Release 20.3R2

There are no new features or enhancements to existing features for NFX Series devices in Junos OS Release 20.3R2.

What’s New in Release 20.3R1

Application Security

  • Listing of micro-applications and non-configurable applications (NFX Series, SRX Series, and vSRX)—Starting in Junos OS Release 20.3R1, we’ve introduced the following operational commands to display applications details:

    • show services application-identification application micro-applications to display the list of micro-applications.

    • show services application-identification application non-configurable to display the list of non-configurable applications.

    [See show services application-identification application micro-applications and show services application-identification application non-configurable.]

  • Application signature package rollback (NFX Series, SRX Series, and vSRX)—Starting in Junos OS Release 20.3R1, you can roll back the current version of the application signature package to the previous version by using one of the following methods:

    • Automatic—The system automatically rolls back to the previous version of the application signature package when the signature package installation fails on your security device.

    • Manual—You can roll back the application signature package to its previous version on your security device using the request services application-identification rollback command.

      [See Predefined Application Signatures for Application Identification.]

Wireless WAN

  • LTE support in dual CPE deployments (NFX250 NextGen)—Starting in Junos OS Release 20.3R1, you can provide a backup WAN connection by configuring LTE modules on a pair of NFX250 NextGen devices operating in cluster mode.

    [See Configuring the LTE Module on NFX Devices.]

What's Changed

Learn about what changed in the Junos OS main and maintenance releases for NFX Series devices.

What’s Changed in Release 20.3R3

There are no changes in the behavior of Junos OS features or in the syntax of Junos OS statements and commands in Junos OS Release 20.3R3 for NFX Series devices.

What’s Changed in Release 20.3R2

There are no changes in the behavior of Junos OS features or in the syntax of Junos OS statements and commands in Junos OS Release 20.3R2 for NFX Series devices.

What’s Changed in Release 20.3R1

There are no changes in the behavior of Junos OS features or in the syntax of Junos OS statements and commands in Junos OS Release 20.3R1 for NFX Series devices.

Known Limitations

There are no known limitations for NFX Series devices in Junos OS Release 20.3R3.

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

Open Issues

Learn about open issues in this release for NFX Series devices.

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

Platform and Infrastructure

  • The following messages are seen during FTP: ftpd[14105]: bl_init: connect failed for /var/run/blacklistd.sock (No such file or directory) messages are seen during FTP. PR1315605

  • On vmhost platforms, if the XML output of the request vmhost mode test | display xml rpc command is used in netconf, it fails. As a workaround, use the following XML command:

    PR1559786

Resolved Issues

Learn which issues were resolved in the Junos OS Release 20.3R3 for NFX Series devices.

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

Resolved Issues: 20.3R3

General Routing

  • The l2cpd core files might be seen on reboot. PR1561235

Platform and Infrastructure

  • On NFX150 devices, when J-Flow v5 is configured and the J-Flow v5 server is reachable through an IPsec tunnel, and the MTU size of this IPsec tunnel is configured as 1500, the J-Flow packets are not generated on NFX Series devices. As a workaround, use J-Flow v9 or IPFIX version, instead of J-Flow v5, to enable the J-Flow functionality on NFX Series devices. PR1539964

Resolved Issues: 20.3R2

Interfaces

  • When you configure analyzers on VNF interfaces with output port as other VNF interfaces, all the incoming and outgoing packets can be mirrored on to the designated analyzer port. However, it is noticed that after a system reboot, this functionality stops working and no packets are mirrored on the output analyzer port. PR1480290

Platform and Infrastructure

  • False positive TSensor errors are reported on vjunos0. PR1508580

  • When you upgrade the NFX150 devices from Junos OS Release 19.4 to Junos OS Release 20.2, the upgrade fails and an error message is displayed: “/usr/sbin/boot_mgmt_fsm: line 40: echo: write error: No space left on device issue". PR1532334

Resolved Issues: 20.3R1

Application Security

  • AppQoE is sending active probe packets for the deleted active-probe-params. PR1492208

High Availability

  • On an NFX250 chassis cluster, L3 interfaces are not getting created after secondary automatic reboot when control port recovery is enabled. PR1502449

Interfaces

  • On NFX350 devices, the show interfaces | no-more command output stops appearing for around 20 seconds after displaying the dl0 interface. PR1502626

  • On NFX350 devices, the clear interface statistics all command takes a longer time to execute. PR1475804

Platform and Infrastructure

  • After initiation of zeroization, the NFX250 device is going into a reboot loop. PR1491479

  • The request vmhost power-off command reboots the NFX250 NextGen device instead of powering off the device. PR1493062

  • On NFX150 devices, MAC aging does not work. You must remove aged MAC entries from the CLI. PR1502700

  • After you upgrade the JDM image from Junos OS Release D497.1 to Junos OS Release 18.4R3-S2, tunnels are down in the gateway router (GWR). PR1507165

  • On NFX150 devices, ZTP over LTE configuration commit fails for operation=create in XML operations configuration. PR1511306

  • The device reads the board ID from eeprom directly using I2C upon power cycle. PR1529667

Documentation Updates

There are no errata or changes in Junos OS Release 20.3R3 documentation for NFX Series devices.

Migration, Upgrade, and Downgrade Instructions

This section contains the procedure to upgrade Junos OS, and the upgrade and downgrade policies for Junos OS for the NFX Series. Upgrading or downgrading Junos OS might take several hours, depending on the size and configuration of the network.

Note

For information about NFX product compatibility, see NFX Product Compatibility.

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.

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.

Basic Procedure for Upgrading to Release 20.3

When upgrading or downgrading Junos OS, use the jinstall package. For information about the contents of the jinstall package and details of the installation process, see the Installation and Upgrade Guide. Use other packages, such as the jbundle package, only when so instructed by a Juniper Networks support representative.

Note

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 device, 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 device. For more information, see the Software Installation and Upgrade Guide.

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.

To download and install Junos OS Release 20.3R3:

  1. Using a Web browser, navigate to the All Junos Platforms software download URL on the Juniper Networks webpage:

    https://www.juniper.net/support/downloads/

  2. Select the name of the Junos OS platform for the software that you want to download.
  3. Select the Software tab.
  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 Download Software page.
  5. In the Install Package section of the Software tab, select the software package for the release.
  6. Log in to the Juniper Networks authentication system using the username (generally your e-mail address) and password supplied by Juniper Networks representatives.
  7. Review and accept the End User License Agreement.
  8. Download the software to a local host.
  9. Copy the software to the device or to your internal software distribution site.
  10. Install the new package on the device.