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

  • In the platform using indirect next hop (INH), 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. When the version-id of session-id of INH is above 256, the Packet Forwarding Engine might not respond to session update, which might cause the session-id permanently to be stuck with the weight of 65535 in Packet Forwarding Engine. It might lead Packet Forwarding Engine 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

  • When subscribing to sensor paths /junos/system/linecard/packet/usage/, /junos/services/label-switched-path/usage/ or other line card (Packet Forwarding Engines) sensor paths in gNMI subscription mode, packet drops may be seen in the CLI command show network-agent statistics gnmi detail output. The collector output may also contain missing sequence numbers. For example, the sequence number output may be 0, 3, 6, 9, 12, etc. instead of 0, 1, 2, 3, 4, etc. PR1703418

  • In Chassisd, Junos Telemetry interface thread takes more time in streaming Junos Telemetry interface packets because of the volume of data and number of sensors involved with this daemon. Junos Telemetry interface thread engaged for more time to process streaming events cause chassisd master thread to lose receive or send keepalive messages to and from other Routing Engine, which eventually cause automatic Routing Engine switchover in most of the cases. PR1706300

  • On QFX10000 and PTX Series platforms, traffic going over unilist is dropped when unilist member goes from next-hop hold state to unicast and aggregate state.PR1713279

  • During heavy network churn (interface flaps, session flaps etc.) Packet Forwarding Engine crash may be seen when streaming both SR and SRTE stats on PTX Series Junos OS platforms. Issue is not seen when only SR stats or SRTE stats are enabled. PR1730927

  • RPD core is sometimes seen if there are many unilist nexthop with identical key values but different metric in Evo, esp when ACK is requested for those nexthops. PR1745509

  • On PTX10008, PTX10016 and PTX10004 platforms, the Routing Engine mated on the Control Board are one FRU(Field Replaceable Unit). Upon Routing-Engine replacement the Control-board might be stuck in State 'Present' while the Routing Engine is fully operational and online. To get the Control Board back online, execute the following command request chassis cb slot slot online. PR1747567


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