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

runt, fragment and jabber counters are not incrementing on EX4300-MPs. PR1492605
On all EX platforms, whenever beacon LED functionality is enabled, there is a mismatch between the physical LED status and the output of the CLI command ?show chassis led? showing incorrect port LED status for interfaces as LED up instead of off. PR1697678
on EX2300-48 MP without VC pre-provisioned configuration, If master's member-id and master member's interface config are changed then VC is taking more time to get stabilized.PR1764542
during device reboot, mge connected ports on the peer goes up after 90s into reboot.PR1767347
After rebooting a mixed Virtual Chassis (VC) of EX4300-P and EX4300-MP switches or rebooting a EX4300-P member, interfaces with Power over Ethernet (PoE) configured won`t come up on EX4300-P members. PR1782445
Ex-Hardening:Local/Remote fault insertion from TG is failing. PR1789999
(EX4400): after clearing arp on access error seen on aggregation devices with metro configuration.PR1793885

When storage on hardware is full, a panic resulting in vmcore and is dumping the core file in /var/crash leads to memory storage in negative, and potentially results in a truncated vmcore.PR1796186

On EX4300 or EX4300-VC, removal of a Physical Interface Card (PIC), or if the software fails to detect a PIC that is installed, it can cause a crash in the pfex process. This crash can lead to high CPU usage and potentially disrupt network traffic.PR1779410
On EX4300 Platforms, Packet Forwarding Engine (PFE) crash will be seen due to an unexpected switchover after committing interface configuration .PR1785058