Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Open Issues

Learn about open issues in this release for EX Series switches.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.


  • On all Junos OS platforms with EVPN scenario, the number of MAC-IP binding counters might reach the limit when MAC-IP is moved between interfaces. Since MAC-IP counters are not decremented when entry is deleted due to this defect, repeated moves will result in a limit (default value is 1024) that will be reached even though there are fewer entries. Meanwhile, traffic loss might be seen. PR1591264

Forwarding and Sampling

  • fast-lookup-filter with match not supported in FLT hardware might cause the traffic drop. PR1573350

General Routing

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

  • On EX9208 switch, a few xe- interfaces go down with an error message "if_msg_ifd_cmd_tlv_decode ifd xe-0/0/0 #190 down with ASIC error". PR1377840

  • On EX9214 device, the following error message is observed after rebooting and MACsec-enabled

    link flaps: "errorlib_set_error_log(): err_id(-1718026239)". PR1448368

  • When running the command show pfe filter hw filter-name 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 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

  • A delay of 35 seconds is added in reboot time in Junos OS Release 20.4R3 compared to Junos OS Release 19.4R2. PR1514364

  • License daemon will restart and start providing the required support when intermittent license-

    check.core file is seen during the device initialization. There is no service impact. PR1545175

  • When ICMP packets egress from the device, that might take Best-Effort queue. This avoids

    congestion case protocol flap when huge number of ICMP traffic being generated. Other control

    protocol such as OSPF and others take network-control queue, which is in parity with other

    QFX5000 line of switches. PR1550293

  • When dot1x server-fail-voip vlan-name is configured, ensure that both server-fail-voip vlan-name and voip vlan are configured using vlan name and not by using vlan-id. PR1561323

  • Observing traffic drop during unified ISSU due to LAG interface flap. PR1569578

  • BUM traffic replication over VTEP is sending out more packets than expected and there seems to be a loop also in the topology. 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

  • Pause frames counters are not getting incremented when pause frames are sent. PR1580560

  • On EX Series switches such as EX2300, EX3400, EX4300, EX4600, and EX4650 with broadcom 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 great than 1496 bytes, the IS-IS hello (IIH) PDUs with jumbo frame size (that is, great than 1496 bytes) might be dropped and not sent to the IS-IS neighbors. The following is the product list of EX Series switches with broadcom chip as the Packet Forwarding Engine. PR1595823

  • On EX4600, after performing an upgrade, the peer device is rebooted or the peer interface is disabled and then enabled. As a result, the SFP-T port on EX4600 might remain in UP state but might not forward traffic. PR1600291

  • Observing pfex core file at 0x01fdf324 in pfe_bcm_ifd_mac_config /../src/pfe/common/pfe-arch/broadcom/applications/l2/pfe_bcm_l2_intf while cleanup of the configurations after NSSU. PR1602873

  • On EX Series line of switches, the system reboot takes approximately 9 minutes for FPCs to come online after system reboot command is issued. PR1605002

  • After performing ZTP, default configuration under ge-0/0/* will be missing in EX4600 product. PR1614098


  • On EX Series switches except EX4300, EX4600, and EX9200, an interface is configured for single vlan or multiple vlans, if all these vlans of this interface have igmp-snooping enabled, then this interface will drop Hot Standby Router Protocol for IPv6 (HSRPv2) packets. But if some vlans do not have igmp-snooping enabled, then this interface is working fine. PR1232403

  • On EX Series switches, If you are configuring a large-scale number of firewall filters on some interfaces, the FPC might crash and generate core files. PR1434927

  • IFDE: Null uint32 set vector, ifd and IFFPC: 'IFD Ether uint32 set' (opcode 151) error message is observed continuously in AD with base configurations. PR1485038

  • 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 to for more information. PR1497768

  • On EX4400 family of devices, sometimes login prompt is not shown after the login session ends. PR1582754

  • On EX4400 device, the cli command show system processes detail will not display CPU details under the CPU column. PR1588150

Layer 2 Features

  • On EX Series line of switches, memory leak might be seen because of the eswd daemon that displays the following system log message: eswd[1330]: JTASK_OS_MEMHIGH: Using 212353 KB of memory, 158 percent of available /kernel: KERNEL_MEMORY_CRITICAL: System low on free memory, notifying init (#2). /kernel: Process (1254,eswd) has exceeded 85% of RLIMIT_DATA: used 114700 KB Max 131072 KB. PR1262563

  • On EX4600 platforms, if a change related to TPID is made in the device control daemon, a traffic drop might be seen in the Packet Forwarding Engine due to failure on Layer 2 learning or interfaces flapping. PR1477156

Platform and Infrastructure

  • 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, the offer gets dropped due to incorrect ASIC programing. PR1530160

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

Routing Policy and Firewall Filters

  • On all Junos OS platforms with set policy-options rtf-prefix-list configured, if upgrade to a specific version, the device might fail to validate its configuration which eventually causing rpd to crash unexpectedly due to a software fault. PR1538172

User Interface and Configuration

  • The issue is seen on EX Series VC only which can be avoided with a simple workaround as to providing a valid package during upgrade command. PR1557628