Damien/arista-evpn-vxlan-clab
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

BGP EVPN neighbors stuck in Active state for leaf3, leaf4, leaf7, leaf8 #5

New Issue
Closed
opened 2025-11-28 11:23:00 +00:00 by Damien · 1 comment
Damien commented 2025-11-28 11:23:00 +00:00
Owner
Copy Link

Issue

BGP EVPN neighbors on spine1 show "Active" state instead of "Established" for:

  • 10.0.250.13 (leaf3)
  • 10.0.250.14 (leaf4)
  • 10.0.250.17 (leaf7)
  • 10.0.250.18 (leaf8)

While leaf1/leaf2/leaf5/leaf6 have successful EVPN adjacencies (Established).

Root Cause

The leaf3, leaf4, leaf7, and leaf8 configurations have duplicate network advertisements in the BGP IPv4 address-family that aren't properly cleaned up:

address-family ipv4
  network 10.0.250.13/32
  network 10.0.255.12/32
  network 10.0.250.13/32      <- DUPLICATE
  network 10.0.255.12/32      <- DUPLICATE

This causes BGP parsing/state issues. The working leaves (1, 2, 5, 6) have clean single advertisements.

Fix Required

  • Remove duplicate network statements from BGP IPv4 address-family in leaf3.cfg, leaf4.cfg, leaf7.cfg, leaf8.cfg
  • Keep only one instance of each loopback network advertisement
  • Reload/reconfigure BGP on affected leaves

Expected After Fix

All 8 EVPN neighbors should reach "Established" state on both spines with matching PfxRcd/PfxAcc counts.

## Issue BGP EVPN neighbors on spine1 show "Active" state instead of "Established" for: - 10.0.250.13 (leaf3) - 10.0.250.14 (leaf4) - 10.0.250.17 (leaf7) - 10.0.250.18 (leaf8) While leaf1/leaf2/leaf5/leaf6 have successful EVPN adjacencies (Established). ## Root Cause The leaf3, leaf4, leaf7, and leaf8 configurations have duplicate network advertisements in the BGP IPv4 address-family that aren't properly cleaned up: ``` address-family ipv4 network 10.0.250.13/32 network 10.0.255.12/32 network 10.0.250.13/32 <- DUPLICATE network 10.0.255.12/32 <- DUPLICATE ``` This causes BGP parsing/state issues. The working leaves (1, 2, 5, 6) have clean single advertisements. ## Fix Required - Remove duplicate `network` statements from BGP IPv4 address-family in leaf3.cfg, leaf4.cfg, leaf7.cfg, leaf8.cfg - Keep only one instance of each loopback network advertisement - Reload/reconfigure BGP on affected leaves ## Expected After Fix All 8 EVPN neighbors should reach "Established" state on both spines with matching PfxRcd/PfxAcc counts.
Damien added reference fix-bgp-and-mlag 2025-11-28 11:33:35 +00:00
Damien commented 2025-11-28 14:50:33 +00:00
Author
Owner
Copy Link

Update: Dual-homing restored

The lab topology has been reverted from single-homed to dual-homed with LACP bonding as requested.

All 8 leaf configurations have been updated to support:

  • LACP bonding (channel-group 1 mode active)
  • Trunk mode on Port-Channel1
  • Proper VLAN tagging (40, 34, 78)
  • MLAG synchronization

The duplicate BGP network statements in leaf3, leaf4, leaf7, leaf8 still need to be cleaned up for BGP EVPN to work properly.

Next step: Redeploy lab to test dual-homed MLAG connectivity with LACP

## Update: Dual-homing restored The lab topology has been reverted from single-homed to **dual-homed with LACP bonding** as requested. All 8 leaf configurations have been updated to support: - LACP bonding (`channel-group 1 mode active`) - Trunk mode on Port-Channel1 - Proper VLAN tagging (40, 34, 78) - MLAG synchronization The duplicate BGP network statements in leaf3, leaf4, leaf7, leaf8 still need to be cleaned up for BGP EVPN to work properly. **Next step:** Redeploy lab to test dual-homed MLAG connectivity with LACP
Sign in to join this conversation.
fix-bgp-and-mlag
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Damien
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Damien/arista-evpn-vxlan-clab#5
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?