New T0 LAG topo with 8 uplinks (2 ports per LAG)#7673
New T0 LAG topo with 8 uplinks (2 ports per LAG)#7673developfast merged 2 commits intosonic-net:masterfrom
Conversation
|
The pre-commit check detected issues in the files touched by this pull request. For old issues, it is not mandatory to fix them because they were not caused by this change. It is unfair to blame Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
|
@developfast , Please cleanup the errors in the pre-commit check before merge |
* added t0 lag topo filwith 8 LAG uplinks and eos leaf template
* added t0 lag topo filwith 8 LAG uplinks and eos leaf template
* added t0 lag topo filwith 8 LAG uplinks and eos leaf template
* added t0 lag topo filwith 8 LAG uplinks and eos leaf template
* added t0 lag topo filwith 8 LAG uplinks and eos leaf template
Description of PR
Summary: New T0 LAG topo (2 links per LAG) template with 8 up links (LAGs).
Type of change
Back port request
Approach
What is the motivation for this PR?
We need to deploy a new T0 LAG topology with 8 up links (LAGs) in the lab - 2 ports per LAG.
How did you do it?
Created a new T0 topo yml file, as well as a leaf template for the 8 EOS uplinks.
How did you verify/test it?
Ran add-topo successfully on a Mellanox SN2700 using ceos, and all 8 uplinks come up with bgp connections paired successfully.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation