Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Open Issues

Learn about open issues in Junos OS Evolved Release 21.4R3 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 are not coming up after removing channelization through single commit,that is by using delete interfaces. PR1592238

  • On QFX5700 devices, 400G DAC flap might be seen after OIR, FPC restart, device reboot enable or disable interface. PR1618488

  • On QFX5700 devices, 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 may 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 through 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

Network Management and Monitoring

  • An improper access control vulnerability in Juniper Networks, Junos OS Evolved allows a network-based unauthenticated attacker who is able to connect to a specific open IPv4 port, which in affected releases must otherwise be unreachable, to cause the CPU to consume all resources as more traffic is sent to the port to create a Denial of Service (DoS) condition. PR1636338

Routing Policy and Firewall Filters

  • On QFX5700 devices, when we issue clear firewall all command, policer statistics are not cleared. User defined policer statistics are removed. PR1581867

User Interface and Configuration

  • File delete with regex might fail, if you use the filename without regex it works. PR1624562

EVPN

  • 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

Infrastructure

  • Enabling MPLS traffic engineering will cause 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 will solve this issue. PR1617629

Network Management and Monitoring

  • CHEF: hitting SSL: Chef client creation is failing when trying to connect chef-node to chef-server.PR1648066