Open Issues

Runt, fragment and jabber counters are not incrementing on EX4300-MPs.PR1492605

On EX4300-48MP platform, if POE is enabled, a master RE reconnect might be seen which could cause traffic impact. PR1499771

On EX2300, EX3400,:EX4300-48MP and EX4300 , Pause frames counters does not get incremented when pause frames are sent. PR1580560

When the remote end server/system reboots, QFX5100 platform ports with SFP-T 1G inserted might go into a hung state and remain in that state even after the reboot is complete. This may affect traffic after the remote end system comes online and resumes traffic transmission. PR1665800

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

When TISSU upgrade is done from 22.4 release onwards, the box come up as backup RE.PR1703229

On EX4650 and QFX5120-48Y, the SFP-LX interface will not be UP when different Small Form-factor Pluggable(SFP-10GBASE-T and SFP-LX) are plugged in within the same 4 port group. The presence of the 10GE-T SFP resets the speed of the quad back to 10G even if the quad port speed is set to 1G. Normally 10G interface by itself will be up when set to 1G if no other SFP is plugged in. PR1714833

EX4400-48F: Carrier transitions is not setting properly for channelized ports on non-DUT Lagavulin for QSFP28-100G-AOC-30M 740-064980 of FINISAR. PR1723924

During device reboot, mge connected ports on the peer goes up after 90s into reboot. PR1767347

EX2300 VC: Dot1x authentication flapping in multiple supplicant mode with 100 user scale. PR1767706

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

You can configure the routing platform to track IPv6-specific packets and bytes passing through the router. To enable IPv6 accounting, include the route-accounting statement at the [edit forwarding-options family inet6] hierarchy level: [edit forwarding-options family inet6] route-accounting; By default, IPv6 accounting is disabled. If IPv6 accounting is enabled, it remains enabled after a reboot of the router. To view IPv6 statistics, issue the show interface statistics operational mode command. Can be found here: Configuring IPv4 and IPv6 Accounting PR717316

On Junos QFX5100 and EX4600 platforms in Layer 2 Virtual Private Network (L2VPN) scenarios, when an access port flaps or the port related configuration is deactivated and activated, the traffic ingressing or egressing out of that port gets dropped. PR1775553

On Junos OS EX4300 and EX4300-VC platforms, if zeroize or interface configuration deletion performed, PFEX process crash will se seen when interface/device comes up and there will be traffic loss during the PFE restart.PR1714117

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

On EX4300 platforms, when the firewall filter applied on the loopback interface is configured with default action as a discard on the DHCP-Relay and a client is connected to a VLAN with DHCP-security and DHCP-Relay enabled, then the DHCP lease renewal unicast packet sent by the DHCP client will be dropped by the loopback filter on the DHCP-Relay. This will eventually lead to service impact as the DHCP client loses the IP address. PR1730903

On EX4300-VC, the Online Insertion and Removal (OIR) of Quad Small Form-factor Pluggable (QSFP) may result in a PFE crash under near-zero idle CPU conditions.PR1733339

After an upgrade, the SFP modules are not detected in case of EX4300 platforms and the ports remain down impacting traffic. PR1747374

On EX4300, "Error requesting CMTFPC SET INTEGER" and "Error requesting SET BOOLEAN" logs may be seen after device boot up. There is no functional impact for the error messages. PR1749289

On all EX4300 platforms, traffic is sent on an AE interface and sent to the removed child interface from AE (Aggregated Ethernet) where the traffic is lost. PR1749406

On EX switches, if 40G DAC(Direct Attach Copper) cables with PN(Part Number) 740-038624 (QSFP+-40G-CU3M) and 740-044512 (QSFP+-40G-CU50CM) are used, links might not come up after software upgrade to Junos 21.4R3-S3 or after a switch reboot (if the switch is running Junos 21.4R3-S3). The switch ports that use these DAC cables are observed to go down after a reboot. PR1752611

An Incorrect Behavior Order vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on EX4300 Series allows an unauthenticated, network-based attacker to cause an integrity impact to networks downstream of the vulnerable device. Please refer to https://supportportal.juniper.net/JSA79185 for more information.PR1770410

An Improper Check for Unusual or Exceptional Conditions vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on EX4300 Series allows a locally authenticated attacker with low privileges to cause a Denial-of-Service (Dos). Please refer to https://supportportal.juniper.net/JSA79186 for more information.PR1774634

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

On all Junos and Junos Evolved platforms, when the shortest-path-first (SPF) algorithm for IS-IS is triggered frequently, CPU usage might increase and impact the device performance and traffic.PR1667575

On EX4600-VC, when "request system reboot all members" is executed, post-reboot one of the VC member/Flexible PIC Concentrator(FPC) might disconnect and join the VC back due to Packet Forwarding Engine (PFE) restart. Traffic loss is seen when FPC is disconnected.PR1700133