Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

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.

High Availability (HA) and Resiliency

  • Graceful Routing Engine Switchover (GRES) not supporting the configuration of a private route, such as fxp0 , when imported into a non-default instance or logical system. PR1754351

Interfaces and Chassis

  • 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. 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 interfaces statistics operational mode command.

    [See Configuring IPv4 and IPv6 Accounting]. PR717316

Layer 2 Ethernet Services

  • If name-server information is changed via CLI after the DHCP subscribers are up, DNS obtained from DHCP server is overwritten by local config. This may result in DNS look up failures in some cases. PR1743611

MPLS

  • 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

Platform and Infrastructure

  • 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 Junos EX4300-24T/24P when the native CVLAN (Customer Virtual Local Area Network) ID is configured for Q-in-Q setup, the traffic for that particular VLAN gets dropped even if the knob "input-native-vlan-push" is configured. This issue is encountered when the when inner-tag matches 'native-vlan-id' irrespective of the outer tag. PR1722284

  • 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. 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

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

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

  • On EX2300, EX3400, EX4300-48MP and EX4300 devices, the 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 may 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 the EX4600 device with SFP-LX10/SFP-SX, after a power cycle/software reboot, all ports are initialized and links are up with auto-negotiation enabled. Few ports are up and traffic flows whereas few ports are up but no traffic flow through them. PR1672583

  • 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. PR1697678

  • On Junos OS platforms, the dcpfe (Dense Concentrator Packet Forwarding Engine) process crash will be observed due to memory fragmentation issue. This is a very rare case and would impact traffic as due to dcpfe failure the PFE restarts, so the interfaces flaps. PR1711860

  • 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

  • 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

  • On EX4400 devices, the set chassis config-button no-clear command does not work. PR1758042

  • On EX2300 VC, the Dot1x authentication flapping in multiple supplicant mode with 100 user scale. PR1767706

  • On the peer device ports connected to 24-40 port group from ex4100-48P/T going up for 2-3s during device reboot. PR1775479

  • When there are a large number of aggregated (AE) interfaces on a system, deleting all of them together and adding them back can lead to a race condition. This could result in a few of the interfaces not being programmed correctly. PR1781955

Virtual Chassis

  • On Junos EX4600 Virtual Chassis (VC), the primary Routing Engine reboots and all-members reboot lead to the PFE Manager hogging logs when SFP-T pluggable is installed in. The PFE Manager hogging logs has no functionality impact.PR1685067

  • On EX4600-VC, when the request system reboot all members command gets 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