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

  • 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 primary's member-id and primary member's interface configuration 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

  • On EX platforms, after reboot or GRES, the show chassis routing engine command shows incorrect output. The 5 seconds, 1, 5 and 10 minute CPU average utilization is not shown in the output. Its a display issue and there is no functional impact due to this issue. PR1812514

  • Unsupported PEM/PSU is shown as online (green)in the MIST Dashboard and the output of show chassis environment for that PSU shows the status as present/OK. No functional impact. PR1814463

  • In a specific configuration change after NSSU, that is delete and add sequence of link aggregation bundles (LAG) done through load baseline configuration and re-apply original configuration. OSPF session might get stuck in EXSTART state. PR1817034

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

  • An FXPC core might be generated when an offline and online activity is performed on a 1x100GE Uplink module. The system resumes in normal fashion after the core. PR1823097

  • On the EX4400-48MXP/48XP devices with 1x100G or 4x25G Uplink Module(ULM) in PIC slot 2, when we perform a PIC offline/online operation, we might see messages related to CPU hog by the threads CMQFX or Task ACQUIRE_FP_LOCK. These will be seen only during the operation and does not affect the offline or online operation of the PIC. PR1823394

  • While performing a 4x25g channelization configuration on the 1x100GE PIC, following error logs are printed multiple times momentarily. They are transient log messages. <. . . .> qsfp_tk_cdr_control: qsfp-0/2/0 channelization not yet supported.<. . . .> These message will appear while applying the below configuration #set chassis fpc 0 pic 2 port 0 channel-speed 25g #commit. These are harmless logs and can be ignored. There is no functional impact due to these logs. PR1823743

  • In EX platforms, some EVPN VxLAN T5 routes will not pass traffic after a routing-engine switchover (GRES). PR1823764

  • EX4400 series: When an offline and an online command is issued for a PIC 2 installed with a 1x100GE Uplink module configured for Virtual-chassis operation, the link might not come back to operational state and remains down. PR1826147

  • Virtual chassis auto-conversion is attempted for 4x25G Uplink modules when inserted with 10G-SFPP-T transceivers. Auto-conversion fails and links remain down. PR1826410

  • On an EX4400 device with 4x25G Uplink module configured in 1GE or 25G speed, peer side of an interface with 10GBASE-T transceiver may remain up even when the IFD(xe-x/2/y) is not created. For this to happen, a speed mismatched configuration is needed, where a 1G speed or a 25G speed is configured on the PIC 2. PR1831409

Infrastructure

  • 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

Interface and Chassis

  • DCD_CONFIG_WRITE_FAILED: IFL me0.0 configuration write failed for an IFL ADD: File exists - On some rare occurence, the aforementioned message might get filled up in logs after an upgrade to 24.2R1-S1 image. PR1827981

Platform and Infrastructure

  • 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

  • A vmcore and a ksyncd core might be generated during junos image upgrade. PR1827102

  • When a EX4400-48MP/ EX4400-48MXP is rebooted, sometimes the multirate gigabit ethernet (mge- ) interface fails to receive traffic after booting up. However, the interface remains operational at the time of issue. The link is up. PR1827455

  • In a EX4400 Virtual Chassis with multiple member stacked together with PIC 2 as VC Port, a reboot or a routing-engine switch-over might result in a VC Port going down specifically operating on a 4x25GE Uplink module. The aforementioned problem might be seen intermittently. PR1829037