•
•
•
•
•
•
•
•
-m|--mst_flags
MST_FLAGS
Provide mst flags to be used when invoking mst restart step. For example:--
mst_flags="--with_fpga"
-y|--yes Answer “yes” on prompt
--skip_driver| -s Skip driver start/stop stage (driver must be stopped manually)
-v|--version Print tool version
-h|--help Show help message and exit
--skip_fsm_sync Skip fsm syncing
q|query Query for reset level required to load new firmware
r|reset Execute reset Level
reset_fsm_register Reset the fsm sync register to idle state
Reset Levels and Types
Reset levels and types depend on the extent of the changes introduced when updating the
device'sfirmware. The tool will display the supported reset levels and types that will ensure the loading
of the newfirmware. Those reset levels and types are:
Reset-levels:
0: Driver, PCI link, network link will remain up ("live-Patch")
3: Driver restart and PCI reset
4: Warm Reboot
5: Cold Reboot
Reset-types (relevant only for reset-levels 3,4):
0: Full chip reset
1: Phy-less reset ("port-alive" - network link will remain up)
mstfwreset for Multi-Host NICs
mstfwreset supports a Multi-Host setup. To reset the firmware for a device in a Multi-Host setup,you
have to run the tool on all the hosts simultaneously. The tool utilizes a synchronizationmechanism
supported by the firmware in order to synchronize between the different runninginstances of the tool
on the hosts.
For debugging purposes, it is possible to avoid the synchronization by running the tool with theflag --
skip_fsm_sync.
mstfwreset for Socket-Direct NICs
To reset the firmware on a socket-direct NIC, run the tool on all PCI devices related to the same NIC
with function 0 simultaneously.
See the following example on a Linux OSs:
Exact reset level and types needed to load new firmware may differ, as it depends on the
difference between the running firmware and the firmware we are upgrading to.
When running mstfwreset on a Multi-Host setup, a time-out of 3 minutes is expected for
allthe hosts until they join the firmware reset process.