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

[garp_service]: Only send GARPs once at startup #3053

Closed

Conversation

theasianpianist
Copy link
Contributor

Signed-off-by: Lawrence Lee lawlee@microsoft.com

MUST wait to merge until sonic-net/sonic-buildimage#6912 and sonic-net/sonic-utilities#1465 are merged and have been propagated into the internal 202012 image.

Description of PR

Summary:
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Approach

What is the motivation for this PR?

Soon (after the linked PRs above are merged and in the internal image) constantly sending GARP requests will be unnecessary since the ARP table on the standby ToR will be restored after config reload.

How did you do it?

Remove the --interval argument when starting garp_service to make it a oneshot service.

How did you verify/test it?

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

Signed-off-by: Lawrence Lee <lawlee@microsoft.com>
@bingwang-ms
Copy link
Collaborator

We need to clear neigh on standby tor for some test cases, how can we restore it if garp is only sent one round?

@theasianpianist
Copy link
Contributor Author

@bingwang-ms that is a good point. What if we changed this to a function level fixture? We could guarantee that the neighbors are learnt at the start of each test case.

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

Successfully merging this pull request may close these issues.

2 participants