Unable to login into target on iscsi daemon restart

220 views
Skip to first unread message

Prakhar

unread,
Dec 23, 2011, 2:52:32 AM12/23/11
to open-iscsi
Hi,
When I restart the iscsi target daemon set to automatic discovery and
login into targets , the iscsid daemon tries to connect to incorrect
port i.e. port 0 . I am using iSNS discovery records for discovering
targets.

root@Box3:/home/user1# iscsiadm -m discovery -t isns -p
192.168.145.102:3205 --discover
192.168.145.224:0,1 iqn.2011-12.com.example:san02.tgt.server01
192.168.145.224:0,1 iqn.2011-12.com.example:san01.tgt.server01

The following is the syslog output

Dec 23 13:13:40 Box3 iscsid: connect to 192.168.145.224:0 failed
(Connection refused)
Dec 23 13:13:40 Box3 iscsid: connect to 192.168.145.224:0 failed
(Connection refused)
Dec 23 13:13:44 Box3 iscsid: connect to 192.168.145.224:0 failed
(Connection refused)
Dec 23 13:13:44 Box3 iscsid: connect to 192.168.145.224:0 failed
(Connection refused)
Dec 23 13:13:48 Box3 iscsid: connect to 192.168.145.224:0 failed
(Connection refused)
Dec 23 13:13:48 Box3 iscsid: connect to 192.168.145.224:0 failed
(Connection refused)
Dec 23 13:13:51 Box3 iscsid: connect to 192.168.145.224:0 failed
(Connection refused)
Dec 23 13:13:51 Box3 iscsid: connect to 192.168.145.224:0 failed
(Connection refused)

Shouldn't it try to log into the target using 3260 port ??



Mike Christie

unread,
Dec 28, 2011, 3:31:36 AM12/28/11
to open-...@googlegroups.com, Prakhar

3260 is the default port. It looks like the isns server is returning
port 0 though. Either that or there is a bug in the isns pdu parsing code.

When you run the iscsiadm isns discovery command take a
wireshark/tcpdump trace so we can see what the isns server is returning
and know for sure who to blame.

Mike Christie

unread,
Dec 28, 2011, 3:40:17 AM12/28/11
to open-...@googlegroups.com, Prakhar
On 12/28/2011 02:31 AM, Mike Christie wrote:
> On 12/23/2011 01:52 AM, Prakhar wrote:
>> Hi,
>> When I restart the iscsi target daemon set to automatic discovery and
>> login into targets , the iscsid daemon tries to connect to incorrect
>> port i.e. port 0 . I am using iSNS discovery records for discovering
>> targets.
>>
>> root@Box3:/home/user1# iscsiadm -m discovery -t isns -p
>> 192.168.145.102:3205 --discover
>> 192.168.145.224:0,1 iqn.2011-12.com.example:san02.tgt.server01
>> 192.168.145.224:0,1 iqn.2011-12.com.example:san01.tgt.server01

Oh yeah, the output's format above is:

ip_address:port,target_portal_group target_name.

Reply all
Reply to author
Forward
0 new messages