MFT Known Issues

-

4294588

Description: In some cases, BlueField-3 users might experience a misleading error message following mlxfwreset command with sync 1 and method 1 (hot reset), even though the reset was completed successfully.

The error message is: "-E- The PCI link is still up even after the expected time (360.0) seconds has passed. Exiting the process."

4258362

4129306

4089179

Workaround: To get the Power Current values, use mlxreg with PDDR register indexes:

page_select=3, module_info_ext=1, local_port=<local_port> and read rx_power_lane<lane_num>/tx_power_lane<lane_num> to get the data for each lane.

For example:

            

            
mlxreg -d /dev/mst/hgx-isr1-020:23108,@dev@mst@mt41692_pciconf1 --get --reg_name PDDR --indexes "port_type=0,plane_ind=0,lp_msb=0,pnat=0,local_port=1,page_select=3,group_opcode=0,tracer_mode=0,pre_trigger_buff_mode=0,trigger_cond_fsm=0,trigger_cond_state_or_event=0,trigger_cond_state_event_val=0,pport=0,fsm_mask=0,isr_access_enums=0,tracer_sel=0" --op "module_info_ext=1"
        

3262855

3926386

3886315

3872303

Description: Running a command triggers the following error message:

/lib/libgcc_s.so.1: version GCC_4.5.0 required by /usr/local/lib/gcc12/libstdc++.so.6 not found

Workaround: Run the following command:

export LD_LIBRARY_PATH=/usr/local/lib/gcc12:$LD_LIBRARY_PATH

3549141

Description: mlxfwreset does not work on mlnx-os/sonic/cumulus.

Description: When entering link speed values, you can specify a single value (i.e "HDR") or a list of values separated by commas (i.e "HDR, FDR, SDE"). In the current MFTshell version, the autocomplete feature suggesting possible values, only works for the first value in a list of values separated by commas.

Additionally, the autocompletion list includes all possible speeds. Some of them may not be supported by the device. Once the command is fired, you will be notified in case the selected speed is not supported.

Affected shell commands are:

port speed

port autonegotiation on speed

port autonegotiation off speed

Any inconvenience caused by these limitations will be addressed in future MFTshell updates.

Workaround: When entering a link speed, you may press the key first. This will provide you with all possible values. You can then select the desired link speed value, copy and paste it into the command prompt, and type a comma (,) to select the next speed. Repeat the process to form a list of all desired link speed values separated by commas.

Once the command is fired, the underlying MFT tool will inform you if the selected speed is not supported by the device.

In addition, the helpcontext for the affected shell commands includes detailed explanations of the available options.

Description: Some firmware scratchpad registers have been moved to a different location. Therefore, if you use your own utility to dump mstdumps, you must update your CSV file with the latest CSV, CSV2 files that are included in the MFT package.

Otherwise, the mstdumps device will not retrieve the firmware version, and the FAEs will not be able to use NVIDIA internal tools to debug the error.

2787479

2823492

2715716

2752916

2838222

2703663

2670833

2484780

Workaround: To work with the new speeds specify the number of lanes as shown below:

• 100G_1X/200G_2X/400G_4X/800G_8X for NDR speeds
• 50G_1X/100G_2X/200G_4X/400G_4X for HDR speeds

2392334

Description: Using the MFT with the --with-pcap option to install stedump utility requires the following third-party dependencies:

• Libraries and header files for the libpcap library
• Libraries and header files for Python development library
• Package Installer for Python (PIP) available

Workaround: To install the third-party dependencies, perform the following:

1. Install libpcap-devel or libpcap-dev on Debian-based distributions.
2. Install python3-devel or python3-dev on Debian-based distributions.
3. Bootstrap the PIP installer in one of the following ways:

• On Python 3.4 or newer bootstrap it from the standard library by running the "python -m ensurepip" command.
• Install PIP with Linux Package Manager, for more details see: https://packaging.python.org/guides/installing-using-linux-tools/

2376425

2208845/2099263

-

Workaround: To avoid this issue, perform one of the following options:

• Use OpenSM (with or without -o)
• Use only active ports

2234589

2167841

2149437

1780276

2001890

1923665 / 1939791