Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Known Limitations

Learn about limitations in this release for PTX Series routers.

For the most complete and latest information about known Junos OS Evolved defects, use the Juniper Networks online Junos Problem Report Search application.

General Routing

  • If multiple sibs goes in to the Offlining state and halt the primary Routing Engine, the SIBs gets stuck in the Offlining state for sometime. Eventually the SIBs goes in to the Offline state. The show chassis sibs command must be used to check the state of the SIBs. PR1584712

  • On all PTX platforms, addition or deletion of the filter configuration in loopback interface might result in error messages with some packet drop for short duration, which would be self-recovered. PR1589296

  • IPv6 primary-only IP address does not move to the new primary Routing Engine after a switchover. As a workaround, you must deactivate and activate the primary-only IPv6 address on the primary Routing Engine. PR1648371

  • When a fully loaded Scapa16 setup with line rate traffic reboots, sometimes few interfaces might experience traffic loss (reduced throughput). PR1649979

  • Output filter cannot match the actual TTL value of packet for filter decapsulation traffic with no decrement ttl configured. PR1666673

Routing Policy and Firewall Filters

  • IPv4 unsupported filter match fragment-flags reserved command should not be used, as the matches do not fragment traffic pattern as well. PR1676517

User Interface and Configuration

  • In a dual-Routing Engine, assume ZTP process gets started on the primary Routing Engine node RE0. While ZTP and configuration commits on the primary Routing Engine RE0 (as part of ZTP) and configuration commit does not get completed on RE0. During this situation, if the Routing Engine switchover gets triggered then the configuration commit gets aborted or stopped ungracefully on the node RE0. The ZTP process gets started freshly on the new primary node Routing Engine RE1. Due to the ungraceful exit of commit process on RE0, the ZTP might not succeed on the Routing Engine RE1 because it might face commit failures on primary node Routing Engine RE1. PR1649786