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 

Resolved Issues

This section lists the issues fixed in the Junos OS 15.1X53 releases for the EX2300 and EX3400 switches.

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

Resolved Issues: Release 15.1X53-D55

Class of Service

  • On EX2300 switches, a packet loss priority (PLP) of medium-low is not supported for firewall filter configurations. PR1180586
  • EX2300 and EX3400 switches do not support weighted random early detection (WRED) profiles. PR1187354

High Availability

  • DHCP renew or release packets might not be forwarded to the server when the EX2300 switch acts as a VRRP node. PR1157056

Layer 2 Features

  • On EX3400 and EX2300 switches, for the mac-move-limit statement, the drop and drop-and-log actions might not work. PR1178693
  • On EX2300 and EX3400 switches, the hash-mode option is not available at the [edit forwarding-options enhanced-hash-key] hierarchy level. PR1188866
  • On EX3400 and EX2300 switches, LLDP, LACP, and MVRP protocol options are not available under the mac-rewrite configuration statement. PR1189353

Layer 3 Features

  • On an EX2300 switch, if the only configured route is a static default route, transit traffic destined to IP addresses that belong to subnets 128.0.0.1 to 191.255.255.254 are dropped. To work around this problem, configure specific routes in addition to the default route. PR1220078

Platform and Infrastructure

  • On an EX3400 switch, CLI upgrades might fail with an insufficient space error. As a workaround, if there is not enough space for an upgrade, use the request system storage cleanup command to clear up space. PR1148911
  • The EX3400 switch might shift to debug mode prompt or initiate an autoreboot after multiple reboots and switchovers. PR1172524
  • EX2300 and EX3400 switches do not support VRRP authentication. PR1172775
  • On EX3400 switches, the console response might become slow when ARP requests are sent at five percent of the line rate to the management interface. PR1181891
  • On EX3400 switches, high CPU utilization caused by the fxpc process might also increase the latency (up to 100 ms) of traffic directed to the Routing Engine. PR1230716

Virtual Chassis

  • In an EX3400 Virtual Chassis with two members, you might see the Routing Engine become unresponsive for up to 10 minutes while displaying the error message kernel: jlock hog timer expired: jlock acquired followed by additional kernel error messages; eventually the Virtual Chassis recovers on its own. PR1235994

Resolved Issues: Release 15.1X53-D52

Infrastructure

  • On EX2300 and EX3400 platforms, if the switch has been powered off for a couple of days, when you power it on, it boots with the default date of 1970-01-01. If NTP is configured on the switch at this time, the system clock might be set to an incorrect date—for example, 2038-01-01—which results in all protocols and timer-related functionality being affected. PR1215296

Resolved Issues: Release 15.1X53-D51

Class of Service

  • On EX3400 switches, CoS rewrite does not work on IRB interfaces. PR1190361

Infrastructure

  • EX2300 switches do not support the Energy Efficient Ethernet (EEE) feature. PR1178790
  • On EX3400 and EX2300 switches, the request system zeroize media command might not erase USB snapshot. PR1183830
  • On EX3400 switches, the output of the show macsec statistics command might not display MACsec counter details. PR1189042
  • On an EX3400 switch, if N+N PSU redundancy is configured, the switch might not revert to the N+0 mode. PR1191731
  • On EX3400 and EX2300 switches, when the client is authenticated in either dynamic, server-fail, server-reject, or guest VLAN multiple supplicant modes, ping failures might be seen between the client and switch. PR1192363

Layer 2 Features

  • On EX2300 switches, rate-limiting is observed on 10-gigabit ports after a storm control configuration is removed. PR1189027

Layer 3 Protocols

  • On EX2300 and EX3400 switches, LLDP neighbors might not be formed over Layer 3 tagged interfaces. PR1190585

Network Management

  • On EX2300 and EX3400 switches, sFlow sampling might not work for egress traffic. PR1185677

Virtual Chassis

  • On an EX3400 switch, the virtual management Ethernet (VME) interface might not be reachable after a reboot or switchover. As a workaround, enter the ifconfig me0 down command at the shell prompt. PR1187433
  • In an EX3400 Virtual Chassis with two members, you might see the Routing Engine become unresponsive for up to 10 minutes while displaying the error message kernel: jlock hog timer expired: jlock acquired followed by additional kernel error messages; eventually the Virtual Chassis recovers on its own. PR1235994

Related Documentation

Modified: 2017-07-21