Mstflint: Comparing The Binary Image; Mstflint: Firmware Timestamping For Multi-Host Environment - Nvidia MSTFLINT Documentation

Hide thumbs Also See for MSTFLINT:
Table of Contents

Advertisement

mstflint: Comparing the Binary Image

This capability is applicable to ConnectX-5 onwards adapter cards.
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
The
<-silent>/-s>
percentage progress is not displayed.

mstflint: Firmware Timestamping for Multi-Host Environment

In a multi-host environment, every host can upgrade the NIC firmware. All hosts are treated equally
and there is no designated host. Hence, there can be situations where one host will try to upgrade
the firmware and another will try to downgrade; which may lead to two or more unnecessary 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 a timestamp value that is lower
than the current firmware timestamp will fail.
Firmware timestamping can be used on Connect-IB/ConnectX-4/ConnectX-4 Lx HCAs for
controlling the firmware upgrade/downgrade flow.
Setting a Timestamp on Image
In order to set a timestamp on an image, run:
# mstflint -i ./fw-4115.bin timestamp set [UTC time]
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.
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
"Current timestamp" represents the current running firmware timestamp. If "N/A" is visible,
then the timestamp entry is invalid (example: first use of the feature or after resetting the
timestamp).
"Next timestamp" represents the next firmware that is allowed to be burnt on the HCA.
Updating the "Next timestamp" requires an equal or newer timestamp to be provided.
04:00.0
> -i <binary file *.BIN> <-silent>/<-s> bc
parameter is optional. However, if the silent mode is chosen, the
12.15.0005
52

Advertisement

Table of Contents
loading

Table of Contents