Interpreting software iSCSI error codes
The following table provides us with the information we need to decipher a software iSCSI error code in the vSphere logfiles. If the code is displayed as decimal, we can simply use the decimal column. If the code is displayed as an 8-digit hex code, in order to read it properly, we need to split it into two 4-digit hex numbers and use the Hex Code column. For example, I.E. 00050201 becomes 0005 and 0201.
|
Hex Code |
Decimal Code |
Source |
Description |
|---|---|---|---|
|
0000 |
0 |
Initiator |
No Error |
|
0001 |
1 |
Initiator |
Generic Error |
|
0002 |
2 |
Initiator |
Object Not Found |
|
0003 |
3 |
Initiator |
Out of Memory |
|
0004 |
4 |
Initiator |
Transport Failure: This is a common error and indicates a network problem preventing the initiator from reaching the target |
|
0005 |
5 |
Initiator |
Login Failure: Check for a target-related code to determine if the login failed due to something on the array side |
|
0006 |
6 |
Initiator |
Database Failure |
|
0007 |
7 |
Initiator |
Invalid Operation |
|
0008 |
8 |
Initiator |
Transport Timeout: Cannot connect to the target before the timeout value expired and occurs due to array or network congestion |
|
0009 |
9 |
Initiator |
Internal Initiator Engine Fault |
|
000a |
10 |
Initiator |
Logout Failure |
|
000b |
11 |
Initiator |
PDU send/receive timeout: Initiator established a socket/link to the target and sent the Login Request PDU, but has not received an answer from the target within the specified time and the Initiator aborted the login |
|
000c |
12 |
Initiator |
Transport not found |
|
000d |
13 |
Initiator |
Access error |
|
000e |
14 |
Initiator |
Transport capabilities error: This should never be seen in a production environment with any supported iSCSI HBA/Driver |
|
000f |
15 |
Initiator |
Object exists |
|
0010 |
16 |
Initiator |
Invalid request |
|
0011 |
17 |
Initiator |
iSNS server is unavailable |
|
0012 |
18 |
Initiator |
|
|
0000 |
NA |
Target |
No Error |
|
0101 |
NA |
Target |
Target temporarily moved: The requested target has moved to a new IP address, but the change is not permanent |
|
0102 |
NA |
Target |
Target permanently moved: The requested target has moved to a new IP address and the change is permanent |
|
0200 |
NA |
Target |
Miscellaneous initiator failure |
|
0201 |
NA |
Target |
Authentication failure |
|
0202 |
NA |
Target |
Authorization failure: The initiator is denied access to attempt to login |
|
0203 |
NA |
Target |
Not Found: The requested target does not exist at this address |
|
0204 |
NA |
Target |
Target removed |
|
0205 |
NA |
Target |
Unsupported version |
|
0206 |
NA |
Target |
Too many connections: The array can no longer service incoming sessions as it is at capacity |
|
0207 |
NA |
Target |
Missing parameter |
|
0208 |
NA |
Target |
Cannot include in session |
|
0209 |
NA |
Target |
Session type not supported |
|
020a |
NA |
Target |
Requested session does not exist |
|
020b |
NA |
Target |
Invalid request type during login |
|
0300 |
NA |
Target |
Target error (hardware or software) |
|
0301 |
NA |
Target |
Service unavailable |
|
0302 |
NA |
Target |
Out of resources |
Note
For more information on iSCSI software initiator error codes, read the VMware KB Article 2012171 located at http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2012171.
