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 22.1R1 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.

Class of Service (CoS)

  • Protocol-specific rewrite rules are not yet supported in Junos OS Evolved based products. PR1632134

General Routing

  • During boot up PTP FPGA link resets which toggles the link, Hence the message Error: severity=Uncorrected (Fatal), type=Transaction Layer is observed in the console. PR1572061

  • Removal or addition of the nested firewall filter in lo0 sets or clear, displays the following error message:

  • Sflow ingress sampling reports incorrect OIF and NH with MPLS traffic (MPLS-IPV4/MPLS-IPV6 with ECMP and Ultimate Hop Pop(UHP) ) on the egress node. PR1602448

  • When the multicast traffic is sent from the Juniper Networks Session and Resource Control (SRC) to the receivers with egress sampling enabled then Jflow records report incorrect source IP and destination IP. PR1609008

  • 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 programed in FLT (hence a baseline issue). PR1610506

  • The memory usage of the rpd process on the backup Routing Engine might increase indefinitely due to leak in krt_as_path_t. PR1614763

  • This is for 400G or 4x100G interfaces using 400G-ZR optics. After the data path of the optics is powered up and Tx laser enabled, sometimes the actual transmitting power might appear very low. Inside 400G-ZR software driver, a check-and-recovery mechanism has been implemented. If the actual Tx power appears very low after powered-up and Tx laser enabled, a data path powering-down and re-init sequence is exercised. The Tx power level recovers back to normal. The user-visible side effect is that, if such a hardware bug is hit, the actual link up time is longer than expected. Because the workaround is built in the software, no further user-intervention is needed. PR1616445

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

  • On all Junos OS Evolved platforms with NSR turned on, the cosd (Class-of-Service process) might generate a core file after multiple Routing Engine switchovers. PR1620758

  • Layer 3 VPN (L3VPN) license warning message is generated with commit check, even though L3VPN license is installed. commit completes without errors.

  • On PTX10008 routers, license installation succeeds with the request system license add terminal command but installing the same license fails with the validation hook evaluation failed error message while performing commit. PR1628733

  • In some reload scenarios the config-sync service might fail due to xinetd limiting the SSH service, leading to the alarm status Major Application config-sync fail on node Re1. This might cause configuration difference between the primary and backup Routing Engines. As a workaround, restart the service from CLI using the restart config-sync command. PR1629952

  • In a working and non-working logs, l2d index is different for vrrp group number 187. This is the same group for which the packet gets dropped out of 400 groups, other groups are working as expected. So there is some fix which goes between working and NKWR related to l2dId which exposed the 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 same hash index. Ideally hash movement should happen to address collision but somehow it is not properly done. PR1633986

  • System reboot or boot up with traffic might result in init time fabric link crc errors and small percentage of traffic drops. PR1635178

  • The issue is 400G-ZR/400G-ZR-M optic transceiver firmware upgrade failure. It is a generic issue faced across all single RU platforms supporting QDD-400G-ZR/QDD-400G-ZR-M.PR1638284

  • NPU utilization properties and backpressure sensors are included to indicate the FLT utilization for the ZX and BT based PTX Series devices. The CLI used is show npu utilization stats filter pfe <>

  • When there is a transient drop in syncE clock quality, the line card incurs a variation in time error for a few additional seconds. Time error recovers to the expected value when syncE clock quality gets restored. PR1640332

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

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

  • PTX10003: Firewall counters might not increment upto 4 minutes, on adding new term to the existing filter using multiple commits. PR1649324

  • On PTX10008, SyncE clock hold-off-time configuration does not work due to incorrectly computed timer value. Only default hold-off 1000 ms works correctly. PR1649358

  • When a fully loaded PTX10016 setup with line rate traffic is rebooted, sometimes few interfaces might experience traffic loss (reduced throughput). PR1649979

  • Classifcation override configuration statement does not work for queue 0 to 3 for both IPv4 and IPv6 release.

    set class-of-service forwarding-policy class to_bronze classification-override forwarding-class bronze

    set class-of-service forwarding-policy class to_platinum_v6 classification-override forwarding-class platinumPR1650622

  • DCF8: PTX10008: EVPN-VXLAN intra-VLAN known unicast traffic flooded due to MAC installation failure on Packet Forwarding Engine. PR1652876

  • Multiple rewrite rules aggregated Ethernet: mpls-any and mpls-inet-both-non-vpn are not supported on PTX running BT ASIC. The order of applying the rewrite rules is not correct. The non-VPN rewrite rule gets into effect for the VPN traffic - See Rewriting MPLS and IPv4 Packet Headers.] PR1655653


  • On all Junos OS Evolved platforms, near-end port is not within RFC/IANA standards as the ephemeral or dynamic port range has been modified. PR1602717

Juniper Extension Toolkit (JET)

  • On all Junos OS Evolved platforms, 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 the * file. PR1580789

Network Management and Monitoring

  • The mgd process might crash when you configure an invalid value for identityref type leafs or leaf-lists while configuring Openconfig or any other third-party YANG. The issue occurs with JSON and XML loads. PR1615773

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

  • GrpcBundle anomalies in EDO are caused by addition and deletion of Grpc related configuration. These anomalies do not cause any functional issue. PR1619974

  • The issue with patch creation is when we unprotect the configuration of type setof. During commit synchronize MGD creates the patch for backup Routing Engine and commit fails because of the wrong patch. PR1636385

  • For an OpenConfig interface, if you configure a matching interface-range, then the deletion of that OpenConfig interface does not take effect. As a workaround, do not use the interface-range configuration for OpenConfig interfaces. PR1637381

  • If after any configuration commit an anomaly occurs for configd in the output of the show platform object-info anomalies app configd command, the APP configd does not release the shared pointer after deleting the published object. This has no functional impact and the anomaly can be cleared by restarting the application. PR1643192