User Manual

Rev 4.70
Mellanox Technologies
164
• Mellanox ConnectX EN 10Gbit Ethernet Adapter <X> device detected that the link connected to port
<Y> is up, and has initiated normal operation.
• Mellanox ConnectX EN 10Gbit Ethernet Adapter <X> device detected that the link connected to port
<Y> is down. This can occur if the physical link is disconnected or damaged, or if the other end-port
is down.
• Mismatch in the configurations between the two ports may affect the performance. When Using
MSI-X, both ports should use the same RSS mode. To fix the problem, configure the RSS mode of
both ports to be the same in the driver GUI.
• Mellanox ConnectX EN 10Gbit Ethernet Adapter <X> device failed to create enough MSI-X vec-
tors. The Network interface will not use MSI-X interrupts. This may affects the performance. To fix
the problem, configure the number of MSI-X vectors in the registry to be at least <Y>.
Issue 10. SR-IOV Environment
In SR-IOV environment, Mellanox driver fails to load a host machine.
Symptom: In SR-IOV environment, Mellanox bus driver fails to load and appears with yellow
bang in Device Manager. Clicking on the properties will show the reason:
"This device cannot find enough free resources that it can use. (Code 12) If you want to use this
device, you will need to disable one of the other devices on this system."
Suggestion: This happens because the BAR space required by device cannot be satisfied by the
system.To resolve this issue, please follow the following steps:
Step 1. Boot to BIOS and disable SR-IOV
Step 2. Burn Firmware with lower number of VFs.
Step 3. Re-enable SR-IOV in BIOS.
For more information, please contact Mellanox support.
Issue 11. NVGRE configuration
Due to an OS issue, NVGRE changes done on a running VM, are not propagated and do not
take effect until OS is restarted.
Suggestion: Change of NVGRE configuration on VM connected to the SR-IOV-enabled vir-
tual switch can be done only when VM is stopped.
15.3 Performance Troubleshooting
Issue 1. Windows Settings
Suggestion 1: In Windows 2012 and above, when a kernel debugger is configured (not neces-
sarily physically connected), flow control is disabled unless the following registry key is set
(reboot required after setting):
Registry Path: HKLM\SYSTEM\CurrentControlSet\Services\NDIS\Parameters
Type: REG_DWORD
Key name: AllowFlowControlUnderDebugger
Value: 1
Suggestion 2: Go to "Power Options" in the "Control Panel". Make sure "Maximum Perfor-
mance" is set as the power scheme, reboot is needed.
Issue 2. General Diagnostic