Open Issues

Modifying the I-ESI value is traffic effecting event. If this must be done then follow the below steps in order to avoid the issue:

• Deactivate interconnect stanza for the routing-instance in question.

• Modify the I-ESI value.

• Activate the interconnect stanza.

  PR1600600

With translation VNI, when you move MAC 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 configuration might not get effective immediately when it has already learned remote MH MACs. Clear the MAC table from all MH PE devicess and configure the MAC limit over local ESI interfaces. PR1619299

On QFX5000 and QFX10,000 devices, on interface up or down event loop prevention might not work resulting in BUM traffic being silently discarded. PR1669811

When VLAN gets added as an action for changing the VLAN in both ingress and egress filters, the filter does not get installed. PR1362609

VXLAN VNI (multicast learning) scaling on QFX5110 device, traffic issue occurs from VXLAN tunnel to Layer 2 interface. PR1462548

When running the show pfe filter hw filter-name command, the command fails to retrieve the Packet Forwarding Engine 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) gets installed, the CPU utilization might go up by around 5 percent. PR1534234

5M DAC connected between QFX10002-60C and MX2010 devices doesn't link up. However, with 1M and 3M DAC this interop works as expected. With 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 hardware and SI teams. PR1555955

To avoid the additional interface flap, interface hold time must be configured. PR1562857

In a mixed QFX5100 setup, duplicate traffic might be observed for some Layer 3 multicast traffic streams. PR1568152

In a fully loaded devices, at times the firewall programming fails due to scaled prefix configuration with more than 64800 entries. PR1581767

PIM VXLAN does not work on the TD3 chipsets enabling the VXLAN flexflow after Junos OS 21.3R1 release. PIM VXLAN or data plane VXLAN must use Junos OS 21.3R1 release. PR1597276

On QFX5100 device, the optical power gets displayed after detaching and attaching QSFP on the disable interface. PR1606003

The dfwd process generates a core file when accessing the ephemeral database files, which gets deleted through script. PR1609201

In QFX10002-60C devices under MAC statistics, the output-mac-control-frames and output-mac-pause-frames does not increment. PR1610745

Minimal traffic loss might occur if the number of interfaces in the aggregated Ethernet interface and might observe slight increase if the number of interfaces in the aggregated Ethernet interface is increased but the drop is inconsistent and the packet drop would be expected around ~0.0001%. PR1629661

On QFX5000 devices with 5e image, chassis status LED does not work properly. You might observe unexpected state of SYS or MST LED on the primary or backup FPC. PR1630380

The backup FPC lose their connection to primary when the new members are added to the VCF (Virtual Chassis Fabric). PR1634533

On QFX devices, IPv6 traffic output byte (IPv6-transit-statistics) would not be in expected range as per traffic generator status. PR1653671

On QFX5120-48T devices, NSSU fails with below combinations:

• From 22.1R1.10 to 22.2R1.6

• From 21.4R1.12 to 22.2R1.6

• From 21.3R2.11 to 22.2R1.

  PR1669702

On QFX10,000 devices with scaled number of BFD (Bidirectional Forwarding Detection) sessions configured, addition of a new BFD session might cause flapping in the newly added session and other existing BFD sessions. PR1621976

On QFX5000 devices, the MAC address from local CE devices (customer edge) might not get learned when you configure EVPN-VXLAN. The traffic drops as MAC might not be learnt. PR1651827

On QFX5100-24Q devices, Virtual Chassis goes in to the Unstable state for 3 to 7 minutes causing traffic loss. PR1661349

On QFX5000 devices, when unicast ARP (Address Resolution Protocol) is received for a MAC address that is already learned in an EVPN-VXLAN environment, the ARP request is flooded and duplicate packets might be seen on leaf devices. We might see some service impact where split-horizon might not work or continuous mac-move might be seen. This issue is rare and very unlikely to occur in a production environment due to presence of intermediate switches which might resolve the unicast ARP query.PR1665306

On all QFX10002 devices, multihop Bidirectional Forwarding Detection (BFD) over routing instance with inline mode configuration keeps the BFD sessions down.PR1667751

On Junos OS Releases 21.4 and 22.1, when QFX5120 device performs IFA init for VLAN flows, the device does not update the congestion field of IFA meta-data stack which needs to be copied from ECN field of outer IP header. PR1674431

If LAG interface has VLAN translation configuration and a member interface is deleted or removed from LAG interface than it will delete the VLAN translation programing from PFE on local FPC. If there is another active interface on same FPC in the same LAG then traffic hitting on this LAG member will get drop belongs to VLAN translation. PR1676772

On QFX5200-32C devices, unwanted packets gets generated by the router interface even though there was no traffic being sent. PR1670728

When the DHCP client configuration comes from the AIU script and vsdk sandbox, the DHCP client configuration coming from AIU script has the serial ID in the vendor ID where as the default configuration from sandbox does not have. There is no impact on functionality or service. PR1601504

In case of the access-side interfaces used as SP-style interfaces, when you add a new logical interface and if there is already a logical interface on the physical interface, there is 20 to 50 milliseconds traffic drop on the existing logical interface. PR1367488

When you configure the DHCP relay mode as no-snoop, the offer gets dropped due to incorrect ASIC programming. This issue occurs while running the DHCP relay on EVPN-VXLAN environment. PR1530160

If you use the source-address NTP configuration parameter and issue the set ntp date command, 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 the accept-remote-source command under PIM gets removed, the PIM SG entries might not get updated with the correct RPF. PR1593283

The mcsnoopd process generates core files due to the nexthop index being quickly reused by the Kernel. As a result, when application holds the old nexthop reference, which waits for deletion response from Kernel, the same nexthop Index can be received from other applications like RPD for EVPN core-Nexthop updates as in current case. This will lead to the mcsnoopd process wrongly manipulating the nexthop ref counting, leading to using a freed nexthop memory when this nexthop-index finally gets freed. This will be fixed through a feature enhancement underway where the Kernel maintains a timer to ensure a nexthop-index does not put to free pool immediately for reuse and hence can be reused post the new timer expiry. PR1605393