Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

evpn-overlay peering spine-spine dci no more rendered with commit #932

See original GitHub issue

Issue Type

Bug Report
EOS Configuration rendering error
Documentation Issue Report

Summary

As soon as we use avd devel including commit #932 we are loosing the following cli configuration on our spine dci:

router bgp 65101
   <snip>
   neighbor 10.0.254.129 peer group EVPN-OVERLAY-PEERS
   neighbor 10.0.254.129 remote-as 65201
   neighbor 10.0.254.129 description spine-2a7-01.DC.MU
   neighbor 10.0.254.130 peer group EVPN-OVERLAY-PEERS
   neighbor 10.0.254.130 remote-as 65201
   neighbor 10.0.254.130 description spine-2a7-02.DC.MU

When I revert to commit #936 right before #932 the cli lines are generated again.

Thie config should be related to the following seeting in the fabric.yml:

  nodes:
    spine-1a7-01.DC.MU:
      id: 1
      evpn_route_servers: [spine-2a7-01.DC.MU, spine-2a7-02.DC.MU]

Component Name

eos_designs

Steps to reproduce

Expected results

Actual results

Issue Analytics

State:
Created 2 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

kmueller68commented, May 31, 2021

@ClausHolbechArista @carlbuchmann We have re-organized our playbooks for both fabrics to meet your changes with PR #932. Everything is working well again. Thank you very much for your support on this.

0reactions

ClausHolbechAristacommented, May 31, 2021

We have added warnings if plays are only running for some switches in the fabric.

Top Results From Across the Web

NextGen DCI with VXLAN EVPN Multi-Site Using vPC Border ...

EVPN Multi-Site architecture brings back hierarchies to overlay networks introducing external BGP (eBGP) for VXLAN BGP EVPN networks, whereas until now ...

EVPN-OVERLAY-PEERS is defined on Spines with ... - GitHub

Right now we generate EVPN_OVERLAY_PEERS peer group for spine even if we have overlay-controller defined. This should not be rendered ...

Junos® OS EVPN User Guide - Juniper Networks

Spine 1: Overlay Network Configuration | 611 ... is no longer a need to advertise MAC+IP route for each tenant ... metro peering...

EVPN & DCI lab: time for the real DCI and L2 stretch

For this reason, we can leverage the existing iBGP overlay session. Remember, spine acts as route reflector for this session.

28 – Is VxLAN with EVPN Control Plane a DCI solution for ...

VxLAN is just another encapsulation type model establishing dynamically an overlay tunnel between two end-points (VTEPs). There is nothing new ...