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][202311] Adding SKU Mellanox-SN4700-O32 and Mellanox-SN4700-V64 #42

Closed
wants to merge 2 commits into from

Conversation

ayurkiv-nvda
Copy link
Owner

@ayurkiv-nvda ayurkiv-nvda commented Aug 19, 2024

Additional changes for 202311

  • On master branch, pg_profile_lookup.ini was pointed to pg_profile_lookup.ini from SN4280 as a symlink
    But SN4280 wasn't merged to 202311
    Need to use files instead of links

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. .
  • 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 default, 300m max; 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)
  • 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 default, 300m max, 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
Support for independent module added for both SKUs, so Auto-negotiation changed to NO

Work item tracking
  • Microsoft ADO (number only):

How I did it

Unlink pg_profile_lookup.ini and copy files under directory

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 and others added 2 commits August 19, 2024 20:41
…nic-net#19681)

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. .
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 default, 300m max; 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)
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 default, 300m max, 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
Support for independent module added for both SKUs, so Auto-negotiation changed to NO

Signed-off-by: Andriy Yurkiv <[email protected]>
…-SN4700-O32 and Mellanox-SN4700-V64

Signed-off-by: Andriy Yurkiv <[email protected]>
@ayurkiv-nvda ayurkiv-nvda changed the title [Mellanox][202311] Use pg_profile_lookup.ini from SN4280 for Mellanox-SN4700-O32 and Mellanox-SN4700-V64 [Mellanox][202311] Adding SKU Mellanox-SN4700-O32 and Mellanox-SN4700-V64 Aug 19, 2024
limitations under the License.
#}
{% set default_cable = '5m' %}
{% set ingress_lossless_pool_size = '51806208' %}

Choose a reason for hiding this comment

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

do we need to support dual tor in 202311 for o32 t0?

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.

2 participants