Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Resolved Issues

Learn about the issues fixed 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.

Interfaces and Chassis

  • The vrrpd core might be observed after interface state change. PR1646480

Layer 2 Ethernet Services

  • DHCP packets might not be sent to the clients when forward-only is reconfigured under the routing instance. PR1651768

Platform and Infrastructure

  • Traffic is dropped after chassis-control restart when filter is attached and source and destination knob is enabled. PR1615548

  • Traffic loss might be seen when the interface fails to verify the parameter "LOCAL-FAULT". PR1623215

  • GARP reply doesn't update ARP entry though gratuitous-arp-reply option is configured. PR1644616

  • Fabric Board reset with an error message might be observed on certain Junos platforms. PR1648850

  • The dc-pfe might crash due to the VCCP flap. PR1655530

  • EX4300 request system software add ftp fails with the message The /var/tmp filesystem on JUNOS is low on free disk space PR1659460

  • The EX2300 might unexpectedly drop VOIP VLAN traffic after reboot. PR1633883

  • The fxpc process crash might be triggered when a MAC is aging out. PR1634433

  • DHCP snooping table might fail on all Junos platforms to populate MAC address after a VLAN change. PR1637380

  • The adapted sample rate might get reset to the configured sample rate without changing the sampling rate information in sFlow datagrams. PR1604283

  • The VMcore might be observed on EX platforms in rare scenario. PR1641988

  • Traffic impact might be seen if you enable persistent-learning on an interface. PR1643258

  • Traffic loop might occur due to STP ports not created in new master Routing Engine after switchover due to reboot of master Routing Engine on EX4300, EX3400, and EX2300 platforms in Virtual Chassis (VC). scenario PR1647000

  • The Virtual Chassis port might not be formed automatically after Zeroize. PR1649338

  • L2PT configuration on a transit switch in a Q-in-Q environment breaks L2PT. PR1650416

  • L2PT might not work for AE interfaces in Q-in-Q environment. PR1653260

  • Port mirroring traffic not being flooded on the expected interfaces. PR1654812

  • EX4300-48MP does not generate ICMPv6 too big messages. PR1655654

  • All Slaac-snooping entries learnt on an IFL are deleted when an IFBD is deleted such that IFL is member of more than 1 VLANs. PR1655913

  • port/mac gbp tags might not be carried forward to the spine. PR1659384

  • The fxc crash might be observed with rpf check enabled. PR1662508

  • EX4300-48MP: Virtual Chassis: NSSU aborted with Backup Routing Engine might be in inconsistent state. PR1665562