Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
  
[+] Expand All
[-] Collapse All

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 14.1X53 for the EX Series.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Authentication and Access Control

  • On EX4300 switches, when 802.1X single-supplicant authentication is initiated, multiple EAP Request Id Frame Sent packets might be sent. PR1163966
  • On an EX4300, EX4600, EX9200, or QFX5100 standalone switch or its Virtual Chassis or VCF, with a port configured in access mode and with dot1x enabled, if this port is converted to trunk mode, then this port might not be able to learn a MAC address or might drop packets silently. PR1239252
  • On Enhanced Layer 2 Software (ELS) platforms, due to a memory leak issue, the l2ald process might crash when many dot1x clients are being reauthenticated, for example, 150 clients with transmit-period set to 5. It is around 40–60 bytes memory leak per reauthentication for one dot1x client. Here the leak is due to the interaction between dot1x and the l2ald process; with more frequent reauthentication and more clients, the crash will be observed more often. PR1269945

Firewall Filters

  • [EX4600] RSVP packets are incorrectly dropped when using an lo0 filter. PR1286269
  • Policers do not work for 224.0.0.X multicast traffic to the kernel on EX4300s. PR1313251

Infrastructure

  • The kernel might crash due to file system corruption. PR1028972
  • Due to a rare race condition, the UFS file system might get corrupted, resulting in a kernel panic. PR1181132
  • OID jnxFruState disappears after one of the members of the Virtual Chassis is rebooted on EX2200, EX3300, EX4200, EX4500, or EX4550 Virtual Chassis. PR1221943
  • A maximum of 8 elements within all the vlan-id-list can be accepted on a physical interface for EX4300 due to product limitation. This is regardless of the span of each element (a single VLAN or a range spanning 500 VLANs) and whether 8 elements are on a single logical unit or over 8 logical units (or somewhere in between). If there are more than 8 elements configured on a physical interface then the configuration is accepted but only the first 8 elements will be acted upon. The behavior remains the same only a warning message is displayed. However, the commit check succeeds. PR1225281
  • On EX Series switches except EX4300 and EX4600, if an interface is configured for a single VLAN or multiple VLANs and if all these vlans of this interface have igmp-snooping enabled, then this interface will drop HSRPv2 (Hot Standby Router Protocol for IPv6) packets. But if some VLANs do not have igmp-snooping enabled, then this interface works fine. PR1232403
  • EX4200 Virtual Chassis: Memory leak for chassisd. PR1285832
  • On EX4300 switches, when unknown unicast ICMP packets are received by an interface, packets are routed, so TTL is decremented. The interface should process packets only when the packet destination MAC is a router interface MAC or a multicast address. PR1302070

Interfaces and Chassis

  • On an EX4300 switch, packets received on a Layer 2 interface might be dropped if their destination MAC address matches the MAC address of the destination Layer 3 interface. PR1162277
  • Executing request support information on the CLI increments the interface input octets for the physically up ports on EX4500 Virtual Chassis. PR1180683
  • On EX4300-VC with link aggregation group (LAG) interface configured, if the old master RE reboots during NSSU, then the new master might start with old Link Aggregation Control Protocol (LACP) state, and this could result in LAG interface flap. PR1228494
  • If an EX4550-32T is configured with 100m fixed speed without auto-negotiation, sometimes the interface does not come up. The peer device that is supporting Auto-MDI detects incorrectly and causes the link to go down. PR1235868
  • EX Series switches running eswd (Ethernet switching) daemon may not learn MAC addresses on some interfaces after reboot if duplicate Interface index is seen. PR1248051
  • On EX4300 platform with power redundancy N+N mode, PoE interfaces flap when any side power supply unit (PSU) is removed and only one PSU is left. PR1258107
  • On all EX Series platforms, the configuration of speed and auto-negotiation properties may not be committed successfully if it is applied on a group of interfaces. PR1258851
  • Virtual Chassis: Traffic might be lost for about 10 seconds if the master member FPC reboots. PR1283702
  • When a network port is used as a Virtual Chassis port (VCP) on EX3300, it doesn't work properly. Once it goes down, it doesn't come up even though physically correct. PR1310819

J-Web

  • On an EX Series switch using the J-Web interface, the J-Web interface might pause indefinitely after STP, RSTP, or MSTP is selected from the Configure > Switching > Spanning tree menu. PR1046051

Layer 2 Features

  • On EX4600/QFX3500/QFX3600/QFX5100 Series switches, if the same VLAN-ID is configured on user-to-network interface (UNI) and network-to-network interface (NNI) in Q-in-Q scenario, feature swap-swap might not work as expected. PR1297772
  • In a Spanning Tree Protocol (xSTP) scenario on EX4500/EX4550, some ports may not come up on PIC 1 or PIC 2 when the third PIC is inserted. PR1298155

Multicast Protocols

  • If igmp-snooping vlan all is enabled with inet6 IRB configured then ipv6 multicast traffic gets dropped on the PFE. PR1185311
  • On EX2200, EX3300, EX3200, EX4200, EX4500, EX4550, EX6200, or EX8200 switches, configure igmp-snooping for the respective VLAN and change the robust-count (for example, robust-count 5) from the default value, after that add or delete any interface configuration that is part of the IGMP snooping VLAN. Then check show igmp-snooping membership detail—the membership timeout value is reduced or changed. As a workaround, issue commit force full. PR1215247

Network Management and Monitoring

  • On EX Series switches except EX4300 and EX4600, the Over temperature SNMP traps are sent when the CPU temperature gets higher than the bad fan temperature threshold even when there are no bad fans in the chassis. PR1226388
  • EX Series switches configured with sFlow and MAC RADIUS might incorrectly send MAC authentication requests for transit DHCPv6 traffic that is picked up by the sFlow agent. PR1298646

Platforms and Infrastructure

  • On EX4300 Virtual Chassis, the FRU PSU removal and insertion traps are not generated for master or backup FPCs. PR1302729

Routing Protocols

  • BGP routes are rejected as cluster ID loop prevention check fails due to a misconfiguration. But when the misconfiguration is removed, BGP routes are not refreshed. PR1211065

Security

  • PHP software included with Junos OS J-Web has been updated to resolve multiple vulnerabilities. Refer to JSA10804 for further details. PR1157572
  • Multiple Products: "Dirty COW" Linux Kernel Local Privilege Escalation, please refer to https://kb.juniper.net/JSA10807 for more information. PR1227266

Software Installation and Upgrade

  • On an EX Series switch that is supporting the zeroize feature, after the switch is booted up from "request system zeroize" and then a configuration is saved, the saved configuration won't be restored after the switch is rebooted. As a workaround, remove the file /var/tmp/config_recovery from the device before going for the second reboot. PR1228274

Virtual Chassis

  • On EX Series or QFX Series Virtual Chassis, if new members are not zeroized prior to being added to the Virtual Chassis, and then one of the new members splits from the Virtual Chassis, then whenever you run commit or commit check, the commit might hang for a long time and then report a timeout error on the FPC that split from the Virtual Chassis. PR1211753
  • On EX4300 Virtual Chassis, a 10-gigabit VCP might not get a neighbor after a system reboot. PR1261363
  • The eswd process might crash after an RE switchover in EX-VC scenario. The crash happens due to disordered processing of VLAN/vmember by eswd and L2PT modules. As the order of processing does not remain the same every time, the crash is random across switchovers. PR1275468

Modified: 2017-11-29