Open Issues
Learn about open issues in Junos OS Release 22.1R3 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)
-
On all Junos platforms, in a scaled scenario when some of the ge/xe/et interfaces are members of Aggregated Ethernet (AE) and the Class of Service (CoS) forwarding-class-set configuration is applied with a wildcard for all the physical interfaces and aggregated Ethernet interface, it would trigger a flexible PIC Concentrators (FPC) crash which leads to traffic loss. PR1688455
EVPN
-
Multiple remote DCI MAC (IRB and Host) entries go missing after the I-ESI modification in the local DC GW nodes. PR1600600
-
This problem happens only with translation VNI when mac moved one from DC1 to DC2. VM move across DC where there is not translate VNI configuration in the interconnect works as designed. PR1610432
-
EVPN Local ESI Mac limit config mayn't not get effective immediately when it has already learned remote MH Macs. Clear the Mac table from all MH PEs and configure the Mac limit over local ESI interfaces. PR1619299
Layer 2 Features
-
In case of the access-side interfaces used as SP-style interfaces, when a new logical interface is added and if there is already a logical interface on the physical interface, there is 20--50 ms traffic drop on the existing logical interface. PR1367488
Layer 2 Ethernet Services
-
On QFX5100 and QFX5110 switches, vendor-id format maybe incorrect for network ports. This does not impact the ZTP functionality or service. The DHCP client config is coming from two places, i.e AIU script and vsdk sandbox. The DHCP client config coming from AIU script has the serial Id in vendor id where as the default config from sandbox does not have. PR1601504
Platform and Infrastructure
-
When the DHCP relay mode is configured as no-snoop, we are observing the offer gets dropped due to incorrect asic programming. This issue only affects while running DHCP relay on EVPN/VXLAN environment. PR1530160
-
On all Junos and Junos OS Evolved platforms, while using source-address NTP configuration parameter and issue the command "set ntp date" from the CLI, packets will be sent with the source address of the outgoing interface rather than the manually configured IP address. Typically, the manually configured IP address would be a loopback address. The problem does not apply to automatically generated NTP poll packets. PR1545022
-
When VLAN is added as an action for changing the VLAN in both ingress and egress filters, the filter is not installed. PR1362609
-
VXLAN VNI (multicast learning) scaling on QFX5110 traffic issue is seen from VXLAN tunnel to Layer 2 interface. PR1462548
-
When running the command: show pfe filter hw filter-name filter name, the command fails to retrieve the PFE programming details of the filter. PR1495712
-
On QFX5100 devices not running the qfx-5e codes (non-TVP architecture), when an image with the Broadcom SDK upgrade (6.5.x) is installed, the CPU utilization may go up by around 5 percent. PR1534234
-
5M DAC connected between QFX10002-60C and MX2010 doesn't link up. But with 1M and 3M DAC this interop works as expected. Also it is to be noted QFX10002-60C and ACX or Traffic generator the same 5M DAC works seamlessly. There seems to be certain SI or link level configuration on both QFX10002-60C and MX2010 which needs to be debugged with the help from HW and SI teams and resolved. PR1555955
-
To avoid the additional interface flap , interface hold time needs to be configured. PR1562857
-
In mixed QFX5100 device, EX4300 VCF setup, duplicate traffic might be observed for some Layer 3 multicast traffic streams. PR1568152
-
On QFX5100, Media type for SFP+-10G-CU1M and SFP-T cables are shown as Fiber. This is only a display issue and no functionality impact is observed. PR1570555
-
In a fully loaded devices, at times, firewall programming was failing due to scaled prefix configuration with more than 64800 entries. However, this issue is not observed in development setup. PR1581767
-
On QFX5110 VC, FPC may gets disconnected with 24K DHCPv6 relay scaling, after the traffic is stopped. "pfe_listener_disconnect" error messages gets generated. PR1594748
-
Pim Vxlan not working on TD3 chipsets enabling VLAN flexflow after release 21.3R1. Customers Pim Vxlan or data plane VxLAN can use the version 21.3R1. PR1597276
-
On QFX5100, optical power is seen after detached and attached QSFP on disable interface. PR1606003
-
Dfwd cored when accessing ephemeral db files which is deleted through script. PR1609201
-
On Junos QFX1000 platforms with scaled number of BFD (Bidirectional Forwarding Detection) sessions configured, addition of a new BFD session might cause flapping in newly added session and other existing BFD sessions. PR1621976
-
minimal traffic loss can be expected if the number of interfaces in ae and could see slight increase if the number of interfaces in ae is increased but the drop is inconsistent and the packet drop would be expected around ~0.0001 percent. PR1629661
-
On the QFX5000 devices switch which is working on the 5e image and with VC setup, the chassis status LED does not work properly. An unexpected state of SYS (System) or MST (Master) LED on master or backup FPC might be seen. This could be observed after reboot or change in FPC role. PR1630380
-
On QFX5110-32Q devices, traffic loss occurs after renumbering master in VC. PR1632565
-
Backup FPC lose their connection to the master when new members are added to the VCF (Virtual Chassis Fabric). PR1634533
-
The bounded delay config feature for IFL is not supported on Pyrite platform. The core is seen only when this config is enabled on the device. PR1634941
-
Management interface speed is displayed as 10G instead of 1G though there is no functionality impact. PR1636668
-
On QFX10002-60c, in EVPN/VxLAN scenario multicast traffic received on the INET interface (L3 interface) might be dropped. PR1636842
-
On all QFX5100 Virtual Chassis platforms, after the reboot, Virtual Chassis port (VCP) ports may not establish a VCP connection and Cyclic Redundancy Check (CRC) errors are also observed. PR1646561
-
On QFX platform, v6 ifl stats are being derived from the underlying ifd stats unlike on PTX where they are hardware assisted. Hence, they are not very reliable and are at best, guesstimate. PR1653671
-
EX4600 and QFX5100-24Q devices VC (Virtual-chassis) is in unstable state for 3-7 minutes causing traffic loss. PR1661349
-
On QFX10002-60c platform, the DHCP (Dynamic Host Configuration Protocol) offer messages from the DHCP server will be dropped when the device acts as a DHCP relay agent over a Type-5 tunnel. Due to this, the IP address will not be assigned to the requesting client from the DHCP server. PR1664656
-
When the remote end server/system reboots, QFX5100 platform ports with SFP-T 1G inserted may go into a hung state and remain in that state even after the reboot is complete. This may affect traffic after the remote end system comes online and resumes traffic transmission. PR1665800
-
On QFX5200, after NSSU upgrade for a 4 member VC , FPC may toggle resulting in interfaces going offline. PR1673116
-
On 21.4 and 22.1 releases, when QFX5120 performs IFA init for vxlan flows, it will not update the congestion field of IFA meta-data stack which needs to be copied from ECN field of outer IP header. PR1674431
-
On all VMHOST based platforms, traffic blackholing happens because the traffic does not re-route quickly as chassisd doesn't recognize an FPC failure from a BAD_VOLTAGE notification. PR1676740
-
Sflow ingress/egress sampling not working when ECMP nexthops are involved. PR1685407
Routing Protocols
-
When the knob accept-remote-source under PIM is removed, the PIM SG entries may not be updated with the correct RPF. Clearing of the states would take care of the issue. This is day-1 behavior. PR1593283
-
MCSNOOPD core is seen sometimes due to Nexthop index being quickly reused by the Kernel. As a result when application is still holding old Nexthop reference which is waiting for deletion response from Kernel, the same Nexthop Index can be hence be received from other applications like RPD for EVPN core-NH updates as in current case. This will lead to MCSNOOPD wrongly manipulating the Nexthop ref counting, leading to using a freed Nexthop memory when this Nexthop-index is finally being freed. This will be fixed via a feature enhancement underway where the Kernel will maintain a timer to ensure a Nexthop-index is not put to free pool immediately for reuse and hence can be reused post the new timer expiry. PR1605393