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

  • PTX Series platforms with FPC-PTX-P1-A or FPC2-PTX-P1A line cards might encounter a single event upset (SEU) event that might cause a linked-list corruption of the TQCHIP. PR1254415

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

  • With Next-Generation Routing Engine (NG-RE), in some race conditions, the following error messages might be seen on master Routing Engine: kernel: interrupt storm detected on "irq11:"; throttling interrupt source. PR1386306

  • FIPS mode is not supported. PR1530951

  • 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 automatically 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 PTX10000 line of routers except PTX10001 and PTX10002, when the Linux Chassis Manager (LCMD) polls power supply modules (PSMs), the memory used for that polling does not get freed. The amount of memory that is not being freed depends on the number of sensors (FPCs and PICs) installed in the chassis. The LCMD process will continue to consume memory until all of the free memory available to VM Host has been exhausted. At that point, the LCMD restarts and causes mastership switchover of the Routing Engine. PR1555386

  • On PTX Series platforms, when 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

Layer 2 Ethernet Services

  • It is observed rarely that issuing the request system zeroize command does not trigger ZTP. As a workaround, reinitiate the ZTP. PR1529246

User Interface and Configuration

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