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.

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

  • On EX4600 platforms, if a change related to TPID is made in the Device Control Daemon, traffic might be dropped in Packet Forwarding Engine due to failure on Layer 2 learning or interfaces flapping. PR1477156

  • The runt, fragment, and jabber counters are not incrementing on EX4300-MPs. PR1492605

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

  • On EX2300, EX3400, EX4300-48MP and EX4300, pause frames counters does 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

  • EX4100-24mp,48mp,24p/t,48p/t,F-24p/t,F-48-p/t: In an interop scenario, when using 1G SFP Optic on PIC-2, auto-negotiation should be disabled on the peer. PR1657766

  • EX4100 MACsec interface statistics of encrypted or decrypted bytes do not increment further after reaching a 40-bit limit (1099511627775). PR1658584

  • High CPU utilization is seen on EX4100-48P with POE and LLDP protocol configurations. PR1660557

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

  • Packet count might occasionally be 0 for some interfaces in monitor interface traffic.PR1661617

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

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

  • EX4100 and EX4100-F Virtual chassis: Non-existing PIC ports (e.g. PIC0:PORT100, PIC2:PORT102) while running the jvision query. PR1681673

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

  • On all Junos OS platforms, configuring Link Layer Discovery Protocol (LLDP) with system services netconf notification enabled will trigger the l2cpd crash. This crash causes the CPU to spike. PR1695057

  • On EX Series platforms, traffic loss will be observed for deleting all Layer 2 related configurations when both Layer 2 and Layer 3 configurations are present. PR1695847

  • On all Junos OS platforms, the dcd (device control daemon) process crash is observed when more than 256 VLANs as name tags are added on the same interface. PR1696428

  • When a sfp is unplugged or plugged in, it might not be recognized. PR1696444

  • Port status LED remains "ON" for a few seconds after removing the link connection. PR1696596

  • On EX2300, EX3400, EX4400, EX4100 and EX4300-MP platforms, when primary FPC with mac-persistence-timer configured on a virtual chassis switch is halted, it leads to Layer 3 (l3) forwarding issues for the integrated routing and bridging (IRB). PR1706845

Platform and Infrastructure

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

  • On EX4300 platform, this issue occurs only when chassisd got restarted after filter configuration. This results in MAC-address change and sometimes MAC-address collision as well. PR1615548

  • On EX4300 platform, if encapsulation ethernet-bridge is configured, 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

Virtual Chassis

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

  • On EX4600-VC, when request system reboot all members is executed, post-reboot one of the VC member/Flexible PIC Concentrator(FPC) might disconnect and join the VC back due to Packet Forwarding Engine (PFE) restart. Traffic loss is seen when FPC is disconnected.PR1700133