> When the child interface on a remote leaf is brought down, the corresponding remote tunnel to this ESI segment remains up on the remote leaf switches.
> This issue can be seen across QFX switches and MX routers
** consider an AE interface (ESI) between leaf 1 and leaf 2 **
** When the child interface of ae0 (on Leaf 2) is brought down **
13:49:13user@qfxrouter> show lacp interfaces ae38 13:49:13Aggregated interface: ae38 13:49:13 LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity 13:49:13 et-0/0/24 Actor No Yes No No No Yes Fast Active 13:49:13 et-0/0/24 Partner No Yes No No No Yes Fast Passive 13:49:13 LACP protocol: Receive State Transmit State Mux State 13:49:13 et-0/0/24 Port disabled No periodic Detached 13:52:26user@qfxrouter> show interfaces ae38 13:52:26Physical interface: ae38, Enabled, Physical link is Down 13:52:26 Interface index: 693, SNMP ifIndex: 720 13:52:26 Description: >TTEPZ_2.2_2BG54.20_EX4300_TOR:ae0 13:52:26 Link-level type: Ethernet, MTU: 1514, Speed: Unspecified, BPDU Error: None, Ethernet-Switching Error: None, MAC-REWRITE Error: None, Loopback: Disabled, << Output Shortened >> 14:25:44user@qfxrouter> show ethernet-switching vxlan-tunnel-end-point esi esi-identifier 01:01:02:03:xx:xx:xx:xx:01:00 14:25:44ESI RTT VLNBH INH ESI-IFL LOC-IFL #RVTEPs 14:25:4401:01:02:03:xx:xx:xx:xx:01:00 default-switch 2798 525128 esi.2798 ae38.0, 1 Aliasing 14:25:44 RVTEP-IP RVTEP-IFL VENH MASK-ID FLAGS MAC-COUNT 14:25:44 10.113.23.1 vtep.32776 1744 0 2 1 ------>> RVTEP-IFL pointing to Leaf1 (output captured on leaf1) ** Type 1 routes are seen from Leaf1 ** 14:50:53user@qfxrouter> show route | match 01010203xxxx38xxx1xx 14:50:541:10.113.23.1:0::01010203xxxx38xxx1xx::FFFF:FFFF/192 AD/ESI 14:50:541:10.113.23.1:1::01010203xxxx38xxx1xx::0/192 AD/EVI 14:51:064:10.113.23.1:0::01010203xxxx38xxx1xx:10.113.23.1/296 ES 14:51:071:10.113.23.1:0::01010203xxxx38xxx1xx::FFFF:FFFF/192 AD/ESI 14:51:071:10.113.23.1:1::01010203xxxx38xxx1xx::0/192 AD/EVI 14:51:204:10.113.23.1:0::01010203xxxx38xxx1xx:10.113.23.1/296 ES ** on Remote Leaf - LEAF 3, it can be seen that we are only recieving type one routes for this ethernet segment from Leaf1 ** 14:36:31user@LEAF3_QFX5120-32C_LEAF> show route | match 01010203xxxx38xxx1xx 14:36:321:10.113.23.1:0::01010203xxxx38xxx1xx::FFFF:FFFF/192 AD/ESI 14:36:321:10.113.23.1:1::01010203xxxx38xxx1xx::0/192 AD/EVI 14:36:431:10.113.23.1:0::01010203xxxx38xxx1xx::FFFF:FFFF/192 AD/ESI 14:36:431:10.113.23.1:1::01010203xxxx38xxx1xx::0/192 AD/EVI ** However, we are seeing the RVTEP tunnel to both the Leaf switches where the ESI was configured ** 13:44:35user@LEAF3_QFX5120-32C_LEAF> ...01:02:03:00:00:38:00:01:00 13:44:35ESI RTT VLNBH INH ESI-IFL LOC-IFL #RVTEPs 13:44:3501:01:02:03:xx:xx:xx:xx:01:00 default-switch 4019 525129 esi.4019 2 Aliasing 13:44:35 RVTEP-IP RVTEP-IFL VENH MASK-ID FLAGS MAC-COUNT 13:44:35 10.113.23.1 vtep.32779 1744 1 2 1 13:44:35 10.113.23.2 vtep.32776 1741 0 2 1 ----------> This should be down 13:44:35 ** On the remote leaf, the host mac from the ESI segment seems to be learnt from VENH 1744 which is towards Leaf1 and is correct ** 14:03:27user@LEAF3_QFX5120-32C_LEAF> show ethernet-switching table 88:e6:xx:xx:xx:xx 14:03:27 14:03:27MAC flags (S - static MAC, D - dynamic MAC, L - locally learned, P - Persistent static 14:03:27 SE - statistics enabled, NM - non configured MAC, R - remote PE MAC, O - ovsdb MAC) 14:03:27 14:03:27 14:03:27Ethernet switching table : 4585 entries, 4585 learned 14:03:27Routing instance : default-switch 14:03:27 Vlan MAC MAC Logical SVLBNH/ Active 14:03:27 name address flags interface VENH Index source 14:03:27 VLAN52 88:e6:xx:xx:xx:xx DR esi.4019 1744 01:01:02:03:xx:xx:xx:xx:01:00 14:03:27 14:03:27{master:0}
Ideally there should be no impact to the customer's services as this issue is only cosmetic. Upgrade to these fixed releases to solve the problem.
junos:21.2R3-S5 junos:21.4R3 junos:21.4R3-S3 junos:22.1R3 junos:22.2R2 junos:22.3R1 junos:22.4R1
2024-05-28 : Article Created
2026-10-29 : Updated Article and externalized.