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.2R3 for the NFX Series. 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.2R3

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

What's New in Release 20.2R2

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

What's New in Release 20.2R1

Application Security

  • AppQoE multihoming with active-active deployment (NFX150, NFX250, SRX320, SRX340, SRX345, SRX550HM, SRX1500, SRX4100, SRX4200, and vSRX)—Starting In Junos OS Release 20.2R1, AppQoE is enhanced to support multihoming with active/active deployment. In previous releases, AppQoE supports multihoming with active/standby deployment.

    In active/active deployment, the spoke device connects to multiple hub devices. Application traffic can transit through any of the hub devices if the link to the hub device meets SLA requirements. Application traffic can switch seamlessly between the hub devices in case of SLA violation or if the active hub device is not responding.

    To support active/active mode, you must enable the BGP multipath to allow the device to select multiple equal-cost BGP paths to reach a given destination.

    [Application Quality of Experience (AppQoE).]

  • Packet capture for unknown application traffic (NFX Series, SRX Series, and vSRX)—Starting in Junos OS Release 20.2R1, you can generate packet capture information for unknown application traffic on your security device. You can use this information to get more insight on unknown applications.

    After you configure packet capture for the application traffic on your device, the packet capture function captures the packet details and stores the information in a packet capture (.pcap) file. You can use the packet capture details of an unknown application to define a new custom application signature and create a security policy rule to manage the application traffic more efficiently.

    You can submit the packet capture information to Juniper Networks to debug why an application is not detected, and if required, request to create an application signature.

    [See Application Identification.]

High Availability

  • High availability on NFX250 NextGen devices—Starting in Junos OS Release 20.2R1, NFX250 NextGen devices support the high availability feature. You can configure a cluster of two NFX250 NextGen devices to act as primary and secondary devices for protection against device failures. The high availability feature supports Layer 2 and Layer 3 features in dual CPE deployments.

    By default, the ge-0/0/0 interface functions as the control interface. You can configure one of the remaining front panel interfaces as the fabric interface. On the LAN, the active/backup mechanism is used. If the primary device fails, the secondary device takes over the operation. On the WAN, both active/active and active/backup mechanisms are supported.

    [How to Configure the NFX250 NextGen.]

Interfaces

  • ADSL and VDSL interfaces on NFX350 devices—Starting in Junos OS Release 20.2R1, NFX350 devices support ADSL and VDSL interfaces.

    [How to Configure the NFX350.]

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.2R3

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.2R3 for NFX Series devices.

What’s Changed in Release 20.2R2

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.2R2 for NFX Series devices.

What’s Changed in Release 20.2R1

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.2R1 for NFX Series devices.

Known Limitations

There are no known behaviors, system maximums, and limitations in hardware and software in Junos OS Release 20.2R3 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.

Open Issues

Learn about open issues in Junos OS Release 20.2R3 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.

High Availability

  • On an NFX150 chassis cluster device, the first packet is getting dropped while validating VLAN support on reth interfaces and child link. PR1488462

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

  • 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

Virtual Network Functions (VNFs)

  • On NFX Series devices, while configuring vmhost vlans using vlan-id-list, the system allows duplicate VLAN IDs in the VLAN ID list. PR1438907.

Resolved Issues

Learn which issues were resolved in the Junos OS Release 20.2R3 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.2R3

General Routing

  • False positive TSensor errors are reported on vjunos0. PR1508580

High Availability

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

Interfaces

  • On NFX Series and MX150 devices, the following error messages are seen in the messages log file for the interfaces that have SFP installed in them: fpc0 FAILED(-1) read of SFP eeprom for port: 13. PR1529939

Platform and Infrastructure

  • On NFX150, NFX250 NextGen, and NFX350 devices, the following command is not supported: request load merge filename. PR1533284

  • On NFX250 devices, the l2cpd core files might be seen on reboot. This is a one-time core and does not impact the functionality of the device. PR1561235

Resolved Issues: 20.2R2

High Availability (HA)

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

Interfaces

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

Platform and Infrastructure

  • 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

  • SDWAN NFX150 HA - while upgrade from 19.4 -> 20.2 observed "/usr/sbin/boot_mgmt_fsm: line 40: echo: write error: No space left on device issue" that is not allowing to upgrade.

Resolved Issues: 20.2R1

Application Security

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

High Availability

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

Interfaces

  • On NFX150 devices, no error is displayed when the commit fails after you configure native-vlan-id on an access VNF interface. PR1438854

  • On NFX250 NextGen devices, the monitor interface traffic command might not display the pps output for SXE and physical interfaces. PR1464376

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

  • On NFX350 devices, if you delete and add an SXE interface, the SXE interface moves to the Spanning Tree Protocol blocking (STP BLK) state, and the traffic drops on that interface. PR1475854

Mapping of Address and Port with Encapsulation (MAP-E)

  • On NFX Series devices, IP identification (IP ID) is not changed after MAP-E NAT44 is performed on fragment packets when the packets reach the customer edge (CE) device. PR1478037

Platform and Infrastructure

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

  • On NFX350 devices, if you execute the show vmhost mode command multiple times, JDM might crash and cause the show vmhost mode commands to stop working. PR1474220

  • Core files on NFX250 while adding the second LAN subnet. PR1490077

  • 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

Virtualized Network Functions (VNFs)

  • On NFX150 and NFX250 NextGen devices, when two flowd interfaces are mapped to the same physical interface and if you delete the interface mapping to VF0, the traffic flow is disrupted. Even though the mapping is moved to VF0, the MAC address is not cleared in VF1, which disrupts the traffic. PR1448595

  • On NFX350 devices, VNF instantiation is not working properly. PR1478456

Documentation Updates

There are no errata or changes in Junos OS Release 20.2R3 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.2

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.2R3:

  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.