)

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.