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 PTX Series routers.

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

General Routing

  • On a PTX Series router with a third-generation FPC, an error message shows up when the FPC goes online or offline. PR1322491

  • This is a timing issue during the sxe interface bring up (w.r.t i40e driver). This can be recovered by rebooting the complete board. PR1442249

  • FIPS mode is not supported. PR1530951

  • Socket to sflowd closed error comes up when the ukern socket to sflowd daemon (server) is closed. The error is rectified as the client successfully reestablishes the connection in the subsequent attempts. When these errors are consistent, it indicates a communication issue between sflowd and the sFlow running on the FPC. PR1538863

  • On PTX platforms, when inline jflow is configured and high sampling rate (more than 4000 per second) is set, high CPU utilization might be observed and this might result in relevant impacts on traffic analysis and billing. PR1569229

  • Copying files to /tmp/ causes a huge JTASK_SCHED_SLIP. Copy files to /var/tmp/ instead. PR1571214

  • When firewall is configured with both discard and port-mirror as actions in the same term, mirrored packet will be corrupted (will have two l2 headers). PR1576914

  • On PTX10008, the end-to-end traffic is not flowing for ethernet-switching in EP Style. PR1583219

  • On PTX3000 platform, if RPD is thrashing while doing GRES switchover there may be traffic loss on MPLS LSPs. PR1590681

  • Sflow Ingress sampling with ECMP export is not working due to TAL request failure for both single and double VLAN tagged traffic. Works fine without ECMP. PR1598263

  • On PTX10008 and PTX10016 devices with LC1101, LC1102, and LC1103 line cards, interface flapping might cause the interface CRC errors increase continuously, then traffic loss might be seen. This is a rare timing issue. PR1600768

  • The RS Fatal error (like "RS PHi Parity Fatal") is not handled in Chassis Management Error Handling Infrastructure (CMError) in Junos. Normally, the RS Fatal error is caused by hardware problem. If RS Fatal error happens on Packet Forwarding Engine (PFE) on FPC-PTX-P1-A/FPC2-PTX-P1A in PTX5000 or FPC-SFF-PTX-P1-A/FPC-SFF-PTX-T in PTX3000, any new operation on the FPC experiencing RS Fatal error will fail. For example, once any other FPC in the same chassis is rebooted and coming online, the FPC experiencing RS Fatal error will try to flush the virtual output queues (VOQs) towards the restarted FPC. However, the flush will fail due to the RS Fatal error and hence the buffers for VOQs towards the restarted FPC is not programmed. And this will result in traffic drops on all Packet Forwarding Engines of the problem FPC (even on the Packet Forwarding Engine not having "RS Fatal" error) towards the restarted FPC. PR1600935

  • On PTX5000 platforms with QSFP-100GBASE-LR4 optics, after a software upgrade, link flaps might be observed momentarily due to a firmware upgrade issue. This issue might cause traffic impact. PR1606008


  • On all Junos platforms with NSR configured, when dual-tranport is configured under protocols ldp and the inet-lsr-id/inet6-lsr-id is different from the router-id, the Label Distribution Protocol (LDP) replication session might not get synchronized and causing traffic loss during Routing Engine switchover. PR1598174

  • On all Junos platforms that is NSR configured, when configuration statement dual-transport is configured under protocols ldp and the inet-lsr-id/inet6-lsr-id is different from the router-id, VPLS connection on peer device might get down and traffic loss would occur during Routing Engine switchover. PR1601854

Routing Protocols

  • Due to a race condition between route re-convergence and the BGP-PIC version up message to the Packet Forwarding Engine, after a remote transit router reboot, certain BGP routes might reuse stale LDP next hops and cause packet discard at the transit router during the route re-convergence window. PR1495435

  • Here two routers with two different capacities are converging at two different times, so the micro loop occurs between the two nodes. So please check the work around provided. PR1577458

User Interface and Configuration

  • When a user tries to deactivate the MPLS related configuration, the commit fails on backup Routing Engine. Work-around details are provided in the corresponding section below. PR1519367

  • On PTX platforms, the default routing policy might not be changed back after it is changed to network-services enhanced mode. PR1587174