You can use the following tools to troubleshoot general iSCSI configuration problems:
snoop – This tool has been updated to support iSCSI packets.
wireshark – This tool is a GUI tool for dumping and analyzing network traffic. For more information, see https://www.wireshark.org/.
tshark – This is a CLI tool for dumping and analyzing network traffic.
For example, tracing iSCSI packets on an iSCSI port, which is 3260 by default.
This section describes how to troubleshoot various iSCSI issues and error messages.
This section describes the error messages that are related to an Oracle Solaris iSCSI and RADIUS server configuration, and provides possible solutions for recovery.
empty RADIUS shared secret
Cause: The RADIUS server is enabled on the initiator, but the RADIUS shared secret key is not set.
Solution: Configure the initiator with the RADIUS shared secret key. For more information, see How to Configure a RADIUS Server for an iSCSI Target in Managing Devices in Oracle Solaris 11.4.
WARNING: RADIUS packet authentication failed
Cause: The initiator failed to authenticate the RADIUS data packet. This error can occur if the shared secret key that is configured on the initiator node is different from the shared secret key on the RADIUS server.
Solution: Reconfigure the initiator with the correct RADIUS shared secret. For more information, see How to Configure a RADIUS Server for an iSCSI Target in Managing Devices in Oracle Solaris 11.4.
To identify possible causes for a connection problem, become an administrator and list your iSCSI target information.
For example:
initiator# iscsiadm list target
Target: iqn.2001-05.com.abcstorage:6-8a0900-37ad70401-bcfff02df8a421df-zzr1200-01
TPGT: default
ISID: 4000002a0000
Connections: 0
If no connections are listed in the output, check the /var/adm/messages file for possible reasons why the connection failed.
You can verify whether the connection is accessible by using the ping command. You can also verify by connecting to iSCSI port of the storage device by using the telnet command to ensure that the iSCSI service is available. The default port is 3260.
In addition, check the log file of the storage device for errors.
If your target is not listed in the output, check the /var/adm/messages file for possible causes.
If you are using SendTargets as the discovery method, try listing the discovery-address by using the –v option to ensure that the expected targets are visible to the host. For example:
initiator# iscsiadm list discovery-address -v 10.0.0.1 Discovery Address: 10.0.0.1:3260 Target name: eui.210000203787dfc0 Target address: 10.0.0.1:11824 Target name: eui.210000203787e07b Target address: 10.0.0.1:11824
If you are using iSNS as the discovery method, try enabling the iSNS discovery method and listing the isns-server using the –v option to ensure that the expected targets are visible to the host. For example:
initiator# iscsiadm list isns-server -v
iSNS Server IP Address: 203.0.113.56/27:3205
Target name: iqn.1992-08.com.xyz:sn.1234566
Target address: 203.0.113.35/27:3260, 1
Target name: iqn.2003-10.com.abc:group-0:154:abc-65-01
Target address: 203.0.113.66/27:3260, 1
Target name: iqn.2003-10.com.abc:group-0:154:abc-65-02
Target address: 203.0.113.66/27:3260, 1
.
.
.
To troubleshoot iSCSI device or disk unavailability, become an administrator and identify the LUNs that were discovered on the target during enumeration.
For example:
# iscsiadm list target -S
Target: iqn.2001-05.com.abcstorage:6-8a0900-37ad70401-bcfff02df8a421df-zzr1200-01
TPGT: default
ISID: 4000002a0000
Connections: 1
LUN: 0
Vendor: ABCSTOR
Product: 0010
OS Device Name: /dev/rdsk/c3t34d0s2
The –S option shows which LUNs were discovered on the target during enumeration.
Review the /var/adm/messages file to see if an error is reported. If you think a LUN should be listed but it is not, then check the /var/adm/messages log file.
Check the log files of the storage device for errors.
Ensure that any storage device LUN masking is properly configured.
Avoid using the iSNS discovery domain as the means to control storage authorization to specific initiators. Use LUN masking instead to ensure that only authorized initiators can access a LUN.
If you remove a target from a discovery domain while the target is in use, the iSCSI initiator does not log out from this target. If you do not want this initiator to access this target (and the associated LUNs), you must use LUN masking. Removing the target from the discovery domain is not sufficient.
See your vendor specific storage documentation for more information about LUN masking.
This section describes the iSCSI messages that might appear in the /var/adm/messages file, and potential solutions for recovery.
The message format is as follows:
iscsi TYPE (OID) STRING (STATUS-CLASS#/STATUS-DETAIL#)
Either connection or session.
The object ID of the connection or session. This ID is unique for an OS instance.
A description of the condition.
These values are returned in an iSCSI login response as defined by Internet Small Computer Systems Interface (iSCSI), RFC 3720.
iscsi connection(OID) login failed - Miscellaneous iSCSI initiator errors.
Cause: The device login failed due to some form of initiator error.
iscsi connection(OID) login failed - Initiator could not be successfully authenticated.
Cause: The device could not successfully authenticate the initiator.
Solution: If applicable, verify that the settings for CHAP names, CHAP passwords, or the RADIUS server are correct.
iscsi connection(OID) login failed - Initiator is not allowed access to the given target.
Cause: The device cannot allow the initiator access the iSCSI target device.
Solution: Verify your initiator name and confirm that it is properly masked or provisioned by the storage device.
iscsi connection(OID) login failed - Requested ITN does not exist at this address.
Cause: The device does not provide access to the iSCSI target name (ITN) you are requesting.
Solution: Verify that the initiator discovery information is specified properly and that the storage device is configured properly.
iscsi connection(OID) login failed - Requested ITN has been removed and no forwarding address is provided.
Cause: The device can no longer provide access to the iSCSI target name (ITN) you are requesting.
Solution: Verify that the initiator discovery information is specified properly and that the storage device has been configured properly.
iscsi connection(OID) login failed - Requested iSCSI version range is not supported by the target.
Cause: The initiator's iSCSI version is not supported by the storage device.
iscsi connection(OID) login failed - No more connections can be accepted on this Session ID (SSID).
Cause: The storage device cannot accept another connection for this initiator node to the iSCSI target device.
iscsi connection(OID) login failed - Missing parameters (e.g., iSCSI initiator and/or target name).
Cause: The storage device is reporting that the initiator or target name has not been properly specified.
Solution: Specify the iSCSI initiator or target name.
iscsi connection(OID) login failed - Target hardware or software error.
Cause: The storage device encountered a hardware or software error.
Solution: Consult your storage documentation or storage vendor for further assistance.
iscsi connection(OID) login failed - iSCSI service or target is not currently operational.
Cause: The storage device is currently not operational.
Solution: Consult your storage documentation or storage vendor for further assistance.
iscsi connection(OID) login failed - Target has insufficient session, connection or other resources.
Cause: The storage device has insufficient resources.
Solution: Consult your storage documentation or storage vendor for further assistance.
iscsi connection(OID) login failed - unable to initialize authentication
iscsi connection(OID) login failed - unable to set authentication
iscsi connection(OID) login failed - unable to set username
iscsi connection(OID) login failed - unable to set password
iscsi connection(OID) login failed - unable to set ipsec
iscsi connection(OID) login failed - unable to set remote authentication
Cause: The initiator was unable to initialize or set authentication properly.
Solution: Verify that your initiator settings for authentication are properly configured.
iscsi connection(OID) login failed - unable to make login pdu
Cause: The initiator was unable to make a login payload data unit (PDU) based on the initiator or storage device settings.
Solution: Try resetting any target login parameters or other non-default settings.
iscsi connection(OID) login failed - failed to transfer login
iscsi connection(OID) login failed - failed to receive login response
Cause: The initiator failed to transfer or receive a PDU across the network connection.
Solution: Verify that the network connection is reachable.
iscsi connection(OID) login failed - received invalid login response (OP CODE)
Cause: The storage device has responded to a login with an unexpected response.
iscsi connection(OID) login failed - login failed to authenticate with target
Cause: The initiator was unable to authenticate the storage device.
Solution: Verify that your initiator settings for authentication are properly configured.
iscsi connection(OID) login failed - initiator name is required
Cause: An initiator name must be configured to perform all actions.
Solution: Verify that the initiator name is configured.
iscsi connection(OID) login failed - authentication receive failed
iscsi connection(OID) login failed - authentication transmit failed
Cause: The initiator was unable to transmit or receive authentication information.
Solution: Verify network connectivity with the storage device or the RADIUS server, as applicable.
iscsi connection(OID) login failed - login redirection invalid
Cause: The storage device attempted to redirect the initiator to an invalid destination.
Solution: Consult your storage documentation or storage vendor for further assistance.
iscsi connection(OID) login failed - target protocol group tag mismatch, expected <TPGT>, received <TPGT>
Cause: The initiator and target had a TPGT (target portal group tag) mismatch.
Solution: Verify your TPGT discovery settings on the initiator or the storage device.
iscsi connection(OID) login failed - can't accept PARAMETER in security stage
Cause: The device responded with an unsupported login parameter during the security phase of login.
Solution: The parameter name is noted for reference. Consult your storage documentation or storage vendor for further assistance.
iscsi connection(OID) login failed - HeaderDigest=CRC32 is required, can't accept VALUE
iscsi connection(OID) login failed - DataDigest=CRC32 is required, can't accept VALUE
Cause: The initiator is configured to accept only a HeaderDigest or DataDigest that is set to CRC32 for this target. The device returned the value of VALUE.
Solution: Verify that the initiator and device DIGEST settings are compatible.
iscsi connection(OID) login failed - HeaderDigest=None is required, can't accept VALUE
iscsi connection(OID) login failed - DataDigest=None is required, can't accept VALUE
Cause: The initiator is configured to accept only a HeaderDigest or DataDigest that is set to NONE for this target. The device returned the value of VALUE.
Solution: Verify that the initiator and device DIGEST settings are compatible.
iscsi connection(OID) login failed - can't accept PARAMETER
Cause: The initiator does not support this parameter.
iscsi connection(OID) login failed - can't accept MaxOutstandingR2T VALUE
Cause: The initiator does not accept MaxOutstandingR2T of the noted value.
iscsi connection(OID) login failed - can't accept MaxConnections VALUE
Cause: The initiator does not accept the maximum connections of the noted value.
iscsi connection(OID) login failed - can't accept ErrorRecoveryLevel VALUE
Cause: The initiator does not accept an error recovery level of the noted value.
iscsi session(OID) NAME offline
Cause: All connections for this target name have been removed or have failed.
iscsi connection(OID) failure - unable to schedule enumeration
Cause: The initiator was unable to enumerate the LUNs on this target.
Solution: You can force LUN enumeration by running the devfsadm -i iscsi command. For more information, see the devfsadm(8) man page.
iscsi connection(OID) unable to connect to target NAME (errno:ERRNO)
Cause: The initiator failed to establish a network connection.
Solution: For information about the specific error number related to the connection failure, see the /usr/include/sys/errno.h file.