[Mellanox]Adding SKU Mellanox-SN4700-O32 and Mellanox-SN4700-V64 (202311)

[ayurkiv-nvda]

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 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)
• 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)