Mlxfwmanager --online -u does not update to the latest published firmware (key=last_release returns an older version)

Infrastructure & Networking Adapters and Cables Firmware Tools
, ,
1

Summary

mlxfwmanager --online -u (which internally calls
mlx_fw_online_query.php with key=last_release) returns a firmware
version that is a plain GA patch release, not the officially tagged LTS
release, even though it is on the same minor branch as the LTS releases.

Steps to reproduce

  1. Query the online server (same request mlxfwmanager --online issues
    internally):
   curl -s -X POST "https://www.mellanox.com/downloads/firmware/mlx_fw_online_query.php" \
     -H "Content-Type: application/json" \
     -d '{"mode":3, "psids":"MT_0000000531", "key":"last_release"}' | jq .
  1. Compare the returned Ver.FW against the version history shown on
    NVIDIA’s Firmware Download Center for the same PSID
    ( Firmware for ConnectX®-6 Lx | NVIDIA ).

Expected result

key=last_release should return NVIDIA’s latest GA release, or clearly
document that it may return an untagged patch release rather than the
current LTS-tagged one.

Actual result

For PSID MT_0000000531 (ConnectX-6 Lx, PN MCX631102AN-ADA_Ax), the
version history on the Download Center (newest first) is:
26.49.1014
26.48.1000
26.47.3576 - 2025 LTS U3
26.47.2682 - 2025 LTS U2
26.47.1088 - 2025 LTS U1
26.47.1026 ← returned by key=last_release
26.46.3048
… etc

key=last_release returns 26.47.1026, which is five releases behind
the current latest (26.49.1014), and also behind three subsequent
LTS-tagged releases on the same 26.47 branch (U1, U2, U3). This is neither
the latest GA release nor the latest LTS release — it appears to be
whatever GA patch happened to precede the first LTS tag on that branch,
and the query does not seem to advance from there.

Questions

  1. What does key=last_release actually track? It currently returns
    26.47.1026, five releases behind the current latest (26.49.1014) and
    behind three subsequent LTS tags (U1/U2/U3) on the same branch. Is this
    expected behavior, a stale cache, or a query bug?
  2. Is there a --key value that reliably returns the latest LTS-tagged
    release (currently 26.47.3576 - 2025 LTS U3)?
  3. Is there a --key value that reliably returns the latest GA release
    (currently 26.49.1014)?
1 Like