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 process might generate core file in the auto-channelization scenario or when you plug out SFP. PR1616847

  • The uplink interface remains down for a longer duration due to VXLAN scaled configuration. PR1631448

EVPN

  • A few ARP/ND/MAC entries for VLANs are missed with the MAC-VRF configuration. PR1609322

  • mac-table aging timeout fails in some scenarios. PR1612866

  • IRB proxy-arp unrestricted might not work if EVPN/l2alm proxy is enabled. PR1613201

  • Multiple memory leaks might be seen, leading to process rpd crash. PR1626416

  • The MAC address might not be visible in the EVPN-VXLAN environment. PR1645591

High Availability (HA) and Resiliency

  • Memory might leak on the backup Routing Engine when the ksyncd process is in the Inconsistent state and had encountered an initialization error. PR1601960

Infrastructure

  • A false error related to insufficient space might appear while installing a corrupted Junos OS image. PR1570148

Layer 2 Ethernet Services

  • Enabling DHCP on Junos OS might cause the file system storage of the router to get filled up with log files. PR1617695

MPLS

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

  • On QFX5000 switches, traffic loss occurs after the STP topology changes. PR1616878

  • On QFX5000 switches, traffic towards MPLS-Core does not get rerouted to alternate port. PR1627002

Platform and Infrastructure

  • The unexpected next-hop might appear after the route gets deleted. PR1477603

  • Multiple entries to vlan-id-list might not work in the EVPN-VXLAN scenario. PR1564403

  • The grpcd process might crash if the route or interface flaps. PR1565255

  • On QFX10K2-60C switches, disk missing alarms does not appear. PR1573139

  • When you commit the soft loopback port and analyzer configurations together, mirror ingress to local port does not work. PR1581542

  • On QFX5000 switches, the output of the show route detail command might not display next-hop type IPoIP chained component next hop. PR1584322

  • IPv6 link-local traffic getting classified to firewall might affect communication on the IPv6 link-local addresses. PR1600085

  • Packet might drop on FPC on the Trio-based platforms.

  • On QFX5000 switches, the dcpfe process might crash. PR1588704

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

  • The DCI InterVNI and IntraVNI traffic might be silently discarded in the gateway node due to the tagged underlay interfaces. PR1596462

  • On QFX5110 switches during FRR, when more than one multi-home interface goes in to the Down state, traffic might loop. PR1596589

  • The following error message gets generated on the device during continuous software upgrade:

    PR1596955

  • On QFX10000 switches, the dcpfe or fpc process might crash in a rare case. PR1597479

  • On QFX10008 switches, the Routing Engine1 goes to the DB prompt when you try to load the profile configurations over the LRM configurations. PR1598814

  • The VCP might not form adjacency after rebooting the primary FPC in the Virtual Chassis scenario. PR1600398

  • Removing and adding Virtual Chassis ports might cause the FPC to reboot. PR1601557

  • InterDC traffic loss might occur in the MAC-VRF EVI with the dlu.ucode.discard trap status. PR1601961

  • In a very rare case, the l2ald process generates a core file when EVPN(mac-vrf) uses the IPv4 underlay. PR1602244

  • On QFX5120 switches, even after deactivating the analyzer configuration, traffic gets mirrored. PR1603192

  • Unicast DHCP packets might get flooded when you configure the DHCP relay in the non-default routing-instance. PR1603444

  • Virtual Chassis ports might remain in the Down state after the addition and removal of the ports. PR1606705

  • The sFlow samples might not get generated for the transit MPLS traffic carrying the IPv6 packets. PR1607497

  • FPC might crash post firewall filter configuration changes. PR1608610

  • On QFX10016 switches, an additional VLAN tag might be added for Point-to-Point Protocol over Ethernet (PPPoE) packets. PR1610012

  • On QFX10000 switches, continuous Layer 3 traffic drop might occur with MC-LAG configuration. PR1610173

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

  • On QFX10002-60C switches, continuous FPC crash and dcpfe process might generate core file. PR1612871

  • ARP resolution for data traffic received over Type5 might fail. PR1612905

  • On QFX10002-60C switches, the FPC 0 Major Errors alarm might get generated due to a rare timing issue. PR1613229

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

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

  • On QFX5000 switches, the VLAN firewall filter does not get deleted in the Packet Forwarding Engine after configuration change. PR1614767

  • The l2ald process might crash in the EVPN scenario. PR1615269

  • Slow memory leakage (32 bytes each time) of rpd process might occur. PR1616065

  • On QFX5120-48YM switches, the BFD session might flap. PR1616692

  • The l2cpd process generates core file with FIP snooping configuration on any interface. PR1617632

  • The BFD session might become nonresponsive in the Init state after l2-learning restart due to incomplete ARP resolutions. PR1618280

  • Core file might be generated after the configuration changes. PR1618352

  • Traffic might be dropped when you configure IRB and remove from VLAN. PR1618425

  • The sample and accept firewall action drops inbound packets destined to cpu-host. PR1646740

  • On QFX5000 switches, the dcpfe process might crash after performing VXLAN VNI configuration change and deleting the configuration. PR1619445

  • Disabled VCP (Virtual chassis port) goes in to the Up state after the optic on it is reseated. PR1619997

  • High wired memory utilization might be observed if you enable GRES. PR1620599

  • Routes learned through the EVPN Type-5 route are not resolved. PR1620627

  • On QFX10000 switches, the EVPN-VXLAN Type5 traffic might get fail on the Spine device. PR1620924

  • NSSU (nonstop-upgrade) CLI gets missed from Junos OS Release 21.2R1. PR1621611

  • On QFX5120 switches, the following error message gets generated while loading the build:

    PR1621630

  • LED indicator might display the status as ON once you remove QSFP. PR1622580

  • Host generated IPv4 traffic sent over IPv6 next-hop with IRB interface might get dropped. PR1623262

  • On QFX52000 switches, interface does not come up after swapping from 100G to 40G. PR1623283

  • MACsec session might flap if multiple logical interfaces gets created on the single physical interface. PR1624524

  • In rare circumstances, PKID might crash and generate a core file when there was limited memory available on the routing-engine. PR1624613

  • On QFX5000 switches, the following log messages do not process packet further:

    PR1624925

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

  • On QFX10002 and QFX10008 switches, the no-incoming-port command does not get applied after reboot. PR1625988

  • The show task scheduler-slip-history command displays the number of scheduler slips and last 64 slip details. PR1626148

  • Routing Engine generating traffic might not be forwarded when next-hop is indirect unilist of the EVPN Type 5 tunnel. PR1627363

  • The QFX10002-60C switches might not respond back to ICMP packets received with TTL or hop limit value of 1. PR1627566

  • On QFX10002, QFX10008, and QFX10016 switches, the Layer 3 traffic failure might occur with the scaled MC-LAG configuration. PR1627846

  • The 802.1p BA classification might not work on the mixed Virtual Chassis when the interface has a DSCP and 802.1p classifier. PR1628447

  • When you use DHCP smart relay, DHCP inform acknowledge might be sent with the broadcast address. PR1628837

  • The vmhost process might crash in a rare condition when you add and change the route. PR1629200

  • On QFX5110-32Q Virtual Chassis, some ports (port 20 and above) might not come up after a device restarts or the Packet Forwarding Engine reboots. PR1629231

  • Traffic might get dropped when you configure family ethernet-switching on the interface in the Q-in-Q scenario. PR1629680

  • On QFX5000 switches, the Chassis Status LED does not work. PR1630380

  • The interface might remain in the UP/UP state even if the admin disables the interface. PR1632440

  • On QFX5000 switches, the FBF filtered VLAN traffic does not get passed properly to the forwarding routing instances over the aggregated Ethernet interfaces. PR1633452

  • Traffic loss after the MAC ages. PR1633879

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

  • Data might not be exchanged through the EVPN-VxLAN domain. PR1635347

  • On QFX10008 switches, chassisd crashes after configuring the chassis disk-partition. PR1635812

  • Traffic might be silently discarded when you configure STP in the VXLAN environment. PR1636950

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

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

  • On QFX5000 switches, the targeted broadcast or WOL feature might not work. PR1638619

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

  • Packets drop in ingress QFX5000 switches with EVPN-LAG multihoming due to VP-LAG programming issue. PR1644152

  • On QFX5200 switches, the dcpfe process generates core file while testing ISSU from Junos OS Release 21.1R1.11 to Junos OS Release 21.2R1.7. PR1600807

  • Junos OS does not support the Dot1x based firewall policers. PR1619405

  • The third 802.1Q tag might not be pushed onto the stack in the Q-in-Q tunneling. PR1626011

  • The show interface extensive command might not display the Local/Remote fault. PR1629735

  • LACP timeout might be observed during high CPU utilization. PR1630201

  • Inner VLAN might be stripped off when input-native-vlan-push gets disabled. PR1631771

  • The KRT queue might get stuck with the ENOMEM -- Cannot allocate memory error message. PR1642172

Routing Policy and Firewall Filters

  • The rpd process might become nonresponsive at 100 percent when you enable the EVPN vrf-target and after changing any configuration. PR1616167

Routing Protocols

  • When you remove igmp-snooping from the device, the device might encounter inconsistent MCSNOOPD. PR1569436

  • The interface might receive multicast traffic from a multicast group. PR1612279

  • The incorrect BGP path might get selected when a preferred route becomes available. PR1616595

  • Traffic drops when the VPN labels gets incorrectly allocated due to change in nexthop. PR1617691

  • Verification of the BGP peer count fails after deleting the BGP neighbors. PR1618103

  • Time delay to export prefixes to the BGP neighbors might occur post applying the peer-specific BGP export policies. PR1626367

  • OSPF adjacency might take longer time to converge when the neighbour restarts non-gracefully. PR1634162

User Interface and Configuration

  • On QFX5700 switches, you cannot use the file delete /var/core/*/vmcore* command to delete the Linux core file. PR1624562