-
Notifications
You must be signed in to change notification settings - Fork 547
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
[neighsync] bug: VXLAN EVPN neighbors not in NEIGH_TABLE #3478
Open
bradh352
wants to merge
1
commit into
sonic-net:master
Choose a base branch
from
bradh352:bradh352/vxlan-evpn-neighbors
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
VXLAN EVPN learned routes are not entered into NEIGH_TABLE as per Issue sonic-net#3384. The EVPN VXLAN HLD specifically states this should be populated so it triggers an update to the SAI database: https://github.com/sonic-net/SONiC/blob/master/doc/vxlan/EVPN/EVPN_VXLAN_HLD.md#438-mac-ip-route-handling The reason it was not occurring is NOARP entries were being rejected, this patch adds an exception for externally learned neighbors. Signed-off-by: Brad House (@bradh352)
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
bradh352
changed the title
[neighsync] VXLAN EVPN neighbors not in NEIGH_TABLE
[neighsync] bug: VXLAN EVPN neighbors not in NEIGH_TABLE
Jan 21, 2025
bradh352
added a commit
to bradh352/sonic-swss
that referenced
this pull request
Jan 21, 2025
VXLAN EVPN learned routes are not entered into NEIGH_TABLE as per Issue sonic-net#3384. The EVPN VXLAN HLD specifically states this should be populated so it triggers an update to the SAI database: https://github.com/sonic-net/SONiC/blob/master/doc/vxlan/EVPN/EVPN_VXLAN_HLD.md#438-mac-ip-route-handling The reason it was not occurring is NOARP entries were being rejected, this patch adds an exception for externally learned neighbors. Signed-off-by: Brad House (@bradh352)
bradh352
added a commit
to bradh352/sonic-swss
that referenced
this pull request
Jan 22, 2025
VXLAN EVPN learned routes are not entered into NEIGH_TABLE as per Issue sonic-net#3384. The EVPN VXLAN HLD specifically states this should be populated so it triggers an update to the SAI database: https://github.com/sonic-net/SONiC/blob/master/doc/vxlan/EVPN/EVPN_VXLAN_HLD.md#438-mac-ip-route-handling The reason it was not occurring is NOARP entries were being rejected, this patch adds an exception for externally learned neighbors. Signed-off-by: Brad House (@bradh352)
github-actions bot
pushed a commit
to bradh352/sonic-swss
that referenced
this pull request
Jan 22, 2025
VXLAN EVPN learned routes are not entered into NEIGH_TABLE as per Issue sonic-net#3384. The EVPN VXLAN HLD specifically states this should be populated so it triggers an update to the SAI database: https://github.com/sonic-net/SONiC/blob/master/doc/vxlan/EVPN/EVPN_VXLAN_HLD.md#438-mac-ip-route-handling The reason it was not occurring is NOARP entries were being rejected, this patch adds an exception for externally learned neighbors. Signed-off-by: Brad House (@bradh352)
bradh352
added a commit
to bradh352/sonic-swss
that referenced
this pull request
Jan 22, 2025
VXLAN EVPN learned routes are not entered into NEIGH_TABLE as per Issue sonic-net#3384. The EVPN VXLAN HLD specifically states this should be populated so it triggers an update to the SAI database: https://github.com/sonic-net/SONiC/blob/master/doc/vxlan/EVPN/EVPN_VXLAN_HLD.md#438-mac-ip-route-handling The reason it was not occurring is NOARP entries were being rejected, this patch adds an exception for externally learned neighbors. Signed-off-by: Brad House (@bradh352)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why I did it
VXLAN EVPN learned routes are not entered into NEIGH_TABLE as per Issue #3384.
The EVPN VXLAN HLD specifically states this should be populated so it triggers an update to the SAI database:
https://github.com/sonic-net/SONiC/blob/master/doc/vxlan/EVPN/EVPN_VXLAN_HLD.md#438-mac-ip-route-handling
What I did
The reason it was not occurring is NOARP entries were being rejected, this patch adds an exception for externally learned neighbors (which have NOARP set).
How I verified it
Installed on a physical switch and observe remotely learned neighbors are present in NEIGH_TABLE
Details if related
Fixes #3384
Signed-off-by: Brad House (@bradh352)