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

Enable option to activate BGP neighbors based on peer group instead of ipv4 address #3972

Open
1 task done
bdugg21 opened this issue May 8, 2024 · 2 comments
Open
1 task done
Labels
state: stale type: enhancement New feature or request

Comments

@bdugg21
Copy link

bdugg21 commented May 8, 2024

Enhancement summary

please detail your feature enhancement

Which component of AVD is impacted

eos_designs

Use case example

Need the ability to modify how a neighbor is activated. Currently IPv4 is the only option.

Describe the solution you would like

neighbor activation key with value options of ipv4 address or peer-group

Describe alternatives you have considered

eos cli gen overrides

Additional context

No response

Contributing Guide

  • I agree to follow this project's Code of Conduct
@bdugg21 bdugg21 added the type: enhancement New feature or request label May 8, 2024
@ClausHolbechArista
Copy link
Contributor

We have added this recently in #3887 (v4.8.0 should have it).

Please test it out and let me know if it works out for you.

Note that EOS does not show the address familiy configs under the VRFs for peer-groups. The config will show up in the global context, but if a VRF neighbor is associated with the peer-group, the peer-group activation will be applied in the VRF AF as well.

tenants:
  - name: mytenant
    bgp_peer_groups:
      - name: mybgppeergroup
        <...>
        address_family_ipv4:
          activate: true
    vrfs:
      - name: myvrf
        bgp_peer_groups:
          - name: myotherbgppeergroup
            <...>
            address_family_ipv6:
              activate: true

Copy link

github-actions bot commented Sep 6, 2024

This issue is stale because it has been open 90 days with no activity. The issue will be reviewed by a maintainer and may be closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state: stale type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants