Skip to content
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

[Mellanox]Adding SKU Mellanox-SN4700-O32 and Mellanox-SN4700-V64 | internal | master #40

Closed
wants to merge 3 commits into from

Conversation

ayurkiv-nvda
Copy link
Owner

@ayurkiv-nvda ayurkiv-nvda commented Jul 2, 2024

Why I did it

A new SKUs for MSN4700 Platform: Mellanox-SN4700-O32 and Mellanox-SN4700-V64

Requirements for Mellanox-SN4700-O32:

  • 8 x 400Gbps uplink to T2 switch (O13 to O20)
  • 24 x 400Gbps downlinks to T0 switch (O1-O12, O21-O32)
  • Breakout mode No breakout mode. All ports working in 400Gb mode. .
  • Auto-negotiation : Yes
  • FEC mode: RS
  • Type of transceiver: 400Gb Optical.
  • warm boot should be supported “No for T1 role”
  • VxLAN source port range set N/A
  • Static Policy Based Hashing supported N/A
  • Cable length “T0-T1 40m; T1-T2 2000m”
  • Tradition buffer model is must “Yes”
  • Shared headroom should be supported “Yes”
  • Over-subscription ratio: “2”.

Requirements for Mellanox-SN4700-V64

  • 16 x 200Gbps uplink to T1 switch (V-25&V26 to V-39&40)
  • 48 x 200Gbps downlinks to servers (Left panel downlink ports: V-1&2 to V-23&24; Right panel downlink ports: V-41&42 to V-63&64)
  • Breakout mode split from 400Gbps ports (2x200)
  • Auto-negotiation : Yes
  • FEC mode: RS
  • Type of transceiver: 200Gb AOC between T0 and T1; 200Gb DAC between T0 and host.
  • warm boot should be supported “Yes for T0 role”
  • VxLAN source port range set N/A
  • Static Policy Based Hashing supported N/A
  • Cable length “T0-T1 40m, T0-Server 5m”
  • Tradition buffer model is must “Yes”
  • Shared headroom should be supported “Yes”
  • Over-subscription ratio: “2”.

Additional Details:

  • QoS configs for Mellanox-SN4700-V64 updated in order to fulfill Dual-ToR buffer (+DSCP remapping) requirements
Work item tracking
  • Microsoft ADO (number only):

How I did it

How to verify it

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211
  • 202305

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

@ayurkiv-nvda ayurkiv-nvda force-pushed the 4700_add_sku_V64_O32_forked branch 2 times, most recently from d0f6c24 to 7380c05 Compare July 2, 2024 22:06
@@ -0,0 +1 @@
../ACS-MSN4700/sai_4700.xml

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we get from SAI team a xml file with 64 ports?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

@stephenxs
Copy link

in the description 48 x 400Gbps downlinks to servers (Left panel downlink ports: V-1&2 to V-23&24; Right panel downlink ports: V-41&42 to V-63&64) typo? 48 * 200G downlinks?

@ayurkiv-nvda ayurkiv-nvda force-pushed the 4700_add_sku_V64_O32_forked branch 2 times, most recently from c8157f4 to 2786258 Compare July 12, 2024 12:29
Signed-off-by: Andriy Yurkiv <ayurkiv@nvidia.com>
Signed-off-by: Andriy Yurkiv <ayurkiv@nvidia.com>
@ayurkiv-nvda
Copy link
Owner Author

…O32 and Mellanox-SN4700-V64

Signed-off-by: Andriy Yurkiv <ayurkiv@nvidia.com>
@ayurkiv-nvda ayurkiv-nvda changed the title [Mellanox]Adding SKU Mellanox-SN4700-O32 and Mellanox-SN4700-V64 [Mellanox]Adding SKU Mellanox-SN4700-O32 and Mellanox-SN4700-V64 | internal | master Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants