Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Resolved Issues: 21.3R2

Class of Service (CoS)

  • The dcpfe process might generate core file in the auto-channelization scenario or when you plug out SFP. PR1616847

Infrastructure

  • The fxpc process might crash and generate core files. PR1611480

Interfaces and Chassis

  • SNMP_TRAP_LINK_UP and SNMP_TRAP_LINK_DOWN traps might be seen while activating and deactivating firewall filters. PR1609838

Layer 2 Ethernet Services

  • The jdhcpd process started spiking and DHCP becomes nonresponsive when modifying the configuration to add override always-write-giaddr and remove forward-only. PR1618306

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

MPLS

  • MPLS VPN packets drop due to missing ARP entry on the PE device. PR1607169

Platform and Infrastructure

  • During flooding, MAC gets learnt only on the normal access port but not on the aggregated Ethernet interface trunk port. PR1506403

  • Some transmitting packets might get dropped due to the disable-pfe action not being invoked when the fabric self-ping failure gets detected. PR1558899

  • On EX2300 and EX3400 switches, the upgrade of the PoE firmware might fail. PR1584491

  • During day one stage of EX4400 device management from MIST, the cloud LED remains in the Green state even if the device looses connectivity with the Cloud. PR1598948

  • The l2ald process might crash due to memory leakage when all active interfaces in a VLAN becomes unstable. PR1599094

  • On EX4600 switches, the SFP-T port might stop forwarding traffic. PR1600291

  • NSSU performed with MACsec configuration might result in the fxpc process generating core files. PR1603602

  • On EX4400 switches with POE supported device, the PoE firmware upgrade must be done with the bt-firmware command option only. PR1606276

  • Change in commit might generate error message while configuring the same VLAN-ID with different VLAN name through the openconfig command. PR1612566

  • FPC might crash after the device restart in the EVPN-VXLAN scenario. PR1613702

  • On EX4300 switches, the OAM CFM adjacency does not get formed. PR1619231

  • On EX2300, EX2300-MP, and EX3400, a slow memory leakage due to processing of the specific IPv6 packets (CVE-2022-22180) occurs. PR1619970

  • EVPN Type-5 routes might not be installed. PR1620808

  • Traffic might be lost after configuring VXLAN over the IRB interface. PR1625285

  • Packet drop might be observed when you configure L2PT on the transit device. PR1627857

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

  • On EX4300 switches, verification of the LOCAL-FAULT interface parameter insertion fails on the xe interface. PR1623215

  • Route leakage from the primary routing-instance to the custom routing-instance failure occurs for the local interface. PR1623429

  • The et-interface becomes nonresponsive and remains down between two particular ports. PR1535078

  • On EX4300 devices, MAC addresses aging issue occurs. PR1600029

  • Traffic loss might be observed if you configure dot1X with the supplicant multiple and authenticated user from radius in the single supplicant mode. PR1610746

  • Inter-vlan connectivity might be lost in an EVPN-VXLAN with CRB topology. PR1611488

  • Traffic stops when traffic switches from one LAG member to another member if you configure MACsec. PR1611772

  • The EX2300, EX3400, EX4300-MP, and EX4400 devices causes MAC to move when the IGMP query packet gets received on the backup FPC port. PR1612596

  • Removing the JNP-SFPP-10GE-T optical module from a port might cause certain ports to go down. PR1614139

  • The Packet Forwarding Engine might crash due to deletion of storm control configuration for IFL in CLI, which might lead to traffic loss. PR1616646

  • Core files might be generated on EX devices after configuration changes. PR1618352

  • The dcpfe process might crash after changing and deleting the VXLAN VNI configuration on EX devices. PR1619445

  • OAM CFM session does not go to the Up state if the configured ERPS and CFM control traffic uses the same VLAN as ERPS control traffic. PR1620536

  • The filter required for routing the Layer 3 traffic of targeted broadcast and static ARP entry with multicast-mac address might fail to install. PR1626620

  • Clients connected to the isolated VLAN through trunk port cannot communicate to the network. PR1626710

  • The line card might crash and reload if the EVPN MAC entry does not get deleted correctly. PR1627617

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

  • On EX3400 Virtual Chassis, traffic loss for 20 seconds occur when you reboot the backup FPC with the static link-protection. PR1633115

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

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

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

  • On EX4600 switches, the interface on SFP-T or SFP-SX might stop forwarding traffic. PR1598805

  • The Packet Forwarding Engine might get crash when the Virtual Chassis member flaps. PR1634781

  • Delay might be observed for the interfaces to come up after reboot or transceiver replacement. PR1638045

Routing Protocols

  • The rpd process might generate core file due to memory corruption. PR1599751

  • The rpd process might crash and restart when you enable NSR. PR1620463

Subscriber Access Management

  • Adding the new radius access configuration might fail. PR1629395

Virtual Chassis

  • During NSSU, errors related to link might be observed while you attach or detach IFDs. PR1622283

  • Delay might be observed while establishing the virtual-chassis post upgrading or rebooting device. PR1624850