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 Junos OS Release 22.2R1 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.

Forwarding and Sampling

  • The fast-lookup-filter with match not supported in FLT Hardware might cause the traffic drop. PR1573350

Infrastructure

  • On ARM64 platforms such as EX4100, if a live vmcore is attempted to be created, the DUT might get stuck and reboot. PR1656625

Layer 2 Features

  • On QFX5100/EX4600 platforms, if a change related to TPID is made in the device control daemon (dcd), there might be a traffic drop in Packet Forwarding Engine due to failure on l2 learning or interfaces flapping. PR1477156

Network Management and Monitoring

  • A minor memory leak is seen in the event-daemon process when you perform multiple GRES switchovers.PR1602536

Platform and Infrastructure

  • During Routing Engine switchover, interface flap might be seen along with Scheduler slippage. PR1541772

  • Traffic drops after chassis-control restart when filter is attached and source and destination configurations are enabled. PR1615548

  • Firewall: End-to-End traffic validation fails before applying filter on interface. PR1634347

  • When VLAN is added as an action for changing the VLAN in both ingress and egress filters, the filter is not installed. PR1362609

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

  • Pause frames counters are not getting incremented when pause frames are sent. PR1580560

  • On EX4400 family of devices, sometimes login prompt is not shown after the login session ends. PR1582754

  • EX4400-48MP - VM crash and Virtual Chassis split might be observed with multicast scale scenario. PR1614145

  • When a 100G interface on a QFX5120 is converted to a Virtual Chassis port, the interface stays down as the port is configured as 40G internally. PR1638156

  • With SFP+-10G-CU3M DAC, link remains up on EX4100-48P devices even though the admin is down on peer.

    PR1640799
  • Class-of-service buffer-size exact configuration is not supported. The respective configured queue will still use the shared-pool. PR1644355

  • On EX4100 devices, the input pps, bps, and byte counters gets displayed as 0 for some ports while traffic runs without any issues. The interface status gets cleared for 0 to 23 and not cleared for 24 to 47 after interface flaps. PR1657995

  • On EX4100 devices, the Junos telemetry interface FAN and power supply names do not match with CLI. PR1648739

  • Incorrect trap is generated after removal of fan0 in FPC4. PR1652388

  • Momentary traffic loss might be observed with type-5 and NSR/NSB configuration on routing-engine switchover on EX4100 with Junos OS release 22.R1. PR1655052

  • Interop for 1G interfaces between EX4100 SKUs and ACX5448/ACX5448-M/D will not work. PR1657766

  • EX4100 MACsec interface statistics of encrypted/decrypted bytes won't be updating properly after a certain value. PR1658584

  • On EX4600 devices, Virtual-chassis remains in the Unstable state for 3 to 7 minutes, causing traffic loss. PR1661349

  • On EX4600 devices, memory leakage occurs in the eventd process with the longevity test of back to back GRES. 1645852

  • Some of interfaces gets zero status in the monitor interface traffic command, when traffic gets sent across all interfaces and applied speed of 100m on all 1g copper ports. The issue occurs when you clear the status for interfaces. PR1661617

  • On EX2300 and EX3400 devices, high CPU utilization might be observed when more PoE devices (more than 25 PDs) gets connected to the switch. PR1667564

  • When dot1x enabled access port is member of a secondary pvlan (either community or isolated vlan) by configuration then CLI show dot1x interface detail shows the 'Authenticated Vlan' as primary vlan and 'Authenticated secondary vlan' as configured secondary vlan though client/port is not yet authenticated. Data traffic is still blocked until client is authenticated. This is just an incorrect display and discrepancy with other release. There is no know functional impact. PR1668144

  • On EX4300MP devices, the dcpfe process generates core files when you perform NSSU from Junos OS release 21.1R3.12 to Junos OS release 21.3R3.6. PR1668414

  • On EX4100 devices, traffic does not go through on the management port at link speed 10 and 100M in Junos OS release 22.2R1 and Junos OS release 22.2R1-S1. PR1676433

  • If you insert 1G optic on the uplink ports of EX4100-24mp, EX4100-48p, EX4100-48t, EX4100-24p, and EX4100-24t SKUs, then the activity LED gets lit irrespective of the link Present or Up status. PR1682633

  • On EX4100 devices, secondary USB Type C console port in the front panel does not display proper output. PR1616315

  • On EX4100 devices, Layer 2 IGMP, MLD snooping requires Layer 3 irb to be configured. PR1681478

Virtual Chassis

  • On EX4600 and EX4650 Virtual Chassis (VC), when tyou reboot the primary Routing Engine, the line card might be disconnected from VC. The Packet Forwarding Engine (PFE) planned restart might be seen on the new backup due to which line card leaves and rejoins the VC automatically. PR1669241