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 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 PTX Series platforms with FPC model FPC-PTX-P1-A or FPC2-PTX-P1A, you might encounter single event upset (SEU) event that might cause a linked-list corruption of the TQCHIP. The following syslog message gets reported:

    The Junos OS Chassis management error handling detects such a condition, raises an alarm, and disables the affected Packet Forwarding Engine entity. To recover this Packet Forwarding Engine entity, restart the FPC. Contact your Juniper Networks support representative if the issue persists even after the FPC restarts. PR1254415

  • The Next Generation Routing Engine (NG-RE) with models RE-S-X6-64G, RE-S-2X00x6, and RE-PTX-X8-64G on PTX Series platforms might encounter a transient system freeze of the Linux based host (VM Host) for about 20 - 35 seconds, cause protocol flaps, FPC restart, and mastership switch between Routing Engines. Because of the incorrect handling of the disk I/O commands, a disk I/O timeout is reported and the system will recover by resetting the solid-state drives (SSD) channel. The system will continue to operate correctly after such an event. PR1312308

  • The following log message might appear in some race conditions when NG-RE is used: kernel: interrupt storm detected on "irq11:"; throttling interrupt source PR1386306

  • On Junos PTX Series platforms, the J-Flow service might not report the accurate throughput rate. This issue is seen when there is high sampled traffic rate with low flow cache hit ratio. PR1502645

  • Flapping might be observed on channelized ports of PTX Series routers during ZTP, when one of the ports is disabled on the supporting device. PR1534614

  • The Socket to sflowd closed error comes up when the ukern socket to sflowd daemon (server) is closed. The error is rectified by itself 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 Series platforms, when the inline J-Flow is configured and high sampling rate (more than 4000 per second) is set, a high CPU utilization might be observed. This might impact traffic analysis and billing. PR1569229

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

  • On PTX1000 and PTX10002-60C platforms, file permissions for /var/db/scripts files are changed after reboot. This might impact scripts running on the box. PR1583591

  • When a congestion is on the link where telemetry streams are connected, then in a race condition, na-grpcd core files are generated. This impacts the telemetry service as the na-grpcd will take a minute to come back online. PR1587956

  • When the interface transitions from down to up, the carrier transition counter value of a particular interface can be incorrect when the peer interface takes longer time to come up. Configuring the hold-time for up and down helps to resolve. PR1601946

  • Under MAC statistics, the output-mac-control-frames and the output-mac-pause-frames do not increment. PR1610745

Layer 2 Ethernet Services

  • It is observed rarely that issuing the request system zeroize does not trigger ZTP. A simple workaround is to reinitiate ZTP. PR1529246