Closed dgonzalez85 closed 4 months ago
This is most likely caused by some unforseen combination. The RM-CONN-2-BGP
route-map is usually used on the redistribute connected
under BGP. The route-map is only applied for EVPN VTEPs, explaining why it is not being applied here.
We need to capture this condition and not generate the route-map + prefix-list for those cases.
Issue Summary
L2LS deployment, with leaves as L2 switches and Spines performing routing.
In the spines the following configuration is generated by AVD to allow the inband subnet:
However the route-map RM-CONN-2-BGP is not applied anywhere. My understanding is that it could be applied in the "redistribute attached-host" (or remove the definition and leave it unfiltered):
Which component(s) of AVD impacted
eos_designs
How do you run AVD ?
Ansible CLI (with virtual-env or native python)
Steps to reproduce