Dell Emulex Family of Adapters - Manual (Page 1136)

Emulex Drivers Version 10.2 for VMware ESXi User Manual P010087-01A Rev. A
4. Troubleshooting
Troubleshooting the iSCSI Driver
1136
Troubleshooting the iSCSI Driver
The following table provides information on troubleshooting the iSCSI driver.
Retrieving iSCSI Error Log Codes
The iSCSI 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
#vim vmkernel.log
For example, you may see the following message:
Sep 9 19:48:04 esx-server vmkernel: OneConnect iSCSI Driver: The
be2iscsi driver received a Task Management Function that is not
supported and rejected this request. The error log entry immediately
following this entry will indicate the TMF function code that was
rejected.
iSCSI Error Log Code Entries
The following is a brief description of the error log codes generated by the iSCSI driver.
It includes the message displayed, the meaning of the message, and the recommended
resolution.
Table 4-6 Troubleshooting the iSCSI Driver
Issue Resolution
Mutual CHAP authentication cannot be
configured with the vSphere client. One-way CHAP is the only authentication method that can be
configured with the vSphere Client. In order to set Mutual
CHAP authentication, you must use iSCSISelect.
IPV6 support is not available in vSphere
client for hardware iSCSI adapters. In order to set the IPv6 address, you must use iSCSISelect.
Table 4-7 iSCSI Error Log Code Entries
Severity Message Recommended Resolution
Error The be2iscsi driver failed to load
because initialization failed during a
power management boot-up. This failure may be due to the
firmware not being present or running
currently. This failure may also
indicate a hardware problem.
Error The be2iscsi driver was unable to map
one or more PCI Base Address Register
and hence failed to load. This failure may indicate a low
memory condition or a hardware error.