Login error (5 - encountered iSCSI login failure)

[Dongmin Kim]

Hello,



While I was tying to use iscsiadm, I found out that iSCSI initiator
couldn't connect to the iSCSI target.

It looks strange because the output from some commands looks normal.

Then, does anyone from the group help me to fix it?



For reference, the number of iSCSI storage nodes are two because I need to
configure HA.



Thank you in advance.





*[***@host ~]# iscsiadm -m node -p 10.24.**.27:3260,2 -T
iqn.1986-03.com.sun:02:b1127d57-e17c-40bc-d782-c53b0f88c60a --login*

Logging in to [iface: default, target:
iqn.1986-03.com.sun:02:b1127d57-e17c-40bc-d782-c53b0f88c60a, portal:
10.24.**.27,3260] (multiple)

iscsiadm: Could not login to [iface: default, target:
iqn.1986-03.com.sun:02:b1127d57-e17c-40bc-d782-c53b0f88c60a, portal:
10.24.**.27,3260].

*iscsiadm: initiator reported error (5 - encountered iSCSI login failure)*

iscsiadm: Could not log into all portals



*[***@host ~]# iscsiadm -m node*

10.24.**.28:3260,2
iqn.1986-03.com.sun:02:0644cb8c-d4fe-617d-a7b8-cf7a0ef5362f

10.24.**.27:3260,2
iqn.1986-03.com.sun:02:b1127d57-e17c-40bc-d782-c53b0f88c60a

[***@host ~]#



--------------------------------------------------------------------------



*[***@host ~]# cat /etc/iscsi/initiatorname.iscsi *

InitiatorName=iqn.2005-03.org.open-iscsi:bcc8652691f6



--------------------------------------------------------------------------



*[***@host ~]# iscsiadm -m discovery -t sendtarget -p 10.24.**.27*

# BEGIN RECORD 2.0-872.13.el5

discovery.startup = manual

discovery.type = sendtargets

discovery.sendtargets.address = 10.24.**.27

discovery.sendtargets.port = 3260

discovery.sendtargets.auth.authmethod = None

discovery.sendtargets.auth.username = <empty>

discovery.sendtargets.auth.password = <empty>

discovery.sendtargets.auth.username_in = <empty>

discovery.sendtargets.auth.password_in = <empty>

discovery.sendtargets.timeo.login_timeout = 15

discovery.sendtargets.use_discoveryd = No

discovery.sendtargets.discoveryd_poll_inval = 30

discovery.sendtargets.reopen_max = 5

discovery.sendtargets.timeo.auth_timeout = 45

discovery.sendtargets.timeo.active_timeout = 30

discovery.sendtargets.iscsi.MaxRecvDataSegmentLength = 32768

# END RECORD



--------------------------------------------------------------------------



*[root@** ~]# cat /etc/iscsi/iscsid.conf *

#

# Open-iSCSI default configuration.

# Could be located at /etc/iscsi/iscsid.conf or ~/.iscsid.conf

#

# Note: To set any of these values for a specific node/session run

# the iscsiadm --mode node --op command for the value. See the README

# and man page for iscsiadm for details on the --op command.

#



#############################

# NIC/HBA and driver settings

#############################

# open-iscsi can create a session and bind it to a NIC/HBA.

# To set this up see the example iface config file.



#*****************

# Startup settings

#*****************



# To request that the iscsi initd scripts startup a session set to
"automatic".

# node.startup = automatic

#

# To manually startup the session set to "manual". The default is automatic.

node.startup = automatic



# For "automatic" startup nodes, setting this to "Yes" will try logins on
each

# available iface until one succeeds, and then stop.. The default "No"
will try

# logins on all availble ifaces simultaneously.

node.leading_login = No



# *************

# CHAP Settings

# *************



# To enable CHAP authentication set node.session.auth.authmethod

# to CHAP. The default is None.

#node.session.auth.authmethod = CHAP



# To set a CHAP username and password for initiator

# authentication by the target(s), uncomment the following lines:

#node.session.auth.username = username

#node.session.auth.password = password



# To set a CHAP username and password for target(s)

# authentication by the initiator, uncomment the following lines:

#node.session.auth.username_in = username_in

#node.session.auth.password_in = password_in



# To enable CHAP authentication for a discovery session to the target

# set discovery.sendtargets.auth.authmethod to CHAP.. The default is None.

#discovery.sendtargets.auth.authmethod = CHAP



# To set a discovery session CHAP username and password for the initiator

# authentication by the target(s), uncomment the following lines:

#discovery.sendtargets.auth.username = username

#discovery.sendtargets.auth.password = password



# To set a discovery session CHAP username and password for target(s)

# authentication by the initiator, uncomment the following lines:

#discovery.sendtargets.auth.username_in = username_in

#discovery.sendtargets.auth.password_in = password_in



# ********

# Timeouts

# ********

#

# See the iSCSI REAME's Advanced Configuration section for tips

# on setting timeouts when using multipath or doing root over iSCSI.

#

# To specify the length of time to wait for session re-establishment

# before failing SCSI commands back to the application when running

# the Linux SCSI Layer error handler, edit the line..

# The value is in seconds and the default is 120 seconds.

node.session.timeo.replacement_timeout = 120



# To specify the time to wait for login to complete, edit the line.

# The value is in seconds and the default is 15 seconds.

node.conn[0].timeo.login_timeout = 15



# To specify the time to wait for logout to complete, edit the line.

# The value is in seconds and the default is 15 seconds.

node.conn[0].timeo.logout_timeout = 15



# Time interval to wait for on connection before sending a ping.

node.conn[0].timeo.noop_out_interval = 5



# To specify the time to wait for a Nop-out response before failing

# the connection, edit this line. Failing the connection will

# cause IO to be failed back to the SCSI layer. If using dm-multipath

# this will cause the IO to be failed to the multipath layer.

node.conn[0].timeo.noop_out_timeout = 5



# To specify the time to wait for abort response before

# failing the operation and trying a logical unit reset edit the line.

# The value is in seconds and the default is 15 seconds.

node.session.err_timeo.abort_timeout = 15



# To specify the time to wait for a logical unit response

# before failing the operation and trying session re-establishment

# edit the line.

# The value is in seconds and the default is 30 seconds.

node.session.err_timeo.lu_reset_timeout = 30



#******

# Retry

#******



# To specify the number of times iscsid should retry a login

# if the login attempt fails due to the node.conn[0].timeo.login_timeout

# expiring modify the following line. Note that if the login fails

# quickly (before node.conn[0].timeo.login_timeout fires) because the
network

# layer or the target returns an error, iscsid may retry the login more than

# node.session.initial_login_retry_max times.

#

# This retry count along with node.conn[0].timeo.login_timeout

# determines the maximum amount of time iscsid will try to

# establish the initial login. node.session.initial_login_retry_max is

# multiplied by the node.conn[0].timeo.login_timeout to determine the

# maximum amount.

#

# The default node.session.initial_login_retry_max is 8 and

# node.conn[0].timeo.login_timeout is 15 so we have:

#

# node.conn[0].timeo.login_timeout * node.session.initial_login_retry_max =

#
120 seconds

#

# Valid values are any integer value. This only

# affects the initial login. Setting it to a high value can slow

# down the iscsi service startup. Setting it to a low value can

# cause a session to not get logged into, if there are distuptions

# during startup or if the network is not ready at that time.

node.session.initial_login_retry_max = 8



################################

# session and device queue depth

################################



# To control how many commands the session will queue set

# node.session.cmds_max to an integer between 2 and 2048 that is also

# a power of 2. The default is 128.

node.session.cmds_max = 128



# To control the device's queue depth set node.session.queue_depth

# to a value between 1 and 1024. The default is 32.

node.session.queue_depth = 32



##################################

# MISC SYSTEM PERFORMANCE SETTINGS

##################################



# For software iscsi (iscsi_tcp) and iser (ib_iser) each session

# has a thread used to transmit or queue data to the hardware. For

# cxgb3i you will get a thread per host.

#

# Setting the thread's priority to a lower value can lead to higher
throughput

# and lower latencies. The lowest value is -20. Setting the priority to

# a higher value, can lead to reduced IO performance, but if you are seeing

# the iscsi or scsi threads dominate the use of the CPU then you may want

# to set this value higher.

#

# Note: For cxgb3i you must set all sessions to the same value, or the

# behavior is not defined.

#

# The default value is -20. The setting must be between -20 and 20.

node.session.xmit_thread_priority = -20





#***************

# iSCSI settings

#***************



# To enable R2T flow control (i.e., the initiator must wait for an R2T

# command before sending any data), uncomment the following line:

#

#node.session.iscsi.InitialR2T = Yes

#

# To disable R2T flow control (i.e., the initiator has an implied

# initial R2T of "FirstBurstLength" at offset 0), uncomment the following
line:

#

# The defaults is No.

node.session.iscsi.InitialR2T = No



#

# To disable immediate data (i.e., the initiator does not send

# unsolicited data with the iSCSI command PDU), uncomment the following
line:

#

#node.session.iscsi.ImmediateData = No

#

# To enable immediate data (i.e., the initiator sends unsolicited data

# with the iSCSI command packet), uncomment the following line:

#

# The default is Yes

node.session.iscsi.ImmediateData = Yes



# To specify the maximum number of unsolicited data bytes the initiator

# can send in an iSCSI PDU to a target, edit the following line.

#

# The value is the number of bytes in the range of 512 to (2^24-1) and

# the default is 262144

node.session.iscsi.FirstBurstLength = 262144



# To specify the maximum SCSI payload that the initiator will negotiate

# with the target for, edit the following line.

#

# The value is the number of bytes in the range of 512 to (2^24-1) and

# the defauls it 16776192

node.session.iscsi.MaxBurstLength = 16776192



# To specify the maximum number of data bytes the initiator can receive

# in an iSCSI PDU from a target, edit the following line.

#

# The value is the number of bytes in the range of 512 to (2^24-1) and

# the default is 262144

node.conn[0].iscsi.MaxRecvDataSegmentLength = 262144



# To specify the maximum number of data bytes the initiator will send

# in an iSCSI PDU to the target, edit the following line.

#

# The value is the number of bytes in the range of 512 to (2^24-1).

# Zero is a special case. If set to zero, the initiator will use

# the target's MaxRecvDataSegmentLength for the MaxXmitDataSegmentLength.

# The default is 0.

node.conn[0].iscsi.MaxXmitDataSegmentLength = 0



# To specify the maximum number of data bytes the initiator can receive

# in an iSCSI PDU from a target during a discovery session, edit the

# following line.

#

# The value is the number of bytes in the range of 512 to (2^24-1) and

# the default is 32768

#

discovery.sendtargets.iscsi.MaxRecvDataSegmentLength = 32768



# To allow the targets to control the setting of the digest checking,

# with the initiator requesting a preference of enabling the checking,
uncomment

# the following lines (Data digests are not supported and on ppc/ppc64

# both header and data digests are not supported.):

#node.conn[0].iscsi.HeaderDigest = CRC32C,None



#

# To allow the targets to control the setting of the digest checking,

# with the initiator requesting a preference of disabling the checking,

# uncomment the following line:

#node.conn[0].iscsi.HeaderDigest = None,CRC32C

#

# To enable CRC32C digest checking for the header and/or data part of

# iSCSI PDUs, uncomment the following line:

#node.conn[0].iscsi.HeaderDigest = CRC32C

#

# To disable digest checking for the header and/or data part of

# iSCSI PDUs, uncomment the following line:

#node.conn[0].iscsi.HeaderDigest = None

#

# The default is to never use DataDigests or HeaderDigests.

#

node.conn[0].iscsi.HeaderDigest = None

[Mike Christie]

Post by Dongmin Kim
Hello,
While I was tying to use iscsiadm, I found out that iSCSI initiator
couldn't connect to the iSCSI target.
It looks strange because the output from some commands looks normal.
Then, does anyone from the group help me to fix it?

Thank you for providing so much info. There is just one more piece of
info I need though. Could you send the /var/log/messages from when you
ran the iscsiadm command and it failed? It will have more info about
what failed.