Troubleshooting the iscsi driver, Iscsi driver troubleshooting, Table 4-5 – Dell Emulex Family of Adapters User Manual
Page 690: Table 4-6

Emulex Drivers for Windows User Manual
P010077-01A Rev. A
4. Troubleshooting
Troubleshooting the iSCSI Driver
690
Troubleshooting the iSCSI Driver
Troubleshooting the Cisco Nexus Switch Configuration
Note: The LACP cannot be used on the an iSCSI port.
iSCSI Driver Troubleshooting
The following table provides troubleshooting information for the iSCSI driver.
Table 4-5 Cisco Nexus Switch Situations for iSCSI
Issue
Solution
The system is showing an excessive number of
I/O timeouts as a result of the switch routing
frames to the incorrect port.
Ensure that the LACP is not used on the
iSCSI port.
Table 4-6 Troubleshooting the iSCSI Driver
Issue
Answer/Solution
Overall failure.
Use the iSCSISelect utility to clear the Adapter Configuration.
See the Emulex Boot for NIC, iSCSI, FCoE, and RoCE Protocols
User Manual for instructions.
The driver loads successfully, but
there are event 11 entries in the
event log for the iSCSI driver.
The most common cause is that the UCNA link is down. See “iSCSI
Error Log on Windows Server 2008” on page 710 and look for
specific event codes to confirm.
Unable to create a memory dump file
on a system booted over iSCSI.
Make sure the disk has enough free disk space to create the
dump file. If a full memory dump is selected, the disk must have
free space at least equivalent to the amount of physical memory
in the system.
Unable to log in to target from WMI. • Ensure that the IP address on the UCNA is valid and the
network connection has been set up to reach the target.
• If login is attempted after discovering the target, ensure that
the correct UCNA port has been selected for the login.
The iSCSI WMI GUI shows the target
state as connected, but no LUNs are
seen from the disk manager.
Verify that the UCNA name used to connect to the target
matches the UCNA name configured on the iSCSI target.
Multipath configuration shows
duplicate LUNs on the disk manager.
Ensure that MPIO software is installed and the login options have
selected the MPIO flag. On Windows Server 2008 and Windows
Server 2008 R2 Operating Systems, the server role must be set up
for Multipath. See the Emulex Boot for NIC, iSCSI, FCoE, and
RoCE Protocols User Manual for more information on MPIO.
Multipath configuration takes a long
time to fail over or failover does not
occur.
Ensure that LDTO settings and ETO settings have been configured
for MPIO. These values must be set to 0. For more information,
see “Configuring LDTO and ETO on the Windows Server” on
page 668.
Sendtargets to an IET target fails
because it violates the iSCSI
specification.
If you still want to add an IET target, you must add the target
manually. This issue affects Sendtargets only.