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 QFX5130-32CD and QFX5220.

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 QFX5220-32CD, VLANs between 3968 and 4095 are reserved for Layer 3 interfaces by default. So, these VLANs cannot be used for Layer 2 interfaces. As of now there is no commit check added for this purpose. You need to take care of this while configuring VLANs for Layer 2. PR1423468

  • On the QFX5130-32CD platform running Junos OS Evolved, you cannot clear or reset the disk option specified in the scheduled request node reboot command. The node reboots with the disk option last specified. PR1517596

  • When the evo-pfemand process is re-started due to any error conditions, the channelized interfaces (if configured) will flap two times ( once during the initialisation) and the second time after the configuration is programmed. PR1526984

  • On all QFX devices that support Junos OS Evolved, if scaled OSPF neighbors (e.g 512 neighbors) are formed over IRB interfaces with layer 2 interfaces in the interface-mode trunk, the OSPF routes might be not learned from the neighbors. The issue results in traffic loss. PR1570498

  • QFX5220-32CD: Rarely, a picd daemon core seen after bootup. This doesn't affect the functionality as the device recovers itself automatically by restarting picd daemon. PR1583164

  • In the latest 21.1R1 release, regression script can trig PTP BC of QFX5220-32cd platform ran into freerun state (expected Phasee Aligned). It seems below configuration sequence can pontentially trigger the issue: (1) config PTP BC, then commit; (2) config IP address on interface, then commit; The workarund to avoid this happening in the release, follow below config sequence: (1) config PTP BC; (2) config IP address on interface; (3) commit; The key workaround is that don't do seperate commit and do commit once. PR1604699

  • On Junos OS Evolved platforms when NDP (neighbor discovery protocol) entries are scaled to 32000 over IRB in one shot, ndp process might reach to 100% CPU utilization and unicast nexthops for all 32000 entries might not be present. This will result in traffic drops for entries for which unicast nexthop is not present. PR1551644

Layer 2 Ethernet Services

  • It was observed rarely that issuing a request system zeroize does not trigger Zero Touch Provisioning (ZTP). A workaround is to re-initiate the ZTP. PR1529246

Routing Protocols

  • On Junos OS Evolved platforms, an rpd crash might be seen after reboot of the Junos Evolved device when MSDP is enabled. This might cause traffic drop until rpd comes up after the crash and restores all the routes. PR1536593

User Interface and Configuration

  • On Junos Evolved platforms, HTTPS URLs are not handled properly in the backend code handling file copy https-url destination .. command. PR1596881