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 Evolved Release 21.2R3 for QFX Series switches.

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

  • FIPS mode is not supported. PR1530951

  • On QFX5700 platforms few interfaces do not come up after removing channelization through single commit that is by using delete interfaces. PR1592238

  • On QFX5220-128C, FEC mode does not come into effect after manual configuration change. The link might go down after FEC mode change. PR1603302

  • On QFX5700 ungraceful removal (OIR) of FPC or an FPC fault might result in a PCIE MAJOR alarm PCI Uncorrected error on dev 0000:00:03.0 which does not get cleared. The only way to clear this alarm is reboot the device. There are 2 situations in which this alarm can be seen: 1. FPC is faulty: In rare FPC fault cases, the PCI uncorrected error alarm might be seen along with FPC going to a Fault state as indicated by the show chassis fpc command. This will be accompanied by other FPC major alarms. Once the faulty FPC is replaced with a good one, the alarm will still be seen, and a reboot is required to clear this alarm. Post identification of the fault and FPC replacement, this alarm is harmless, and FPC state can be confirmed via the show chassis fpc command. 2. Ungraceful OIR: The ungraceful removal of FPCs is not recommended on QFX5700. This operation might result in PCI Uncorrected Error alarm. Please use one of the following two methods to do a graceful FPC OIR removal: a. Execute the request chassis fpc slot <slot #> offline command from the CLI. b. Press the Offline Button for 1 second on the FPC to offline the FPC. Once the FPC is gracefully offlined both LEDs - PWR and STS will go off. The FPC can be removed at this point. PR1620197

  • Enabling MPLS traffic engineering causes LDP session not to come up, the reason behind is that the underlying TCP connection stays at SYN-SENT state. Disabling or deactivating the MPLS traffic engineering solves this issue. PR1617629


  • On a Junos OS Evolved system, with EVPN VXLAN enabled, if there is a default route in primary instance pointing to management interface, it could result in anomalies in Junos OS Evolved database. PR1622035

Layer 2 Features

  • If request system zeroize does not trigger zero-touch provisioning, re-initiate the ZTP as a workaround. PR1529246

User Interface and Configuration

  • File delete with regular expressions might fail. It works if you using filename without regular expressions. PR1624562