BGP EVPN Neighbors - leaf3, leaf4, leaf7, leaf8 stuck in Connect state #2

Closed
opened 2025-11-28 10:51:50 +00:00 by Damien · 0 comments
Owner

Issue

Leaf3, Leaf4, Leaf7, Leaf8 have BGP EVPN neighbors stuck in Connect state (0 MsgRcvd/MsgSent).

Leaf1, Leaf2, Leaf5, Leaf6 are correctly in Established state.

Root Cause

Spine configs were missing neighbor evpn activate in the EVPN address family. This has been fixed in spine1.cfg and spine2.cfg.

Solution Applied

Updated both spine configs to include:

address-family evpn
   neighbor evpn activate

Next Steps

  1. Manually apply fix to spine1 and spine2 ✓ Done via SSH CLI
  2. Wait for leaf EVPN neighbors to establish (should happen within 30 seconds)
  3. Verify all leaves show Established state
  4. Run connectivity tests

Expected Result

All leaf EVPN neighbors should transition from Connect → Established automatically once spines have the fix applied.

## Issue Leaf3, Leaf4, Leaf7, Leaf8 have BGP EVPN neighbors stuck in **Connect** state (0 MsgRcvd/MsgSent). Leaf1, Leaf2, Leaf5, Leaf6 are correctly in **Established** state. ## Root Cause Spine configs were missing `neighbor evpn activate` in the EVPN address family. This has been fixed in spine1.cfg and spine2.cfg. ## Solution Applied Updated both spine configs to include: ``` address-family evpn neighbor evpn activate ``` ## Next Steps 1. ~~Manually apply fix to spine1 and spine2~~ ✓ Done via SSH CLI 2. Wait for leaf EVPN neighbors to establish (should happen within 30 seconds) 3. Verify all leaves show Established state 4. Run connectivity tests ## Expected Result All leaf EVPN neighbors should transition from Connect → Established automatically once spines have the fix applied.
Damien added reference fix-bgp-and-mlag 2025-11-28 11:33:14 +00:00
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Damien/arista-evpn-vxlan-clab#2