mstflint: Comparing the Binary Image
This enables the user to verify a firmware image on a device which operates in livefish mode by
comparing it with an existing binary firmware file.
Example:
mstflint -d <device BDF, like 04:00.0 > -i <binary file *.BIN> <-silent>/<-s> bc
mstflint: Firmware Timestamping for Multi-Host
Environment
In a multi-host environment, every host can upgrade the NIC firmware. All hosts are treatedequally
and there is no designated host. Hence, there can be situations where one host will try toupgrade the
firmware and another will try to downgrade; which may lead to two or moreunnecessary server
reboots. In order to avoid such situations, the administrator can add a timestamp to the firmware they
want to upgrade to. Attempts to burn a firmware image with atimestamp value that is lower than the
current firmware timestamp will fail.
Setting a Timestamp on Image
In order to set a timestamp on an image, run:
# mstflint -i ./fw-4115.bin timestamp set [UTC time]
Querying a Timestamp on Image
To view the timestamp that was set on the device, run:
# mstflint -d /41:00.0/mt4115_pciconf0 timestamp query
Current timestamp : N/A. No valid timestamp found
Next timestamp : 2015-12-21T10:58:23Z 12.15.0005
This capability is applicable to ConnectX-5 onwards adapter cards.
The <-silent>/-s> parameter is optional. However, if the silent mode is chosen, the
percentage progress is not displayed.
Firmware timestamping can be used on Connect-IB/ConnectX-4/ConnectX-4 Lx HCAs for
controlling the firmware upgrade/downgrade flow.
The user can either specify a combined date and time timestamp in UTC which conforms to
ISO 8601, or let the tool use the machine’s time for the timestamp.
To Next Page
Loading...
Need help?
General