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.

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

General Routing

  • EX4300MP: VC member status toggling between "Inactive" and "NotPrsnt" state after member downgradePR1751871

  • 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

  • In EX4400 devices with 4x25G or 1x100g ULM, when we perform PIC online, CPU hog by CMQFX thread may be seen for as much as 3.5secondsPR1870962

  • 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 may go undetected causing the interface to not be created in the system.PR1887303

  • During bootup of the switch hog messages can be observed in /var/log/messages without any functional impact.PR1887725

  • On Junos QFX5100 and EX4600 platforms with releases 21.4R3-S3, 21.4R3-S10, and 21.4R3-S11, the SNMP trap generated after reinserting a PEM on the master switch incorrectly reports the jnxOperatingState as 6 (down) instead of the expected value 2 (running). This behaviour is consistently reproducible across multiple versions and persists even after performing a mastership switchover.PR1888543

  • With SFP-T optics and DUT configured speed=100M with Auto-Neg enabled and peer configured speed=10M with Auto-Neg enabled. Link will not come upPR1905956

  • On EX3400 and EX4400-48F, when using 1G optics, the auto-negotiation information does not appear in the output of the "show interfaces" command.PR1909608

  • While verifying export EFP group, sensor components verification failedPR1922040

Junos Fusion Enterprise

  • Power Class for the PoE device (Ruckus AP) connecting to EX2300 Fusion Satellite device is being negotiated incorrectly by LLDP_MED. Device requires class 4 power, Juniper satellite is supplying class 3.PR1796151