Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


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.

Class of Service (CoS)

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

General Routing

  • When you add VLAN as an action for changing the VLAN in both ingress and egress filters, the filter does not ge installed. PR1362609

  • runt, fragment and jabber counters are not incrementing on EX4300-MPsPR1492605

  • On EX4300-48MPdevices, if POE is enabled, a primary Routing Engine might reconnect which could cause traffic impact. PR1499771

  • 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

  • On EX4600 devices, the Virtual-chassis goes in to the Unstable state for 3 to 7 minutes causing traffic loss. PR1661349

  • On EX4100 and EX4100-F devices, PIC 1 ports with 1G optic displays AN enabled but it is not enabled in the hardware. PR1666227

  • 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

  • On EX4100 and EX4100-F Virtual Chassis, non-existing PIC ports (example, PIC0:PORT100 and PIC2:PORT102) while running the jvision query. PR1681673

  • If MVRP is enabled on an MSTP enabled interface, the interface will be made part of all the existing instances on the switch, So, 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. So, when traffic is received in vlan-200 it will be sent out of et-0/0/1, it gets dropped. PR1686596

  • When a sfp gets unplugged or plugged in, the sfp might not be recognized. PR1696444

  • Traffic loss could be seen in case config changes lead to switching from fallback to primary or vice-versa are committed, while SAK rollover from current live session is in progress. The issue is dependent on sequence of event at specific time. Example - MACsec session is live with primary key and at non-keyserver CAK for primary is changed this will lead to switching to fallback session, in case at same instance SAK rollover was triggered by Key-server then traffic loss will be observed. PR1698687

Interfaces and Chassis

  • On EX46000 Virtual Chassis (VC), if a primary member gets unplugged or forced to power off, the unicast traffic drops due to mac-persistence-timer expiry difference in MAC addresses between logical aggregated parent interface and member aggregated ethernet(ae) interface. PR1695663

Platform and Infrastructure

  • On EX4400-48MP devices, VM file generates core files and Virtual Chassis might split with multicast scale scenario. PR1614145

  • On EX4300 devices, if you configure encapsulation ethernet-bridge, the interface gets 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 devices, 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 the Blocking state. PR1673000

Virtual Chassis

  • On EX4600 Virtual Chassis (VC), the primary Routing Engine reboot and all-members reboot leads to the Packet Forwarding Engine Manager hogging logs when you install SFP-T pluggables. The Packet Forwarding Engine Manager hogging logs has no functionality impact. PR1685067

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