Mstresourcedump Utility - Nvidia MSTFLINT Documentation

Hide thumbs Also See for MSTFLINT:
Table of Contents

Advertisement

mstlink -d lid-<LID> -p <formula>
Formula :
1.
portnum = round_down[(Iblinkinfo_port_num + 1)*0.5]
2.
if (Iblinkinfo_port_num + 1) modulo 2 = 1 then add '/2'
3.
in case of 4X port, use only item #1 above
Example:
43 23[ ] ==( 2X 53.125 Gbps Active/ LinkUp)==> mstlink -d lid-43 -p 12
43 24[ ] ==( 2X 53.125 Gbps Active/ LinkUp)==> mstlink -d lid-43 -p 12/2
When using mstlink tool with NIC, notice that the "label_port" flag -p should not be used. To address
different ports please use different mst devices.
For example:
To address port 1 in ConnectX-4 use:
mstlink -d
41:00.0
To address port 2 use:
mstlink -d
41:00.1
Any mstlink command for switch should include the "-p" flag to address the specific
port in the switch.
When working with the NIC, if an MTUSB is used for communication with the NVIDIA
NIC, to address port 2, use mstlink -d /dev/mst/mt4115_pciconf0 --gvmi_address
<0xAddress>.

mstresourcedump Utility

The mstresourcedump tool extracts and prints data segments generated by the firmware. It is
supported in 5th generation NIC's devices. The dump output is used by NVIDIA for debug and
troubleshooting.
mstresourcedump can be used only if Python 3.x is installed. Using lower versions will result
in tool's failure.
It is important for the user to generate a bin file for debugging and troubleshooting cases
when needed by NVIDIA.
If the firmware version used is not supported, the tool will generate the following error
message:
"Error: Failed to fetch query data with exception: Failed to send Register
RESOURCE DUMP with rc: 515. Exiting...".
80

Advertisement

Table of Contents
loading

Table of Contents