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.4R2 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

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

  • On Junos OS Evolved PTX10008 platforms, if multiple SIBs are in offline state and GRES is performed immediately, SIBs might be stuck in offline state for sometime. PR1554423

  • When an aggregated Ethernet link is brought down, a transient error message [Error] Nexthop: EalNhHandler: failed to add Nh: xxxx, type: composite, as pil add failed might be seen. There is no functional impact due to these errors. PR1570710

  • During boot up the PTP FPGA link resets which toggles the link, therfore the message Chassis : NG-RE : PCIe Bus Error: severity=Uncorrected (Fatal), type=Transaction Layerobserved in the console. PR1572061

  • A vulnerability in handling of exceptional conditions in Juniper Networks Junos OS Evolved allows an attacker to send specially crafted packets to the device, causing the Advanced Forwarding Toolkit manager (evo-aftmand-bt or evo-aftmand-zx) process to crash and restart, impacting all traffic going through the FPC, resulting in a Denial of Service (DoS). PR1572969

  • On all PTX Series platforms running Junos OS Evolved, addition or deletion or modification of the firewall filter configuration applied on the loopback interface in some scenarios (for example, change of one-pass to two-pass filters) might result in error messages with some packet drop for very short duration, which is self-recovered. PR1589296

  • 10,000 Term ISF filter (with or without fast-lookup filter configuration) with a set of add or delete ISF events leads to an evo-aftmand core file generation. This is not an FFT crash as the filter is programed in FLT (hence a baseline issue). PR1610506

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

  • When an aggregated Ethernet link is brought down, a transient error message [Error] Nexthop: EalNhHandler: failed to add Nh: xxxx, type: composite, as pil add failed might be seen. There is no functional impact due to these errors. PR1617388

  • Traceroute in MPLS OAM on SR over IPv6 might fail in ECMP case if Junos OS Evolved device is in the 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 NH details. Packet Forwarding Engine however takes the flow label into account and calculates the NH details. This difference in calculation of NH details leads to a mismatch in the path the packet takes to the destination and can cause traceroute to fail. PR1618406

  • Traffic loss observed on BGP-LU paths after restoring primary paths in setup with IGP or LDP RLFA enabled. PR1619229

  • Some of the frequencies shall fail in performance for PTP-PTP and PTP-1PPS. PR1624478

  • In working and non-working logs, l2d index is different for vrrp group number 187. This is the same group for which packet is getting dropped out of 400 groups, other groups are working as expected. Probably, a fix between working and NKWR related to l2dId exposed VRRP issue. Both VRRP MAC and interface MAC get stored in SLU my_mac_hash table. For finding hash index for vrrp mac we use l2dId, protocol type and vrrp group number as a key. In a non-working scenario there is a collision between interface mac and vrrp mac on the same hash index. PR1633986

  • MTS-MCAST: [PTX10003] Auto RP base verification failed with multiple RPs with same group range.PR1634982

  • System reboot or boot up with traffic could result in init time fabric link crc errors and cause traffic drop. PR1635178

  • The system ID that is exported should be different for UDP and GRPC/GNMI. In the case of UDP, the system name should be appended with the local IP address. PR1640442

  • On Junos OS Evolved PTX Series platforms, next-header match in IPv6 firewall filter doess not work as expected. Next-header matches the payload-protocol (last-header) on Junos OS Evolved PTX Series platform. PR1645401

  • Filter is not hit, after trying to program unsupported combination of match types in filter configuration. PR1648923

  • Junos OS Evolved: PTX10003 : Unsupported bit-op-type message seen for tcp flag match - (syn and ack) and !(syn and ack and rst). PR1649253

  • After configuring the warm-standby option, please wait for 3 minutes before performing a Routing Engine switchover. PR1623601

  • The show task replication returns not started for all protocols. When disabling or removing warm standby configuration and enabling or adding NSR, split these into two separate configuration commits. PR1655249

Class of Service (CoS)

  • The issue is seen only with the show command inconsistently while the physical interface scheduler map bindings are not updated correctly or in a transition state during booting time and initiating the show command show interface ifd-name name. Cosd is recovered after the crash and does not affect any other programming. Potential workaround : Wait until all the interfaces are up and interface binding configs are commit completed before triggering the show command show interface if-name extensive. PR1604169

Fault Management

  • On FPC log, when the system is up, the Packet Forwarding Engine error msg Jexpr: JexprHandleDdos faile to update plct pfe:1f proto:0x8400 is seen. This error msg is just a debugging error message, there is no functional impact with this log error messages. PR1610764

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 *pb2_grpc.py and *pb2.py. The stub creation functions are present in *pb2_grpc.py. PR1580789

  • Until Junos OS Evolved 21.3 release mgd is 32-bit binary. libsi can only be linked with 64-bit binaries. To access data or WAN ports in Junos OS Evolved we need libsi to be linked with the binary. By default the shell on the Junos OS Evolved device includes libsi, but it is not available to CLI commands as CLI makes mgd invoke cscript to run a Python script through CLI. PR1603437

MPLS

  • In Junos OS Evolved platforms, LDP session authentication key-chain configuration done based on session remote-id on initiator stops from session establishment even though the responder's authentication key-chain is configured for its remote-id. PR1592431

Network Management and Monitoring

  • mgd can crash when an invalid value is configured for identityref type leafs/leaf-lists while configuring Openconfig or any other third-party YANG, problem happens with json and xml loads. PR1615773

Routing Policy and Firewall Filters

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

Routing Protocols

  • This scenario happens when we enable IS-S authentication key-chain having multiple keys between routers. The IS-IS adjacency is up because both routers have the same key active. When we manually change the system time in such a way that routers have different keys active in the key chain, the IS-IS adjacency must go down. But that does not happen. PR1572441

User Interface and Configuration

  • Passwordless authentication successful for configured user even after deleting ssh public key details from user login hierarchy PR1625032
  • 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 CLI using: restart configd.PR1641960

  • If after any configuration commit an anomaly is seen for configd in the output of the following CLI show platform object-info anomalies app configd, it would mean 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 app configd. PR1643192