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 Release 22.2R1 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.

Class of Service (CoS)

  • The class-of-service (CoS) values associated with default code-point aliases are inconsistent with Junos OS. Therefore, the incoming packets associates with incorrect CoS servicing level (forwarding class and packet loss priority (PLP)). PR1667404

General Routing

  • On the PTX Series routers 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

  • On routers and switches running Junos OS, with Link Aggregation Control Protocol (LACP) enabled, deactivating a remote aggregated Ethernet (AE) member link makes the local member link move to LACP detached state and cause traffic drops on that member link. The same scenario applied when a new member link is added where the other end of that link is not yet configured with LACP. PR1423707

  • In link aggregation groups (LAGs) enhanced link aggregation group (a.k.a. aggregated Ethernet child NH reduction/AE simple/LAG enhanced) scenario, if FPC hosting single child member aggregated Ethernet bundle is rebooted, the aggregate next-hops on such aggregated Ethernet bundles might be discarding traffic, as the logical interfaces reroute tables might get stuck in the down state, the packets drop might be seen on all other FPCs that the ingress traffic towards such aggregated Ethernet bundles and the aggregated Ethernet interfaces might not be used. PR1551736

  • Copying files to /tmp/ causes a huge JTASK_SCHED_SLIP. Copy files to /var/tmp/ instead. PR1571214

  • In PTX Series router under MAC statistics output-mac-control-frames and output-mac-pause-frames does not increment. PR1610745

  • Tunnel statistics displays incorrect values because of the tunnel interfaces cache flow. PR1627713

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

  • V6 default route will not get added after successful DHCPv6 client binding on PTX1000 router during ZTP. PR1649576

  • Junos OS Release 20.2R1 and later has introduced firmware version for PHY chip on some MIC and PIC models. After that migration, some of the 100GE ports on MIC/PIC or its peer devices might see PCS and framing errors. PR1651526

  • On all Junos OS PTX Series platforms, an FPC heap memory leak occurs while creating the composite multicast next-hop. PR1661286


  • With the rsvp local reversion configuration a PLR originates the "Bw_unavailable PathErr" during Fast Reroute (FRR). Junos Label Edge Router (LER or ingress router) ignores this type of PathErr message. However, this can be a problem if an ingress LER implementation reacts to this PathErr by bringing down the protected LSP causing packet loss.PR1670638


  • On Junos OS PTX Series platforms, the traffic might silently drop because of the next-hop installation failure for multicast Resource Reservation Protocol (RSVP) Point to Multipoint (P2MP) traffic. This failure might encounter in a scaled RSVP P2MP environment after a network event that cause reconvergence.PR1653920