Resolved Issues
Learn about the issues fixed in this release for NFX Series.
For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.
Flow-Based and Packet-Based Processing
-
High latency and packet drops will be observed with the
transmit-rate exact
knob enabled for one or more schedulers of an IFL/IFD.
Interfaces
-
On the NFX350 device, even though the ethernet cable is physically plugged in and the
show interface
command displays the Front panel LED status asup
, the front panel LED is not ON
-
When issuing request support information, there was a syntax error when looking at the nfx-back-plane (was nfx-backplane, instead of nfx-back-plane)
-
On Junos NFX350 Platforms, if you disable any RJ-45 interface through configuration, auto-negotiation at the MAC (Media Access Control) level on the remaining ports of the group of 4 ports (either 0-3 or 4-7) is disabled, resulting in traffic disruption. The impact is confined to the group of ports on which the port is disabled and the other group is not affected.
VPNs
-
IPSec tunnel is down if IKE external-interface is configured with IPv4 and IPv6 address. As a workaround, specify the local-address inside the ike gateway object if the configured external-interface contains both IPv4 and IPv6 address hosted on it.
VNFs
-
Non-root user cannot access VNF through SSH, Telent, and console.
On Junos NFX350 Platforms, in spite of disabling the Auto Negotiation (AN) on the interface through configuration, it stays enabled on the copper ports.This could result in mismatch of AN settings with the remote side configuration and disrupt traffic.
PR1719973