Cannot login to ISCSI Target - hangs after sending login details
- by Frank
I have an ISCSI target volume, to which i am trying to connect using CentOS Linux server. Everything works fine, but cannot its stuck at login. Here are the steps i am performing:
[root@neon ~]# iscsiadm -m node -l iscsiadm: could not read session
targetname: 5 iscsiadm: could not find session info for session20
iscsiadm: could not read session targetname: 5 iscsiadm: could not
find session info for session21 iscsiadm: could not read session
targetname: 5 iscsiadm: could not find session info for session22
iscsiadm: could not read session targetname: 5 iscsiadm: could not
find session info for session23 iscsiadm: could not read session
targetname: 5 iscsiadm: could not find session info for session30
iscsiadm: could not read session targetname: 5 iscsiadm: could not
find session info for session31 iscsiadm: could not read session
targetname: 5 iscsiadm: could not find session info for session78
iscsiadm: could not read session targetname: 5 iscsiadm: could not
find session info for session79 iscsiadm: could not read session
targetname: 5 iscsiadm: could not find session info for session80
iscsiadm: could not read session targetname: 5 iscsiadm: could not
find session info for session81 Logging in to [iface: eql.eth2,
target:
iqn.2001-05.com.equallogic:0-8a0906-ab4764e0b-55ed2ef5cf350a66-neon105,
portal: 10.10.1.1,3260] (multiple)
After this step, its stucks, waits for some time and then gives this output:
Logging in to [iface: iface1, target:
iqn.2001-05.com.equallogic:0-8a0906-ab4764e0b-55ed2ef5cf350a66-neon105,
portal: 10.10.1.1,3260] (multiple) iscsiadm: Could not login to
[iface: eql.eth2, target:
iqn.2001-05.com.equallogic:0-8a0906-ab4764e0b-55ed2ef5cf350a66-neon105,
portal: 10.10.1.1,3260].
My iscsi.conf is this:
node.startup = automatic
node.session.timeo.replacement_timeout = 15 # default 120; RedHat recommended
node.conn[0].timeo.login_timeout = 15
node.conn[0].timeo.logout_timeout = 15
node.conn[0].timeo.noop_out_interval = 5
node.conn[0].timeo.noop_out_timeout = 5
node.session.err_timeo.abort_timeout = 15
node.session.err_timeo.lu_reset_timeout = 20
node.session.initial_login_retry_max = 8 # default 8; Dell recommended
node.session.cmds_max = 1024 # default 128; Equallogic recommended
node.session.queue_depth = 32 # default 32; Equallogic recommended
node.session.iscsi.InitialR2T = No
node.session.iscsi.ImmediateData = Yes
node.session.iscsi.FirstBurstLength = 262144
node.session.iscsi.MaxBurstLength = 16776192
node.conn[0].iscsi.MaxRecvDataSegmentLength = 262144
discovery.sendtargets.iscsi.MaxRecvDataSegmentLength = 32768
node.conn[0].iscsi.HeaderDigest = None
node.session.iscsi.FastAbort = Yes
Also, in access control, i have given full access to Any IP, Any CHAP user and fixed iscsi initiator name. With same access level, all other volumes on rest of servers are working, except this one.