Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Resolved Issues

Learn about the issues fixed 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.

Class of Service (CoS)

  • The fixed classifier might not work in the MPLS and VXLAN scenario. PR1650051

EVPN

  • The MAC address might not be visible in the EVPN-VXLAN environment. PR1645591

  • The spine might have stale vtep entry for the ESI even though the host MAC does not get advertised by the leaf. PR1648368

  • The ARP/NS response to anycast IRB might fail due to missing MAC-IP entry. PR1650202

Forwarding and Sampling

  • The jnxL2aldMacNotificationMIBObjects does not work on some QFX devices. PR1647660

General Routing

  • On QFX5200 devices, the dcpfe process might generate core file while testing ISSU from Junos OS 21.1R1.11 release to Junos OS 21.2R1.7 release. PR1600807

  • On QFX10008 and QFX10016 devices, the chassisd process generates the Cannot read hw.chassis.startup_time value: m error message every five seconds. PR1603588

  • On QFX5 devices, the ports might remain in the Down state. PR1611354

  • The packet drop might occur when packet size exceeds 9000 MTU. PR1615447

  • On QFX5120 devices, one-time interface flap might occur. PR1618891

  • The interface on the peer device might remain up even after disabling the 10G interface. PR1629637

  • On QFX5130 devices as Border Leaf with Layer 3 interface connectivity, traffic forwarding deos not occur to multihomed receiver connected to Border Leafs when the Layer 3 interface goes down on the DF side. PR1631249

  • On QFX5120-48T-6c devices, slow response or timeout on the CLI or SNMP with accessing to sxe-0/0/0 might occur. PR1632620

  • On QFX5120-48Y devices, traffic loss might occur when there is a link flap. PR1634495

  • The chassisd process might crash if you configure the chassis disk-partition. PR1635812

  • Routes might be slow to install in the LPM table. PR1635887

  • Multicast traffic received on the INET interface might be dropped. PR1636842

  • The Packet Forwarding Engine might crash while removing the port from a VLAN. PR1637013

  • On QFX5000 devices, targeted broadcast or WOL feature might not work. PR1638619

  • MAC address of the hosts might get learned on the incorrect VLAN thatmight lead to traffic loss. PR1639938

  • ICMP TTL exceeded packets are not sent out of the switch. PR1643457

  • On QFX5000 devices with EVPN-LAG multihoming, packets gets dropped in ingress due to the VP-LAG programming issue. PR1644152

  • VXLAN tunnel termination fails due to a change in configuration. PR1646489

  • The firewall might drop inbound packets if you configure the filter under the IRB interface. PR1646740

  • The CLNP traffic tunneled through EVPN-VXLAN fabric might get dropped PR1648078

  • OSPF control packets might get dropped due to the flow check function in the interoperability case. PR1648272

  • The local-minimum-links feature not working as expected on QFX5100 VC platforms PR1649637

  • In EVPN-VXLAN environment, the non-VXLAN traffic might be dropped if the VXLAN and non-VXLAN traffic shares the same ECMP next-hop. PR1649841

  • Traffic Loss will be observed with Virtual-Router PR1650335

  • L2PT configuration on a transit switch in a Q-in-Q environment breaks L2PT. PR1650416

  • The local-bias might stop working after you reboot the device. PR1651151

  • Transit traffic might get dropped and protocols might be down when you modify the firewall filters. PR1651546

  • Port might be down after inserting a specific SFP. PR1653723

  • The ARP might not resolve with the native-vlan configuration. PR1654215

  • LACP sent IN SYNC to server facing interface when core-isolation is in effect. PR1654459

  • On QFX5200 devices, the interface cannot fetch the FEC details after you disable or enable the interface. PR1657534

  • Traffic loss might occur when a VXLAN port recovers from a failure. PR1659533

  • The OSPF Flow Check function violates RFC6864. PR1660369

  • BUM traffic received on the CE interface loopback to the ingress interface after removing the EVPN VXLAN FRR configuration (reroute-address). PR1662515

  • On QFX5110 devices, the IPv6 ND packets gets dropped. PR1662707

  • ALB status does not display in the CLI. PR1663881

  • Static MACs do not get programmed after reboot, resulting in floods of unicast traffic. PR1666399

  • RIB and Packet Forwarding Engines gets out of synchronization due to a memory leak caused by interface flaps or route churn. PR1642172

  • On QFX5000 devices, an interface might be detached from LACP when you configure the VLAN tagging in the EVPN-VXLAN scenario. PR1645929

  • The inner tag (C-tag) value might get modified to zero for egress traffic when the inner tag values are copied to the outer tag (S-tag). PR1652976

  • Valid software licenses might not be in synchronization between members in the Virtual chassis. PR1658913

  • The slave PTP device does not lock the clock with the primary PTP device. PR1659453

  • On QFX10,000 devices, Junos platforms configuration of IGMP group range might result in traffic loss. PR1659732

  • Verification of statuss for BFD session is in the Up state while checking the BFD session. PR1663790

  • On specific QFX5000 devices, member links might reduce their configured speed when the other side does not have auto-negotiation disabled. PR1669436

Interfaces and Chassis

  • VRRP flaps between MC-LAG peers when deleting VLANs on the MC-AE interfaces. PR1579016

  • Traffic might get loss for the MAC addresses learned on the ICL interface. PR1639713

  • Incorrect configuration and rollback might cause issues with ARP learning between ICL interface and local MC-AE interfaces. PR1648271

  • The MAC address might be learned over the incorrect interface in the MC-AE scenario. PR1658742

Layer 2 Ethernet Services

  • On QFX5210-64C devices, default configurations do not get generated properly from port 32. PR1639410

Network Management and Monitoring

  • VTEP might report a high speed on the sub-interface causing SNMP alarms. PR1651774

Routing Protocols

  • The BFD session might be down when you configure multiple addresses of same subnet. PR1635700

  • Ipv6 Inline BFD sessions goes down when neighbor does not get resolved. PR1650677

  • A policy with a community policy action configuration might not work. PR1660424

  • Routing Process Daemon (rpd) crashes and restarts when a specific timing condition is hit with BGP configuration. PR1659441

VPNs

  • On QFX10000 devices, auto-RP goes down after some time in the NGMVPN scenario. PR1617620