Open Issues

After Routing Engine switchover, a momentary traffic loss may be observed with EVPN VxLAN on EX4400 switches. PR1659315

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

When launching a guest Virtual Machine (VM) to run a third party application on Junos OS release 15.1R1 and later, the guest VM might be shown as "UNAVAILABLE" even after successfully installing the third party application. This is due to duplicated device ID assigned to different disks. PR1529596

When launching a guest virtual machine to run a third party application on the Junos OS 15.1R1 and above, the guest virtual machine might be shown as "UNAVAILABLE" even after successfully installing the third party application. This is due to duplicated device ID assigned to different disks. PR1529596

Pause frame counters do not increment when pause frames are sent on the EX2300, EX3400, EX4300-48MP, and EX4300 line of switches. PR1580560

In an interoperable scenario, when using 1G SFP optic on PIC-2, you must disable auto-negotiation on the peer. PR1657766

On the EX4600 device with SFP-LX10/SFP-SX, after a power cycle or software reboot, all ports are initialized and links are up when you enable auto-negotiation. Few ports are up and traffic flows whereas few ports are up but no traffic flow through them.PR1672583

If MVRP is enabled on an MSTP enabled interface, the interface will be made part of all the existing instances on the switch. If there are two interfaces between R1 and R2 as below: R1(et-0/0/1 and et-0/0/2)======(et-0/0/1 and et-0/0/2)R2. And one interface is MVRP enabled (say et-0/0/1), and et-0/0/2 is not MVRP enabled. By configuration et-0/0/1 is part of MSTI-1 and et-0/0/2 is part of MSTI-2. MSTI-1 is running on vlan-100 and MSTI-2 is running on Vlan-200. R2 in this case, is advertising only vlan-100. The MVRP enabled interface will become part of all the MSTIs (MSTI-1 and MSTI-2 both) configured on the device and it will take part in the FSM of all the MSTIs. Although et-0/0/1 is not member interface of vlan-200 (correspnding to MSTI-2). This potentially can cause a problem where et-0/0/1 although not a vlan-200 member, will go into FWD state and et-0/0/2, genuine member of vlan-200 goes into BLK state for MSTI-2. When traffic is received in vlan-200 it will be sent out of et-0/0/1, an it will be dropped.PR1686596

When you enable port beacon LED for the port, show chassis led statement output shows incorrect port LED status for the interfaces as lit up instead of off. PR1697678

EX4600 with redundant trunk group (RTG) configured, after VCP port between members of EX4600 disconnect and connect again. MAC address entry created in RTG cannot ageout. PR1707878

When high number of MACsec sessions present (more than 200) and traffic is passed over these interface, some of the MACsec session flap and there is traffic drop.PR1709431

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

On EX4650 and QFX5120-Y, the 10G interfaces are not coming up simultaneously when different Small Form-factor Pluggable(SFPs - 10G and 1G) are plugged in within the same 4 port group. Normally 10G interface by itself will be up when set to 1G if no other SFP is plugged in.PR1714833

This is a Broadcom limitation and Day 1 issue affecting broadcom chipsets such as EX4650's, QFX5ks, EX4300. One VLAN can be mapped to only on ERPS ring. For example, VLAN 100 can be mapped to only one ERPS ring. This same VLAN 100 cannot be part of another ERPS ring on the same switch.PR1732885

request system reboot usb doesn't seems to be supported in EX4300-48MP(tvp based model) Generally if want to upgrade image from USB in EX4300-48MP. Follow the below steps:

• reboot the device

• go to BIOS Manager

• select USB to boot and upgrade image

PR1734925

On EX4400, request system halt/power off CLI doesn't turn off rear FAN LEDs.PR1737500

On EX4400, a "BCM Error: API bcm_plp_mode_config_set" error msg may be seen in the syslog when converting a VCP to network port. There is no functionality impact.PR1738410

In case of role swap along with fpc slot change between master and linecard, the older ifds are retained on master. PR1740024

On EX2300, on VCP enable and disable, "optic_set_activity_led" error messages may be seen. There is no functionality impact for these error messagesPR1740064

EX4400: With pre existing configuration of 1g for the uplink interfaces, the 1G uplink ports might not come up on 4x10G module insertion event.PR1741724

When system comes up with BULK L2 configuration, a subsequent CONFIG delete in a way that L2ALD is still not finished processing the configuration create, could lead to a race condition where FLOOD ROUTE DEL event can cause l2ald crash. PR1742613

Disable the vme interfaces or have the default route added properly from the shell script for the connectivity with the ztp server to work.PR1743222

On EX2300 when zeroise is /var/db/leases gets deleted and due to this dhcp-client ip-address is not saved. PR1743467

On EX4100, VC formation will not happen automatically after zeroize each device will function as Standalone. PR1744190

On 1G port if tx rate is applied with 4m(Q0) + 996m (Q1). Configuration fails in COSD with the following log and not get pushed to PFE. COSD_TX_QUEUE_RATES_TOO_HIGH: cos_validate_scheduler_shaper_conflict:820 : Unable to apply scheduler map CPE-Transmit-VPN1G-normal-only to interface ge-x/x/x: sum of scheduler transmission rates exceeds interface shaping or transmission rate. PR1759821

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

EX4400 could be stuck during boot, when one end of the twisted pair cable is connected to the primary console port and the other end is left unconnected/dangling.PR1754548

EX-hardening: EX4400: set chassis config-button no-clear is not working. PR1758042

On all Junos OS platforms, a warning message is seen when installing the license key where features don't support the product.PR1766515

EX2300 VC: 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 rebootPR1775479

When there are a large number of aggregated Ethernet 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

GRES do not support the configuration of a private route, such as fxp0, when imported into a non-default instance or logical system. As work around, see KB26616resolution rib policy is required to apply. PR1754351

Name-server resolution failure may be seen intermittently after zeroize or loading factory default config resulting in MIST on-boarding failure. Workaround is to restart dhcp-service. PR1747800

The memory might leak because of the eswd daemon on the EX Series platforms. A message like the following is displayed in the system log: eswd[1330]: JTASK_OS_MEMHIGH: Using 212353 KB of memory, 158 percent of available /kernel: KERNEL_MEMORY_CRITICAL: System low on free memory, notifying init (#2). /kernel: Process (1254,eswd) has exceeded 85% of RLIMIT_DATA: used 114700 KB Max 131072 KB. PR1262563

On Junos OS 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

In mixed mode virtual Chassis (vc) when the 10G DAC is used as a Virtual Chassis Port (VCP) between Junos QFX5100 and EX4300 VC, the 10G DAC VCP will not come up after rebooting EX4300.PR1665250

On EX4300 platform, if you configure encapsulation ethernet-bridge statement, the interface is getting programmed as trunk instead of access in VLAN membership. This leads to untagged traffic drop. PR1665785

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 can incorrectly go into blocking state. PR1673000

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 OS 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-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 EX4300MP-EX4300 mixed VC setup, "show system software sets" command shows 'Pending set' software version even after rebooting.PR1738406

On EX4300 VC setup, "qsfp_tk_read_mem_page: Rear QSFP+ PIC failed to select addr 127 err 1000" messages may be seen intermittently. There is no functionality impact for these error messagesPR1747126

After an upgrade, the SFP modules are not detected in case of EX4300 platforms and the ports remain down impacting traffic.PR1747374

On EX4300, "Error requesting CMTFPC SET INTEGER" and "Error requesting SET BOOLEAN" logs may be seen after device boot up. There is no functional impact for the error messagesPR1749289

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

On EX Series 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 all Junos OS and Junos OS Evolved platforms, whenever a commit is done, that involves mcsnoopd daemon config parsing such as (VLAN creation/deletion, interface add/delete to VLAN, interface enable/disable, IGMP (Internet Group Management Protocol) snooping/MLD (Multicast Listener Discovery) snooping related configuration commands) mcsnoopd will consume CPU. In less scaled setup (few IGMP snooping enabled VLANs and few hundred IGMP snooping memberships), the CPU time taken is less. In a more scaled setup (many IGMP snooping-enabled VLANs and a few thousand IGMP snooping memberships), the CPU may reach greater than 90 percent. Since mcsnoopd is taking high CPU, it may affect other daemons like rpd. It may affect all the protocols if the CPU is not available to the protocols/daemons. This can impact route entries expiring and cause traffic drop.PR1710565

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

On EX4600-VC, when you execute the request system reboot all members statement, post-reboot one of the Virtual Chassis member or Flexible PIC Concentrator (FPC) might disconnect and join the Virtual Chassis back due to Packet Forwarding Engine restart. Traffic loss is seen when FPC disconnects. PR1700133