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.

Class of Service (CoS)

  • The class-of-service (COS) commit validation is missing for classifier when using code-point-aliases. The user can configure duplicate code-point-aliases and use them in a classifier. This will result in the cosd crash. The system can be recovered by correcting the config and applying the "restart class-of-service" command.PR1766873

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

  • When system comes up with BULK Layer 2 configuration, a subsequent CONFIG delete in a way that L2ALD is still not finished processing the config create, could lead to a race condition where FLOOD ROUTE DEL event can cause l2ald crash.PR1742613

  • On all Junos OS platforms, due to timing issues the PFE or PICs will be slow and services will face slowness issue and error message: 'Minor potential slow peers are: X' will be seen. This is rare timing issue.PR1747077

  • On Junos OS PTX Series platforms, with Protocol Independent Multicast- Bidirectional (PIM BIDR) mode with set protocols pim rp bidirectional address group-ranges configuration, PIM/MLD joins will not be learnt for multicast IPs other than link local IP and MY IP which will lead to traffic impact. Also, lo0 filter which were introduced with PR 1701756 for IGMP and MLD will be applied only for MY IPs and Link local IPs. For any other IPs other than above, lo0 filter will not work.PR1774562

  • On QFX10002-60c express based Junos platform the error logs are seen during boot time. These errors are not impacting any functionality. The table is getting programmed correctly. These are seen during system reboot and fpc reboot time. We will be emitting the logs for non default routing instances and not for default routing instance. PR1779890


  • 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

  • On vPTX platforms, the PFE receives an invalid token from RPD for composites next-hops due to which the PFE will crash leading to traffic drop.PR1740390

Network Management and Monitoring

  • If there is management-instance configuration, it is mandatory to add "routing-instance-access".PR1766854

Routing Policy and Firewall Filters

  • On all Junos OS and Junos OS Evolved platforms, the static routes are installed in the routing table even though the corresponding interface routes are not present.PR1714163