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

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

  • 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 of 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 is accompanied by other FPC major alarms. Once the faulty FPC is replaced with a good one, the alarm is still 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 by issuing 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. Use one of the following two methods to do a graceful FPC OIR removal:

      1. Execute the request chassis fpc slot <slot #> offline command from the CLI.

      2. 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.


  • 400G LR4-10 link does not come up after deleting interface disable configuration when port is disabled followed by system reboot. PR1625494

  • Interface convergence time for QFX5220-128C is 1 min more than earlier. PR1636181

  • Unexpected carrier transitions are seen on JNP-100G-2X50G-xM after cable plug out and plug in on QFX5130-32CD and QFX5220-32CD. It is observed that the Carrier Transitions counter increments by 1 on cable plug out and by 3 on cable plug in. It should increment by 1 in both cases. PR1642744

  • During bulk mac move scenarios, we see few MAC entries missing in the Routing Engine CLI show ethernet-switching table, even though those entries are present in the hardware. As MAC is present in the hardware, there is no impact to the Packet Forwarding Engine. PR1650329

  • TOS(DSCP+ECN) bits are not getting copied from the Inner Layer 3 header to outer VXLAN header at the Ingress VTEP. Because of this in the core, ECN marking and DSCP classification are not working.PR1658142

  • On QFX5700, if JNP-FPC-20Y is restarted, in rare situations traffic flow does not resume on all ports of the FPC.PR1659566

  • The general recommendation with OISM is to not have CE interfaces in SBD. Adding the same can lead to traffic drops. PR1668921

  • After evo-pfemand restart, one interface does not come up. PR1669037

  • On QFX5130-32CD, ND resolve packets are subjected to loopback filters configured. The resolve packets might get dropped as per the loopback filter configuration. In some cases, if IPv6 neighbours are cleared using clear ipv6 neighbors command, the device may not re-learn those IPv6 neighbours. PR1671730