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 Junos OS Rlease 21.4R3 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

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

  • The 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 Packet Forwarding Engine 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

  • The FPC process might not get spawned after hard reboot in a rare case, which causes the FPC to not come online successfully. PR1540107

  • 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

  • In rare circumstances when doing routing-engine switchover, the routing protocol daemon in former active routing-engine (new backup routing-engine) might restart with a coredump while in process of being terminated.PR1589432

  • On EX series devices with vendor chip as Packet Forwarding Engine (PFE), if IS-IS is enabled on an integrated routing and bridging (IRB) interface and the maximum transmission unit (MTU) size of the IRB interface is configured with a value great than 1496 bytes, the IS-IS hello (IIH) PDUs with jumbo frame size (i.e., great than 1496 bytes) might be dropped and not sent to the IS-IS neighbors. The following is the product list of EX series switches with vendor chip as PFE. EX2300, EX3400, EX4300, EX4600, and EX4650 PR1595823

  • EX4400 platforms have a Cloud LED on the front panel to indicate the onboarding of the device to cloud (day0) and management after onboarding (day1). If MIST is used as a Management entity in cloud then, the cloud LED will display green in situations where device would have lost connectivity to cloud. This is dues to MIST using outbound SSH for management. This behavior is not applicable to any other management entity which uses outbound https and LED will display appropriate states to indicate the loss on connection to cloud. PR1598948

  • Issue: DHCP binding will not happen, when MLD snooping is enabled. Root cause: During DHCPv6 binding process, ICMPv6 neighbour discovery packets will be transacted between DHCP server device and client device tp learn adjacency. As per the design, ICMPv6 multicast packets will get dropped in DHCP security device and DHCPv6 binding will not happen as well. This issue is applicable only for Trinity based line cards and this is in parity with the older legacy Line cards. So, this config is not supported on this platform. DHCP-security vlan config: set vlans dhcp-vlan vlan-id 100 set vlans dhcp-vlan forwarding-options dhcp-security option-82 circuit-id set interfaces xe-0/1/3:1 unit 0 family ethernet-switching vlan members dhcp-vlan set interfaces xe-0/1/3:3 unit 0 family ethernet-switching interface-mode trunk set interfaces xe-0/1/3:3 unit 0 family ethernet-switching vlan members dhcp-vlan set interfaces xe-0/2/2:0 unit 0 family ethernet-switching interface-mode trunk set interfaces xe-0/2/2:0 unit 0 family ethernet-switching vlan members dhcp-vlan Committing MLD snooping on the vlan: set protocols mld-snooping vlan dhcp-vlan PR1627690

  • Mixing of GBP and non GBP terms in a single firewall filter is not supported and commit error is provided at CLI.PR1630982

  • On EX4600, show dot1x firewall output for clients authenticated in CP (after fallback) might show incorrect packet count.PR1636503

  • When a EX4400 virtual chassis is upgraded to 21.4R2 release using non-stop image upgrade process, the virtual chassis may report a alarm indicating a virtual chassis member is having different software version though all members are running same software versions. This alarm will be cleared on subsequent reboot of the chassis.PR1658508

  • On EX4300-48MP : While NSSU is in progress , DCPFE core can be seen on FPC but NSSU goes through successfully. PR1668414

Forwarding and Sampling

  • When the fast-lookup-filter statement is configured with a match that is not supported in the FLT hardware, traffic might be lost. PR1573350

Infrastructure

  • A Double Free vulnerability in the software forwarding interface daemon (sfid) process of Juniper Networks Junos OS allows an adjacently-connected attacker to cause a Denial of Service (DoS) by sending a crafted ARP packet to the device. Please refer https://kb.juniper.net/JSA11162 for more information. PR1497768

  • USB AUX console is not working on EX4100 box.PR1616315

Platform and Infrastructure

  • 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

  • When a EX4400 Virtual Chassis is scaled with different features configurations and device is stressed with traffic, device may not respond for cli commands for a short period of time and a vmcore might be reported at that time. Once VM core is saved, device will continue to operate normally. PR1599498

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