-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Increase LAG Ids to 1024 #10519
Increase LAG Ids to 1024 #10519
Conversation
/Azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/Azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/Azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
@ysmanman - could you check why test is failing and resolve? |
For 7800 LCs, set LAG mode to support 1024 number of 16-member system LAGs. Why I did it The SOC property changes are necessary to match #10519 which increases the number of system LAG IDs to 1024. Description for the changelog For 7800 LCs, set LAG mode to support 1024 number of 16-member system LAGs.
For 7800 LCs, set LAG mode to support 1024 number of 16-member system LAGs. Why I did it The SOC property changes are necessary to match #10519 which increases the number of system LAG IDs to 1024. Description for the changelog For 7800 LCs, set LAG mode to support 1024 number of 16-member system LAGs.
For 7800 LCs, set LAG mode to support 1024 number of 16-member system LAGs. Why I did it The SOC property changes are necessary to match sonic-net#10519 which increases the number of system LAG IDs to 1024. Description for the changelog For 7800 LCs, set LAG mode to support 1024 number of 16-member system LAGs.
Related work items: sonic-net#284, sonic-net#288, sonic-net#624, sonic-net#630, sonic-net#640, sonic-net#2164, sonic-net#2206, sonic-net#2207, sonic-net#2233, sonic-net#2234, sonic-net#2238, sonic-net#8857, sonic-net#10034, sonic-net#10519, sonic-net#10685, sonic-net#10711, sonic-net#10987, sonic-net#10990, sonic-net#11047, sonic-net#11070, sonic-net#11117, sonic-net#11186, sonic-net#11207, sonic-net#11213, sonic-net#11215, sonic-net#11220, sonic-net#11221, sonic-net#11257, sonic-net#11291, sonic-net#11298, sonic-net#11301, sonic-net#11326, sonic-net#11333, sonic-net#11335, sonic-net#11341, sonic-net#11344, sonic-net#11347, sonic-net#11359, sonic-net#11366, sonic-net#11368, sonic-net#11370, sonic-net#11372, sonic-net#11375, sonic-net#11385, sonic-net#11386, sonic-net#11394, sonic-net#11397, sonic-net#11401, sonic-net#11402, sonic-net#11403, sonic-net#11405, sonic-net#11414
/Azp Azure.sonic-buildimage |
Command 'Azure.sonic-buildimage' is not supported by Azure Pipelines. Supported commands
See additional documentation. |
/Azp Azure.sonic-buildimage |
Command 'Azure.sonic-buildimage' is not supported by Azure Pipelines. Supported commands
See additional documentation. |
/Azp Azure.sonic-buildimage |
Command 'Azure.sonic-buildimage' is not supported by Azure Pipelines. Supported commands
See additional documentation. |
/Azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/Azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/Azp run Azure.sonic-buildimage |
Commenter does not have sufficient privileges for PR 10519 in repo sonic-net/sonic-buildimage |
/Azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @arlakshm , I think we need to cherry-pick this PR into 202205. |
@arlakshm please add a MSFT ADO for the cherry-pick request |
MSFT ADO 25260643 |
Why I did it Today at most 128 LAGs are supported. This is not sufficient if there are many LAGs with just few ports. How I did it Increase LAG Ids to 1024 for DNX device.
Why I did it Today at most 128 LAGs are supported. This is not sufficient if there are many LAGs with just few ports. How I did it Increase LAG Ids to 1024 for DNX device.
Adding a note here that the reason this change was not requested for 202305 branch is because this change is already present in 202305. |
Why I did it Today at most 128 LAGs are supported. This is not sufficient if there are many LAGs with just few ports. How I did it Increase LAG Ids to 1024 for DNX device. Co-authored-by: Song Yuan <[email protected]>
Why I did it Today at most 128 LAGs are supported. This is not sufficient if there are many LAGs with just few ports. How I did it Increase LAG Ids to 1024 for DNX device.
Why I did it
Today at most 128 LAGs are supported. This is not sufficient if there are many LAGs with just few ports.
How I did it
Increase LAG Ids to 1024 for DNX device.
How to verify it
Which release branch to backport (provide reason below if selected)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)