Skip to content

Define new topology t0-56-o8v48#11033

Merged
bingwang-ms merged 3 commits intosonic-net:masterfrom
bingwang-ms:topo_topo_t0-56-o8v48
Dec 21, 2023
Merged

Define new topology t0-56-o8v48#11033
bingwang-ms merged 3 commits intosonic-net:masterfrom
bingwang-ms:topo_topo_t0-56-o8v48

Conversation

@bingwang-ms
Copy link
Collaborator

Description of PR

Summary:
This PR is to define a new topology t0-56-o8v48.

Port layout:

  • 8 LAGs (400Gbs link)
  • 48 downstream ports (24 admin up and 24 admin down)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Back port request

  • 201911
  • 202012
  • 202205
  • 202305

Approach

What is the motivation for this PR?

This PR is to define a new T0 topology t0-56-o8v48.

How did you do it?

Add a new file ansible/vars/topo_t0-56-o8v48.yml

How did you verify/test it?

The topology is verified by deploying it on a physical testbed.

Any platform specific information?

No.

Supported testbed topology if it's a new test case?

Not a new test case.

Documentation

@wangxin
Copy link
Collaborator

wangxin commented Feb 1, 2024

This PR was merged before 202311 branch was created from master branch. No need to cherry-pick for 202311 branch.

mssonicbld pushed a commit to mssonicbld/sonic-mgmt that referenced this pull request Feb 1, 2024
* Define new topology t0-56-o8v48
@mssonicbld
Copy link
Collaborator

Cherry-pick PR to 202305: #11468

mssonicbld pushed a commit that referenced this pull request Feb 1, 2024
* Define new topology t0-56-o8v48
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