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 this release for the PTX10001-36MR, PTX10003, PTX10004, and PTX10008.

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

  • On all the platforms with BGP SR-TE (Spring-TE), in segment routing topology the transit v4 traffic might have missing labels and might get dropped in first hop, when ingress is forwarding traffic. It might miss out all the labels except the last hop in the v4 traffic forwarded by NH interface. PR1505592

  • VSTP vport scale crosses 3500 leading to VSTP convergence issues due to BPDU drops in packetio of the Packet Forwarding Engine. This issue can be solved by adding DDOS configuration to support the increased scale. PR1509685

  • BGP-SRTE binding-sid with more than one label stack needs enhancement for PTX10003-80C PTX10003-160C. For PTX Series does not support more than 1 chain-composite-next-hop, it can configure this CLI configuration statement to disable chain-composite-next-hop as a workaround. With this configuration statement configured, all labels are pushed from egress.


  • The SR-TE label with BSID traffic gets dropped in PTX10003. Please use the following configuration statement as a workaround:


  • In a scaled setup it is possible that during GRES operation, the rpd on the new primary Routing Engine can receive an ifstates update (DEL and CHANGE) and these are not expected during rpd re-syncing in such case the rpd can generate a core file and might recover automatically after sometime. PR1537947

  • GRES is not supported when FPCs are restarted. PR1539685

  • Issue the CLI command show system fabric app-status to see list of fabric applications that are running in the system and fetch the application status using the right application name. PR1540706

  • On PTX10008 with inherit VRRP configuration some of the sessions might take longer time to converge. And during this period we see traffic loss for those sessions. So if system has inherit sessions configured then it is recommended to reduce the inherit advertisement interval timer to 6 seconds to avoid traffic loss. Default value of the inherit time is 120 seconds. PR1571339

  • sflow ingress sampling does not work for user IPv6 traffic with aggregated Ethernet ECMP case at last hop router with UHP LSP. PR1582960

  • IPv6 based PKID enrollment operations are not supported over revenue ports on Junos OS Evolved platform.PR1584378

  • Used-power and allocated-power leaves for telemetry under /components path are currently shown as "0" for all FRUs. PR1587184

  • Brief multicast traffic loss is observed while performing Routing Engine switchover with GRES. PR1593810

  • Explicit fault trigger while Packet Forwarding Engine is in transition is not supported. Once Packet Forwarding Engine is in FAULT, Packet Forwarding Engine restart does not recover the Packet Forwarding Engine. PR1596476

  • The [Error]Jexpr: cannot find ifToken for counterType:12 has no impact on the operation of the system and can be safely ignored. Nothing needs to be done if this error is seen. PR1597355

  • When all Packet Forwarding Engines go offline and are brought online with multicast route being active during this cycle, multicast traffic is permanently lost due to the absence of mcast route. PR1598894

  • Due to issue in AGEOUT notification for inline sessions, sessions remain up till peer sends BFD down packet or BFD client brings it down. PR1599257

  • Do not restart fabric hub and fabric spoke applications during the FPC offline or online event. Wait for the FPC to be in stable state, before restarting the application. PR1600094

  • In PTX10008, at times, MVRP enabled trunk ports can go into blocked or designated state if the peer connected to the interface has no VLANs configured in its trunk port. PR1601915

  • If multiple Packet Forwarding Engines are brought online rapidly using the request chassis fpc x pfe-instance y online | restart, it might cause evo-aftmand to terminate and the FPC to reboot. PR1602035

  • Powering off Packet Forwarding Engines gives error messages Jexpr: deleteFdbEntry: Null. This happens when any of FPC has all the Packet Forwarding Engines go offline but the FPC is online and there are some routes deleted from the control plane. It does not affect any functionality. PR1602670

  • Slow counters (off-chip) used for ingress nexthops might not work. PR1603518


  • When using a source IP address as the management address of the box to ping a network address on a peer, the response for the ICMP ping from the peer, can end up on the management interface of the box, which is dropped by the Linux kernel as the RPF check is set to strict by default on the Linux kernel used on Junos OS Evolved. The Linux kernel expects the path to the peer to be on the WAN side and so drops the packet when it is received on the management interface from the peer when the RPF check for the management interface is set to strict. PR1498255

  • A rare software race condition within the Juniper Tunnel Device (JTD) driver might trigger a kernel core file. This condition might occur during the cleanup of a TCP flow from the JTD driver session table. PR1591820

Interfaces and Chassis

  • Change to IFD properties in 25G Mode brings down the adjacent channels. PR1594740
  • The licenses used value for Port Bandwidth Usage (PAYG) field under show system license does not update when new interfaces are created. In order to correct the value, the IFMAND process needs to be restarted to invoke a refresh. PR1595179
  • The show platform object-info anomalies summary CLI command may time out after the system is up for some time. This does not affect normal operation of the system but this debug command will not work.


  • The rpd generates a core file most of the times in standby LDP module when static LDP P2MP configuration is deleted. PR1594405
  • Multipoint LDP (mLDP) transit statistics reset after Routing Engine switchover. PR1596395

Routing Protocols

  • This scenario happens when we enable IS-IS authentication key-chain having multiple keys between routers. TheIS-IS adjacency is up since 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. However, that does not happen. PR1572441

Network Management and Monitoring

  • Reported Junos OS User Interface Scripting Environment (JUISE) generates a core file while using request-system-storage-cleanup RPC with POST method in HTTP. The root cause is that this RPC sends a long list of file details. Other RPCs do not have this issue. PR1587337

Routing Protocols

  • This scenario happens when we enable IS-IS authentication key-chain having multiple keys between routers. The IS-IS adjacency is up because both the 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 should go down. However, that is not happening. PR1572441

User Interface and Configuration

  • When a user tries to deactivate the MPLS related configuration, the commit fails on backup Routing Engine. PR1519367

  • If an inet filter is configured with or without family statement then changing its configuration to without or with family statement might cause the filter process (firewalld) to restart unexpectedly. PR1556426

  • The scp CLI command does not work from CLI. Users can use the file copy CLI command instead of scp CLI command as a workaround. PR1582916

  • Post request system zeroize operation, sshd service is not enabled by default due to race condition on PTX10008. Hence it is recommended to enable edit system services ssh as part of the first commit on the device so that user 'ssh' credentials are created properly on the device and there is no need for password to log in to the backup Routing Engine. PR1594258