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.

Class of Service (CoS)

  • On all Junos platforms, in a scaled scenario when some of the ge/xe/et interfaces are members of Aggregated Ethernet (AE) and the Class of Service (CoS) forwarding-class-set configuration is applied with a wildcard for all the physical interfaces and AE, it would trigger a Flexible PIC Concentrators (FPC) crash, which leads to traffic loss. PR1688455

Infrastructure

  • Auxiliary serial port (type USB-C on the front panel) does not show any output. PR1616315

  • There is a possibility of kernel crash when the system will be in the process of coming up after reboot (and observed only with multiple iterations of continuous reboot ccyles). This is observed only during init sequence of mgmt driver and impact is limited to increased system boot time. PR1642287

Platform and Infrastructure

  • 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

  • When running the command: show pfe filter hw filter-name filter name, the command fails to retrieve the PFE programming details of the filter. PR1495712

  • A delay of 35 seconds is added in reboot time in Junos OS Release 20.2R1 compared to Junos OS Release 19.4R2. PR1514364

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

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

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

  • Due to an Improper Initialization vulnerability in Juniper Networks Junos OS on EX4650 devices, packets received on the management interface (em0) but not destined to the device, might be improperly forwarded to an egress interface, instead of being discarded. Refer to https://kb.juniper.net/JSA69494 for more information. PR1628754

  • FXPC core file is seen while loading Junos OS 21.3R3.1 MR build with abort,junos_abort,panic, dcbcm_discover,pic_discover ,cmqfx_pic_sw_init,cmqfx_all_pic_sw_init ,cmqfx_module_init (). PR1660130

  • EX4600 and QFX5100-24Q devices VC (Virtual chassis) is in unstable state for 3-7 minutes, causing traffic loss.PR1661349

  • On certain units, with set system ports console log-out-on-disconnect, when you log in to the device through a console, the user will be ejected out to the login prompt and be asked to log in again. PR1680408

  • On EX4300-48MP, NSSU abort is seen with error: rebooting VC". VC instability and dc-pfe core is observed after reboot.PR1668414

  • When the DHCP relay mode is configured as no-snoop, we are observing the offer gets dropped due to incorrect asic programming. This issue only affects while running DHCP relay on EVPN/VXLAN environment. PR1530160

  • EX4400-48MP - VM cores and VC split might be observed with multicast scale scenario. PR1614145

  • On EX4300-24T, EX4300-48P, EX4300-VC, EX430024P, EX430032F and EX430048T platforms, when a VSTP (VLAN Spanning Tree Protocol) BPDU (Bridge Protocol Data Unit) arrives with a VLAN ID that is not configured in the switch, but that matches with an HW Token of any other configured VLAN, the VLAN ID of the BPDU will be changed to the VLAN ID corresponding to the matched HW Token and flooded. This disrupts STP convergence on the configured VLAN because some ports might incorrectly go into blocking state. PR1673000