Open Issues

On the PTX platform with FPC-PTX-P1-A or FPC2-PTX-P1A, you might encounter a single event upset (SEU) event that might cause 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 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 support representative if the issue persists even after the FPC restarts. PR1254415

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

Unsupported configuration is being attempted by the script that then hits the maximum threshold for the given platform PTX5000. 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

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

While loading baseline configurations in Gladiator box, continuous FPC core seen at pci_user_pio_read_func and posix_interface_abort along with scheduler hog messages. PR1644576

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 ztp. PR1649576

A limitless resource allocation vulnerability in FPC resources of Juniper Networks Junos OS Evolved on PTX Series allows an unprivileged attacker to cause Denial of Service (DoS). Please refer to https://kb.juniper.net/JSA69916 for more information. PR1657659

ZTP: DHCPACK not received at ztp-server after zeroize of the device (client)PR1658287

When an FPC (Flexible PIC Concentrator) on PTX5000 platforms is shut down by issuing a request command (request chassis offline slot <slot-number>) or by FPC power off configuration (set chassis fpc x power off), it gets stuck in the 'Announce Offline' state since the associated timer (fru_graceful_offline_timer) doesn't increment and expire as it is supposed to. PR1683562

Sflow ingress or egress sampling does not work when ECMP nexthops are involved.PR1685407

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

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

After an interface is disabled, show mpls lsp bypass statistics shows BackupActive Timeout failure bypass. PR1597733

In rare occurrence Routing Engine kernel might crash while handling TCP sessions if GRES/NSR are enabled. PR1546615

Any platforms with Micro BFD configured on member links of the LAG or aggregated Ethernet interface, BFD Session state in Routing Engine remains as UP always even though PEER device has ceased. PR1675921