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.

General Routing

  • EX4100-24mp,48mp,24p/t,48p/t,F-24p/t,F-48-p/t: In an interop scenario, when using 1G SFP Optic on PIC-2, auto-negotiation should be disabled on the peer. PR1657766

  • The interface of ge-x/0/1 port might go down after virtual-chassis split and merge on EX4300-VC. PR1745855

  • EX4300MP: VC member status toggling between "Inactive" and "NotPrsnt" state after member downgrade. PR1751871

  • Local or remote fault insertion from TG is failing. PR1789999

  • Time Domain Reflectometry (TDR) support for detecting cable breaks and shorts aborts intermittently on some random ports. PR1820086

  • It should not be a show-stopper for customer release, as there will be no impact on traffic, problem on displaying extra lanes in SNMP query. PR1844751

  • When a poe bounce command is issued in quick succession for multiple ports, the 'poe enabled' logs may not be printed for some of the poe ports. This is a cosmetic issue and functionality works as expected. PR1845161

  • A memory corruption issue can result random dense concentrator packet forwarding engine (dcpfe) process crashes on all Junos OS EX and QFX platforms configured with Virtual Extensible Local Area Network (VXLAN ) configuration. PR1856424

  • After multiple iterations of dc-pfe process restart, we may see interface with 10g-base-t transceiver (part# 740-123734) will not come up. PR1864715

  • dhcp-snoop routes are not installed when IPSG group is full when IPv4 or IPv6 source guard is enabled along with DAI or NDI. When dhcp snooping binding entries exceed 512, even new bindings show up in the binding table, the dhcp-snoop route is not installed in HW. New bindings will be dropped due to DAI or NDI. This behavior is expected. As we are running out of space of FP entries in HW, routes are NOT installed beyond the scale. IPv4 and IPv6 uses the same VFP in HW. switch request pfe execute command show filter hw groups target fpc0 Unit:0 Group Information: VFP groups: Dynamic group id: 1. Pipe: 0 Entries: 1 Total_available: 512 Pri: 0 Def Entries: 0 VFP group for COS id: 143. Pipe: 0 Entries: 7 Total_available: 512 Pri: 2 Def Entries: 0 VFP group for DYN IPSG group id: 391. Pipe: 0 Entries: 512 Total_available: 512 Pri: 3 Def Entries: 0 full group with 512 entries. PR1878355

Platform and Infrastructure

  • It is noticed that EX4300 switches after an upgrade of Junos from 21.2R3-SX to 21.4R3-SX may exhibit a higher CPU. Issue is resulting from fast path thread profiling code. It takes on an average 1 ms more for one fast path thread cycle, cumulatively overall fast path thread usage had increased. PR1794342

  • On the EX4300, the egress Router Access Control List (eRACL) configured on the Layer 3 IPv6 interface with action count is not working.PR1848179

  • VLAN Spanning Tree Protocol (VSTP), Bridge Protocol Data Units (BPDU) are dropped by EX4300 when the interface is configured in Service Provider style causing VSTP not to converge impacting the network traffic.PR1849492

  • On all EX4300 series platforms, Packet Forwarding Engine process crashes and traffic via all the ports on this FPC could be impacted. PR1859134

  • On EX4300 switches, Address Resolution Protocol (ARP) requests used for Media Access Control (MAC) learning are not handled correctly when MAC limiting features, such as the mac-move-limit configuration statements, are configured. These features change MAC learning from hardware-based to software-based. PR1873052