MFT release notes - Mellanox

Mellanox Technologieswww.mellanox.com

Mellanox Firmware Tools (MFT)Release Notes

Rev 4.5.0

Mellanox Technologies350 Oakmead Parkway Suite 100Sunnyvale , CA 94085U.S.A.www.mellanox.comTel: (408) 970-3400Fax: (408) 970-3403

© Copyright 2016. Mellanox Technologies Ltd . All Rights Reserved .

Mellanox®, Mellanox logo, Accelio®, BridgeX®, CloudX logo, CompustorX®, Connect -IB®, ConnectX®, CoolBox® , CORE-Direct® , EZchip®, EZchip logo, EZappliance®, EZdesign® , EZdriver®, EZsystem®, GPUDirect®, InfiniHost®, InfiniBridge®, InfiniScale®, Kotura®, Kotura logo, Mellanox CloudRack® , Mellanox CloudXMellanox® , Mellanox Federal Systems®, Mellanox HostDirect® , Mellanox Multi-Host®, Mellanox Open Ethernet®, Mellanox OpenCloud® , Mellanox OpenCloud Logo® , Mellanox PeerDirect® , Mellanox ScalableHPC® , Mellanox StorageX®, Mellanox TuneX®, Mellanox Connect Accelerate Outperform logo , Mellanox Virtual Modular Switch®, MetroDX®, MetroX®, MLNX-OS®, NP-1c®, NP-2®, NP-3®, Open Ethernet logo, PhyX®, PlatformX®, PSIPHY®, SiPhy®, StoreX®, SwitchX®, Tilera®, Tilera logo, TestX®, TuneX®, The Generation of Open Ethernet logo, UFM®, Unbreakable Link® , Virtual Protocol Interconnect®, Voltaire® and Voltaire logo are registered trademarks of Mellanox Technologies , Ltd.

All other trademarks are property of their respective owners .

For the most updated list of Mellanox trademarks, visit http://www.mellanox.com/page/trademarks

NOTE:THIS HARDWARE, SOFTWARE OR TEST SUITE PRODUCT (“PRODUCT(S)”) AND ITS RELATED DOCUMENTATION ARE PROVIDED BY MELLANOX TECHNOLOGIES “AS-IS” WITH ALL FAULTS OF ANY KIND AND SOLELY FOR THE PURPOSE OF AIDING THE CUSTOMER IN TESTING APPLICATIONS THAT USE THE PRODUCTS IN DESIGNATED SOLUTIONS. THE CUSTOMER'S MANUFACTURING TEST ENVIRONMENT HAS NOT MET THE STANDARDS SET BY MELLANOX TECHNOLOGIES TO FULLY QUALIFY THE PRODUCT(S) AND/OR THE SYSTEM USING IT. THEREFORE, MELLANOX TECHNOLOGIES CANNOT AND DOES NOT GUARANTEE OR WARRANT THAT THE PRODUCTS WILL OPERATE WITH THE HIGHEST QUALITY. ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT ARE DISCLAIMED. IN NO EVENT SHALL MELLANOX BE LIABLE TO CUSTOMER OR ANY THIRD PARTIES FOR ANY DIRECT, INDIRECT, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING, BUT NOT LIMITED TO, PAYMENT FOR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY FROM THE USE OF THE PRODUCT(S) AND RELATED DOCUMENTATION EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Rev 4.5.0Document Number: 2Mellanox Technologies

Rev 4.5.0 3Mellanox Technologies

Table of Contents

Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release Update History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Chapter 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.1 Package Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2 Software Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.3 Supported Operating Systems and Platforms . . . . . . . . . . . . . . . . . . . . . . . 91.4 Supported Flash Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.5 Supported Mellanox ICs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 2 Changes and New Features in Rev 4.5.0. . . . . . . . . . . . . . . . . . . . . 13Chapter 3 Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Chapter 4 Bug Fixes History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Chapter 5 History of Changes and New Features . . . . . . . . . . . . . . . . . . . . . . 37


List of Tables

Table 1: Release Update History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Table 2: Mellanox Firmware Tools (MFT) Available Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Table 3: MFT Software Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Table 4: Supported Operating Systems and Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Table 5: Supported Flash Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Table 6: Mellanox IC Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Table 7: Changes and New Features in Rev 4.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Table 8: Known Issues and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Table 9: Bug Fixes History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Table 10: History of Changes and New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37


Release Update HistoryTable 1 - Release Update History

Release Date Description

Rev 4.5.0 December 11, 2016 Added ESXi 6.5 to the Table 4, “Supported Operating Systems and Platforms,” on page 9

September 30, 2016 Initial release of this MFT version

Overview


1 OverviewThese are the release notes for Rev 4.5.0 of the Mellanox Firmware Tools (MFT).

This release supports the following operating systems: Linux, Windows, VMware ESXi and FreeBSD. Please see the supported platform table for further details.

The tools functionality is identical in all operating systems unless otherwise noted.

1.1 Package ToolsThe following is a list of the available tools in the package, together with a brief description of each tool. The tools apply to single switch systems or adapter cards. The MFT tools do not pro-vide cluster wide functionality.Table 2 - Mellanox Firmware Tools (MFT) Available Tools (Sheet 1 of 3)

Category Tool DescriptionOperating

System

MST Service mst Starts/stops the register access driver (Linux and VMware ESXi only) Lists the available mst devices

All

Firmware Update and Configuration

mlxburn This tool provides the following functions:• Generating a standard or customized Mellanox firm-

ware image for burning in .bin format• Burning an image to the Flash attached to a Mellanox

HCA or switch device• Querying the firmware version loaded on a Mellanox

device.• Displaying the Vital Product Data (VPD) of a Mella-

nox network adapter

All

flint This tool burns a firmware binary image or an expansion ROM image to the Flash of a Mellanox network adapter/bridge/switch device. It includes query functions to the burnt firmware image and to the binary image file.

All

mlxfwmanager The mlxfwmanager is a Mellanox firmware update and query utility. It provides a simple 'single click' firmware update functionality.Note: The same tool with embedded firmware binaries is released separately and is named mlxup.

All

mlxconfig Allows the user to change some of the device configura-tions without having to create and burn a new firmware.

All

mlxphyburn A tool for burning externally managed PHY Linux

mlx_fpga A tool for burning and debugging Mellanox devices with FPGA. It allows the user to burn their own hardware code on an FPGA integrated with Mellanox HCA board. It also provides the user with read/write registers in the QDR memory of the FPGA.

Linux

Rev 4.5.07 Mellanox Technologies

Firmware Update and Configuration

cpld_update A tool for programing on board CPLDs for Mellanox devices for the OEM packages only.

Linux

Debug and Diagnostics Utilities

itrace Extracts and prints trace messages generated by the firm-ware of a ConnectX-3 adapter cards.

All

fwtrace Extracts and prints trace messages generated by the firm-ware of 5th generation devices

LinuxWindowsFreeBSD

mlxtrace Dumps trace messages generated by the device hardware. All

mlxdump Dumps device internal configuration registers. The dump file can be used by Mellanox Support for hardware trou-bleshooting.

All

mlxmcg Displays the current multicast groups and flow steering rules configured in the device. Target users: Developers of Flow Steering aware applica-tions.

All

wqdump Dumps the current QP contexts and Work Queues of a ConnectX®/Connect-IB™/ConnectX-4® family network adapter

All

mcra Reads/writes a single word from/to a device configuration register space

All

i2c Generates an i2c transaction using an mtusb usb to i2c adapter or using the device internal i2c compatible master

All

mlxi2c Scans the i2c busRoutes the i2c bus of an externally managed InfiniscaleIV/SwitchX system to connect to the switch silicon.

All

mget_temp Reads the hardware temperature from Mellanox Technolo-gies devices internal sensors (5th generation family devices), and prints the reading in Celsius degrees.

All

pckt_drop Corrupts the next transmitted packet from a ConnectX®, Connect-IB™ and ConnectX-4® family adapter port.

All

mlxuptime Prints Mellanox devices' up time and measured/configured core clock frequency (at Beta level)

All

mlxfwreset Load Firmware after firmware update on ISFU capable devices.(5th generation devices)

LinuxWindowsFreeBSD

mlxmdio Used to read/write MDIO registers (Clause 45) on boards with externally managed PHY

All

mlxreg This tool exposes supported access registers, and allows users to obtain information regarding the registers fields and attributes, and to set and get data with specific register.

All

Table 2 - Mellanox Firmware Tools (MFT) Available Tools (Sheet 2 of 3)


System

Overview


Detailed installation instructions along with complete descriptions of the various tools in the package can be found in the Mellanox Firmware Tools User’s Manual.

1.2 Software Dependencies

Debug and Diagnostics Utilities

mlxcables This tool reads/writes Mellanox cable registers and queries the cables info

Linux Windows FreeBSD

Table 3 - MFT Software Dependencies

Software Package Required Version

Linux

Kernel sources Machine’s kernel version

OFED / MLNX_OFED 1, 2

1. OFED can be downloaded from http://www.openfabrics.org. Note that installing OFED is not required if you wish to install MFT without In-Band capabilities.

2. For the ‘mst ib add’ command to run, one of the OFED packages “ibutils” or “ibutils2” or “infiniband-diags” should be installed and available in the PATH. (For details on OFED installation, visit http://www.mella-nox.com and under OFED.)

1.5.0 or higher

Perl 5.6 or later

Python3

3. Required for the mlxmcg tool only.

2.6 and above

lsusb4

4. Required for the mtusb device usage.

rpmbuild

xz5

5. For creating UPMF (update package for Mellanox firmware)

Windows

Mellanox WinOF VPI6

6. WinOF is required only for In-Band access. The package can be downloaded from www.mellanox.com > Products > Software >InfiniBand /VPI Drivers >Windows SW Drivers.

3.0.0 and later

VMware ESXi

Python 2.6 and above

Table 2 - Mellanox Firmware Tools (MFT) Available Tools (Sheet 3 of 3)


System


1.3 Supported Operating Systems and PlatformsMFT is supported on the following platforms:.Table 4 - Supported Operating Systems and Platforms

OS Arch

Windows 7 x86_64

Windows 8.1 x86_64

Windows 10 x86_64

Windows Server 2008 R2 x86_64

Windows Server 2012 x86_64

Windows Server 2012 R2 x86_64

Windows Server 2016 Technical Preview1 x86_64

WinPE 3.0 x86/x86_64

WinPE 4.0 x86/x86_64

WinPE 5.0 x86/x86_64

WinPE 5.1 x86/x86_64

VMware ESXi 5.5 Native x86_64

VMware ESXi 5.5 VMK Linux x86_64


VMware ESXi 6.0 VMK Linux x86_64


FreeBSD 11.0-CURRENT amd64

FreeBSD 10.2-STABLE amd64

FreeBSD 9.1 amd64

RHEL6.2 x86_64

RHEL6.3 x86_64

RHEL6.5 x86_64

RHEL6.6 x86_64

RHEL6.6 PPC64

RHEL6.7 x86_64/ PPC64

RHEL6.8 x86_64/ PPC64

RHEL7.0 x86_64/ PPC64

RHEL7.1 x86_64/PPC64/ PPC64LE [Power8]

RHEL7.2 x86_64/ PPC64/ PPC64LE [Power8]/ARM

RHEL7.3 x86_64/PPC64/ PPC64LE [Power8]

Debian 7.6 x86_64

Debian 8.0 x86_64

Overview


Debian 8.1 x86_64

Debian 8.2 x86_64

Debian 8.3 x86_64

Fedora 19 x86_64

Fedora 20 x86_64

Fedora 21 x86_64/ PPC64LE [Power 8]

Fedora 22 PPC64LE [Power8]

Fedora 23 x86_64/ PPC64 [Power8]/ PPC64LE [Power8]

Fedora 24 x86_64

GAIA R77.30 x86_64

GAIA R80 x86_64

OEL 6.5 x86_64

OEL 6.6 x86_64

OEL 6.7 x86_64

OEL 6.8 x86_64

OEL 7.1 x86_64

Sles10 SP3 x86_64

Sles11 SP1 x86_64

Sles11 SP2 x86_64

Sles11 SP3 x86_64/ PPC64 [Power 7]

Sles11 SP4 x86_64/ PPC64

Sles12 x86_64/ PPC64LE [Power 8]

Sles12SP1 x86_64/ PPC64LE

Sles12SP2 x86_64/ PPC64LE

XenServer6.5 x86_64

XenServer7.0 x86_64

WindRiver6.0 x86_64

XenServer4.2 x86_64

PowerKVM3.1.x PPC64LE

Ubuntu 12.04.4 x86_64

Ubuntu 14.04 x86_64/ PPC64LE [Power 8]

Ubuntu 14.10 x86_64/ PPC64LE [Power8]


Ubuntu 15.10 x86_64/ PPC64LE [Power8]

Table 4 - Supported Operating Systems and Platforms

OS Arch



Ubuntu 16.10 Beta PPC64LE [Power 8]

Kernel.org 3.10.28 x86_64

Kernel.org 3.16 x86_64












1. Windows Server 2016 Technical Preview offers a new installation option: Nano Server.

Table 4 - Supported Operating Systems and Platforms

OS Arch

Overview


1.4 Supported Flash TypesMFT supports the following Flash types.

1.5 Supported Mellanox ICsWith respect to MFT, Mellanox IC devices are divided into two groups: Group I and Group II (4th generation and 5th generation, respectively). The ICs are listed in the following table:

Table 5 - Supported Flash Types

Vendor Flash Family Tested P/N

Micron M25Pxx M25P16

M25PXxx M25PX16

N25Qxxx N25Q032

Winbond W25QxxBV W25Q32BV

Spansion S25FL11xx S25FL116K

Atmel AT25DFxxx AT25DF161

Table 6 - Mellanox IC Devices

IC Group IC Device

Group I/4th Generation • ConnectX®-3• ConnectX®-3 Pro• SwitchX®• SwitchX®-2

Group II/5th Generation • Connect-IB®• Switch-IB™• Switch-IB™ 2• Spectrum™• ConnectX®-4• ConnectX®-4 Lx


2 Changes and New Features in Rev 4.5.0

For further information, please refer to the MFT User Manual.

Table 7 - Changes and New Features in Rev 4.5.0

Component/ Tool

DescriptionOperating

System

General Added support for Innova IPsec 4 Lx EN /Innova Flex 4 Lx EN Linux

MFT package size has been reduced in Linux by separating the architec-ture specific RPMs, and in ESXi, by moving relevant tools to the OEM package.

Linux / ESXi

Added support for Windows Server 2016: Nano Server. Nano Server is a remotely administered server operating system optimized for private clouds and datacenters.

Windows

mlxcables Enhanced cable query capabilities. Added the additional registers below for debug purposes when running the query (-q) flag: • device technology• identifier• wavelength/attenuation• speed/compliance

All

Added a new query to read thresholds and monitor the cable's properties: • Temperature• Voltage• RX/TX powers• TX Bias

All

Added a new RAW format for printing the data of the cable’s pages using the “--raw/--format raw” flags.

All

mlxconfig Enabled mlxconfig to work with a database that describes the meta data of the TLVs configuration of fifth generation devices.

All

Added the following configuration TLVs to mlxconfig:• MPFS• KEEP LINK UP• SW OFFLOAD CONF

All

mlxreg Added support for PPTT, PPRT and PPAOS access registers in switches. All

flint Added support for viewing and changing OEMs’ device flash parameters using an IB device when using flint.

All

Known Issues


3 Known IssuesThe following table provides a list of known issues and limitations in regards to this release of the Mellanox Firmware Tools.Table 8 - Known Issues and Limitations (Sheet 1 of 7)

Internal Ref.

Issue

207320 Description: MFT tools that run in parallel on the same device may interrupt one another, and may cause the device to be in an undefined state.

WA: Avoid running more than one MFT tool at a time with the same device

Keywords: General

374188 Description: The MFT driver is not a native VMware driver, thus it can not take ownership of the PCI device in livefish mode.

WA: N/A

Keywords: General

374188/374039

Description: The MFT driver is not a native VMware driver, thus it can access the Mella-nox PCI device only after the MLNX-OFED ESXi driver marks it as accessible by vmkli-unx drivers.

WA: Install and load MLNXOFED ESXi driver (which is part of inbox drivers in ESXi 5.5 and newer)

Keywords: General

362100/366285/366286

Description: MFT does not support MTUSB devices nor remote ETH and IB devices in FreeBSD and VMware ESXi.

WA: N/A

Keywords: General

592673 Description: PCI access in PowerPC machines is up to 10 times slower than other plat-forms, therefore, there are performance issues in all MFT tools running on PowerPC machines.

WA: N/A

Keywords: General

587965 Description: Running MFT tools on ConnectX-4/ConnectX-4 Lx on a Windows machine with PCI Gen1 or Gen2 causes machine to hang when Network adapted is disabled.

For Example:Running mlxfwreset on ConnectX-4/ConnectX-4 Lx on the aforementioned server causes the machine to hang since disabling the network adapter is a part of the reset flow.

WA: Enabled the network adapter before using any of the tools. For loading the firmware, reboot the server.

Keywords: General


607508 Description: Wrong localization settings in the operating system cause some tools to fail with error: locale::facet::_S_create_c_locale name not valid

WA: Run: export LC_ALL=C

Keywords: General

676412 Description: Aggressive killing of a tool that is locking the vendor specific semaphore (in ConnectX-4/ConnectX-4 Lx devices) will leave the semaphore locked, and any tool will get stuck waiting for semaphore.

WA: Run: mcra -c <pci device>

Keywords: General

576287 Description: When burning firmware with old MFT tools, the firmware version compari-son might not work correctly and might return a prompt that the old firmware is newer. This is due to changes in firmware version format.

WA: When prompted, press "y" to force update, or add the following flag to the command line:flint: -y|--yesmlxburn: -forcemlxfwmanager: -f|--force

Keywords: Firmware Burning Tools

- Description: Firmware burn will fail due to invalid/old timestamp on ConnectX-4/Con-nectX-4 Lx devices running these firmware versions: 12.14.0060/14.14.0060, or 12.14.0074/14.14.0075

WA: Use MFT v4.1.0 to upgrade/downgrade the firmware version.


692397 Description: When burning a new firmware image that does not contain Expansion ROM on a flash that contains FW and Expansion ROM, the burning tool will save the Expansion ROM in the flash.

WA: This issue can be avoided by:1. Removing the ROM from the flash before the FW update process by running the following flint command:

flint -d <dev> --allow_rom_change drom2. Adding the

--use_image_rom flag to the flint FW update command


669272 Description: mlxfwmanager self-extractor tool will not work properly in ESXi machines if there is no mlx driver or MST installed on the machine.

WA: Install the driver and the mst that matches the machine, then run the tool.

Keywords: mlxfwmanager

Table 8 - Known Issues and Limitations (Sheet 2 of 7)

Internal Ref.

Issue

Known Issues


534010/647911

Description: mlxconfig allows setting port parameters for both ports from a single function on ConnectX-4. This poses a security issue since a certain physical function is able to change port parameters for all ports regardless of its designated port.

WA: N/A

Keywords: mlxconfig

533942 Description: mlxphyburn fails to query firmware version.

WA: N/A

Keywords: mlxphyburn

465159 Description: mlxmdio PHY address may differ when the read/write transactions are per-formed either directly by manipulating the hardware gateway or by asking the firmware.

WA: Run with -g 0 flag (forcing gateway access).

Keywords: mlxmdio

385113 Description: Reading the VPD using the “-vpd_rw” flag or programing the VPD may take up to 5 mins.

WA: N/A

Keywords: mlxburn

554872 Description: FreeBSD PCI access API is currently not supported.

WA: N/A

Keywords: mlxburn

221201 Description: The firmware update process in Connect-IB™, Switch-IB™, ConnectX®-4 and ConnectX®-4 Lx and may take up to two minutes.

WA: N/A

Keywords: flint

326763 Description: The sg command on Connect-IB™, Switch-IB™, ConnectX®-4 and Con-nectX®-4 Lx fails if the -override_cache_replacement flag is not used

WA: Set the GUIDs only when firmware is not active (driver is not loaded) by using the flag -override_cach_replacement

Keywords: flint

409212/408374

Description: Attempting to access Remote/MTUSB device for parallel does not work well.

WA: Avoid working in parallel through these interfaces.

Keywords: flint

540073 Description: Attempt to burn firmware while specifying the -use_fw flag fails as firmware does not support write operation on this flash.

WA: Do not use the -use_fw flag for burn operations.

Keywords: flint


Internal Ref.

Issue


166709 Description: wqdump does not support WQEs receiving of 1024B on Connect-IB®, Con-nectX®-4 and ConnectX®-4 Lx.

WA: N/A

Keywords: wqdump

202870 Description: “mst ib add” may fail when there is a device with zero system GUID in the fabric. The failure occurs when the “mst ib add” uses the ibnetdiscover tool.

WA: Run 'mst ib add --discover-tool ibdiagnet'

Keywords: mst

202869 Description: When an IB subnet manager is not running in the fabric, some of the ports may be in INIT state. Devices that are accessed via these ports are added to the in-band device list even though they are inaccessible to in-band traffic.

WA: Verify a subnet manager is running and that all the ports are in ACTIVE state.

Keywords: mst

15454 Description: In Windows, mst remote devices added by the ‘mst remote add’ command may still be present after uninstalling MFT.

WA: If you still see old remote devices after installing a new WinMFT, you can either run ‘mst restart’ or remove the devs directory manually (resides under the WinMFT install directory)

Keywords: mst

383471 Description: In Windows, “mst ib add” uses only ibnetdiscover to discover the cluster “--discover-tool” option is not used to choose the intended tool. The discover tool argument is intended only for parsing purpose, thus the topology file must be specified when using the “--discover-tool”.

WA: N/A

Keywords: mst

190903 Description: When i2c-diolan-u2c driver is installed, it takes ownership over the mtusb device and prevents mst to load it, consequently, pre-vents access to MFT tools.

WA: Stop the i2c-diolan-u2c driver.

Keywords: mst

529237 Description: Accessing MST device in Windows machine remotely in parallel is not sup-ported; only one connection at the same time is supported.

WA: N/A

Keywords: mst

535639 Description: When there are multiple ConnectX-4 devices in Windows, the MST status shows them in a gap of 2 in indexes (even numbers).

WA: N/A

Keywords: mst


Internal Ref.

Issue

Known Issues


540511 Description: If an unexpected shutdown occurs after running the firmware update package (UPMF) in Windows, 'mst status' may not show any devices when the machine comes up.

WA: Run: ‘sc delete mst64’ or ‘sc delete mst32’ for cleanup.

Keywords: mst

15629 Description: XenServer machine does not have an rpmbuild command which is used to recompile the kernel-mft source RPM in installation phase therefore, MFT installation fails.

WA: 1. Prepare the kernel-mft RPM in the DDK server of the xenserver installed in your machine by running: "

install.sh --rebuild-srpm”2. Install the kernel-mft binary RPM generated in stage one in the xenserver normal machine by:

"rpm -i <kernel-mft binary RPM>"3. Install MFT by: "install.sh --without-kernel"

Keywords: Install Script

18889 Description: If the mcg tool is running while steering entries are added or removed from the device, the tool may display warnings in the following format:"mcg [0x1bff5].next points to non-existing mcg index 0x1b7f5"And the displayed data may be incorrect.

WA: It is recommended to run the tool when the steering table is in a static mode.

Keywords: mlxmcg

676539 Description: mlxuptime and mget_temp are not working against INBAND ConnectX-4/ConnectX-4 Lx devices.

WA: Work against other available devices’ interfaces such as PCI/remote.

Keywords: mlxuptime

383719 Description: Terminating the tool when running it in MEM mode with CTRL+Z can cause issues to the device and to the firmware.

WA: Do not send CTRL+Z to the tool.

Keywords: mlxtrace

517837 Description: When running mlxtrace against in-band device, a ctrl+c is handled by the other library that is used by mlxtrace. Therefore, mlxtrace does not create all files needed.

WA: N/A

Keywords: mlxtrace

384366 Description: Downgrading WinMFT to an older version might corrupt the installation dir.

WA: Remove MFT prior to installing any earlier versions of MFT.

Keywords: WinMFT Installation

589929 Description: mlxfwreset is not supported in VMware.

WA: N/A

Keywords: mlxfwreset


Internal Ref.

Issue


543840 Description: When attempting to reset a pass-through device on a VM, the reset will fail because mlxfwreset fails to locate the PCI bridge for the specified device.

WA: To load the firmware, reboot the machine


594755/786715/787204

Description: mlxfwreset is not functional is FreeBSD 9.1.

WA: Reboot the machine after firmware upgrade.


781514/781569

Description: MFT is not functional if Advance Toolchain Runtime (at7.1) for PPC64LE is installed on the machine.

WA: Export LD_PRELOAD="<path to the correct libc>"

For example:

Export LD_PRELOAD="/lib/powerpc64le-linux-gnu/libc.so.6"

Keywords: Advance Toolchain Runtime, PPC64LE

759915/778296

Description: Segmentation fault may occur in fwtrace on RedHat 6.5 and 6.7 systems.

WA: N/A

Keywords: fwtrace

Description: In order for mlxcables to work locally on the switch, the following switch firmware version must be installed on the switch:• Switch-IB - 11.1100.0026 or higher• Switch-IB 2 - 15.0400.0026 or higher• Spectrum - 13.1100.0026 or higher

WA: N/A

Keywords: mlxcables

783756 Description: When upgrading firmware from v12.14.2036 to v12/14.16.1004 using mlxfwreset, Pass-Through in ConnectX-4 adapter cards might not function properly. In this case, such error message will appear: “-device vfio-pci,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x7: vfio: Error: Failed to setup INTx fd: No such device 2016-05-22T06:46:39.164786Z qemu-kvm: -device vfio-pci,host=04:00.0,id=host-dev0,bus=pci.0,addr=0x7: Device initialization failed.”

WA: Reboot the server for the firmware upgrade changes to take effect.

Keywords: Installation, firmware upgrade

572074 Description: Running mlxtrace/fwtrace with MEM mode on Connect-IB/ConnectX-4 and ConnectX-4 Lx devices is not supported in FreeBSD and VMware ESXi.

WA: Use tracer mode FIFO (-m FIFO)

Keywords: mlxtrace/fwtrace


Internal Ref.

Issue

Known Issues


767933/777735

Description: mlxreg does not support big registers (the maximum SMP MAD size is 64 bytes) when running it with an Inband device (through IB mads).

WA: Run mlxreg locally with the PCI device

Keywords: mlxreg/fwtrace

- Description: For mlxfwreset to work on PowerPC, the minimum firmware version that must be installed on the device is:• ConnectX-4: 12.16.1004• ConnectX-4 Lx: 14.16.1004• ConnectIB: 10.16.1004

WA: N/A


795028/795705

Description: mlxburn fails to read VPD on machines where the device shares the same B:D:F address with another PCI device on different PCI domains

WA: To view the VPD's read only fields, use lspci application if available: lspci -s <PCI_address_D:B:D:F> -vv

Keywords: mlxburn

795226/795657

Description: Occasionally, MFT tools (driver mode) do not function after running mlxf-wreset in PowerPC machines.

WA: Run MFT tools without driver (run: 'mst stop' to stop driver)


855416 Description: Running mlxfwreset on an ARM server with Ubuntu 16.04, may result in machine hanging.

WA: Reboot the server in order to load the firmware


860431 Description: MFT tools do not function properly with the interactive prompt on Windows Server 2016: Nano server.

WA: Use the “-y/--yes”, “-n/--no” flags with the relevant tools to allow non interac-tive execution.

Keywords: Windows Server 2016: Nano server

669711 Description: mst.exe is not functional in Windows Server 2016: Nano Server.

WA: Use mdevices.exe to get list of available devices

Keywords: Windows Server 2016: Nano server, mst

858798 Description: Occasionally, when running the mst status command in some ESXi machines, the command freezes and cannot provide a list of the Mellanox devices.

WA: Run mdevices_info -v to get the list of Mellanox devices.

Keywords: mst status


Internal Ref.

Issue


4 Bug Fixes HistoryTable 9 lists the history of bugs fixedTable 9 - Bug Fixes History (Sheet 1 of 16)

Internal Ref. Issue

795756/795916

Description: mlxfwreset disables and enables all Mellanox devices’ Network Interfaces when resetting the firmware on a device that at least one of its network interfaces is up.


Discovered in Release: 4.4.0

Fixed in Release: 4.5.0

795479/795521

Description: Running mlxfwreset against OEM devices may enter the device to a unde-fined state.




697509 Description: PPTT and PPRT registers are not supported in switches.

Keywords: mlxreg



757651/778451

Description: Fixed an issue causing the mlxcables tool to show wrong temperature value when querying the cable several times in loop.

Keywords: mlxcables



691073 Description: In Linux/Windows, updating firmware on an unmanaged InfiniScale IV switch by Inband fails with the following error: MFE_SEM_LOCKED




418735 Description: Added fwtrace and mlxfwreset to the MFT package for PPC.

Keywords: General



360252 Description: Fixed an issue that caused the target machine to hang when running mlxtrace over an mtusb connected to an HCA/NIC in a Windows target machine. In this mode, mlx-trace may cause memory corruption on the target machine which causes it to hang.

Keywords: mlxtrace



Bug Fixes History


416368 Description: Fixed an issue causing read/write corruption and yields unexpected behavior when running mlxfwmanager_pci with MFT tools in parallel.




434487 Description: Fixed an issue causing mlxfwreset to fail due to some missing files in ARM machines.




519137 Description: Added mlxfwmanager as part of the MFT package intended to FreeBSD 9.1.

Keywords: mlxfwmanager.



522101 Description: Fixed functionality issues of query/set VPD flags in mlxburn in ESXi VMware.

Keywords: mlxburn



604749 Description: Fixed cpldupdate calibration option (-c flag) functionality.

Keywords: cpldupdate



681475 Description: Fixed an issue which showed both Base MAC and Base GUID when running mlxfwmanager query on ConnectX-4 devices, even if the two ports were configured to be ETH only, or IB only.




692194/692373

Description: Fixed an issue preventing mlxfwreset from working in Linux when MLNX_OFED or an inbox driver was not installed.




Table 9 - Bug Fixes History (Sheet 2 of 16)

Internal Ref. Issue


702505/735109

Description: Fixed an issue which caused Flint brom/drom operations to fail when using 5th Generation devices firmware.

Keywords: flint



591283 Description: Performing mlxfwreset on a server with SR-IOV enabled corrupts the virtual functions




600751 Description: Resetting the firmware using mlxfwreset in a machine where the Mellanox driver is Inbox (not MLNX_OFED) might cause the device to hang




590990 Description: MFT package does not include support for ConnectX-4 and ConnectX-4 Lx devices for VMware

Keywords: General



563395 Description: ConnectX-4 and ConnectX-4 Lx devices have a physical function per port, for example: 01:00.0 and 01:00.1. MFT creates an MST device for the first function only. Therefore, MFT can run only against the first function

Keywords: General



592211 Description: On PowerPC 8, mst status -v does not show any information on the multiple functions of the device. For example, in ConnectX-4 devices, each port has a function of its own by default, but it is not shown in mst status -v

Keywords: mst



549867 Description: Setting one of the ports to ETH and the other to IB using mlxconfig may cause the firmware to crash. This was fixed in ConnectX-4 firmware v12.12.1100

Keywords: mlxconfig




Internal Ref. Issue

Bug Fixes History


- Description: HCR tools are not supported in FreeBSD

Keywords: mlxconfig/mlxphyburn



- Description: pci_cr interface is not supported in VMware ESXi 2015

Keywords: General



434287 Description: Running online updates/downloads in parallel may fail




543669 Description: Dumping eqe on Connect-IB and ConnectX-4 adapters fails

Keywords: wqdump



534009 Description: Reset configuration is not supported in mlxconfig for ConnectX-4

Keywords: mlxconfig



408360 Description: UPMF Generation is not supported in VMware ESXi and FreeBSD

Keywords: General



417033 Description: mlx_mfa_gen can not create MFA file under directory with whitespace




499995 Description: flint sg/sv/set_vsd commands with Connect-IB firmware 10.10.5020 or newer corrupt the firmware image

Keywords: flint




Internal Ref. Issue


385797 Description: Running burning tools (for burn/query) and restarting the driver or machine boot at the same time may cause the machine to hang

Keywords: Burning tools (mlxfwmanager, flint and mlxburn)



- Description: mlxtrace activates a hardware component which may lead to decreasing the packet rate of the HCA

Keywords: mlxtrace



434106 Description: If a burning process is killed forcefully (such as: by kill -9 in Linux), subse-quent runs of burning tools will not function as they require hardware resources cleanup

Keywords: Burning tools (mlxfwmanager, flint and mlxburn)



228953 Description: “mst status -v” does not show MLNX_OFED device name (mlx4/mlx5) in XEN server machines. Hence, the MFT tools cannot be run on these devices. Also, mlx-trace/ fwtrace on Connect-IB in MEM mode cannot work, since it is using these devices

Keywords: mst



417033 Description: mlx_mfa_gen fails to calculate CRC when MFA's directory name includes spaces




- Description: mlxfwmanger_pci fails to detect devices in virtual machines of RedHat KVM. <Where the pci address of the device has dev.func !=00.0>

Keywords: mlxfwmanager_pci



417181 Description: Stopping/restarting mst service while one tool is running may cause some issues with the device or driver or the tool itself

Keywords: All




Internal Ref. Issue

Bug Fixes History


418261 Description: mft_uninstall failed in some Ubuntu machines

Keywords: mft_uninstall.sh



419183 Description: mlxfwreset failed due to a parsing issue on some machines where the Express capability register address contains hex digit (such as: b0)




418256 Description: On some Connect-IB® board types driver failed to load after loading new firmware using mlxfwreset




- Description: Kernel installation failed in fbk13 Operating System

Keywords: Installation



427821 Description: MFT installation failed in PPC64LE when TCL is not installed there

Keywords: Install script and mlxburn



- Description: Burning tools may cause machine reboots in some ConnectX cards

Keywords: Burning tools



- Description: Updating a non-failsafe image is not supported

Keywords: Mlxfwmanager



- Description: Killing an WinMFT process may interrupt subsequent runs of WinMFT tools





Internal Ref. Issue


- Description: mlxfwmanager_pci does not work in VMware




- Description: MFT supports only one connected MTUSB-1 device at a time

Keywords: All

Discovered in Release: 2.7.2b


mlxuptime Description: The displayed configured frequency may present wrong results

Keywords: mlxuptime



- Description: mst remote feature does not work when the client machine is windows and the server machine is Linux

Keywords: mst



- Description: Devices in livefish mode in FreeBSD does not appear in mst status

Keywords: mst



- Description: Cannot read vpd when accessing via PCI device in the format:domain:bus:dev.fn

Keywords: mlxburn



- Description: First flint run may fail after Ctrl+C

Keywords: flint



- Description: Flint Connect-IB® burn corrupts the flash when burning a verbatim full flash dump as the firmware image

Keywords: flint




Internal Ref. Issue

Bug Fixes History


- Description: Flint Connect-IB® burning using the “-vsd” flag is not functional

Keywords: flint



- Description: Occasionally, CTRL+C causes flint to hang in WinPE OS

Keywords: flint



- Description: Unexpected behavior when running swreset on flint

Keywords: flint



- Description: CTRL+C does not clear semaphores

Keywords: flint



- Description: Connect-IB® burning: Flint supports VSD of up to 128 chars

Keywords: flint



- Description: wbne command causes endiannes swap

Keywords: flint



- Description: On Windows Power Shell Ctrl+C does not function properly

Keywords: flint



- Description: On FreeBSD, burning new firmware on a device with corrupt empty firmware does not work

Keywords: flint




Internal Ref. Issue


- Description: Occasionally, if a node has a LID set to 0, the ”mst ib add --use-ibdr” com-mand will not add that nodes to the mst device list

Keywords: mst



- Description: On Windows, mst may not show any devices

Keywords: mst



- Description: mlxmcg fails on PPC

Keywords: mlxmcg (formerly mcg)



- Description: On Windows Ctrl+C does not exit gracefully

Keywords: itrace



- Description: On Windows Power Shell MFT might not work on mst devices that contain a comma

Keywords: All



- Description: On Windows x64, some tools are 32 bit binaries

Keywords: All



- Description: The mst cr device is not functional on VMware VMware ESXi. When running it, the following message is received:“You cannot access the HW configurations by mt4099_pci_cr0 device in ESXi”

Keywords: mst




Internal Ref. Issue

Bug Fixes History


- Description: Running the “sg” (set guids) command on a striped image file containing a large expansion rom image may fail

Keywords: flint



- Description: mst status does not show the mtusb-1 when adding in-band devices

Keywords: mst



- Description: mst shows all devices when connected to Flex10 remotely

Keywords: mst



- Description: mst does not display a message when there is no HCA device connected to the machine

Keywords: mst



229211 Description: ”mst ib add --use-ibdr” may not add all nodes in a cluster when the ports are inactive

Keywords: mst



- Description: mtusb is not supported in Windows 2012

Keywords: mst



272122 Description: Running the itrace tool when the driver is not loaded or when the driver failed to load may cause the server to crash

Keywords: itrace




Internal Ref. Issue


15526 Description: Setting the GUIDs on an image file which was generated using the “-exp_rom” and “-striped_image” flags fails when the expansion rom size is larger than 400KB.Current rom sizes are much smaller, thus it is not expected to cause an actual issue

Keywords: flint



212679 Description: mlxtrace not functional when using the PCI format device against Connect-IB™

Keywords: mlxtrace



202857 Description: CTRL-C stops wqdump but does not clear (release) semaphores

Keywords: wqdump



15392 Description: Running wqdump with ‘-ignore’ ignores only the QPC gateway lock but does not ignore the OB gateway

Keywords: wqdump



111212 Description: Setting an empty keyword is not reported as an error, but will prevernt further using of the vpd_set_keyword flagSetting a keyword value longer than 255 characters is not reported as an error, but may cor-rupted the vpd

Keywords: mlxburn



187430 Description: The flag "-fw_dir" is not supported when burning ConnectX®-3 Pro adapter card

Keywords: mlxburn



188943 Description: When a read/write operation over mtusb/remote device fails while running flint, flint may crash, hence not handling the error well

Keywords: flint




Internal Ref. Issue

Bug Fixes History


190153 Description: When trying to burn a firmware+ROM that contains a unified product version to a device where the firmware has no product version, the flint tool allows keeping the device ROM instead of burning the new firmware+ROM as is

Keywords: flint



202856 Description: Access the trace messages area in host memory may fail when using Mellanox HCA cards without on-board memory (MemFree) running on Red Hat Fedora and OEL OSs. Consequently, the application may crash or no trace messages will be printed

Keywords: itrace



190998 Description: Activating counter gateways in ConnectX®-3 via an inband device causes firmware to hang (dead lock)

Keywords: mlxdump



191134/191131/189851

Description: Installing MFT with a different prefix than /usr, causes mlxmcg, fwtrace and mstdump to not work.On Fedora OS, in addition to the above tools, mst and mlxburn do not work either

Keywords: Installation



187135 Description: Running mget_temp against ConnectX®-3 Pro even after initializing the diode results in high temperature (e.g. 120)

Keywords: mget_temp



188802 Description: On certain boards where the external oscillator is connected only to one port, the other port's thermal sensor will not function

Keywords: mget_temp




Internal Ref. Issue


137857 Description: On SwitchX-A0, the YU-sensor reports the wrong temperature

Keywords: mget_temp



189851 Description: Installing MFT with a different prefix than /usr, causes mlxmcg to not work




99897 Description: Occasionally, the fwtrace executable may stop working and display the fol-lowing output:Cannot open self /usr/bin/fwtrace or archive /usr/bin/fwtrace.pkg

Keywords: fwtrace



128149 Description: wqdump uses certain hardware gateways which are used by the firmware. Thus when it accesses the device via the firmware and owns the hardware gateways, it causes issues for the firmware and does not work

Keywords: wqdump



- Description: MFT cannot be installed in a path different than the default /usr

Keywords: Install script

Discovered in Release: 2.7.1a


- Description: The installation script fails if OFED v1.4 or older is installed in the machine as it tries to search for non-existing RPMs

Keywords: Install script



- Description: After firmware upgrade or downgrade, the externally managed SwitchX-A1 should be rebooted through power-cycle and not via flint "swreset" command

Keywords: flint




Internal Ref. Issue

Bug Fixes History


- Description: The flag "-fw_dir" is not supported when burning ConnectX-3 A1 adapter card

Keywords: mlxburn



- Description: The uninstall operation leaves device files under /dev/mst

Keywords: mst



- Description: The tool shows the rules of port 1 in port2 line and vice versa




- Description: Running mstdump on a ConnectX®-3 device may cause the firmware to hang

Keywords: mstdump


Fixed in Release: 2.7.1a

- Description: Accessing the SwitchX flash by MFT has a bug, while reading on PPC64 plat-form, therefore the SwitchX cannot be updated via the PPC64 machine

Keywords: flint



- Description: The flag “-fw_dir” is not supported when burning SwitchX devices

Keywords: mlxburn



- Description: Running mstdump on a SwitchX device may cause it to malfunction

Keywords: mstdump



- Description: Burning the firmware into ConnectX®-3 A1 adapter using the MST CR device resulted in failure

Keywords: flint




Internal Ref. Issue


- Description: In-band access is not supported in Windows MFT

Keywords: mst



- Description: No MTUSB-1 support for 64-bit architecture in Windows MFT

Keywords: All



- Description: “mst ib add” fails to add in-band devices when the IB driver is newer than MLNX_OFED_LINUX-1.5.3-0

Keywords: mst ib add



- Description: mlxi2c scan fails the first time when using mtusb

Keywords: Mlxi2c



- Description: The sg (set guids) command on a VPI device may burn MACs/GUIDs with value 0xff

Keywords: flint



- Description: If the “-striped_image” flag is used in a burn command, image burn will fail or burn a corrupt image

Keywords: flint



- Description: Occasionally, 'mst restart' locked the flash semaphore

Keywords: mst



- Description: 'mst ib add' added non-Mellanox device to the in-band device list

Keywords: mst




Internal Ref. Issue

Bug Fixes History


- Description: Typo in flint help description of Expansion ROM read. The flint help display lists the Expansion ROM read command as “rrrom” instead of “rrom”

Keywords: flint



- Description: In-band access does not work with OFED 1.5

Keywords: mst




Internal Ref. Issue


5 History of Changes and New FeaturesTable 10 - History of Changes and New Features

Component / Tool Description Operating System

Rev. 4.4.0

mlxfwreset Added support for mlxfwreset in PowerPC Linux

mlxconfig Added the following new configurations:• Number of TCs• Number of VLs• Enable DCBX in CEE mode• Enable DCBX in IEEE mode• Allow the NIC to accept DCBX configuration from the

remote peer• Enable DCBX• Enable the internal LLDP client• Select which LLDP TLV will be generated by the NIC

All

General Added support for all tools to work when the MST driver is not installed

Linux

mlxcables Added support for dumping Mellanox cables EEPROM by mstdump/mlxdump tools


Added a new tool (mlxcables) that reads/writes Mellanox cable registers and queries the cables info


Build Created one MFT package for all 64 bits FreeBSD OSs FreeBSD

mlxfwmanager_pci Removed support for mlxfwmanager_pci tool (it is depre-cated), since all the Linux tools can work without a kernel now. When required, use mlxfwmanager instead.

Linux

mcra Added support for clearing VSEC PCI semaphore by the mcra tool. The new capability can be used after killing a tool force-fully without clearing the semaphores.Supported devices: ConnectX-4, ConnectX-4 Lx and Connect-IB

All

mlxreg Added support for Switch-IB, Switch-IB 2 and Spectrum in the mlxreg tool

All

mlxconfig Added the mlxconfig tool to the MFT package for WinPE Windows

Added a backup command in mlxconfig which allows user to save backup of the non-volatile configurations in a RAW file. This file can be set on the device by using the set_raw com-mand

All

Build Added support for running wrapped python tools (like fwtrace) in PPC64, PPC64LE and ARM platforms

Linux

mlxreg Added support for PPRT and PPTT registers in ConnectX-4 and ConnectX-4 Lx

All

Rev. 4.3.0

History of Changes and New Features


General Added support for Spectrum device. All

Added support for Switch-IB 2 device. All

Added support for ConnectX-4 and ConnectX-4 Lx in VMware Esxi.

VMware ESXi

Added support for VMware ESXi 5.5 Native. VMware ESXi

4th generation and 5th generation IC devices are now also named Group I ICs and Group II ICs, respectively.

N/A

mlxconfig Added support for setting some of the parameters in textual values in addition to numerical values.

All

Added new configurations:• The PF log bar size • The VF log bar size • The number of PF MSIX• The number of VF MSIX• port owner • Allow RD counters• IP protocol used by flexboot

All

Added the option to display the configuration’s default values. All

flint Added support to calculate checksum on selected sections in the firmware image.

All

Added the option to attach a timestamp to the firmware image. All

Burning Tools Improved firmware burn performance in livefish mode on 5th generation devices.

All

Added the ability to show the running firmware version in case it does not match with the burnt firmware version on the flash. This case generally occurs after firmware upgrade and before firmware reload.

All

mlxreg Added support for mlxreg tool which can be used to modify access registers or to query them.

All

mst Created an mst device per physical function. It can be seen by running 'mst status -v'.

All

mlxfwmanager Added support to create self-extractors in VMware ESXi OSs. VMware ESXi

fwtrace Added support for the fwtrace tool in FreeBSD. FreeBSD

mlxfwreset Added support for mlxfwreset in Windows and FreeBSD. WindowsFreeBSD

Rev. 4.1.0

General Added support for ConnectX®-4 Lx Linux/Windows/FreeBSD

Added support for ConnectX®-4 FreeBSD



mlxconfig Added support for the following configurations in ConnectX-4, ConnectX-4 Lx and Connect-IB: • IB Dynamically Connect• Internal Settings• RoCE Congestion Control ECN• RoCE Congestion Control Parameters• Wake on LAN

Linux/Windows/FreeBSD

Added support for the following configurations in ConnectX-3 and ConnectX-3 Pro: • InfiniBand Boot Settings• Preboot Boot Settings

Linux/Windows/FreeBSD

mlxtrace Added support for MEM mode in ConnectX-4 Windows

cpld_update Added the cpld_update tool to the OEM package Linux

mlxfwreset Added support for resetting the firmware Windows/FreeBSD

fwtrace Added support in FreeBSD FreeBSD

Burning Tools This version supports new ConnectX-4/Connect-IB firmware version format (MM.mm.ssss).It also enables upgrade of older firmware version format: MM.mmmm.ssss

All

Rev. 4.0.0

General Added support for ConnectX-4 device Linux/Windows

Removed support for ConnectX and ConnectX-2 All

mlx_fpga Added a new tool that dumps registers and burns hardware for FPGA

Linux

mlxconfig Added support for ConnectX-4 and Connect-IB (Beta level) Linux/Windows/ VMware ESXi

mlxfwmanager Added support for FreeBSD and VMware ESXi FreeBSD/VMware ESXi

mlxburn Added support for VMware ESXi VMware ESXi

Rev. 3.8.0

General Added support for Switch-IB device (at beta level) Linux/Windows

Added support for Debian/Ubuntu in PPC64 platform Linux

Added support for ESXi 2015 OS (Native) VMware ESXi

mlxphyburn Added support for burning Aquantia external PHY Linux

mlxconfig Added support for changing BAR size parameter Linux/Windows/ VMware ESXi

Rev. 3.7.1

Bug Fixes See Section 4, “Bug Fixes History,” on page 22 Linux/Windows/VMware ESXi/FreeBSD




Rev. 3.7.0

mlxfwmanager Added online firmware update Linux/Windows/VMware ESXi

mlxburn Added concurrency support to VPD read Linux/Windows

Added mlxburn to MFT FreeBSD

flint Added concurrency support to query firmware Linux/Windows/VMware ESXi/FreeBSD

General Added support for Arm platform and Power8 Linux

Removed support for x86 Windows

mlxfwreset Firmware reset for Connect-IB Linux

fwtrace Added fwtrace tool Windows

Rev. 3.6.1

mlxconfig Added mlxconfig tool for changing non volotaile configura-tion on device

Windows

Burning Tools Added support for micron flash in flint and updated produc-tion burn flow on Connect-IB

Windows

Rev. 3.6.0

mlxconfig Added mlxconfig tool for changing non volotaile configura-tion on device

Linux/VMware ESXi

Burning Tools Added support for micron flash in flint and updated produc-tion burn flow on Connect-IB

Linux/VMware ESXi

mtserver Added support for mstserver FreeBSD

Rev. 3.5.1

package content Added support for the following tools: mst, mlxfwmanager, itrace, mlxtrace, mlxdump, mlxmcg, wqdump, mcra, mget_-temp, pckt_drop, mlxuptime

VMware ESXi

flint mstdump

Added support for ConnectX®-3 Pro VMware ESXi

Redesigned the utility to make its look and feel more user friendly

VMware ESXi

Added support for ConnectX®-3 Pro VMware ESXi

Rev. 3.5.0

flint/wqdump Redesigned the flint and wqdump utility to make their look and feel more user friendly

Linux/Windows

flint Added support for brom in Connect-IB® Linux/Windows

mlxmdio Added support for the mlxmdio utility Linux

mlxfwmanager Added support for Connect-IB Linux/Windows



FreeBSD Added support for FreeBSD operating system (at beta level) FreeBSD

Rev. 3.1.0

General The MFT package now has 2 installation flavours - standard (default mode) and 'OEM'. The OEM mode provides the fol-lowing extra functionality:• Tools for creating mlxfwmanager package• Several features for flint that are used in Connect-IB™

production

Linux

Flint Added support for burning Connect-IB™ via firmware inter-face. The '-override_cache_replacement' flag is not needed. This provides a 'safe' firmware update flow, without the risk of firmware or driver hanging

Linux

mlxfwmanager Added support for the mlxfwmanager utility (at Beta level) Linux

mlxuptime Added support for the mlxuptime utility (at Beta level) Linux

Rev. 3.0.0

General Added support for Connect-IB™ device (at beta level) Linux/Windows

Added support for ConnectX®-3 Pro device (at beta level) Linux/Windows

Added support for Ubuntu operating system Linux

Added support for running tools against PCI device [domain]:bus:dev.fn like: 0000:1a:00.0 or 1a:00.0 and devices used by OFED driver like: mlx4_0

Linux

The package contains only the flint firmware update tool. Other debug tools were removed

Windows

flint Added support for new flash types: N25Q0XX (Micron) and W25Xxx (Winbond)

Linux/Windows

mlxdump Added support for the mlxdump utility (at beta level) Linux/Windows

mlxmcg Renamed mcg to mlxmcg Linux/Windows

spark spark was removed from MFT version 3.0.0 Linux/Windows

Supported Devices The following adapter cards and switch systems are no longer supported in MFT version 3.0.0:• InfiniHost 4X• InfiniHost III Ex• InfiniHost III Lx 4X• InfiniScale• InfiniScale III

Linux/Windows

Rev. 2.7.2b

All Added support for WinPE 4.0 OS Windows

Rev. 2.7.2




General It is no longer required to run mst start/stop when using WinMFT tools. The service is automatically loaded/unloaded when an MFT tool is running. The mst service installation was removed from the setup

Windows

Added support for SwitchX® silicon devices Windows

flint Added support for Atmel AT25DFxx flash family Windows

Added support for burning firmware via Command Line Inter-face (CLI) on SwitchX® devices

Windows

mget_temp mget_temp displays a more accurate temperature reading for ConnectX®-2 and ConnectX®-3 devices by using the adapter’s specific thermal calibration data

Windows

Rev. 2.7.1a

Added the mcg tool (Beta level)

The mcg tool displays the current multicast groups and flow steering rules configured in the device.Target users: Developers of Flow Steering aware applica-tions.This tool dumps the internal steering table which is used by the device to steer Ethernet packets and Multicast IB packets to the correct destination QPs. Each line in the table shows a single filter and a list of destina-tion QPs. Packets that match the filter are steered to the list of destination QPs

Linux

Removed support for In-band access on OFED 1.4 InfiniBand driver

In-band access is supported using OFED 1.5.X and higher Linux

Rev. 2.7.1

General Added mlxconfig tool. This tool sets firmware configurations for Mellanox adapters. These configurations are nonvolatile they apply over device reboots. For further details, please run “mlxconfig -h”. The tool is at beta level

Linux

Added support for Mellanox ConnectX®-3 silicon device Windows

Added the I2CBridge (Dimax’s Driver for USB to I2C Adapter) as part of the WinMFT installation package. How-ever, the I2CBridge is not installed by default

Windows

MFT installationchange

Removed the isw tool.The isw tool functionality was replaced by the "mlxi2c" tool. For example, to scan the devices on the i2c bus, run:> mlxi2c -d <dev> scan instead of> isw -d <dev>

Windows



mget_temp mget_temp displays a more accurate temperature for Con-nectX-2 devices by using chip specific thermal calibration data

Linux

flint Added support for Atmel AT25DFxx flash family Linux

Cleared error messages displayed when trying to burn firm-ware image of a diferent device. For example when burning ConnectX-2 firmware image on ConnectX-3 device

Linux

Added support for flash type SST25VF016B Windows

Added support for flash type M25PX16 Windows

• The ROM section in the image now contains multiple boot images. Therefore flint was modified to display informa-tion for all of the images in the ROM section.

• Added support to display/burn UEFI ROM/

Windows

Added an option to set the VSD and GUIDs in a binary image file. This is useful for production to prepare images for pre-assembly flash burning. These new commands are supported by Mellanox 4th genera-tion devices

Windows

Added an option to set the VSD and GUIDs on an already burnt device. These commands (“sg” and “sv”) re-burn the existing image with the given GUIDs or VSD. When the 'sg' command is applied on a device with blank (0xff) GUIDs, it updates the GUIDs without re-burning the image

Windows

mst Added support for using ibnetdiscover in the 'mst ib add' com-mand

Windows

mlxburn Added support for VPD read/write Windows

Rev. 2.7.0a

Bug Fixes See Section 4, “Bug Fixes History,” on page 22 Linux

Rev. 2.7.0

General Added support for Mellanox ConnectX®-3 and SwitchX™ silicon devices

Linux

Added Secure host feature which enables ConnectX family devices to block access to its internal hardware registers. The hardware access in this mode is allowed only if a correct 64 bits key is provided (see flint changes).MFT tools cannot run on a device with hardware access dis-abled. This feature is enabled only with supporting firmware

Linux

Removed support for Itanium (ia64) Linux




flint Added the following commands:• enable/disable access to the hardware• set/change the key used to enable access to the hardware

Linux

The ROM section in the image now contains multiple boot images. Therefore the flint was modified to display informa-tion for all of the images in the ROM section

Linux

Added support to display/burn UEFI ROM Linux

Added support for burning firmware via Command Line inter-face on SwitchX devices

Linux

Mlxburn Added option to add or replace a single keyword in the VPD writable section (-vpd_set_keyword flag)

Linux

Added the option to set a binary VPD field data Linux

MFT installation Added the option --without-kernel which allows user to install MFT without the mst kernel

Linux

Rev. 2.6.2

MFT installation change

RPM based installation: • Applications are installed using a pre-compiled binary

RPM• Kernel modules are distributed as a source RPM and com-

piled by the installation script • Fast installation process

Linux

Removed prerequisite libraries: expat and zlib-devel Linux

The package tools, libraries and headers are now installed under:{ prefix }/bin or { prefix }/lib and { prefix }/include dirs. Directory /usr/mst is not created.For example, the “mread”, “mwrite” and “mcra” tools that were previously installed by default under /usr/mst/bin, now are installed under /usr/bin

Linux

Linux

Removed the InfiniScale® and InfiniBridge® tools Linux

Removed the Infinivision tool set Linux

Removed the isw tool. The isw tool functionality was replaced by the "mlxi2c" tool.For example, to scan the devices on the i2c bus, run: > mlxi2c -d <dev> scaninstead of > isw -d <dev>

Linux



flint Added support for flash type SST25VF016B Linux

Added support for flash type M25PX16 Linux

Added an option to set the VSD and GUIDs in a binary image file. This is useful for production to prepare images for pre-assembly flash burning.These new commands are supported by Mellanox 4th genera-tion devices

Linux

Added an option to set the VSD and GUIDs on an already burnt device. These commands (“sg” and “sv”) re-burn the existing image with the given GUIDs or VSD. When the 'sg' command is applied on a device with blank (0xff) GUIDs, it updates the GUIDs without re-burning the image

Linux

mst Added support for using ibutils2/ibdiagnet and ibnetdiscover in the 'mst ib add' command

Linux

Removed the _uar, _msix and _ddr devices from the mst device list

Linux

Debug tools Added support for routing I2C bus to the IS4 device on IS50XX systems

Linux

Rev. 2.6.1

Bug Fixes See Section 4, “Bug Fixes History,” on page 22 Linux

Rev. 2.6.0

MFT installation change

Added the options: --without-image-generation, --disable-dc, and --without-kernel which allow for a partial installation in order to avoid problems with SW dependencies

Linux

Now allows a non-root user to prepare MFT RPMs Linux

All Added Mellanox ConnectX®-2 and BridgeX® support Linux/Windows

flint Added a CRC check for the full image Linux

Support for query/burn of clp-gpxe ROM Linux

Prevents burning a ConnectX-2 image onto a ConnectX device and vice versa

Linux

Added a logging option to flint Linux

For the ConnectX device family only:Added commands for an independent burn/read/remove of an Expansion ROM image.For firmware versions earlier than 2.7.000: It is possible to read the ROM image, or to replace an already existing ROM image (by the burn command). However, burning a new ROM image in case a previous image did not exist is not possible, nor is it possible to remove an existing ROM image

Linux




mlxburn Added the -fw_dir option which looks for a suitable firmware file in the given directory

Linux

Support for generating a non-fail-safe image for ConnectX/ConnectX-2, InfiniScale IV, and BridgeX devices

Linux

Debug tools Updated the mlxi2c utility Linux

Added the mget_temp utility which reads the temperature of the ConnectX/ConnectX-2, InfiniScale IV, and BridgeX devices

Linux


MFT release notes - Mellanox

Documents

Transcript of MFT release notes - Mellanox