Added adding static route before startup interfaces#14699
Added adding static route before startup interfaces#14699bingwang-ms merged 5 commits intosonic-net:masterfrom
Conversation
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
/azp run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| duthost.shell("sudo arp -s {0} {1}".format(ip, mac)) | ||
| else: | ||
| logger.info("adding ipv6 static arp entry for ip %s on DUT" % (ip)) | ||
| duthost.shell("sudo ip -6 neigh replace {0} lladdr {1} dev Vlan{2}".format(ip, mac, DEFAULT_VLAN_ID)) |
There was a problem hiding this comment.
Where is the static neighbor removed?
There was a problem hiding this comment.
From 202205 and newer version. When testing shut down an interface, the neighbor/Arp tables will lose the static neighbor
There was a problem hiding this comment.
My concern is the statically added neighbor will be there permanently, which may impact other tests running after test_fgnhg. Suggest adding a cleanup to remove the statically programmed neigh
There was a problem hiding this comment.
Neighbor entries will be flushed when reloading config after tests.
There was a problem hiding this comment.
i thought we fixed it by sonic-net/sonic-swss#2469
There was a problem hiding this comment.
i thought we fixed it by sonic-net/sonic-swss#2469
That PR is not fixing the issue we have on this test.
* added static routes before interface startup * fixed ipv6 from add to replace * address comments * fix pre-commit issue
* added static routes before interface startup * fixed ipv6 from add to replace * address comments * fix pre-commit issue
|
Cherry-pick PR to 202305: #14868 |
* added static routes before interface startup * fixed ipv6 from add to replace * address comments * fix pre-commit issue
* added static routes before interface startup * fixed ipv6 from add to replace * address comments * fix pre-commit issue
|
Cherry-pick PR to 202405: #14869 |
|
Cherry-pick PR to 202311: #14870 |
* added static routes before interface startup * fixed ipv6 from add to replace * address comments * fix pre-commit issue
* added static routes before interface startup * fixed ipv6 from add to replace * address comments * fix pre-commit issue
* added static routes before interface startup * fixed ipv6 from add to replace * address comments * fix pre-commit issue
* added static routes before interface startup * fixed ipv6 from add to replace * address comments * fix pre-commit issue
* added static routes before interface startup * fixed ipv6 from add to replace * address comments * fix pre-commit issue
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
There are new arp and ndp behaviors when shutdown the interfaces:
How did you do it?
We changed and fixed the way of previous fixing to match the new arp and ndp behaviors when shutdown the interfaces:
#14251
We added adding static route before startup interfaces when running testing.
How did you verify/test it?
Tested the script
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation