User Manual
Table Of Contents
- Mellanox WinOF VPI User Manual
- Table of Contents
- List of Tables
- Document Revision History
- About this Manual
- 1 Introduction
- 2 Driver Features
- 3 Deploying Windows Server 2012 with SMB Direct
- 4 Driver Configuration
- 5 Performance Tuning
- 6 OpenSM - Subnet Manager
- 7 InfiniBand Fabric
- 7.1 Network Direct Interface
- 7.2 part_man - Virtual IPoIB Port Creation Utility
- 7.3 InfiniBand Fabric Diagnostic Utilities
- 7.4 InfiniBand Fabric Performance Utilities
- 7.4.1 ib_read_bw
- 7.4.2 ib_read_lat
- 7.4.3 ib_send_bw
- 7.4.4 ib_send_lat
- 7.4.5 ib_write_bw
- 7.4.6 ib_write_lat
- 7.4.7 ibv_read_bw
- 7.4.8 ibv_read_lat
- 7.4.9 ibv_send_bw
- 7.4.10 ibv_send_lat
- 7.4.11 ibv_write_bw
- 7.4.12 ibv_write_lat
- 7.4.13 ibaddr
- 7.4.14 ibcacheedit
- 7.4.15 iblinkinfo
- 7.4.16 ibqueryerrors
- 7.4.17 ibsysstat
- 7.4.18 perfquery
- 7.4.19 saquery
- 7.4.20 smpdump
- 8 Software Development Kit
- 9 Troubleshooting
- 10 Documentation
TroubleshootingRev 4.3
Mellanox Technologies
111
9 Troubleshooting
9.1 InfiniBand Troubleshooting
Issue 1. The IB interfaces is not up after the first reboot after the installation process is com-
pleted.
Suggestion: To troubleshoot this issue, follow the steps bellow:
1. Check that the IB driver is running on all nodes by using 'vstat'. The vstat utility
located at <installation_directory>\tools, displays the status and capabilities of the
network adaptor card(s).
2. On the command line, enter “vstat” (use -h for options) to retrieve information
about one or more adapter ports. The field port_state will be equal to:
• PORT_DOWN - when there is no InfiniBand cable ("no link");
• PORT_INITIALIZED - when the port is connected to some other port ("physical link");
• PORT_ACTIVE - when the port is connected and OpenSM is running ("logical link")
• PORT_ARMED - when the port is connected to some other port ("physical link");
3.
Run OpenSM - see OpenSM operation instructions in the OpenSM section above.
4. Verify the status of ports by using vstat: All connected ports should report
"PORT_ACTIVE" state.
9.2 Ethernet Troubleshooting
Issue 1. The installation of MLNX_VPI for Windows fails with the following (or a similar)
error message:
This installation package is not supported by this processor type. Contact your product vendor."
Suggestion: This message is printed if you have downloaded and attempted to install an incor-
rect MSI -- for example, if you are trying to install a 64-bit MSI on a 32-bit machine (or vice
versa).
Issue 2. The performance is low.
Suggestion: This can be due to non-optimal system configuration. See the section "Perfor-
mance Tuning" to take advantage of Mellanox 10 GBit NIC performance.
Issue 3. The driver does no start.
Suggestion 1: This can happen due to an RSS configuration mismatch between the TCP stack
and the Mellanox adapter. To confirm this scenario, open the event log and look under "Sys-
tem" for the "mlx4eth5" or "mlx4eth6" source. If found, enable RSS as follows:
1. Run the following command: "netsh int tcp set global rss = enabled".
Suggestion 2: This is a less recommended suggestion, and will cause low performance. Dis-
able RSS on the adapter. To do this set RSS mode to "No Dynamic Rebalancing".
Issue 4. The Ethernet driver fails to start. In the Event log, under the mlx4_bus source, the fol-
lowing error message appears: RUN_FW command failed with error -22
Suggestion: The error message indicates that the wrong firmware image has been programmed
on the adapter card.
See http://www.mellanox.com > Support > Firmware Download