Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Open Issues

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

General Routing

  • An improper handling of syntactically invalid structure vulnerability in Object Flooding Protocol (OFP) service of Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). Please refer to https://supportportal.juniper.net/JSA75753 for more information. PR1714333

  • Many issues are observed in Junos OS Evolved library regarding the DNS resolution and these were fixed in this PR. PR1733616

  • When DHCP trace options are enabled, there is a possibility that jdhcpd could generate a core file. In general, traceoptions should be enabled only for debugging. They should be disabled once debuffing is done. PR1771121

  • On PTX10001-36MR and PTX10004/PTX10008/PTX10016 Junos OS Evolved BT Packet Forwarding Engine based platforms, same priority and weights are given to strict-high queue and other non-strict high queues for same transmit-rate set in scheduler CLI configuration which leads to no preference to strict-high queue. This causes tail-drops packets count to increment on strict-high queue. There is no impact on system due to this issue. PR1773709

  • On Junos OS Evolved PTX platforms in the EVPN-VxLAN (Ethernet VPN-Virtual Extensible LAN) DCI (Data Center Interconnect) multihoming scenario, due to source MAC update/modification destination MAC route might be deleted that results in traffic drop. The issue occurs when the MAC is learnt over ESI-LAG (Ethernet Segment Identifier - Link Aggregation Group). PR1783935

  • The support to export key leaves was done through PR 1818150 recently and it is done only in the latest releases. The support to export key leaves is unavailable uniformly across pre-GNMI/ GNMI and UDP on the 23.4 release. PR1831799

  • This is a transient log which sometimes is seen when LSI is recreated. This has no functional impact. It's generated because of additional dependency of LSI with BD. System takes care of cleaning the token for which this error is generated. This can be confirmed via VTY command show sandbox token. PR1834443

  • On Junos Evolved PTX10003 platform the command indirect-next-hop-change-acknowledgements is required in the junos-default configuration. If the said command is missing, it will result in packet loss. PR1836337

  • When AH is in progress and GRES happens, there is a possibility that AH might fail. In case of AH Failure, following recovery mechanisms can be tried: Try executing the AH through CLI to see if it helps. If CLI AH command does not recover the link, PFE offline/online can be tried to recover the link. If PFE offline/online also does not recover the link, then FPC offline/online can be tried. PR1843391

  • The RTI Await LSI Cookie in longevity test during routing instance is added and deleted. PR1843627