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

On Junos OS QFX5000 Series line of switches, configuration-change/protocol flapping/port flapping in EVPN Virtual Extensible LAN (VXLAN) can cause traffic loss (changes related to the underlay network). PR1688323

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

On changing the speed from or to 10m, some of the port might not ping. PR1712495

Booting the device having LLDP PDs connected with perpetual PoE configuration enabled will take time to update the negotiated value in the configuration statement (show poe interface).PR1713545

EX4100MP might allocate the power 0.1w less than the one PD requested. For example, when PD requests the power 19.4W in LLDP, EX4100 will allocate 19.3W to PD.PR1716261

PoE firmware upgrade might fail or might get stuck if the PoE firmware download procedure got interrupted. PR1717869

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

When an EX3400 Virtual Chassis members are zeroized or if it powered on for the first time after halt, set chassis auto-image-upgrade configuration is removed during the process of VC formation. Absence of this configuration will not allow user to download configuration and images via ZTP. PR1694952

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