Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Resolved Issues

Learn about the issues fixed in this release for EX Series.

Infrastructure

  • Recovery snapshot might fail if OAM volume is already mounted. PR1639991

Interfaces and Chassis

  • The vrrpd might crash and generate core files after interface state change. PR1646480

Layer 2 Ethernet Services

  • Option 82 might not be attached on DHCP request packets. PR1625604

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

Platform and Infrastructure

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

  • MAC address learning failure and traffic loss might be observed on VXLAN enabled ports with native-VLAN configured. PR1663172

  • SSH traffic might be affected when filter log action is used. PR1663126

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

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

  • The inner tag (C-tag) value might get modified to zero for egress traffic when the inner tag values are copied to the outer tag (S-tag). PR1652976

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

  • Some interfaces might be down after a power outage or power cycle. PR1580829

  • VSTP might not work in Q in Q environment. PR1622404

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

  • The ARP resolution might fail on VRRP enabled interface. PR1630616

  • Application of firewall filters might break connectivity towards the hosts on EX4300. PR1630935

  • The Packet Forwarding Engine might get crash when Virtual Chassis member flaps on EX platforms. PR1634781

  • SCB reset with error : zfchip_scan line = 844 name = failed due to PIO errors PR1648850

  • FXPC might crash and generate a core file due to Segmentation fault during VCCP flap. PR1655530

  • On EX4300 platform, high CPU usage is seen with generation of log message /kernel: %KERN-3: i802_3_slow_recv_input:oam/esmc PDU dropped. PR1661332

  • Junos 'et-' interface stuck and remains down between two particular ports. PR1535078

  • Error message error: syntax error: request-package-validate will be seen on device CLI output during non stop Software Upgrade. PR1596955

  • The device will be unavailable while performing FIPS 140-2/FIPS 140-3 level 2 internal test on FreeBSD 12 based Junos platforms. PR1623128

  • DHCPv6 server binding might not happen when LDRA is enabled along with DHCPv6 snooping. PR1627600

  • System time might not be updated after reboot on EX2300 platform. PR1627673

  • The error message BCM_PVLAN_UTILS:ERR:pfe_bcm_pvlan_utils_get_sec_bd(),789: Failed to get Secondary-bd is logged when a dhcp packet is received on private vlan. PR1630553

  • Unicast ARP packets with the first four bytes of its destination MAC matching to system macs of a transit system get trapped by the system. PR1632643

  • There might be traffic loss for 20 seconds on Virtual Chassis with AE link-protection when rebooting backup FPC. PR1633115

  • The VCPs connected with the AOC cable might not come up after upgrading to Junos OS Release 17.3 or later releases. PR1633998

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

  • The dot1x ports might be stuck in the connecting state after clearing the dot1x sessions. PR1634820

  • EX4300-48MP - LED state stays OFF in the output of show chassis led for 40G port on PIC 2. PR1635106

  • IPv6 route advertisement sent on management interfaces might cause other devices to fail to get the dhcpv6 address. PR1635867

  • There might be IRB traffic drop when mac-persistence-timer expires. PR1636422

  • Configuring L2PT on a transit switch in a Q-in-Q environment breaks L2PT for other S-VLANs. PR1637249

  • MAC address might not be learned on the new interface after MAC move. PR1637784

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

  • There might be a delay for the interfaces to come up after reboot/transceiver replacement. PR1638045

  • MAC-move might occur when you configure dhcp-security.. PR1639926

  • The error message dot1xd : devrt_rtsock Don't know how to handle message type 2 is logged even if dot1x is not set. PR1641304

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

  • Junos OS: RIB and Packet Forwarding Engines might get out of sync due to a memory leak caused by interface flaps or route churn (CVE-2022-22209). PR1642172

  • There might be traffic impact if you enable persistent-learning on an interface. PR1643258

  • Space issues might be seen on EX3400 devices. PR1643824

  • 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

  • An incorrect PEM alarm will be raised on EX4400 devices. PR1658049

Routing Protocols

  • Message Initialize libjtask-license first! for mcsnoopd is seen after committing configuration. PR1636261