Skip to content

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

Closed
theasianpianist wants to merge 1 commit intosonic-net:masterfrom
theasianpianist:garp-service-oneshot
Closed

[garp_service]: Only send GARPs once at startup#3053
theasianpianist wants to merge 1 commit intosonic-net:masterfrom
theasianpianist:garp-service-oneshot

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>
@theasianpianist theasianpianist requested review from a team, prsunny and tahmed-dev February 27, 2021 01:31
@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