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 

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 15.1X53-D55 for 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.

Dynamic Host Configuration Protocol

  • If an EX2300 switch is configured with the interface-mac-limit statement, the switch does not forward DHCP Offer packets from the server to the client. Configuring IRB on the affected interface might prevent the problem. PR1239633

Platform and Infrastructure

  • On EX3400 and EX2300 switches, Junos OS volume recovery might not work after the switch is booted from a USB recovery snapshot. PR1186127
  • On EX3400 and EX2300, after creation of recovery snapshot, SSH/Telnet login is unsuccessful from OAM volume. PR1191356
  • On a EX2300 switch, the aunchd process might generate a core file when the switch is rebooted. PR1239745
  • On EX2300 and EX3400 switches, the system dumps a fips-error core file when you use the CLI to load a Junos image. This has no effect on functionality and can be ignored. PR1241502

Network Management

  • Real-time performance monitoring (RPM) probe-clients for ICMP or UDP might not work for EX2300 and EX3400 switches. PR1188841

Routing Policy and Firewall Filters

  • On EX3400 switches, filter bind might fail because of TCAM unavailability when:
    • A filter that has more than the supported number of terms is applied on an ingress or egress interface
    • The extra terms are removed from such a filter and the configuration is committed again

    As a workaround, unbind the filter and bind it again to the interface. PR1181501

Software Installation and Upgrade

  • On an EX4300 Virtual Chassis, when performing a nonstop software upgrade (NSSU), you will experience a traffic drop of more than 5 seconds for both Layer 2 and Layer 3 for the following protocols: multicast, Multiple Spanning Tree Protocol, Ethernet Ring Protection, and OSPFv3. PR1224987
  • On an EX2300 Virtual Chassis, when you upgrade the software using the CLI, the device might go into the debug (DB) mode with the following error message: Fatal kernel mode data abort: 'Alignment Fault' on read. PR1237863

Virtual Chassis

  • On an EX2300 Virtual Chassis, the request system reboot all-members at now command might reboot only that particular switch in the Virtual Chassis from which the command is issued. PR1188016
  • On an EX2300 switch in a Virtual Chassis, a VCCP daemon restart might result in existing OSPF sessions over link aggregation interfaces being struck in the Init state. PR1180055

Related Documentation

Modified: 2017-07-21