Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Open Issues

Learn about open issues in Junos OS Evolved Release 21.3R3 for PTX Series routers.

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

  • New fan failure alarm that is reported after 3 consecutive failures interrupt status is high.PR1500920

  • In Junos OS Evolved 20.3, fabsopke-fchip core file might be seen if fabsopke-fchip restarts and SIB goes offline one after the other within the same minute. Any previous alarm does not get cleared.PR1525577

  • Error logs are observed in FPCs once during bootup of LCs after restarting the router or FPC restart. PR1561362

  • For the input subscription paths containing a ":" character, the extension header in case of GNMI and certain fields for the show network-agent statistics command shows incorrect values. PR1581659

  • On all PTX Series devices running Junos OS Evolved, addition or deletion of the filter configuration in the loopback interface might result in error messages with some packet drop for short duration, which might be self-recovered. PR1589296

  • 10,000 term interface-specific-filter (with or without the fast-lookup filter statement) with a set of add or delete interface-specific-filter events leads to the evo-aftmand process generating a core file. This is not an FFT crash as the filter is programmed in FLT (hence a baseline issue).PR1610506

  • Several warning messages show up while the RPD process restarts while performing GRES on a system running Junos OS Evolved. PR1612487

  • Traceroute in MPLS OAM on SR over IPv6 might fail in ECMP case if the Junos OS Evolved device is in topology. This is because Linux kernel in Junos OS Evolved puts an autoflowlabel on every IPv6 packet. This flow label is transparent to daemon process, which uses a null value for it and calculates the nexthop details. The Packet Forwarding Engine however takes the flow label into account and calculates the nexthop details. This difference in calculation of the nexthop details leads to a mismatch in the path the packet takes to the destination and might cause the traceroute to fail. PR1618406

  • When you disable or remove warm standby configuration and enable or add NSR, please split these into two separate configuration commits.PR1655249

  • In case a GRPC client repeatedly connects and disconnects to CDA GRPC server, in some rare scenarios it might lead to CDA crash.PR1655949

  • Error logs from rpd/kernel corresponding to JSR backup registration failed might be observed during extreme scenarios of rpd restart etc,. However, the issue is seen has drastically come down and happens rarely. The issue is benign and self recovers with no impact expected on the connection or traffic. The right fix of the issue is in the latest primary branch, but it cannot be backported as the risk is associated with the fix complexity. PR1660685

Juniper Extension Toolkit (JET)

  • In Junos OS Evolved, there are two different gRPC Python files for each JAPI file. The names of the files are * and * The stub creation functions are present in * PR1580789

Layer 2 Features

  • If request system zeroize does not trigger zero-touch provisioning, re-initiate the ZTP as a workaround. PR1529246

Network Management and Monitoring

  • When maximum-password-length is configured and user tries to configure password whose length exceeds configured maximum-password-length, error is thrown, along with error ok tag is also emitted. (Ideally ok tag should not be emitted in an error scenario.) The configuration does not get committed.PR1585855

Routing Policy and Firewall Filters

  • On all Junos OS Evolved platforms, the unsupported configuration of BGP flow spec interface-group exclude might lead to some errors and Packet Forwarding Engine corruption, which does not permit filter bind. PR1639391

User Interface and Configuration

  • Device running in recovery mode does not show recover mode banner. PR1589165

  • Configd might not clean up shared pointers in DDS as seen in the output of show platform object-info anomalies app configd. There is no functional impact of these anomalies and these can be cleared by restarting configd from the CLI by issuing restart configd.PR1641960

  • If after any configuration commit an anomaly is seen for configd in the output of show platform object-info anomalies app configd, it means that the app configd has not released the shared pointer after deleting the published object. This has no functional impact and the anomaly can be cleared by restarting the app configd.PR1643192