Skip to content

[Mellanox] Fix get component versions script to fetch correct asic fw#16

Open
tirupatihemanth wants to merge 2 commits intomasterfrom
fix_get_components_fw
Open

[Mellanox] Fix get component versions script to fetch correct asic fw#16
tirupatihemanth wants to merge 2 commits intomasterfrom
fix_get_components_fw

Conversation

@tirupatihemanth
Copy link
Copy Markdown
Owner

Why I did it

In systems with DPUs alongside a main Spectrum switch ASIC, running mlxfwmanager --query without specifying a device returns FW versions for all Mellanox devices. So we were inadvertently scraping the DPU firmware version instead of the main ASIC switch firmware because we always picked the first one in the output which could change. This PR ensures we always display the correct asic fw version.

How I did it

pdated get_component_versions.j2 and test_sanity_checker.py to pass the correct Spectrum ASIC device ID using asic_detect.sh -p to mlxfwmanager -d.

How to verify it

Run /usr/bin/get_component_versions.py on a smartswitch and verify that the ACTUAL FW version accurately reflects the main Spectrum ASIC version instead of the DPU's FW version from one of the DPUs.

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

  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511

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)

@dgsudharsan
Copy link
Copy Markdown
Collaborator

Can you verify this both on switch and DPU side?

Signed-off-by: Hemanth Kumar Tirupati <tirupatihemanthkumar@gmail.com>
Signed-off-by: Hemanth Kumar Tirupati <tirupatihemanthkumar@gmail.com>
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