Dell Emulex Family of Adapters - Manual (Page 1133)

Emulex Drivers Version 10.2 for VMware ESXi User Manual P010087-01A Rev. A
4. Troubleshooting
Troubleshooting the NIC Driver
1133
NIC Event/Error Logging for ESXi 5.0 and 5.1
Retrieving ESXi Server NIC Error Log Codes
For ESXi Server systems, the NIC driver generates error codes to the
/var/log/vmkernel log file. The vmkernel log file is an ASCII text file that can be
viewed and searched with a text editor such as vim. The vmkernel log file is
automatically rotated as it gets larger, and the rotated log files are named vmkernel.x,
where x is an integer.
To search the log file for error messages, at the command prompt, type:
#cd /var/log
#less vmkernel
For example, you might see the following message:
Sep 9 19:48:04 esx-server vmkernel: WARNING: Found a OneConnect card
in Gen 1 x8 PCI-e slot. Should be in Gen 2, x8 slot for best
performance.
ESXi Server NIC Event Log Entries
The following is a list of ESXi Server network event log error messages. It includes the
severity of the error, the message displayed, and the message description. When
reporting a problem with the adapter to Emulex, check the message log
(/proc/vmware/log) and report any of these entries that may be present.
Note: In the following table, ,
column refers to decimal values that appear in the error messages.
Table 4-5 ESXi Server NIC Event Log Entries
Severity Displayed Message Description
Error
OneConnect POST failed
Power ON Self Test of the adapter
failed. This indicates either a
hardware or a firmware problem. Try
rebooting the system after a reset.
Error
OneConnect initialization
failed
Either the initialization of the
adapter or the allocation of some
resource for initializing the driver
failed. In most cases, this message is
accompanied by another more
specific error message. Try
rebooting the system after a power
cycling. If the problem persists, this
could indicate a hardware problem
or corrupted firmware.
Warning
Using INTx interrupts.
NetQueues feature will be
disabled
The driver could not allocate MSIx
vector for interrupt. The driver may
continue to work, but the
performance may be impacted.