Open Issues

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

On the EX9214 device, the following error message are observed after reboot and MACsec-enabled link flaps: errorlib_set_error_log(): err_id(-1718026239).PR1448368

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

When a VLAN member is specified as a string, the 'IF_MSG_IFL_VADDR' TLV is not generated with the VLAN infoformation, and the TRIO afttriostream is not updated with the nativevlanId and nativevlanenable flags. Thus, the packet is still treated as untagged, and when it reaches the trunk egress interface, it is dropped because the trunk interface does not allow untagged traffic to pass through. The issue is specific to platforms with ZT line cards, including EX9200-SF3 and EX9200-15C. PR1506403

On the EX4300-48MP device, 35-second delay is added in reboot time. PR1514364

When the streamed telemetry data for a node is deleted during a network churn and the same node is being walked or rendered for the sensor, the rpd process might crash and generate a core file. This is a corner case where rendering and deleting a particular node occur at the same instance. This issue might be seen only in case of an unstable network.PR1552816

Observing traffic drop during an unified ISSU because of a LAG interface flap. PR1569578

On a EX4400 Virtual Chassis, the SNMP MIB object jnRedundencySwitchOverCount will not be reset to 0 when the entire Virtual Chassis is rebooted. PR1570359

Broadcast, Unknown Unicast, and Multicast (BUM) traffic replication over VTEP is sending out more packets than expected and there seems to be a loop. PR1570689

On all Junos OS platforms, traffic loss might be observed due to a rare timing issue when performing frequent Interface Bridge Domain (IFBD) configuration modifications. This behavior is seen when the Packet Forwarding Engine receives out-of-order IFBD(s) from Routing Engine and might lead to the fxpc process crash and traffic drop. PR1572305

On EX Series switches with vendor chip as Packet Forwarding Engine, if IS-IS is enabled on an integrated routing and bridging (IRB) interface and the maximum transmission unit (MTU) size of the IRB interface is configured with a value greater than 1496 bytes, the IS-IS hello (IIH) PDUs with jumbo frame size (i.e., greater than 1496 bytes) might be dropped and not sent to the IS-IS neighbors. EX2300, EX3400, EX4300, EX4600, and EX4650 are the switches with vendor chip as Packet Forwarding Engine. PR1595823

On EX4400 platforms, if image upgrade is attempted using non-stop software upgrade, an error message error: syntax error: request-package-validate will be reported as the CLI output. The error does not have any impact on the non-stop software upgrade process. PR1596955

EX4400 platforms have a Cloud LED on the front panel to indicate onboarding of the device to cloud (day0) and management after onboarding (day1). If MIST is used as a management entity in cloud, then the cloud LED displays green in situations where device has lost connectivity to cloud. This is because, MIST is using outbound SSH for management. This behavior is not applicable to any other management entity that uses outbound https and LED that displays appropriate states to indicate the loss on connection to cloud.PR1598948

There is a remote possibility that during many reboots, the Junos 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

The configuration statement fast-lookup-filter with match condition is not supported in FLT hardware and might cause a traffic drop. PR1573350

A double free vulnerability in the software forwarding interface daemon (sfid) process of Juniper Networks Junos OS allows an adjacently-connected attacker to cause a Denial of Service (DoS) by sending a crafted ARP packet to the device. Refer https://kb.juniper.net/JSA11162 for more information. PR1497768

On all platforms, while directly upgrading from Junos with FreeBSD 6 (e.g. 15.1X49 or before) to the affected releases, the system will check the USB connection. The upgrading will fail if there is no USB device detected during the upgrading process. PR1572963

On a EX4400 device, a cloud LED on the device indicates the phone home client states and device connectivity state with the cloud. When the GRPC application is configured with non-root user, then the cloud LED will not display any pattern related to day1 states. The LED pattern will still be displaying the previous day0 state as applicable. PR1589321

If the device does not have an Layer 3 interface, the handling of ARP packets are altered, resulting in certain corner collaterals. The specific cause is unknown, however vlan addition or deletion could be a factor.PR1602259

Under some conditions a truncated vmcore is generated on panic on EX-2300/EX-3400/EX-2300MP. PR1607299

On EX4300 POE switches, the pfex process CPU utilization becomes high after 6-8 weeks. There is no functional impact. PR1453107

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

On EX9200 line of switches, FPC gets restarted and thereby disrupting traffic when there is an out-of-order filter state. This issue might be seen only in back-to-back GRES in more than 40 to 50 iterations. PR1579182

When a EX4400 Virtual Chassis is scaled with different features configurations and device is stressed with traffic, device might not respond for CLI commands for a short period of time and a vmcore might be reported at that time. Once VM core is saved, device will continue to operate normally. PR1599498