Junos OS Release Notes for NFX Series

New and Changed Features

• Release 18.2R3 New and Changed Features

• Release 18.2R2 New and Changed Features

• Release 18.2R1 New and Changed Features

Release 18.2R3 New and Changed Features

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

Release 18.2R2 New and Changed Features

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

Release 18.2R1 New and Changed Features

Hardware

• ADSL2, ADSL2+, and VDSL2 SFP modules—Starting in Junos OS Release 18.2R1, NFX Series devices support ADSL2, ADSL2+, and VDSL2 SFP modules. The ADSL2, ADSL2+, and VDSL2 SFP modules are supported on the SFP and SFP+ ports on the NFX150 devices. Note that the ADSL2, ADSL2+, and VDSL2 SFPs are not supported on the extension modules.

  [See ADSL2 and ADSL2+ SFP Interfaces on NFX Devices and VDSL2 Interfaces on NFX150 Devices.]

Advanced Policy-Based Routing (APBR)

• Advanced policy-based routing—Starting in Junos OS Release 18.2R1, NFX Series devices support advanced policy-based routing (APBR), also known as application-based routing. APBR involves classifying the traffic based on the attributes of the applications and then applying filters based on these attributes to redirect the traffic. A deep packet inspection (DPI) engine is used to inspect the traffic session to identify the application. APBR provides more flexible traffic-handling capabilities by offering granular control for forwarding packets based on application attributes.

  [See Advanced Policy-Based Routing on NFX Devices.]

Security

• Security—Starting in Junos OS Release 18.2R1, NFX Series devices support the Layer 7 security features such as AppSecure (Application Tracking, Application QoS, Application Firewall), IPS, UserFW, and UTM.

  [See UTM User Guide for NFX Devices.]

Virtual Network Functions

• Support for vMX VNF on NFX250-S1 and NFX250-S2—Starting in Junos OS Release 18.2R1, vMX can be configured as a VNF on NFX250-S1 and NFX250-S2 devices. You can use the JDM CLI to configure the vMX VNF.

  [See JDM User Guide for NFX250 Network Services Platform.]

Changes in Behavior and Syntax

• Factory-default Configuration

• High Availability (HA) and Resiliency

Factory-default Configuration

• Plug-and-play configuration (NFX150 and NFX250 devices)—The factory default configuration for NFX Series devices is modified to include the secure router plug-and-play configuration.

• In Junos OS Release 18.2R2, the factory-default configuration on NFX150 devices is changed to enable the front-panel copper port heth-0-3 to function as a WAN port. Previously, only the SFP ports were configured as WAN ports.

  In this release, the following changes are made to the default configuration:

  • The heth-0-3 copper port is mapped to the virtual ge-1/0/1 interface on FPC1.

  • The heth-0-4 SFP+ port is mapped to the virtual ge-0/0/3 interface on FPC0.

High Availability (HA) and Resiliency

• commit fast-synchronize option not supported for products with single Routing Engine (NFX Series)—Starting in Junos OS Release 18.2R1, Junos OS does not support the configuration option commit fast-synchronize at the [edit system] hierarchy level for all the products with a single Routing Engine for which chassis redundancy graceful-switchover is not supported. This option is disabled from the CLI.

Known Behavior

• Hugepapges

• Interfaces

• Platform and Infrastructure

• SNMP

• Virtual Network Functions (VNFs)

Hugepapges

• On NFX150 devices running Junos OS Release 18.2, 700 MB of hugepages are allocated by default for use by the system components. A portion of the 700 MB is used and the remaining free memory is available for the system as well as for third-party VNFs. PR1354027

Interfaces

• On NFX150 devices, the link will not come up if 1G SFP port is connected from heth-0-4 and heth-0-5 ports to a peer device. As a workaround, disable the auto-negotiation for the interface connected to the NFX150 device on the remote device. PR1330681

• Bi-directional 1G SFPs are not supported on 10G ports. PR1322408

• On NFX150 devices, the PPPoE session does not come up on the interface due to the hardware limitation for both tagged and untagged cases. As a workaround, enable the promiscuous mode on the interface. PR1347830

Platform and Infrastructure

• The Routing Engine boots from the secondary disk when you:

  • press the reset button on the RCB front panel, while the RE is booting up before Junos OS reboots.

  • upgrade the software by booting from the network using the request vmhost reboot network command, and the system fails to boot from the network.

  • upgrade the BIOS and it fails.

  • reboot the system and it hangs before Junos OS reboots.

  As a workaround, interrupt the boot process to select the primary disk. PR1344342

SNMP

• On NFX150 devices, SNMP does not work for the following commands:

  • show snmp mib walk jnxIpSecTunMonOutEncryptedBytes

  • show snmp mib walk jnxIpSecTunMonOutEncryptedPkts

  • show snmp mib walk jnxIpSecTunMonInDecryptedBytes

  • show snmp mib walk jnxIpSecTunMonInDecryptedPkts

  • show snmp mib walk jnxIpSecTunMonLocalGwAddr

  • show snmp mib walk jnxIpSecTunMonLocalGwAddrType

  PR1386894

Virtual Network Functions (VNFs)

• On NFX250 devices, when you configure virtual-network-functions using groups, the show configuration command output does not display the configurations. As a workaround, any one of the group configurations should be applied using the set apply-groups command. PR1302006

Known Issues

• Interfaces

• Platform and Infrastructure

Interfaces

• On NFX Series devices, if the IRB interface configuration and DHCP service configuration on JDM are removed and rolled back while retaining the VLAN mapping to the IRB interface, the DHCP service fails to assign IP address to the corresponding VNF interfaces and the service chaining fails. As a workaround, remove the VLAN mapping to the IRB interface along with IRB and DHCP service configuration on JDM. PR1234055

• On NFX150 and NFX250 NextGen devices, the connectivity fault management (CFM) on CCC interface is not supported. PR1311588

• When you issue a show interface command on NFX150 devices to check the interface details, the system will not check whether the interface name provided is valid or invalid. The system will not generate an error message if the interface name is invalid. PR1306191

• On NFX150 devices, when you reboot the fpc0 interface, a few error messages are seen in the VTY console. PR1326487

• On NFX150 devices, the MTU of a heth interface cannot be set. The configuration knob of set vmhost interfaces heth-X-Y mtu is not supported. PR1346876

• On NFX150 devices, the link will not come up if 1G SFP port is connected from heth-0-4 and heth-0-5 ports to a peer device. As a workaround, disable the auto-negotiation for the interface connected to the NFX150 device on the remote device. PR1428020

• On NFX250-S1E devices, the JSXE0 interface might not get an IP address from DHCP server. PR1354596

Platform and Infrastructure

• On NFX150 running Junos OS Release 18.2, alternate mark inversion (AMI) does not support the ME region upgrade using the ESRT upgrade method. Hence, with the latest BIOS ABDN_U_POR3-SFP_11.37.00, BIOS upgrade for the ME region is not supported. PR1333875

• Starting in Junos Release 18.1, the file transfer rate from an external media over the network to an NFX150 device is around 40-50 Mbps. PR1290263

• Dev signed image from Juniper Networks can be upgraded in NFX150 devices. However, you can rollback if you have upgraded the dev signed image unknowingly. PR1344738

• During FTP on NFX150 devices, the following error message appears: ftpd[14105]: bl_init: connect failed for `/var/run/blacklistd.sock' (No such file or directory). PR1315605

Resolved Issues

• Resolved Issues: 18.2R3

• Resolved Issues: 18.2R2

• Resolved Issues: 18.2R1

Resolved Issues: 18.2R3

• On NFX150 devices, the show cli device-list command gives a syntax error. PR1402855

• On NFX250 devcies, an SFP-T interface will not become active (UP) when it is plugged into either a ge-12/0/0 or a ge-13/0/0 interface. PR1404756

• On NFX150 devices, the request vmhost reboot in minutes command with a delay specified in minutes reboots the device immediately. PR1406018

• When you run the show chassis fpc or show chassis fpc details command, the Temperature field in the command output message is displayed as Testing. PR1433221.

Resolved Issues: 18.2R2

There are no fixed issues in Junos OS 18.2R2 for NFX Series devices.

Resolved Issues: 18.2R1

There are no fixed issues in Junos OS 18.2R1 for NFX Series devices.

Documentation Updates

Migration, Upgrade, and Downgrade Instructions

• Upgrade and Downgrade Support Policy for Junos OS Releases

• Basic Procedure for Upgrading to Release 18.2

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 about 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 18.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.

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.

Product Compatibility

• Hardware Compatibility Tool

• Software Version Compatibility

Hardware Compatibility Tool

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

Software Version Compatibility

This section lists the vSRX and Cloud CPE Solution software releases that are compatible with the Junos OS releases on the NFX Series devices.

NFX250 Software Version Compatibility

This section lists the vSRX and CloudCPE Solution software releases that are compatible with the Junos OS releases on the NFX250 devices: