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_designs): simplify the RFC5549 logic when separate peer groups are used: #4916

Open
gmuloc opened this issue Jan 23, 2025 · 0 comments

Comments

@gmuloc
Copy link
Contributor

gmuloc commented Jan 23, 2025

          Follow up issue for this PR - simplify the RFC5549 logic when separate peer groups are used:
underlay_rfc5549 , overlay_mlag_rfc_5549 unique peer group (current implementation) separate peer group
False, False nothing to do nothing to do
False, True not supported not supported (need to add a guard)
True, False peer group actiavte ipv6 next-hop, disabled for every neighbor in every VRF can be simplified as there is no need to disable it anymore for neighbors
True, True nothing to do nothing to do

Originally posted by @gmuloc in #4881 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant