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

[intfsorch] Init proxy_arp variable while adding router interface. #1473

Merged
merged 1 commit into from
Oct 27, 2020
Merged

[intfsorch] Init proxy_arp variable while adding router interface. #1473

merged 1 commit into from
Oct 27, 2020

Conversation

Minkang-Tsai
Copy link
Contributor

What I did
Init proxy_arp variable while adding router interface.

Why I did it
Proxy ARP will be considered as enabled while dealing with deletion action in void IntfsOrch::doTask(Consumer &consumer) if you never enable it.

How I verified it
Add an router interface and then delete it.

Details if related

@prsunny
Copy link
Collaborator

prsunny commented Oct 22, 2020

retest vs please

@Minkang-Tsai Minkang-Tsai requested a review from prsunny October 27, 2020 02:09
@prsunny prsunny merged commit 1da3c77 into sonic-net:master Oct 27, 2020
@Minkang-Tsai Minkang-Tsai deleted the proxy_arp branch October 27, 2020 02:42
EdenGri pushed a commit to EdenGri/sonic-swss that referenced this pull request Feb 28, 2022
…rator test cases as well (sonic-net#1614)

- What I did
Originally, the method advance_version_for_expected_database was introduced (in sonic-net#1566) to handle the case the latest version in CONFIG_DB is greater than the latest version in mellanox_buffer_migrator.
Now there are other database migrators whose test cases can also encounter this situation, like port auto-negotiation (sonic-net#1568) and port-channel for LACP key (sonic-net#1473).
So I would like to make the method public, available for all database migrators.
Related database migrator test cases have been updated accordingly.

- How to verify it
Run the unit test.

Signed-off-by: Stephen Sun <stephens@nvidia.com>
EdenGri pushed a commit to EdenGri/sonic-swss that referenced this pull request Feb 28, 2022
What I did
Fix issue - sonic-net/sonic-buildimage#4009
Change the LACP key to be generated from the Port Channel name instead of always being 0.
When upgrading without warm-reboot update old port channels to use the new default.

How I did it
When adding a new port-channel add by default the key lacp_key with the value 'auto' to the port-channel table, this is done to change the port-channel LACP key to be generated from the Port Channel name instead of always being 0.

When upgrading without warm-reboot, also update old port channels to use the new default.
This is not done on warm-reboot to avoid the link from going down.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants