Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

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.

Forwarding and Sampling

  • When you configure the fast-lookup-filter statement with a match that is not supported in the FLT hardware, traffic might be lost. PR1573350

Platform and Infrastructure

  • On EX4400-48MP devices, the VM proccess generates core files and VC might split with multicast scale scenario. PR1614145

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

  • On EX4300-MPs devices, the runt, fragment, and jabber counters does not get incremented. PR1492605

  • On EX4300-48MP device, if you enable POE, a primary Routing Engine might reconnect that might impact traffic. PR1499771

  • Pause frames counter do not get incremented when pause frames are sent. PR1580560

  • On EX4400 family of devices, sometimes login prompt does not get displayed after the login session ends. PR1582754

  • In rare circumstances, when the routing-engine switchovers, the routing protocol daemon in former active routing-engine (new backup routing-engine) might restart with a core file while in process of being terminated. PR1589432

  • Interop for 1G interfaces between EX4100 SKUs and ACX5448/ACX5448-M/D, and MX480 will not work. PR1657766

  • The EX4100 devices, the MACsec interface statistics of the encrypted or decrypted bytes does not get updated properly after a certain value. PR1658584

  • The EX4600 devices, Virtual Chassis goes in to the Unstable state for 3 to 7 minutes that causes traffic loss. PR1661349

  • On EX92XX devices with the EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) scenario, the DHCP (Dynamic Host Configuration Protocol) packets from the client get dropped while tunneling to the EVPN-VXLAN. When this happens, the packets does not reach the DHCP server and the host could not get the IP address. PR1662524

  • A common display behavior across EX platforms appears and this is inline with existing platforms. Further in vty, the following log gets generates for pic 1 ports that does not support AN: tvp_port_resource_set AN cfg not supported on Falcon core port:1/3. PR1666227

  • On EX4100 devices, delay in the CLI display for PoE commands might be observed when more POE devices with LLDP enabled (Power via MDI) are connected to the switch in a scaled environment with Perpetual POE scenarios. The LLDP PD requested power for all the ports are processed for each of the connected PDs, however the values in CLI display (CLI sync) might be delayed. PR1671311

  • When system gets rebooted or image gets upgraded, the following log might get generated during shutdown time and it is an harmless log: BCM Error: API bcm_plp_mode_config_set(phy_name, phy_info, speed, intf_type, r_clk, if_mode, aux) at tvp_bcm_mgig_tx_enable_set:616 -> -8

    When system comes up again, there will be no functional impact. PR1678440

  • On a continuous switch reboot trigger and when the switch boots back, sometimes a vmcore process might generate a core file. PR1672731

  • EX4100 and EX4100-F Virtual chassis: Non-existing PIC ports (e.g. PIC0:PORT100, PIC2:PORT102) while running the jvision query. PR1681673

  • If you insert the 1G optic on the uplink ports of EX4100-24mp,EX4100-48p, EX4100-48t, EX4100-24p, and EX4100-24t SKUs, the activity LED gets lit irrespective of link in the Present or Up status. PR1682633

  • EX4100 and EX4100-F series: The secondary console (USB-C type) does not show the boot logs. User will get the login prompt once the device boots up with the Junos OS. PR1684032