windowswideopen.com

iSCSI SAN Troubleshooting

Posted on April 1st, 2008 by thehabgroup

Information to gather when troubleshooting iSCSI issues
==========================

1. Determine the Microsoft iSCSI initiator version?

2. Determine OS version & Service Pack Version Information

3. Network Interface Information:
——————————
- Who is the manufacturer of network interface card (NIC) or iSCSI Host Bus Adapter (HBA)?

- What is the model of NIC or iSCSI HBA?

- What is the firmware revision of NIC or HBA?

- What is the NIC or HBA driver revision number?

4. Network configuration:
———————-
- Do you have Copper or Fiber Optic cabling?

- Who is the manufacturer of network switch?

- What is the speed of network switch?

- What is them model of network switch?

- What is the firmware of network switch?

5. iSCSI Target Information:
————————-
- Who is manufacturer of target?

- What is the model of target?

- What is the firmware of target iSCSI interface?

Example System Events:

Event ID 1 failed connection:

For Event ID 1 (Initiator failed to connect to the target. Target IP address,
port number, and error status are given in dump data.), at offset 0028 in
the dump data IP Address (4 bytes) and Port Number (2 bytes) are given.
For example,

Event Type: Error
Event Source: iScsiPrt
Event Category: None
Event ID: 1
Date: 4/15/2004
Time: 6:50:02 PM
User: N/A
Computer: SERVER1
Description:
Initiator failed to connect to the target. Target IP address, port number, and error status are given in dump data.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 0c 00 01 00 66 00 ……f.
0008: 00 00 00 00 01 00 00 c0 …….À <–status code c0000001
0010: 01 00 00 00 00 00 00 00 …….. (STATUS_UNSUCCESSFUL)
0018: 00 00 00 00 00 00 00 00 ……..
0020: 00 00 00 00 00 00 00 00 ……..
0028: 9d 3b 7a 91 bc 0c 00 00 ;z¼… <<< 9d 3b 7a 91 is IP Address 145.122.59.157
0030: b5 00 00 c0 µ..À <<< Port number is 0×0cbc (3260)
<<< b5 00 00 c0 is the status returned by
TCP for connect request. Here it is
c00000b5 (STATUS_IO_TIMEOUT)

Lost connection to iSCSI target:

In the following example, the connection was lost to the iSCSI target and eventually restored:

Event Type: Error
Event Source: iScsiPrt
Event Category: None
Event ID: 20
Date: 4/15/2004
Time: 6:49:43 PM
User: N/A
Computer: SERVER1
Description:
Connection to the target was lost. The initiator will attempt to retry the connection.

Data:
0000: 00 00 46 00 01 00 a2 00 ..F…¢.
0008: 00 00 00 00 14 00 00 c0 …….À <–status code C0000014
0010: 12 00 00 00 00 00 00 00 …….. (STATUS_UNRECOGNIZED_MEDIA)
0018: 00 00 00 00 00 00 00 00 ……..
0020: 00 00 00 00 00 00 00 00 ……..
0028: 69 00 71 00 6e 00 2e 00 i.q.n… <–Unicode IQN of target
0030: 32 00 30 00 30 00 33 00 2.0.0.3.
0038: 2d 00 30 00 35 00 2e 00 -.0.5…
0040: 63 00 6f 00 6d 00 2e 00 c.o.m…
0048: 76 00 65 00 6e 00 64 00 v.e.n.d.
0050: 6f 00 72 00 3a 00 69 00 o.r.:.i.
0058: 73 00 63 00 73 00 69 00 s.c.s.i.
0060: 2d 00 74 00 61 00 72 00 -.t.a.r.
0068: 67 00 65 00 74 00 g.e.t.

Failed CHAP authentication

In the following example, the iSCSI initiator is configured for CHAP authentication and the iSCSI initiator sent incorrect information to the target during the authentication exchange:

Event Type: Error
Event Source: iScsiPrt
Event Category: None
Event ID: 10
Date: 4/15/2004
Time: 9:35:10 PM
User: N/A
Computer: SERVER1
Description:
Login request failed. The login response packet is given in the dump data.
(at offset 0×0028 in dump data Login Response PDU (48 bytes) is given)

Data:
0000: 00 00 30 00 01 00 8a 00 ..0…?.
0008: 00 00 00 00 0a 00 00 c0 …….À
0010: 09 00 00 00 00 00 00 00 ……..
0018: 00 00 00 00 00 00 00 00 ……..
0020: 00 00 00 00 00 00 00 00 ……..
0028: 23 00 00 00 00 00 00 17 #…….
0030: 40 00 01 37 00 20 00 01 @..7. ..
0038: 00 00 00 01 00 00 00 00 ……..
0040: 00 00 00 01 00 00 00 01 ……..
0048: 00 00 00 1f 02 01 00 00 …….. <<< 02 is Status Class (Initiator Error)
0050: 00 00 00 00 00 00 00 00 …….. <<< 01 is Status Detail (AUTHENTICATION_FAILED)
(All Status Class and Status Detail are given in the iSCSI specification (RFC 3720)
Status Class is Byte 37 and Status Detail is Byte 38 in the Login Response PDU)

Event Type: Warning
Event Source: MSiSCSI
Event Category: None
Event ID: 113
Date: 4/15/2004
Time: 9:35:10 PM
User: N/A
Computer: SERVER1
Description:
iSCSI discovery via SendTargets failed 0xefff0009 to target portal 157.59.122.145 0003260 ffffffff.

(Here error code 0xefff0009 is ISDSC_AUTHENTICATION_FAILURE.)

Using the iSCSICLI.EXE command line tool:

iSCSICLI.EXE command line tool output

iSCSICLI.EXE is the command-line interface utility to the Microsoft iSCSI initiator. This utility can provide some of the best information available for troubleshooting iSCSI issues. The following sample output from the iSCSICLI.EXE utility consists of the iSCSICLI.EXE command and parameter, followed by sample output:

iscsicli versioninfo:

File Version: C:\WINDOWS\system32\iscsiexe.exe
DLL ENU 5.2.3790.218 shp

File Version: C:\WINDOWS\system32\iscsidsc.dll
DLL ENU 5.2.3790.218 shp

File Version: C:\WINDOWS\system32\iscsicli.exe
DLL ENU 5.2.3790.218 shp

File Version: C:\WINDOWS\system32\iscsium.dll
DLL ENU 5.2.3790.218 shp

File Version: C:\WINDOWS\system32\iscsidip.dll
DLL ENU 5.2.3790.218 shp

File Version: C:\WINDOWS\system32\iscsixip.dll
DLL ENU 5.2.3790.218 shp

File Version: C:\WINDOWS\system32\iscsiwip.dll
- - - -

File Version: C:\WINDOWS\system32\iscsidiskonline.dll
DLL ENU 5.2.3790.218 shp

File Version: C:\WINDOWS\system32\iscsiwmi.dll
DLL ENU 5.2.3790.218 shp

File Version: C:\WINDOWS\system32\iscsilog.dll
DRV ENU 5.2.3790.218 shp

File Version: C:\WINDOWS\system32\iscsipp.dll
DLL ENU 5.2.3790.218 shp

File Version: C:\WINDOWS\system32\drivers\iscsiprt.sys
DRV - 5.2.3790.218 shp

File Version: C:\WINDOWS\system32\drivers\msiscsi.sys
DRV - 5.2.3790.218 shp

The operation completed successfully.

iscsicli listinitiators

Initiators List:
Root\SCSIADAPTER\0000_0
The operation completed successfully.

iscsicli listtargetportals

Total of 2 portals are persisted:

Address and Socket: 172.30.136.85 3260
Symbolic Name :
Initiator Name :
Port Number : <Any Port>

Address and Socket: 157.59.122.145 3260
Symbolic Name :
Initiator Name :
Port Number : <Any Port>

The operation completed successfully.

iscsicli sessionlist

Total of 1 sessions

Session Id : ffffffff862a7664-4000013700000001
Initiator Node Name : iqn.1991-05.com.microsoft:server1
Target Node Name : (null)
Target Name : iqn.1992-08.com.netapp:sn.33599275
ISID : 40 00 01 37 00 01
TSID : 95 01
Number Connections : 1

Connections:
Connection Id : ffffffff862a7664-85a50008
Initiator Portal : 0.0.0.0/1091
Target Portal : 172.30.136.85/3260
CID : 01 00

Devices:
Device Type : Disk
Device Number : 2
Friendly Name : NETAPP LUN SCSI Disk Device
Device Description : Disk drive
Reported Mappings : Bus 0, Target Id 0, LUN 0
Location : Bus Number 0, Target Id 0, LUN 0
Volume Path Names :
H:\

Device Type : Disk
Device Number : 1
Friendly Name : NETAPP LUN SCSI Disk Device
Device Description : Disk drive
Reported Mappings : Bus 0, Target Id 0, LUN 1
Location : Bus Number 0, Target Id 0, LUN 1
Volume Path Names :
G:\

The operation completed successfully.

iscsicli listpersistenttargets

Total of 1 peristent targets
Target Name : iqn.1992-08.com.netapp:sn.33599275
Address and Socket : 172.30.136.85 3260
Session Type : Data
Initiator Name : Root\SCSIADAPTER\0000_0
Port Number : <Any Port>
Security Flags : 0×0
Login Flags : 0×0
Header Digest : Disabled
Data Digest : Disabled
Maximum Connections : 0
Default Time To Wait : 0
Default Time To Retain: 0
Authentication : None
Username:

The operation completed successfully.

iscsicli reporttargetmappings

Total of 1 mappings returned
Session Id : ffffffff862a7664-4000013700000001
Target Name : iqn.1992-08.com.netapp:sn.33599275
Initiator : Root\SCSIADAPTER\0000_0
Initiator Scsi Device : \\.\Scsi2:
Initiator Bus : 0
Initiator Target Id : 0
Target LUN: 0×0 <–> OS Lun: 0×0
Target LUN: 0×100 <–> OS Lun: 0×1

The operation completed successfully.

iscsicli ListiSNSServers

No SNS Servers
The operation completed successfully.

- iSCSI Software Installation Problems

Common installation error messages and resolutions:

Error: “A stop control has been sent to a service that other services

are dependent on”

This typically means that a service is running that is dependent upon the Microsoft iSCSI initiator service. From the command line, type “net stop msiscsi” to stop the iSCSI initiator service and all services that depend upon it and then restart the software installation.

Error: “The Microsoft iSCSI Initiator Service could not be started.

The operation returned because the timeout period expired.”

If you see this error, there may have been an error when starting the iSCSI initiator service. Check the system event logs to see if the Microsoft iSCSI Initiator service failed starting or if it started successfully. If it did start successfully then the error can be safely ignored. If it failed starting then review the system event logs for additional information. Restart your computer. If the problem persists then enabling debug logging may provide helpful information.

Error: “The Microsoft iSCSI Initiator Service could not be started.

Overlapped I/O operation is in progress”

You may be running a prerelease version of the iSCSI initiator service after July 31, 2003. Review the system event log for the event “The evaluation period for the iSCSI initiator service has passed.”. Obtain the latest supported version of the iSCSI initiator package.

Error: “The Microsoft iSCSI Initiator could not be upgraded.
No more data is available”

It is likely you are attempting to install an older version of the iSCSI initiator kernel mode driver. Ensure that the version of the iSCSI initiator that you are installing is newer than the version that was previously installed. If this is the case then there may be an error in the versioning of the iSCSI initiator files. To workaround this problem, look for all files matching the pattern oem*.inf the %windir%\inf directory. Examine each individual file to see if it is the INF file for the iSCSI software initiator kernel mode driver. If it is then delete that file and the corresponding .pnf file. For example, if oem1.inf is for the iSCSI initiator then delete oem1.inf and oem1.pnf. Examine all oem*.inf files. When finished, restart the MSI install, choosing the repair option.

Error: “An error occurred while copying a required file [iscsiexe.exe].

The requested operation cannot be performed on a file with a

user-mapped section open.”

This error means it is likely that there is some other program that has the file iscsiexe.exe open for access. Typically this may be the event viewer. If the event viewer is open then close it and restart the MSI install, choosing the repair option.

Error: “An error occurred while setting security for the WMI interfaces”

This error means it is likely that the security descriptors assigned to the Windows Management Instrumentation (WMI) interfaces for iSCSI are not valid or have System Access Control Lists (SACLs) assigned to them. A SACL is a data structure that is included in a security descriptor to indicate that auditing for the object should be done. WMI Globally Unique Identifiers (GUIDs) do not support auditing and will return this error in the case that a WMI GUID is accessed when the security descriptor for the GUID includes a SACL. To resolve this you should determine how the SACLs are assigned to security descriptors for the WMI GUIDs and use that procedure to remove the SACL from the security descriptors for all of the WMI guids. Another way to resolve this is to obtain from a machine that does not have the SACLs assigned to the WMI GUIDs and is running the same version of Windows as your target machine, the contents of the registry values listed below under the following registry key:

HKEY_LOCAL_MACHINE\System\Current Control Set\Control\WMI\Security

You would then overwrite the registry values on your target machine with the registry values containing security descriptors without SACLs assigned. It is also possible to manually delete the following values from the registry key HKEY_LOCAL_MACHINE\System\Current Control Set\Control\WMI\Security. Note that if you do so then these GUIDs will use the default security descriptor for WMI GUIDs and this may allow unauthorized users access to the WMI GUIDs.

7A2C6C2B-E5A5-49ad-AD68-133089ACD74D
C75258E9-BE79-4a48-A23D-EEB6F8FB940C
53EF8D5F-36F3-4124-8B76-C6AD521A1021
45755098-4291-43df-9720-B58642DD63DF
225B9D64-47A9-41c8-81CD-69BC02652D87
8EAEF9D8-C053-49d3-9205-65C703C2ECC1
556BC0B0-0FB5-40f2-9255-B7D9A669DAEC
B35694DE-D323-49d2-ABB2-8139209AD150
EA4D82BF-29DA-4e12-800A-E5437964462C
420512D9-0537-4c67-A779-84BA7B29CE9F
41646815-7524-4bc0-904A-CD7D510EAC02
391F3325-0BA3-4083-A861-CF4F6F97A527
46B122C0-3767-4069-916E-3A43702F05CE
7BB02370-B8AE-4d29-88DE-76951D3245BA
58515BF3-2F59-4f37-B74F-85AEEC652AD6
84CA6FD6-B152-4e6a-8869-FDE5E37B6157
D7931411-0376-4869-A491-8D679BFC004A
36B58EA2-C461-4bb0-AC8E-952F59D251ED
B4D1C606-8682-4b7a-AC6B-D883D91555FB
4AE27CD9-8DFA-4c37-A42C-B88A93E3E521
C827993C-6D1F-4194-9B5C-D7C0A5F1CFB7
F022F413-3BF5-47ec-A942-33B81CF8E7FF
FA30C290-68DB-430a-AF76-91A2E1C49154
5C59FD61-E919-4687-84E2-7200ABE2209B
1221948A-6332-4ac2-AA04-268AABCECE4F
E67E1BDB-D130-4143-9EB2-8BEE1899FD52

If the problem still exists after deleting these values check for the value 00000000-0000-0000-0000-000000000000. If it exists then delete it, however this will reset the security descriptor for all WMI GUIDs that do not have an explicit security descriptor assigned.

iSCSI Initiator Error Codes

The Microsoft iSCSI Initiator Package is an integrated part of Windows and can return any of the standard set of Win32 error codes. In some cases these error codes are not specific enough for iSCSI operations so there is an additional set if iSCSI specific error codes that are also used by the Microsoft iSCSI Initiator Package

// MessageId: ISDSC_NON_SPECIFIC_ERROR

// MessageText:

// A non specific error occurred.

#define ISDSC_NON_SPECIFIC_ERROR ((ISDSC_STATUS)0xEFFF0001L)

// MessageId: ISDSC_LOGIN_FAILED

// MessageText:

// Login Failed.

#define ISDSC_LOGIN_FAILED ((ISDSC_STATUS)0xEFFF0002L)

// MessageId: ISDSC_CONNECTION_FAILED

// MessageText:

// Connection Failed.

#define ISDSC_CONNECTION_FAILED ((ISDSC_STATUS)0xEFFF0003L)

// MessageId: ISDSC_INITIATOR_NODE_ALREADY_EXISTS

// MessageText:

// Initiator Node Already Exists.

#define ISDSC_INITIATOR_NODE_ALREADY_EXISTS ((ISDSC_STATUS)0xEFFF0004L)

// MessageId: ISDSC_INITIATOR_NODE_NOT_FOUND

// MessageText:

// Initiator Node Does Not Exist.

#define ISDSC_INITIATOR_NODE_NOT_FOUND ((ISDSC_STATUS)0xEFFF0005L)

// MessageId: ISDSC_TARGET_MOVED_TEMPORARILY

// MessageText:

// Target Moved Temporarily.

#define ISDSC_TARGET_MOVED_TEMPORARILY ((ISDSC_STATUS)0xEFFF0006L)

// MessageId: ISDSC_TARGET_MOVED_PERMANENTLY

// MessageText:

// Target Moved Permanently.

#define ISDSC_TARGET_MOVED_PERMANENTLY ((ISDSC_STATUS)0xEFFF0007L)

// MessageId: ISDSC_INITIATOR_ERROR

// MessageText:

// Initiator Error.

#define ISDSC_INITIATOR_ERROR ((ISDSC_STATUS)0xEFFF0008L)

// MessageId: ISDSC_AUTHENTICATION_FAILURE

// MessageText:

// Authentication Failure.

#define ISDSC_AUTHENTICATION_FAILURE ((ISDSC_STATUS)0xEFFF0009L)

// MessageId: ISDSC_AUTHORIZATION_FAILURE

// MessageText:

// Authorization Failure.

#define ISDSC_AUTHORIZATION_FAILURE ((ISDSC_STATUS)0xEFFF000AL)

// MessageId: ISDSC_NOT_FOUND

// MessageText:

// Not Found.

#define ISDSC_NOT_FOUND ((ISDSC_STATUS)0xEFFF000BL)

// MessageId: ISDSC_TARGET_REMOVED

// MessageText:

// Target Removed.

#define ISDSC_TARGET_REMOVED ((ISDSC_STATUS)0xEFFF000CL)

// MessageId: ISDSC_UNSUPPORTED_VERSION

// MessageText:

// Unsupported Version.

#define ISDSC_UNSUPPORTED_VERSION ((ISDSC_STATUS)0xEFFF000DL)

// MessageId: ISDSC_TOO_MANY_CONNECTIONS

// MessageText:

// Too many Connections.

#define ISDSC_TOO_MANY_CONNECTIONS ((ISDSC_STATUS)0xEFFF000EL)

// MessageId: ISDSC_MISSING_PARAMETER

// MessageText:

// Missing Parameter.

#define ISDSC_MISSING_PARAMETER ((ISDSC_STATUS)0xEFFF000FL)

// MessageId: ISDSC_CANT_INCLUDE_IN_SESSION

// MessageText:

// Can not include in session.

#define ISDSC_CANT_INCLUDE_IN_SESSION ((ISDSC_STATUS)0xEFFF0010L)

// MessageId: ISDSC_SESSION_TYPE_NOT_SUPPORTED

// MessageText:

// Session type not supported.

#define ISDSC_SESSION_TYPE_NOT_SUPPORTED ((ISDSC_STATUS)0xEFFF0011L)

// MessageId: ISDSC_TARGET_ERROR

// MessageText:

// Target Error.

#define ISDSC_TARGET_ERROR ((ISDSC_STATUS)0xEFFF0012L)

// MessageId: ISDSC_SERVICE_UNAVAILABLE

// MessageText:

// Service Unavailable.

#define ISDSC_SERVICE_UNAVAILABLE ((ISDSC_STATUS)0xEFFF0013L)

// MessageId: ISDSC_OUT_OF_RESOURCES

// MessageText:

// Out of Resources.

#define ISDSC_OUT_OF_RESOURCES ((ISDSC_STATUS)0xEFFF0014L)

// MessageId: ISDSC_CONNECTION_ALREADY_EXISTS

// MessageText:

// Connections already exist on initiator node.

#define ISDSC_CONNECTION_ALREADY_EXISTS ((ISDSC_STATUS)0xEFFF0015L)

// MessageId: ISDSC_SESSION_ALREADY_EXISTS

// MessageText:

// Session Already Exists.

#define ISDSC_SESSION_ALREADY_EXISTS ((ISDSC_STATUS)0xEFFF0016L)

// MessageId: ISDSC_INITIATOR_INSTANCE_NOT_FOUND

// MessageText:

// Initiator Instance Does Not Exist.

#define ISDSC_INITIATOR_INSTANCE_NOT_FOUND ((ISDSC_STATUS)0xEFFF0017L)

// MessageId: ISDSC_TARGET_ALREADY_EXISTS

// MessageText:

// Target Already Exists.

#define ISDSC_TARGET_ALREADY_EXISTS ((ISDSC_STATUS)0xEFFF0018L)

// MessageId: ISDSC_DRIVER_BUG

// MessageText:

// The iscsi driver implementation did not complete an operation correctly.

#define ISDSC_DRIVER_BUG ((ISDSC_STATUS)0xEFFF0019L)

// MessageId: ISDSC_INVALID_TEXT_KEY

// MessageText:

// An invalid key text was encountered.

#define ISDSC_INVALID_TEXT_KEY ((ISDSC_STATUS)0xEFFF001AL)

// MessageId: ISDSC_INVALID_SENDTARGETS_TEXT

// MessageText:

// Invalid SendTargets response text was encountered.

#define ISDSC_INVALID_SENDTARGETS_TEXT ((ISDSC_STATUS)0xEFFF001BL)

// MessageId: ISDSC_INVALID_SESSION_ID

// MessageText:

// Invalid Session Id.

#define ISDSC_INVALID_SESSION_ID ((ISDSC_STATUS)0xEFFF001CL)

// MessageId: ISDSC_SCSI_REQUEST_FAILED

// MessageText:

// The scsi request failed.

#define ISDSC_SCSI_REQUEST_FAILED ((ISDSC_STATUS)0xEFFF001DL)

// MessageId: ISDSC_TOO_MANY_SESSIONS

// MessageText:

// Exceeded max sessions for this initiator.

#define ISDSC_TOO_MANY_SESSIONS ((ISDSC_STATUS)0xEFFF001EL)

// MessageId: ISDSC_SESSION_BUSY

// MessageText:

// Session is busy since a request is already in progress.

#define ISDSC_SESSION_BUSY ((ISDSC_STATUS)0xEFFF001FL)

// MessageId: ISDSC_TARGET_MAPPING_UNAVAILABLE

// MessageText:

// The target mapping requested is not available.

#define ISDSC_TARGET_MAPPING_UNAVAILABLE ((ISDSC_STATUS)0xEFFF0020L)

// MessageId: ISDSC_ADDRESS_TYPE_NOT_SUPPORTED

// MessageText:

// The Target Address type given is not supported.

#define ISDSC_ADDRESS_TYPE_NOT_SUPPORTED ((ISDSC_STATUS)0xEFFF0021L)

// MessageId: ISDSC_LOGON_FAILED

// MessageText:

// Logon Failed.

#define ISDSC_LOGON_FAILED ((ISDSC_STATUS)0xEFFF0022L)

// MessageId: ISDSC_SEND_FAILED

// MessageText:

// TCP Send Failed.

#define ISDSC_SEND_FAILED ((ISDSC_STATUS)0xEFFF0023L)

// MessageId: ISDSC_TRANSPORT_ERROR

// MessageText:

// TCP Transport Error

#define ISDSC_TRANSPORT_ERROR ((ISDSC_STATUS)0xEFFF0024L)

// MessageId: ISDSC_VERSION_MISMATCH

// MessageText:

// iSCSI Version Mismatch

#define ISDSC_VERSION_MISMATCH ((ISDSC_STATUS)0xEFFF0025L)

// MessageId: ISDSC_TARGET_MAPPING_OUT_OF_RANGE

// MessageText:

// The Target Mapping Address passed is out of range for the adapter configuration.

#define ISDSC_TARGET_MAPPING_OUT_OF_RANGE ((ISDSC_STATUS)0xEFFF0026L)

// MessageId: ISDSC_TARGET_PRESHAREDKEY_UNAVAILABLE

// MessageText:

// The preshared key for the target or IKE identification payload is not available.

#define ISDSC_TARGET_PRESHAREDKEY_UNAVAILABLE ((ISDSC_STATUS)0xEFFF0027L)

// MessageId: ISDSC_TARGET_AUTHINFO_UNAVAILABLE

// MessageText:

// The authentication information for the target is not available.

#define ISDSC_TARGET_AUTHINFO_UNAVAILABLE ((ISDSC_STATUS)0xEFFF0028L)

// MessageId: ISDSC_TARGET_NOT_FOUND

// MessageText:

// The target name is not found or is marked as hidden from login.

#define ISDSC_TARGET_NOT_FOUND ((ISDSC_STATUS)0xEFFF0029L)

// MessageId: ISDSC_LOGIN_USER_INFO_BAD

// MessageText:

// One or more parameters specified in LoginTargetIN structure is invalid.

#define ISDSC_LOGIN_USER_INFO_BAD ((ISDSC_STATUS)0xEFFF002AL)

// MessageId: ISDSC_TARGET_MAPPING_EXISTS

// MessageText:

// Given target mapping already exists.

#define ISDSC_TARGET_MAPPING_EXISTS ((ISDSC_STATUS)0xEFFF002BL)

// MessageId: ISDSC_HBA_SECURITY_CACHE_FULL

// MessageText:

// The HBA security information cache is full.

#define ISDSC_HBA_SECURITY_CACHE_FULL ((ISDSC_STATUS)0xEFFF002CL)

// MessageId: ISDSC_INVALID_PORT_NUMBER

// MessageText:

// The port number passed is not valid for the initiator.

#define ISDSC_INVALID_PORT_NUMBER ((ISDSC_STATUS)0xEFFF002DL)

// MessageId: ISDSC_OPERATION_NOT_ALL_SUCCESS

// MessageText:

// The operation was not successful for all initiators or discovery methods.

#define ISDSC_OPERATION_NOT_ALL_SUCCESS ((ISDSC_STATUS)0xAFFF002EL)

// MessageId: ISDSC_HBA_SECURITY_CACHE_NOT_SUPPORTED

// MessageText:

// The HBA security information cache is not supported by this adapter.

#define ISDSC_HBA_SECURITY_CACHE_NOT_SUPPORTED ((ISDSC_STATUS)0xEFFF002FL)

// MessageId: ISDSC_IKE_ID_PAYLOAD_TYPE_NOT_SUPPORTED

// MessageText:

// The IKE id payload type specified is not supported.

#define ISDSC_IKE_ID_PAYLOAD_TYPE_NOT_SUPPORTED ((ISDSC_STATUS)0xEFFF0030L)

// MessageId: ISDSC_IKE_ID_PAYLOAD_INCORRECT_SIZE

// MessageText:

// The IKE id payload size specified is not correct.

#define ISDSC_IKE_ID_PAYLOAD_INCORRECT_SIZE ((ISDSC_STATUS)0xEFFF0031L)

// MessageId: ISDSC_TARGET_PORTAL_ALREADY_EXISTS

// MessageText:

// Target Portal Structure Already Exists.

#define ISDSC_TARGET_PORTAL_ALREADY_EXISTS ((ISDSC_STATUS)0xEFFF0032L)

// MessageId: ISDSC_TARGET_ADDRESS_ALREADY_EXISTS

// MessageText:

// Target Address Structure Already Exists.

#define ISDSC_TARGET_ADDRESS_ALREADY_EXISTS ((ISDSC_STATUS)0xEFFF0033L)

// MessageId: ISDSC_NO_AUTH_INFO_AVAILABLE

// MessageText:

// There is no IKE authentication information available.

#define ISDSC_NO_AUTH_INFO_AVAILABLE ((ISDSC_STATUS)0xEFFF0034L)

// MessageId: ISDSC_NO_TUNNEL_OUTER_MODE_ADDRESS

// MessageText:

// There is no tunnel mode outer address specified.

#define ISDSC_NO_TUNNEL_OUTER_MODE_ADDRESS ((ISDSC_STATUS)0xEFFF0035L)

// MessageId: ISDSC_CACHE_CORRUPTED

// MessageText:

// Authentication or tunnel address cache is corrupted.

#define ISDSC_CACHE_CORRUPTED ((ISDSC_STATUS)0xEFFF0036L)

// MessageId: ISDSC_REQUEST_NOT_SUPPORTED

// MessageText:

// The request or operation is not supported.

#define ISDSC_REQUEST_NOT_SUPPORTED ((ISDSC_STATUS)0xEFFF0037L)

// MessageId: ISDSC_TARGET_OUT_OF_RESORCES

// MessageText:

// The target does not have enough resources to process the given request.

#define ISDSC_TARGET_OUT_OF_RESORCES ((ISDSC_STATUS)0xEFFF0038L)

// MessageId: ISDSC_SERVICE_DID_NOT_RESPOND

// MessageText:

// The initiator service did not respond to the request sent by the driver.

#define ISDSC_SERVICE_DID_NOT_RESPOND ((ISDSC_STATUS)0xEFFF0039L)

// MessageId: ISDSC_ISNS_SERVER_NOT_FOUND

// MessageText:

// The iSNS server was not found or is unavailable.

#define ISDSC_ISNS_SERVER_NOT_FOUND ((ISDSC_STATUS)0xEFFF003AL)

// MessageId: ISDSC_OPERATION_REQUIRES_REBOOT

// MessageText:

// The operation was successful but requires a driver reload or reboot to become effective.

#define ISDSC_OPERATION_REQUIRES_REBOOT ((ISDSC_STATUS)0xAFFF003BL)

// MessageId: ISDSC_NO_PORTAL_SPECIFIED

// MessageText:

// There is no target portal available to complete the login.

#define ISDSC_NO_PORTAL_SPECIFIED ((ISDSC_STATUS)0xEFFF003CL)

// MessageId: ISDSC_CANT_REMOVE_LAST_CONNECTION

// MessageText:

// Cannot remove the last connection for a session.

#define ISDSC_CANT_REMOVE_LAST_CONNECTION ((ISDSC_STATUS)0xEFFF003DL)

// MessageId: ISDSC_SERVICE_NOT_RUNNING

// MessageText:

// The Microsoft iSCSI initiator service has not been started.

#define ISDSC_SERVICE_NOT_RUNNING ((ISDSC_STATUS)0xEFFF003EL)

// MessageId: ISDSC_TARGET_ALREADY_LOGGED_IN

// MessageText:

// The target has already been logged in via an iSCSI session.

#define ISDSC_TARGET_ALREADY_LOGGED_IN ((ISDSC_STATUS)0xEFFF003FL)

// MessageId: ISDSC_DEVICE_BUSY_ON_SESSION

// MessageText:

// The session cannot be logged out since a device on that session is currently being used.

#define ISDSC_DEVICE_BUSY_ON_SESSION ((ISDSC_STATUS)0xEFFF0040L)

// MessageId: ISDSC_COULD_NOT_SAVE_PERSISTENT_LOGIN_DATA

// MessageText:

// Failed to save persistent login information.

#define ISDSC_COULD_NOT_SAVE_PERSISTENT_LOGIN_DATA ((ISDSC_STATUS)0xEFFF0041L)

// MessageId: ISDSC_COULD_NOT_REMOVE_PERSISTENT_LOGIN_DATA

// MessageText:

// Failed to remove persistent login information.

#define ISDSC_COULD_NOT_REMOVE_PERSISTENT_LOGIN_DATA ((ISDSC_STATUS)0xEFFF0042L)

// MessageId: ISDSC_PORTAL_NOT_FOUND

// MessageText:

// The specified portal was not found.

#define ISDSC_PORTAL_NOT_FOUND ((ISDSC_STATUS)0xEFFF0043L)

// MessageId: ISDSC_INITIATOR_NOT_FOUND

// MessageText:

// The specified initiator name was not found.

#define ISDSC_INITIATOR_NOT_FOUND ((ISDSC_STATUS)0xEFFF0044L)

// MessageId: ISDSC_DISCOVERY_MECHANISM_NOT_FOUND

// MessageText:

// The specified discovery mechanism was not found.

#define ISDSC_DISCOVERY_MECHANISM_NOT_FOUND ((ISDSC_STATUS)0xEFFF0045L)

// MessageId: ISDSC_IPSEC_NOT_SUPPORTED_ON_OS

// MessageText:

// iSCSI does not support IPSEC for this version of the OS.

#define ISDSC_IPSEC_NOT_SUPPORTED_ON_OS ((ISDSC_STATUS)0xEFFF0046L)

// MessageId: ISDSC_PERSISTENT_LOGIN_TIMEOUT

// MessageText:

// The iSCSI service timed out waiting for all persistent logins to complete.

#define ISDSC_PERSISTENT_LOGIN_TIMEOUT ((ISDSC_STATUS)0xEFFF0047L)

// MessageId: ISDSC_SHORT_CHAP_SECRET

// MessageText:

// The specified CHAP secret is less than 96 bits and will not be usable for authenticating over non ipsec connections.

#define ISDSC_SHORT_CHAP_SECRET ((ISDSC_STATUS)0xAFFF0048L)

// MessageId: ISDSC_EVALUATION_PEROID_EXPIRED

// MessageText:

// The evaluation period for the iSCSI initiator service has expired.

#define ISDSC_EVALUATION_PEROID_EXPIRED ((ISDSC_STATUS)0xEFFF0049L)

// MessageId: ISDSC_INVALID_CHAP_SECRET

// MessageText:

// CHAP secret given does not conform to the standard. Please see system event log for more information.

#define ISDSC_INVALID_CHAP_SECRET ((ISDSC_STATUS)0xEFFF004AL)

// MessageId: ISDSC_INVALID_TARGET_CHAP_SECRET

// MessageText:

// Target CHAP secret given is invalid.

#define ISDSC_INVALID_TARGET_CHAP_SECRET ((ISDSC_STATUS)0xEFFF004BL)

// MessageId: ISDSC_INVALID_INITIATOR_CHAP_SECRET

// MessageText:

// Initiator CHAP secret given is invalid.

#define ISDSC_INVALID_INITIATOR_CHAP_SECRET ((ISDSC_STATUS)0xEFFF004CL)

// MessageId: ISDSC_INVALID_CHAP_USER_NAME

// MessageText:

// CHAP Username given is invalid.

#define ISDSC_INVALID_CHAP_USER_NAME ((ISDSC_STATUS)0xEFFF004DL)

// MessageId: ISDSC_INVALID_LOGON_AUTH_TYPE

// MessageText:

// Logon Authentication type given is invalid.

#define ISDSC_INVALID_LOGON_AUTH_TYPE ((ISDSC_STATUS)0xEFFF004EL)

// MessageId: ISDSC_INVALID_TARGET_MAPPING

// MessageText:

// Target Mapping information given is invalid.

#define ISDSC_INVALID_TARGET_MAPPING ((ISDSC_STATUS)0xEFFF004FL)

// MessageId: ISDSC_INVALID_TARGET_ID

// MessageText:

// Target Id given in Target Mapping is invalid.

#define ISDSC_INVALID_TARGET_ID ((ISDSC_STATUS)0xEFFF0050L)

// MessageId: ISDSC_INVALID_ISCSI_NAME

// MessageText:

// The iSCSI name specified contains invalid characters or

// is too long.

#define ISDSC_INVALID_ISCSI_NAME ((ISDSC_STATUS)0xEFFF0051L)

// MessageId: ISDSC_INCOMPATIBLE_ISNS_VERSION

// MessageText:

// The iSNS version number returned from the iSNS server is not compatible with this version of the iSNS client.

#define ISDSC_INCOMPATIBLE_ISNS_VERSION ((ISDSC_STATUS)0xEFFF0052L)

- iSCSI Login Issues

Symptoms:

Not able to make the initial connection between initiator and target
Error message: “Target Moved Temporarily” or “Target Moved Permanently”
Error message: “Initiator Instance Does Not Exist”
Potential causes of iSCSI login issues are as follows:

Authentication failures
Network errors
Configuration errors
Potential Resolutions:

Check the host event logs. Look for errors coming from iSCSIPRT or MSISCSI. If there are any errors, look into the data section of the event logs. These error codes may give some indication as to what may be going wrong and lead to a possible resolution. For example:

ISDSC_TARGET_NOT_FOUND Could indicate that the IQN specified on the access control list of the target does not match the IQN being specified and sent to the target during login. Check the IQN on both initiator and target to make sure they are identical

ISDSC_LOGIN_USER_INFO_BAD The initiator is passing bad parameters to the target during login. Check the “key=value” pairs in the traces for both login command and response frame. Check to see that these values are the same as what is being sent in either the iSCSI user-interface or command line.

ISDSC_PERSISTENT_LOGIN_TIMEOUT In this case check the login command and response frames in a trace. Also note the time deltas between command and response. The iSCSI initiator has a relatively long timeout value so you may want to engage the hardware vendor if this is a persistent problem.

ISDSC_INVALID_LOGON_AUTH_TYPE Check the logon parameters being specified when attempting to login to the target.

iscsi microsoft iscsi initiatoriscsi microsoft iscsi initiator

No Comments »
Filed under: iscsi

windowswideopen.com

Translate

Sponsored Links

Link Ads

Recent Posts

Related Products

How Many Visitors?

Important Links

Wireless client not obtaining or renewing its IP address from DHCP

Windows Client machine cannot locate or see the Wireless SSID

How to add OEM drivers to Windows Xp RIS image

The Citrix Management Console could not be started because there was an error in creating the process

iSCSI SAN Troubleshooting

Scheduling Tasks with Soon.exe (Command Scheduling Utility)

Discount Technology for Business - Visit Iplanet.com

Determining the current MTU

Determining the current MTU

Testing MTU Issues with Ping.exe

Changing MTU w/out Reboot

Testing DNS with NSLookup.exe

Basic Windows Networking Troubleshoting

Link to Me!!

RSS Feed

Pages