In EVPN multihoming (ESI-LAG) deployments, enabling Spanning Tree Protocol (RSTP) on access switch uplinks toward the EVPN fabric can cause intermittent connectivity, MAC instability, and traffic blackholing.
This article explains the symptoms, root cause, verification steps, and resolution.
Environment
An EX access switch was dual-homed to QFX EVPN core switches using ESI-LAG. Despite correct EVPN and LACP configuration, the network experienced intermittent connectivity issues.
user@access-switch> show spanning-tree interface
Interface State Role
user@access-switch> show spanning-tree statistics interface
Interface BPDUs Sent BPDUs Received
ae0 18000+ 0
Show more lines
Interpretation:
Observed during troubleshooting:
This ruled out:
A control-plane conflict between:
Since:
The EX switch:
This results in:
set protocols rstp interface ae0 disable
commit
(Optional – recommended if physical members are configured individually):
set protocols rstp interface xe-0/0/0 disable
set protocols rstp interface xe-1/0/0 disable
Best Practice for EVPN Multihoming
Do NOT enable STP on:
This issue was caused by RSTP running on an uplink toward an EVPN multihoming fabric, creating a loop-prevention conflict between STP and EVPN.
Disabling STP on the uplink resolved:
https://www.juniper.net/documentation/us/en/software/nce/evpn-lag-multihoming-guide/topics/concept/evpn-lag-guide-introduction.htmlhttps://www.juniper.net/documentation/us/en/software/junos/evpn/topics/topic-map/easy-evpn-lag-config-script.htmlhttps://www.juniper.net/documentation/us/en/software/nce/evpn-lag-multihoming-guide/topics/task/evpn-lag-guide-configuration-best-practices.htmlhttps://www.juniper.net/documentation/us/en/software/nce/evpn-lag-multihoming-guide/topics/task/evpn-lag-guide-esi-types-lacp.html