Closed vyelpale closed 2 years ago
Currently the SVI creation for non default vrf to use different ip address is being done using custom_structured_configuration_vlan_interfaces
Could be addressed with a new mlag_ibgp_peering_ipv4_pool
under tenants.<>.vrfs.<>
to be consistent with the var naming in that context.
Enhancement summary
AVD today defaults to using mlag_peer_l3_ipv4_pool to create the bgp peering. In the vxlan EVPN environment, ibgp peering created over the SVI in a non default vrf requires the ability to use different ip address across different vrfs.
Which component of AVD is impacted
eos_designs
Use case example
VXLAN evpn deployment which is acting as aggregation for the different routes for running the overlay SDWAN solution. Although reusing the ip addressing across different vrfs should work, customer prefers to use different ip addressing for the ibgp peering vlans.
Describe the solution you would like
Describe alternatives you have considered
Nothing found yet.
Additional context
No response
Contributing Guide