Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat(eos_cli_config_gen): Support of BGP default-originate per VRF #3941

Closed
1 task done
mmaaloul opened this issue May 3, 2024 · 0 comments · Fixed by #4122
Closed
1 task done

Feat(eos_cli_config_gen): Support of BGP default-originate per VRF #3941

mmaaloul opened this issue May 3, 2024 · 0 comments · Fixed by #4122
Assignees
Labels
type: enhancement New feature or request

Comments

@mmaaloul
Copy link
Contributor

mmaaloul commented May 3, 2024

Enhancement summary

My customer is using the following feature:

https://www.arista.com/en/support/toi/eos-4-21-3f/14124-bgp-neighbor-default-originate-always

While the "default-originate" is already supported under "router bgp/peer_groups", it seems not supported to be activated per VRF:

  1. Under "router bgp/vrfs/vrf" stanza:
    We can use "eos_cli" to configure "default-route export evpn always" for example
  2. But, under "router bgp/address_family_evpn/neighbors or peer_groups" stanza, it is not possible to configure "default-route" which is compulsory.

Which component of AVD is impacted

eos_cli_config_gen

Use case example

  1. Under "router bgp/VRF":
default-route export evpn always
  1. Under "router bgp/address-family evpn":
neighbor <peer_group> default-route

Describe the solution you would like

A possible solution is to add a new Boolean field "default_route" under the elements of the following lists:

  • "router bgp/address_family_evpn/neighbors"
  • "router bgp/address_family_evpn/peer_groups"

Describe alternatives you have considered

No response

Additional context

No response

Contributing Guide

  • I agree to follow this project's Code of Conduct
@mmaaloul mmaaloul added the type: enhancement New feature or request label May 3, 2024
gmuloc added a commit that referenced this issue Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant