[arp] Ignore intermittent failure of "ip neigh flush all"#820
Merged
liat-grozovik merged 1 commit intosonic-net:masterfrom Mar 13, 2019
wangxin:ip-neigh-flush-pr
Merged
[arp] Ignore intermittent failure of "ip neigh flush all"#820liat-grozovik merged 1 commit intosonic-net:masterfrom wangxin:ip-neigh-flush-pr
liat-grozovik merged 1 commit intosonic-net:masterfrom
wangxin:ip-neigh-flush-pr
Conversation
In ARP testing, the script needs to run "ip neigh flush all" couple of times to clean up ARP table. Occasionally flushing ARP table may fail with error "*** Flush not complete bailing out after 10 rounds" on ptf32 or ptf64 topology. The reason is that BGP peers are configured on these topologies although the PTF container does not have BGP running. From time to time, DUT will try to contact the BGP peers. ARP requests are firstly sent out. This will create some INCOMPLETE entries in ARP table for the BGP peers. If "ip neigh flush all" is executed at the same moment, the command may fail with "*** Flush not complete bailing out after 10 rounds". The fix is to simply ignore the error of "ip neigh flush all". Purpose of the "ip neigh flush all" command is to cleanup ARP entries generated by previous testing. It doesn't matter when there are ARP entries generated by other activities not flushed. Meanwhile, I changed the command to "ip -stats neigh flush all" to have more detailed output for debug in case of failure. Signed-off-by: Xin Wang <[email protected]>
liat-grozovik
approved these changes
Mar 13, 2019
yxieca
pushed a commit
that referenced
this pull request
Mar 18, 2019
In ARP testing, the script needs to run "ip neigh flush all" couple of times to clean up ARP table. Occasionally flushing ARP table may fail with error "*** Flush not complete bailing out after 10 rounds" on ptf32 or ptf64 topology. The reason is that BGP peers are configured on these topologies although the PTF container does not have BGP running. From time to time, DUT will try to contact the BGP peers. ARP requests are firstly sent out. This will create some INCOMPLETE entries in ARP table for the BGP peers. If "ip neigh flush all" is executed at the same moment, the command may fail with "*** Flush not complete bailing out after 10 rounds". The fix is to simply ignore the error of "ip neigh flush all". Purpose of the "ip neigh flush all" command is to cleanup ARP entries generated by previous testing. It doesn't matter when there are ARP entries generated by other activities not flushed. Meanwhile, I changed the command to "ip -stats neigh flush all" to have more detailed output for debug in case of failure. Signed-off-by: Xin Wang <[email protected]>
deerao02
pushed a commit
to deerao02/sonic-mgmt
that referenced
this pull request
Dec 18, 2025
…t#820) Add cache to get_ports_map. Call transceiver presence once for all ports together.
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
…onic-net#7316) - [pyext] Fix pyext/py2 library (sonic-net#820) - Added --purge of base docker image packages before installing new ones. (sonic-net#819) <--- branch point Signed-off-by: Danny Allen <[email protected]>
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.
In ARP testing, the script needs to run "ip neigh flush all" couple of
times to clean up ARP table. Occasionally flushing ARP table may fail
with error "*** Flush not complete bailing out after 10 rounds" on ptf32
or ptf64 topology.
The reason is that BGP peers are configured on these topologies although
the PTF container does not have BGP running. From time to time, DUT will
try to contact the BGP peers. ARP requests are firstly sent out. This
will create some INCOMPLETE entries in ARP table for the BGP peers. If
"ip neigh flush all" is executed at the same moment, the command may
fail with "*** Flush not complete bailing out after 10 rounds".
The fix is to simply ignore the error of "ip neigh flush all". Purpose
of the "ip neigh flush all" command is to cleanup ARP entries generated
by previous testing. It doesn't matter when there are ARP entries
generated by other activities not flushed.
Meanwhile, I changed the command to "ip -stats neigh flush all" to
have more detailed output for debug in case of failure.
Description of PR
Summary:
Fixes # (issue)
In ARP testing, the script needs to run "ip neigh flush all" couple of
times to clean up ARP table. Occasionally flushing ARP table may fail
with error "*** Flush not complete bailing out after 10 rounds" on ptf32
or ptf64 topology.
The reason is that BGP peers are configured on these topologies although
the PTF container does not have BGP running. From time to time, DUT will
try to contact the BGP peers. ARP requests are firstly sent out. This
will create some INCOMPLETE entries in ARP table for the BGP peers. If
"ip neigh flush all" is executed at the same moment, the command may
fail with "*** Flush not complete bailing out after 10 rounds".
The fix is to simply ignore the error of "ip neigh flush all". Purpose
of the "ip neigh flush all" command is to cleanup ARP entries generated
by previous testing. It doesn't matter when there are ARP entries
generated by other activities not flushed.
Meanwhile, I changed the command to "ip -stats neigh flush all" to
have more detailed output for debug in case of failure.
Type of change
Approach
How did you do it?
How did you verify/test it?
Tested on Mellanox platform.
Any platform specific information?
No
Supported testbed topology if it's a new test case?
Documentation