Open Issues
Learn about open issues in Junos OS Rlease 21.4R1 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
-
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 -
On the EX4300-48MP device, 35 second delay is added in reboot time. PR1514364
-
FPC might not be recognized after the power cycle (hard reboot). 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
-
IS-IS adjacency might fail to be formed if the MTU size of an IRB interface is configured with a value greater than 1496 bytes.PR1595823
-
On EX4400 platforms, if image upgrade is attempted using non-stop software upgrade, an error message error: syntax error: request-package-validate will be reported as the CLI output. The error does not have any impact on the non-stop software upgrade process. PR1596955
-
EX4400 platforms have a Cloud LED on the front panel to indicate 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 displays green in situations where device has lost connectivity to cloud. This is because, MIST is using outbound SSH for management. This behavior is not applicable to any other management entity that uses outbound https and LED that displays appropriate states to indicate the loss on connection to cloud. PR1598948
-
During configuration change of MACsec on LAG, LAG members (port) start reinitializing the STP from fresh and due to STP state of port is getting modified, it moved to disable state and traffic loss occurred. PR1611772
-
When LDRA is configured DHCPV6 server binding is not happening. To use dhcpv6 options, relay-server configuration can be used by the customer. LDRA is an alternative for that. Once we enable dhcp-relay configuration with snooping, dhcpv6 options/binding works fine . Dhcp-relay configuration functionality is similar to LDRA. From customer point of view, LDRA can be achieved by dhcp-relay configuration. PR1627600
-
On Junos platforms with MPC10E line cards, when aggregated Ethernet under the IRB interface is enabled between the snooping device and the DHCP server. The DHCP bindings can be seen in snooping device and DHCP server, but the DHCP client might not go to BOUND state, it might be stuck at discovering or requesting state. PR1627611
-
On all Junos OS platforms, the line card might crash and reload in an EVPN-MPLS scenario when there is a MAC move from local to remote and the request to delete MAC entry is received from remote. Core files are generated and complete traffic loss might be observed until the line card reloads. PR1627617
-
On EX2300 platforms, when dhcp persistence is configured with dhcp security and device reboots, the lease time values may show a high lease value post reboot. PR1627673
-
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
-
On EX2300 platforms as transit switches, when no-arp-trap is enabled, if the ARP packets are unicast of which the destination MAC has upper four bytes matching to the system MAC, the ARP packets are not forwarded but trapped. PR1632643
-
On EX4600 platforms with the Virtual Chassis (VC) scenario, if the Virtual Chassis Ports (VCPs) are connected through QSFP+40GE-AOC cable, post upgrading to 17.3 or later releases, VCPs might not come up or flap impacting VC functionality and services. PR1633998
-
When L2PT (Layer2 Protocol Tunneling) is enabled on a transit switch using SP style configuration, protocol convergence between end nodes might fail. PR1637249
-
On EX3400, EX4300, and EX2300 platforms, when dot1x authentication is configured for a MAC-based VLAN (MBV) and if MAC move happens, the old MBV entry might not get cleared because of which MAC address might not be learned on the new interface and result in traffic loss. PR1637784
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
-
When a three member EX2300-MP VC is power cycled, the primary fpc (before power cycle) might crash when user logs in. PR1625987
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 and VXLAN environment. PR1530160
-
During Routing Engine switchover interface flap might be seen along with Scheduler slippage. PR1541772
-
When a EX4400 Virtual Chassis is scaled with different features configurations and device is stressed with traffic, device might 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
-
Local fault insertion and deletion is failing when fault injected (through a traffic generator). PR1623215
-
USB image upgrade for RE-1800x4 K2re "bare-metal" platforms (SRX5000, MX240, MX480, MX960, MX2010, EX9208 chassis) might not be successful. PR1630040