[Mellanox] Adding SKU Mellanox-SN5600-C256A1

[DavidZagury]

Why I did it

Support Mellanox-SN5600-C256A1

Work item tracking

• Microsoft ADO (number only):

How I did it

Add relevant files to support the new SKU

How to verify it

Regression test

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)

[liat-grozovik]

i believe there is a general issue with master builds, once it is fixed this need to re run.
@prgeor fyi

[prgeor]

dual-TOR test failed

check_result = False
duthosts = [<MultiAsicSonicHost vlab-05>, <MultiAsicSonicHost vlab-06>]
get_mux_status = <function get_mux_status.<locals>._get_mux_status at 0x780bfc49ae50>

    def validate_check_result(check_result, duthosts, get_mux_status):
        """If check_result is False, collect some log and fail the test.
        Args:
            check_result (bool): Check result
            duthosts (list): List of duthost objects.
        """
        if not check_result:
            duthosts.shell('show muxcable config')
            duthosts.shell('show muxcable status')
            simulator_muxstatus = get_mux_status()
            if simulator_muxstatus is not None:
                logger.info('Mux status from mux simulator: {}'.format(json.dumps(simulator_muxstatus)))
            else:
                logger.error('Failed to get mux status from mux simulator')
>           pytest.fail('Toggle mux from simulator test failed')
E           Failed: Toggle mux from simulator test failed

check_result = False
duthosts   = [<MultiAsicSonicHost vlab-05>, <MultiAsicSonicHost vlab-06>]
get_mux_status = <function get_mux_status.<locals>._get_mux_status at 0x780bfc49ae50>
simulator_muxstatus = {'mbr-vms6-4-0': {'active_port': 'vlab-06-1', 'active_side': 'lower_tor', 'bridge': 'mbr-vms6-4-0', 'flap_counter': 1,...11': {'active_port': 'vlab-06-12', 'active_side': 'lower_tor', 'bridge': 'mbr-vms6-4-11', 'flap_counter': 9, ...}, ...}

common/dualtor/mux_simulator_control.py:954: Failed
=============================== warnings summary ===============================
../../../../usr/local/lib/python3.8/dist-packages/paramiko/transport.py:236
  /usr/local/lib/python3.8/dist-packages/paramiko/transport.py:236: CryptographyDeprecationWarning: Blowfish has been deprecated
    "class": algorithms.Blowfish,

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
- generated xml file: /var/src/sonic-mgmt/tests/logs/dualtor_mgmt/test_toggle_mux|||2.xml -

[r12f]

Since this one contains 1 25G port, do you mind to rename the SKU to C256X1?

[DavidZagury]

I agree, but as far as I am aware this should be C256A1 (e.g. Mellanox-SN4700-A96C8V8 )

[r12f]

hi @DavidZagury , not really, the last port is 25Gb, and it should be X not A. @yxieca can correct me, if I am wrong.

[DavidZagury]

@r12f My notes says that the speed / name map is:
10Gb - "S"
25Gb - "A"
50Gb - "D"
100Gb - "C"
200Gb - "V"
400Gb - "O"

And this matches what we see in other SKUs such as SN4700-A96C8V8.
But I don't know where to find an official answer to that.

@liat-grozovik

[r12f]

1 comment on the SKU naming to make it align with the naming convension.

[mssonicbld]

Cherry-pick PR to 202405: #20307