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 QFX Series switches.

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


  • On QFX5000 switches, the end hosts might not communicate via EVPN-VXLAN domain after Ethernet Segment Identifier (ESI) failover. PR1584595

  • Modifying the I-ESI value affects the traffic events. If you are changing the I-ESI value, then do the following actions:

    1) Deactivate the interconnect stanza for the routing-instance in question.

    2) Modify the I-ESI value and then, activate the interconnect stanza. PR1600600

  • MAC-IP move across the L2-DCI is not updated in the MAC-IP table of the GW nodes for VLANs that have translate VNI configuration. This problem occurs only with translation VNI when MAC moved one from DC1 to DC2. Virtual machine move across DC where there is no translate VNI configuration in the interconnect works as designed. PR1610432

  • EVPN local ESI MAC limit configuration might not get effective immediately when it has already learned remote MH MACs. Clear the MAC table from all MH PE devices and configure the MAC limit over local ESI interfaces. PR1619299

Junos Fusion Satellite Software

  • Temperature sensor 2 output for opus SD106 is not showing. PR1582981

Layer 2 Ethernet Services

  • If the request system zeroize command does not trigger zero-touch provisioning (ZTP). As a workaround, reinitiate the ZTP. PR1529246


  • The RSVP interface update threshold configuration syntax has changed between Junos OS Release 18.2X75-D435 and Junos OS Release 20.3X75-D10 to include curly braces around the threshold value. Upgrading and downgrading between these releases is not entirely automatic. The user must delete this stanza if configured before the downgrade, then need to configure manually. PR1554744


  • The rpd process generates a core file at rt_iflnh_set_nhid . The core file is due to assertion caused by failure of hbt_insert for nhid belonging to a logical interface. There is a duplicate entry present which causes the hbt_insert failure. PR1588128

Platform and Infrastructure

  • The commit synchronize command fails when the kernel socket gets stuck. PR1027898

  • On a PTX Series router with a third-generation FPC, an error message is displayed when the FPC goes online or offline. PR1322491

  • On QFX10000 platforms, source MAC and TTL values are not updated for routed multicast packets in an EVPN-VXLAN. PR1346894

  • When a VLAN is added as an action for changing the VLAN in both ingress and egress filters, the filter is not installed. PR1362609

  • Arrival rates are not seen at system level when the global-disable fpc is configured on the QFX Series platforms. PR1438367

  • The unified ISSU is not supported on QFX5200 switches and fails. Also, dcpfe crash might be seen. PR1438690

  • A timing issue during the sxe interface bring up (with respect to i40e driver) is seen. To recover, reboot the complete board. PR1442249

  • The rpd process might crash if the BGP route gets resolved over the same prefix protocol next-hop in the inet.3 table that has both the RSVP and LDP routes. PR1458595

  • The storm control does not rate limit ARP packets on QFX10000 switches although shutdown action works. PR1461958

  • On QFX5110 switches with VXLAN VNI (multicast learning) scaling, traffic issue is seen from VXLAN tunnel to Layer 2 interface. PR1462548

  • On QFX5000 Series platforms with the instance-import configuration, unexpected route next hop occurs if you delete route with next-table. PR1477603

  • When the show pfe filter hw filter-name filter name command is executed, the command fails to retrieve the Packet Forwarding Engine programming details of the filter.PR1495712

  • On a fully scaled system where all the slices are utilized by different families of CLI filters, if you try to delete one family and add or change for another family with a higher number of filter terms which requires either expansion of the filter or creation of a new filter, the Packet Forwarding Engine fails to add the new filter as you receive out of sequence messages. That is, the add or change of the filter is called earlier than the delete of another filter will free up the slices. PR1512242

  • MSDP sessions might reset after a GRES reset even when the nonstop routing (NSR) state is synchronized and ready for switchover. PR1526679

  • When the DHCP relay mode is configured as no-snoop, it is observing that the offer gets dropped due to incorrect ASIC programing. PR1530160

  • FIPS mode is not supported. PR1530951

  • On QFX5100 switches that does not run qfx-5e codes, when an image with the third party SDK upgrade (6.5.x) is installed, the CPU utilization might go up by around 5 percent. PR1534234

  • On QFX5000 Series platforms, under EVPN-VXLAN spine-and-leaf environment, packets sent through VXLAN tunnel might lose Virtual Tunnel End Point (VTEP) IP address (source IP address (SIP)). Packets without SIP might cause memory leak. PR1536895

  • The Socket to sflowd closed error comes up when the ukern socket to sflowd daemon (server) is closed. The error is rectified by itself as the client successfully reestablishes the connection in the subsequent attempts. When these errors are consistent, it indicates a communication issue between sflowd and the sFlow running on the FPC. PR1538863

  • On an EVPN-VXLAN scenario, vmcore files are generated on master and backup Routing Engine with Layer 2 or Layer 3 multicast configuration. PR1539259

  • 100G AOC from third party does not comes up after multiple reboots. It recovers after enabling or disabling the interface. PR1548525

  • Users cannot subscribe to any path that ends with key. PR1553534

  • 5M DAC connected between QFX10002-60C and MX2010 does not link up, but this interoperation works as expected with 1M and 3M DAC. PR1555955

  • The show system license command output show the following error. However, there is no functional impact.


  • On QFX5120-48Y switches, amber LEDs are displayed for the fan modules after upgrading to Junos OS Release 20.2R1 and later. The LEDs are on continuously even if there is no fault in the fans. PR1558407

  • Interface hold time needs to be configured to avoid the additional interface flap. PR1562857

  • Starting in Junos OS Release 21.1R1, Junos OS will be shipping with python3 (python2 is no longer supported). In ZTP process, if a python script is being downloaded, ensure that the python script follows python3 syntax (there are certain changes between python2 and python3 syntax). Also, so far (that is, until Junos OS Release 20.4R1), the python script had #!/usr/bin/python as the first line (that is, the path of the python interpreter). The same needs to be changed to #!/usr/bin/python3 from Junos OS Release 21.1R1. PR1565069

  • The chassisd logs flood with the pic_create_ifname: 0/0/0 pic type F050 not supported messages for every connected port. The flooding might happen every few seconds. PR1566440

  • On all L2NG platforms, MAC address entries might be smaller in the MAC table than in the ARP table, this is because some of the MAC addresses are not relearned successfully after MAC address age timeout. This issue will cause traffic loss for non-existing MAC entries. PR1567723

  • BUM traffic replication over VTEP sends out more packets than expected. PR1570689

  • On QFX10002-60C platforms, known multicast traffic received over a VLAN from the core on VTEP does not get forwarded to the downstream CE interfaces. PR1575841

  • In an EVPN-VXLAN scenario with OSPF configured over the IRB, OSPF sessions might not get established due to connectivity issues. PR1577183

  • On QFX5100 switches, while checking DHCP smart relay over IRB interfaces, the renew-ack might not be seen in the DHCP client. PR1581025

  • When soft loopback port and analyzer configurations are committed together, hardware might not get programmed with the analyzer. This issue is not seen when physical loopback is used to achieve the same. PR1581542

  • In a fully loaded device, firewall programming fails at times due to scaled prefix configuration with more than 64800 entries. However, this issue is not observed in development setup. PR1581767

  • When physical loopback is used and both the ports are with EP style in the same RSPAN VLAN, it might lead to flooding. PR1581876

  • The input ingress and input egress together for the same port will not work in mirroring with VXLAN encapsulation. PR1589854

  • On the QFX10000 Series platforms, the dcpfe process or FPC crash might be observed in boot time. PR1597479

  • Read write lock is not acquired during the sysctl invocation. The assert triggered in the interface state function call leads to Routing Engine 1 going to debug (db>) prompt. PR1598814

  • On QFX5200 switches, dcpfe process generates core files during unified ISSU. PR1600807

  • There is a remote possibility that during many reboots, the Junos OS VM goes into a state where NMI is needed to continue the reboot. There is no workaround for this and a subsequent reboot does not seem to hit this issue. PR1601867

  • In some instances, when the device reboots, the Junos Virtual machine might hang until NMI is triggered and rebooting is completed. PR1602360

  • On QFX5120 switches, traffic loss might be seen when primary link is disabled with aggregated Ethernet link protection configuration. PR1604350

  • The dfwd process generates core file when accessing ephemeral database files which is deleted through script. PR1609201

  • On QFX10002-60C switches under MAC statistics, output-mac-control-frames and output-mac-pause-frames do not increment. PR1610745

  • On QFX10002, QFX10008, and QFX10016 platforms, the following error message is appeared on scaling more than 80,000 ARP/NDP: prds_jpf_nh_token_change: Token change failed for rnh. PR1616224

Routing Protocols

  • In a Virtual Chassis or Virtual Chassis fabric scenario, inconsistent MCSNOOPD core file is seen when igmp-snooping configuration is removed. PR1569436

  • On QFX10002 switches, the multi-hop BFD session might flap if collecting RSI or some other outputs (such as show interface or configuration). It is caused by the missing BFD packets, because the PPMAN thread is not scheduled within the BFD timers which are 300 milliseconds with a multiplier of 3. PR1589765

  • Upon clearing or deleting a peer, peer cleanup process gets stuck and peer stays in an idle (close in progress) state forever. PR1618103

  • On certain conditions where underlay session is flapped due to interface down event, it might see a flap in the overlay BFD session due to delay in route install to reach the packet to the neighbor. PR1618118