AE (Aggregate Ethernet) ports may not forward traffic properly due to defect leading to mis programming of hardware during different triggers e.g. link flap, pfe restart, reboot. It may drop the traffic entering the AE port or may send the traffic with wrong VLAN ids. Following logs may be seen for different AE /VLAN during the issue. BRCM-VIRTUAL,brcm_vxlan_destroy_access_port(),3485:Failed to delete port(ae222) to vxlan BD(8)
Trace logs highlight inadequate AE interface programming during the 10G to 25G transition. Notably, historical events illustrate failed deletions leading to persistent stale entries. While these issues may not be immediately evident upon deletion failure, they become apparent when the partially deleted virtual port is reused.
Oct 5 22:10:44 hostanme mib2d[8580]: SNMP_TRAP_LINK_UP: ifIndex 557, ifAdminStatus up(1), ifOperStatus up(1), ifName ae23 >> ae programming surrounding ae23 didn’t happen at this port UP event.
[Fri Oct 6 16:03:13.850] [179081855] brcm_vxlan_create_access_port:1870 :DUPLICATE TOKEN FOR ae23 vxlan bd(6) port-token(12). >> ae programming surrounding ae23 happened at this port UP event
[Tue Sep 19 15:25:00.232] [160506183] brcm_vxlan_destroy_access_port:3277 :L3 lookup disable failed for port 0x0
[Tue Sep 19 15:25:00.232] [160506184] brcm_vxlan_destroy_access_port:3289 :Failed to delete port(ae12) to vxlan BD(4)
The issue has been addressed through PR1609914: https://prsearch.juniper.net/problemreport/PR1609914
Several fixes including PR 1609914 related to EVPN access port programming are included in the 21.4R3-S4 release.
Mitigation:
The issue may be temporarily resolved by sequentially resetting both uplink ports connecting the access and aggregate switches. However this procedure is not guaranteed to recover the problem state in every situation.
It's recommended to upgrade to a code version listed in "Resolved In" section of PR1609914 to address this issue.