Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Open Issues

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

Note: The EX2300 and EX3400 models are documented but not supported in this release.

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

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

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

  • On EX4400 devices with 4x25G or 1x100g ULM, when we perform PIC online, CPU overuse by CMQFX thread might be seen for as much as 3.5seconds. PR1870962

  • With latest changes in 25.2R1 on EX4000 and EX4100, after bootup there are error logs seen in syslog as below: fpc0 brcm_bcm_l3_ingress_create:52Could not create l3 ingress for error Operation disabled. dc-pfe[11749]: brcm_bcm_l3_ingress_create:52Could not create l3 ingress for error Invalid parameter. These errors have no functionality impact. Request to ignore these logs seen just after bootup. PR1872146

  • When a non-PoE SKU is configured as the master and PoE SKUs are configured as members, the PoE status will be "disabled" in cli even though PDs are powered up. However, if the device is rebooted while in this state, PoE functionality will not resume afterward. PR1881788

  • In the EX4400-48F systems, a 10G-BaseT transceiver that was earlier up may not come up post a reboot/image upgrade event; The transceiver might go undetected causing the interface to not be created in the system.PR1887303

  • EX4400-48F: When we have SFP-SX optics plugged in EX4400-48F device in the ports 0 to 35 and it is rebooted, the activity LED remains on. PR1899248

  • With SFP-T optics and DUT configured speed=100M with Auto-Neg enabled and peer configured speed=10M with Auto-Neg enabled, link might not come up. PR1905956

Platform and Infrastructure

  • In a rare scenario, due to timing issues, the Packet Forwarding Engine (PFE) crash is observed on Junos EX4300 platforms. This causes traffic loss until the PFE comes up. PR1720219

  • 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. Thread profiling code has been optimised and the issue is fixed in the future Junos.PR1794342

Routing Protocols

  • Traffic convergence issue was resolved with the work around provided. BFD issue was known limitation. PR1888400