- Why I did it The capability files were incorrect in comparison to the marketing spec of the SN4410 platform. - How I did it Aligned the capability files according to the marketing spec. - How to verify it Basic manual sanity checks: 1. Check if critical docker containers were UP 2. Check if interfaces were created and were UP 3. Check if interfaces created in the syncd docker container by executing – sx_api_ports_dump.py script 4. Check the logs from the start of the switch – everything was OK 5. Verified the port breakout Signed-off-by: Vadym Hlushko <vadymh@nvidia.com> |
||
---|---|---|
.. | ||
x86_64-mlnx_lssn2700-r0 | ||
x86_64-mlnx_msn2010-r0 | ||
x86_64-mlnx_msn2100-r0 | ||
x86_64-mlnx_msn2410-r0 | ||
x86_64-mlnx_msn2700_simx-r0 | ||
x86_64-mlnx_msn2700-r0 | ||
x86_64-mlnx_msn2740-r0 | ||
x86_64-mlnx_msn3420-r0 | ||
x86_64-mlnx_msn3700_simx-r0 | ||
x86_64-mlnx_msn3700-r0 | ||
x86_64-mlnx_msn3700c-r0 | ||
x86_64-mlnx_msn3800-r0 | ||
x86_64-mlnx_msn4410-r0 | ||
x86_64-mlnx_msn4600-r0 | ||
x86_64-mlnx_msn4600c-r0 | ||
x86_64-mlnx_msn4700_simx-r0 | ||
x86_64-mlnx_msn4700-r0 | ||
x86_64-mlnx_x86-r5.0.1400 | ||
x86_64-nvidia_sn2201-r0 | ||
x86_64-nvidia_sn4800_simx-r0 | ||
x86_64-nvidia_sn4800-r0 | ||
x86_64-nvidia_sn5600_simx-r0 |