Open Issues

Modifying the I-ESI value causes traffic effecting event. To modify the value, you must deactivate interconnect stanza for the routing-instance in question, modify the I-ESI value, and then activate the interconnect stanza. PR1600600

VM move across DC where there is no translate VNI configuration in the interconnect. This issue occurs when you move MAC from DC1 to DC2 with translation VNI. PR1610432

PR1610432

There are 10 seconds of traffic loss when a MH leaf in the scaled environment is brought down. The loss is both in the Layer 2 and Layer 3 traffic. When the MH peer is brought up, there are no traffic loss. PR1611565

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

When BUM traffic is sent on MCLAG, MAC entries are learnt on ICL interface as DLR when ICL gets flapped as MAC learning. This might cause traffic loss with certain traffic flow. PR1639713

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

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

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

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

On QFX5100 switches not running the QFX 5E codes (non-TVP architecture), when you install an image with the Broadcom SDK upgrade (6.5.x), the CPU utilization might increase by around 5 percent. PR1534234

5M DAC connected between QFX10002-60C and MX2010 does not link up. But with 1M and 3M DAC this interop works as expected. Also, it is to be noted that the QFX10002-60C and ACX devices, or the traffic generator of the same 5M DAC works seamlessly. There seems to be certain SI or link level configuration on both the QFX10002-60C and MX2010 devices. PR1555955

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

On QFX51000 Virtual Chassis fan setup, duplicate traffic might be observed for some Layer 3 multicast traffic streams. PR1568152

Partial traffic loss occurs after disabling the protected link on R2 due to which convergence delays for link-protection for the PE1_P link. PR1579931

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 Release 21.3R1. PR1597276

On QFX5100 switches, optical power appears after detaching and attaching QSFP on the disable interface. PR1606003

On QFX10002-60C switches, the output-mac-control-frames and output-mac-pause-frames MAC statistics does not increment. PR1610745

On QFX5000 switches 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

Junos OS does not support the bounded delay configuration feature for IFL. Core file gets generated only when you enable the configuration on the device. PR1634941

On the QFX10008 and QFX10016 switches, the following logs gets generated every 5 seconds in the output of the show log chassisd command: Jun 14 18:09:38 CHASSISD_UTIL_RW_ERR: Cannot read hw.chassis.startup_time value: m Jun 14 18:09:43 CHASSISD_UTIL_RW_ERR: Cannot read hw.chassis.startup_time value: m Jun 14 18:09:48 CHASSISD_UTIL_RW_ERR: Cannot read hw.chassis.startup_time value: m Jun 14 18:09:53 CHASSISD_UTIL_RW_ERR: Cannot read hw.chassis.startup_time value: m Jun 14 18:09:58 CHASSISD_UTIL_RW_ERR: Cannot read hw.chassis.startup_time value: m Jun 14 18:10:03 CHASSISD_UTIL_RW_ERR: Cannot read hw.chassis.startup_time value: m Jun 14 18:10:08 CHASSISD_UTIL_RW_ERR: Cannot read hw.chassis.startup_time value: m Jun 14 18:10:13 CHASSISD_UTIL_RW_ERR: Cannot read hw.chassis.startup_time value: m Jun 14 18:10:18 CHASSISD_UTIL_RW_ERR: Cannot read hw.chassis.startup_time value: m Jun 14 18:10:23 CHASSISD_UTIL_RW_ERR: Cannot read hw.chassis.startup_time value: m Jun 14 18:10:28 CHASSISD_UTIL_RW_ERR: Cannot read hw.chassis.startup_time value: m PR1603588

The dfwd process generates file when accessing ephemeral db files, which gets deleted through script. PR1609201

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

When the accept-remote-source configuration statement under PIM is removed, the PIM SG entries might not be updated with the correct RPF. Clearing of the states would take care of the issue. This is day-1 behavior. PR1593283

The mcsnoopd process generates a core file sometimes due to nexthop index being quickly reused by the kernel. As a result, when the application still holds the old nexthop reference, which waits for the deletion response from kernel, the same nexthop index can be received from the other applications like RPD for EVPN core-NH updates as in current case. This leads to the mcsnoopd process incorrectly manipulating the nexthop reference counting, leading to the usage of a freed Nexthop memory when this nexthop-index gets freed. PR1605393