Skip to content

[action] [PR:8586] Defined new T2 Scaled Topology (5LC, 96 Neighbors)#8677

Merged
mssonicbld merged 1 commit intosonic-net:202205from
mssonicbld:cherry/202205/8586
Jun 21, 2023
Merged

[action] [PR:8586] Defined new T2 Scaled Topology (5LC, 96 Neighbors)#8677
mssonicbld merged 1 commit intosonic-net:202205from
mssonicbld:cherry/202205/8586

Conversation

@mssonicbld
Copy link
Collaborator

Summary:

  1. new T2 Topology with 5 Linecards (96 Neighbors),

Type of change

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

Back port request

  • 201911
  • 202012
  • 202205

Approach

What is the motivation for this PR?

Needed a new t2 topology to stress out T2 chassis.

How did you do it?

Defined a new T2 topology which uses 5 Linecards.
Total Number of T3 Nbrs: 16
Total No of T1 Nbrs: 80
1 Linecards dut0 connected to Uplink(T3 VMs)
4 Linecards dut1 - dut4 are connected to downlink (T1 VMs)

The new topology has mixture of 4 port Lags/2 Port Lags/1 Port lag for T3 Neighbors. It also has mixture of 2Port lag/1port Lag/single port link for t1 Nbrs.

How did you verify/test it?

  1. Verified that server is stable with this topo config.
  2. On Dut: verified that all BGP sessions come up and routes are learnt.
    image

@mssonicbld
Copy link
Collaborator Author

Original PR: #8586

@mssonicbld mssonicbld merged commit 3b8a733 into sonic-net:202205 Jun 21, 2023
@mssonicbld mssonicbld deleted the cherry/202205/8586 branch February 4, 2024 09:23
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.

2 participants