Nvidia MSTFLINT, Documentation

Page: 86 / 123

86
•
•
•
•
•
•
1.
2.
3.
4.
Troubleshooting
You may be able to easily resolve the issues described in this section. If a problem persists and you
are unable to resolve it yourself please contact your NVIDIA representative or
Support.
General Related Issues
Issue Cause Solution
Adapter is no longer identified by
the operating system after
firmware upgrade Happens due to burning the wrong
firmware on the adapter, firmware
corruption or adapter's hardware
failure. Power cycle the server. If the issue
persists, extract the adapter and
contact Support
Server is booting in loop/not
completing boot after performing
adapter firmware upgrade Happens due to burning the wrong
firmware on the adapter, firmware
corruption or adapter's hardware
failure. Extract the adapter and
contact Support
Enabling hardware access after
configuring new secure host key,
fails The new configuration of the secure
host key was not loaded by the
driver Restart the driver before enabling
the hardware access again
mstflint tools fail on PCI device
with the following errors:
Operation not permitted
Failed to identify device
Failed to detect device ID
Unknown device
No such device
Failed to open device
Tools PCI semaphore might be
locked due to unexpected process
shutdown. Run the following command:
# mcra -c <mst_pci_device>
*Supported on mstflint-4.4.0 and
newer versions.
mstconfig Related Issues
Issue Cause Solution
Server not booting after
enabling SRIOV with high
number of VFs Setting number of VFs larger
than what the Hardware and
Software can support may
cause the system to cease
working To solve this issue:
Disable SRIOV in bios
Reboot server
Change num of VFs
Enable SRIOV in bios
When Querying for current
configuration on ConnectX-3/
ConnectX-3Pro, some of the
parameters are shown as “N/A”
The current firmware on the
device does not support
showing the device's default
configuration Update to the latest firmware