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 Junos OS Rlease 21.4R3 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 PTX platforms, some non-fatal interrupts (for example, CM cache or AQD interrupts) are logged as fatal interrupts. The following log messages will be shown on CM parity interrupt: fpc0 TQCHIP 0: CM parity Fatal interrupt,Interrupt status:0x10 fpc0 CMSNG: Fatal ASIC error, chip TQ fpc0 TQCHIP 0: CM cache parity Fatal interrupt has occurred 181 time(s) in 180010 msecs TQCHIP 0: CM cache parity Fatal interrupt has occurred 181 time(s) in 180005 msecs. PR1089955

  • 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

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

  • In the platform using INH (indirect next hop, such as Unilist) as route next hop type for multiple paths scenario (such as BGP PIC or ECMP), the session fast-reroute might be enabled in Packet Forwarding Engines (PFEs). When the version-id of session-id of INH is above 256, the PFE might not respond to session update, which might cause the session-id permanently to be stuck with the weight of 65535 in PFE. It might lead PFE to have a different view of Unilist against load-balance selectors. Then either the BGP PIC or the ECMP-FRR might not work properly and traffic might be dropped or silently discarded. PR1501817

  • On PTX Series devices and QFX Series devices running Junos OS, the JFlow 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 devices 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. PR1555159

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

  • A vulnerability in the handling of exceptional conditions in Juniper Networks Junos OS Evolved (EVO) allows an attacker to send specially crafted packets to the device, causing the Advanced Forwarding Toolkit manager (evo-aftmand-bt or evo-aftmand-zx) process to crash and restart, impacting all traffic going through the FPC, resulting in a Denial of Service (DoS). PR1572969

  • On PTX10000 platforms running Junos, file permissions might be changed for /var/db/scripts files after rebooting the device. This issue might have an impact on the scripts running on the box. PR1583839

  • When a number of routes resolve over an ECMP path, the inline BFD sessions might flap during clear isis adjacency command or RPD restart trigger. PR1612802

  • 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

  • Fetching SR JVision sensors for aggregated Ethernet IL per member link stats will not reset after doing the restart routing. PR1652372

  • 20.2R1 and later release has introduced firmware version for PHY chip on some PIC models. After that migration, some of the 100GE ports on PIC or its peer devices would see PCS and framing errors.PR1669267

MPLS

  • On PTX3000 devices, 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

Multicast

  • On Junos PTX platforms there might be a traffic blackhole which happens because of next-hop installation failure for multicast RSVP(Resource Reservation Protocol) P2MP(Point to Multipoint) traffic. This issue might only be encountered in a scaled RSVP P2MP environment after a network event which might cause reconvergence.PR1653920