[bgp_fact]Add ip neighbor(arp/nd) displaying#951
Merged
qiluo-msft merged 1 commit intosonic-net:masterfrom Jun 25, 2019
stephenxs:bgp-show-ipneigh
Merged
[bgp_fact]Add ip neighbor(arp/nd) displaying#951qiluo-msft merged 1 commit intosonic-net:masterfrom stephenxs:bgp-show-ipneigh
qiluo-msft merged 1 commit intosonic-net:masterfrom
stephenxs:bgp-show-ipneigh
Conversation
…' state Recently bgp test has failed due to non-established neighbor state frequently. We highly suspect it is due to some topo deployment issue which causes DUT unable to learn arp/nd of its bgp neighbor. By displaying ip neigh info we can easily distinguish this reason from others thus saving effort of diagnosing.
qiluo-msft
approved these changes
Jun 25, 2019
auspham
pushed a commit
to auspham/sonic-mgmt
that referenced
this pull request
Feb 3, 2026
…c-net#951) PR: sonic-net#19074 is missing backport to msft-202503
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description of PR
Summary:
Add ip neighbor(arp/nd) displaying prior to asserting BGP neighbor state.
Type of change
Approach
Recently bgp test has failed due to non-established neighbor state frequently.
We highly suspect it is due to some topo deployment issue which causes DUT unable to learn arp/nd of its bgp neighbor.
By displaying ip neigh info we can easily distinguish this reason from others thus saving effort of diagnosing.
How did you do it?
register the output of "ip neigh show" to ip_neighbors and display it via "debug".
How did you verify/test it?
Run bgp_fact test on t1.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation
Signed-off-by: Stephen Sun stephens@mellanox.com