Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

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

  • PTX Series platforms with the FPC-PTX-P1-A or FPC2-PTX-P1A line card might encounter a single event upset (SEU) event that causes a linked-list corruption of the TQCHIP. The following syslog message gets reported: Jan 9 08:16:47.295 router fpc0 TQCHIP1: Fatal error pqt_min_free_cnt is zero Jan 9 08:16:47.295 router fpc0 CMSNG: Fatal ASIC error, chip TQ Jan 9 08:16:47.295 router fpc0 TQ Chip::FATAL ERROR!! from PQT free count is zero jan 9 08:16:47.380 router alarmd[2427]: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 0 Fatal Errors - TQ Chip Error code: 0x50002 Jan 9 08:16:47.380 router craftd[2051]: Fatal alarm set, FPC 0 Fatal Errors - TQ Chip Error code: 0x50002 The Junos OS chassis management error handling does detect such a condition, raises an alarm, and performs the disable-pfe action for the affected Packet Forwarding Engine entity. To recover this Packet Forwarding Engine entity, restart the FPC as needed. Soft errors are transient or non-recurring. FPCs experiencing such SEU events do not have any permanent damage. Contact your Juniper Networks support representative if the issue occurs after an FPC restart.PR1254415

  • Flapping might occur on the channelized ports of PTX Series devices during ZTP, when one of the port gets disabled on the supporting device. PR1534614

  • Unsupported configuration is attempted by the script that then hits the maximum threshold for the given platform. PR1555159

  • 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

  • The output-mac-control-frames and output-mac-pause-frames counters do not increase. PR1610745

  • When sending BGP Labeled Unicast (BGP-LU) traffic or Layer 3 VPN traffic over IPIP tunnels, the remote end device is a purely an IP device that does not understand labels, the labeled unicast or Layer 3 VPN label cannot go on top. PR1631671

  • On all PTX platforms, EDAC errors are triggered but alarms are not observed until the FPC gets rebooted due to the data corruption in hardware.PR1646339

  • V6 default route will not get added after successful DHCPv6 client binding on PTX1000 router during zero-touch provisioning. PR1649576

  • On PTX10002, PTX10003, PTX10008, and PTX10016 devices; if protocols l2circuit and channel tcc is enabled for providing layer 2 transaction, IS-IS connection through the layer 2 domain might get failed and traffic loss might be seen. PR1590387

  • Junos might translate the custom yang configuration even after disabling the custom Yang package. PR1599107

Interfaces and Chassis

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

MPLS

  • On PTX3000 devices, if RPD thrashes during a GRES switchover, there might be traffic loss on MPLS LSPs. PR1590681

Platform and Infrastructure

  • In rare occurrence, Routing Engine kernel might crash while handling TCP sessions if you enable GRES or NSR. PR1546615