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.

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 can cause a linked-list corruption of the TQCHIP. The following syslog message is 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, and raises an alarm and performs the disable-pfe action for the affected Packet Forwarding Engine entity. To recover this Packet Forwarding Engine entity, a restart of the FPC is 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 is seen after an FPC restart. PR1254415

  • The following log message might be seen on an FPC with WINTEC mSATA SSD: SMART ATA Error Log Structure error: invalid SMART checksum. PR1354070

  • The firewall counter for the lo0 interface might not increase. PR1420560

  • An rpd core file is generated when FIPS mode is set. PR1530951

  • sFlow reports incorrect Extended Router Data for traffic going over a nondefault VRF. PR1537190

  • The output VLAN is not reported correctly in the extended switch data for IP-IP transit traffic when you configure both dynamic tunnel and FTI as backups. PR1537648

  • The following error comes up when the ukern socket to sflowd daemon (server) is closed: Socket to sflowd 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 sFlow running on the FPC with the sflowd. PR1538863

  • A crash is triggered when the IPv6 transit statistics feature is bounced, that is, enable - disable - enable in presence of aggregated Ethernet configuration. With scalar interfaces, this is not known to occur. This only affects the uKern (Packet Forwarding Engine) and has no effect on the Routing Engine. PR1571279

Interfaces and Chassis

  • The resiliencyd.re.re0 core file is seen when executing cminfra scripts. There is no functional impact on resiliencyd. Once cored resiliencyd recovered, then it behaves normally as expected. PR1578822

Layer 2 Ethernet Services

  • Issuing the request system zeroize command sometimes does not trigger ZTP. Workaround is to reinitiate ZTP. PR1529246

MPLS

  • The RSVP interface update threshold configuration syntax has changed between Junos OS Releases 18.2X75-D435 and 20.3X75-D10 to include curly braces are the threshold value. As such upgrading and downgrading between these two releases is not entirely automatic and now requires the user to delete this stanza if configured before the downgrade and then manually reconfigure. PR1554744

Routing Protocols

  • After a remote transit router reboot, due to a race between route reconvergence and BGP PIC version up message to the Packet Forwarding Engine, certain BGP routes might reuse stale LDP next hops and cause packet discard at the transit router during the route reconvergence window. PR1495435

  • Device allows more SSH connection than configured under connection-limit. PR1559305