-
Notifications
You must be signed in to change notification settings - Fork 557
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
[teammgrd]: Create unique LACP key for port-channel #1660
[teammgrd]: Create unique LACP key for port-channel #1660
Conversation
/AzurePipelines run |
Commenter does not have sufficient privileges for PR 1660 in repo Azure/sonic-swss |
29fe875
to
33d2483
Compare
@lguohan - please keep in mind that the fix for this issue (#4009) arrive with this PR and additional PR: |
thank you. commented on 1473 pr. |
b3a3868
to
1f7a4fa
Compare
@ judyjoseph any comments on this PR? can you please explain why the recent mentioned PR is related and how you would like to move forward with this one? |
i have concerns on the sleeps in the test, code looks good to me. please add yang model as well in sonic-buildimage repo. |
1f7a4fa
to
83f5ca9
Compare
83f5ca9
to
92ed8ca
Compare
92ed8ca
to
06bfed4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, will wait for all reviewers.
@lguohan any further feedback? |
this looks like a new feature, not sure why needs backport. |
) To update the yang model to support the new key interduced in sonic-net/sonic-swss#1660
…nic-net#7297) To update the yang model to support the new key interduced in sonic-net/sonic-swss#1660
…nic-net#7297) To update the yang model to support the new key interduced in sonic-net/sonic-swss#1660
Fix issue - sonic-net/sonic-buildimage#4009 When a member port is added to port-channel, create a unique LACP key. When adding a member port to port-channel set the LACP key to a unique number. The number is extracted from the port-channel name and will be the number at the end of the port-channel name with an additional digit at the beginning in order to make sure that this number will be unique in the system. Why I did it If LACP key is not set, then the peer will not be able to distinguish the ports which are connected to different port-channels, as it will receive the LACP key as 0 for all the ports from different port-channels. How I verified it I configure a SONiC switch to have two port-channels and on a second switch, I created one port-channel for both links between the switches. On the second switch only one of the ports comes up in the PO and the other one stayed down.
…anox switches (sonic-net#1660) - What I did Enhance the way techsupport collects dumps provided by SAI and do not keep them in the filesystem once the techsupport is created. - How I did it Create a temporary directory once techsupport script is executed, gather all files SAI dumps created, add them to the tech support and remove the temporary directory and files. Remove direct call to FW trace collection as it is done now by SAI dump - How to verify it Run techsupport, verify newly created files are part of it including mlxtrace which is no longer called directly by the techsupport script.
What I did
Fix sonic-net/sonic-buildimage#4009
When a member port is added to port-channel, create a unique LACP key.
When adding a member port to port-channel set the LACP key to a unique number.
The number is extracted from the port-channel name and will be the number at the end of the port-channel name with an additional digit at the beginning in order to make sure that this number will be unique in the system.
Why I did it
If LACP key is not set, then the peer will not be able to distinguish the ports which are connected to different port-channels, as it will receive the LACP key as 0 for all the ports from different port-channels.
How I verified it
I configure a SONiC switch to have two port-channels and on a second switch, I created one port-channel for both links between the switches.
On the second switch only one of the ports comes up in the PO and the other one stayed down.
Which release branch to backport (provide reason below if selected)