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: 22.1R1

Class of Service (CoS)

  • The dcpfe core files might be seen in the auto-channelization scenario or when SFP is plugged out. PR1616847

Infrastructure

  • For EX4400 product family, net installation (PXE) does not work. PR1577562

  • FreeBSD12: On Panic 0-size vmcore file gets generated. PR1607299

  • DHCP packets originated from QinQ/SP vlans will have vlan-id of C-vlan in DHCP options82 circuit-id field. Whereas when configured to use vlan description, then S vlan name will be used in circuit-id. PR1616613

  • Primary FPC might crash when you log into the device post powercyle of a three member EX2300-MP Virtual Chassis. PR1625987

Interfaces and Chassis

  • SNMP_TRAP_LINK_UP and SNMP_TRAP_LINK_DOWN trap might be generated while activating and deactivating firewall filters. PR1609838

  • The vrrpd core files might be observed after the interface state changes. PR1646480

Juniper Extension Toolkit (JET)

  • JET SDK cannot produce bsd6/legacy Junos compatible package. PR1636189

Junos XML API and Scripting

  • File download using request system download might fail. PR1604622

Layer 2 Ethernet Services

  • The jdhcpd process starts spiking and DHCP becomes unresponsive if you modify 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 packet drop occurs due to missing ARP entry on the provider edge. PR1607169

Platform and Infrastructure

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

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

  • ARP resolution failure might occur in the EVPN-VXLAN scenario. PR1561934

  • IS-IS adjacency might fail to be formed if the MTU size of an IRB interface gets configured with a value greater than 1496 bytes. PR1595823

  • Error message error: syntax error: request-package-validate gets generated on device CLI output during Non Stop Software Upgrade. PR1596955

  • The interface on SFP-T or SFP-SX might stop forwarding traffic on EX4600 devices. PR1598805

  • During day1 stage of EX4400 device management from MIST, the cloud LED remains in green state even if device loses connectivity with cloud. PR1598948

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

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

  • The SFP-T port might stop forwarding traffic on EX4600 platforms. PR1600291

  • Traffic loss might be observed if you configure dot1X with supplicant multiple and authenticated user from radius is 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 in case MACsec is configured. PR1611772

  • Change in the commit error message appears while configuring the same vlan-id with different vlan name through openconfig CLI. PR1612566

  • EX2300, EX3400, EX4300-MP, and EX4400 devices causes MAC movement when the IGMP query receives packet on the backup FPC port. PR1612596

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

  • On EX9204 device, entAliasMappingIdentifier does not reflect the correct SNMP entity to ifindex mapping for 100G and 40G ports. PR1614081

  • After performing zeroize factory default configuration does not display appropriate interface in the device. PR1614098

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

  • 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 seen on EX and QFX devices after the configuration changes. PR1618352

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

  • On EX2300 Series, EX2300-MP Series, and EX3400 Series, a slow memory leak occurs due to processing of specific IPv6 packets. PR1619970

  • OAM CFM session does not come up if the configured ERPS and CFM control traffic uses the same VLAN as ERPS control traffic. PR1620536

  • EVPN Type5 routes might not be installed. PR1620808

  • NSSU (nonstop-upgrade) CLI is not present in the Junos OS Release 21.2R1. PR1621611

  • Traffic loss might be observed after configuring VXLAN over IRB interface. PR1625285

  • 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

  • When clients connect to the isolated Virtual Local Area Network (VLAN) through trunk port can't communicate to the network. PR1626710

  • DHCP clients might not go to BOUND state when you enable the AE bundle between the DHCP server and snooping device. PR1627611

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

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

  • The error message BCM_PVLAN_UTILS:ERR:pfe_bcm_pvlan_utils_get_sec_bd(),789: Failed to get Secondary-bd gets logged DHCP server receives packet on a private VLAN. PR1630553

  • 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

  • Traffic loss occurs for 20 seconds on Virtual Chassis with aggregated Ethernet link-protection when rebooting backup FPC. PR1633115

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

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

  • IRB traffic drop might be observed 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

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

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

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

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

  • Route leak from the primary routing-instance to custom routing-instance fails for local interface. PR1623429

  • The ARP resolution might get failed on the VRRP enabled interface. PR1630616

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

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

Routing Protocols

  • The rpd core files might be observed due to memory corruption. PR1599751

  • The rpd 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 IFDs are attached or detached. PR1622283

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