On 06/21/2012 01:35 PM, Meska wrote:
> hi,
> 
> thanks for quick reply
> 
> On Tuesday, June 19, 2012 11:07:09 PM UTC+3, Mike Christie wrote:
>>
>>
>> After you run the discovery command could you do 
>>  
>>
> iscsiadm -m node -P 1 
>>
> 
> [root@edlrac1 ~]#  iscsiadm -m discovery -t sendtargets -p 172.16.1.3
> Starting iscsid:                                           [  OK  ]
> 172.16.1.3:3260,1 iqn.2006-01.int.internal:edlrac.fra1
> 192.168.49.105:3260,1 iqn.2006-01.int.internal:edlrac.fra1
> 172.16.1.3:3260,1 iqn.2006-01.int.internal:edlrac.crs1
> 192.168.49.105:3260,1 iqn.2006-01.int.internal:edlrac.crs1
> 172.16.1.3:3260,1 iqn.2006-01.int.internal:edlrac.data1
> 192.168.49.105:3260,1 iqn.2006-01.int.internal:edlrac.data1
> [root@edlrac1 ~]# iscsiadm -m node -P 1
> Target: iqn.2006-01.int.internal:edlrac.data1
>         Portal: 172.16.1.3:3260,1
>                 Iface Name: default
>         Portal: 192.168.49.105:3260,1
>                 Iface Name: default
> Target: iqn.2006-01.int.internal:edlrac.crs1
>         Portal: 172.16.1.3:3260,1
>                 Iface Name: default
>         Portal: 192.168.49.105:3260,1
>                 Iface Name: default
> Target: iqn.2006-01.int.internal:edlrac.fra1
>         Portal: 172.16.1.3:3260,1
>                 Iface Name: default
>         Portal: 192.168.49.105:3260,1
>                 Iface Name: default
> [root@edlrac1 ~]#
> 
> 
>  
> 
>>
>> Could you also tar up the contents of /var/lib/iscsi 
>>
> 
> Attaching
>  
> 
>>
>> and send it? iscsiadm basically looks in those dirs for the targets that 
>> were found with the discovery command. 
>>
>>
>> Would you run all these commands with debugging on and send the output? 
>> To do this add "-d 8" to the end of the command. 
>>
> 
> Attached
>  

In the logs it looks like when you ran

 iscsiadm -m node -T * -p 172.16.1.3 -l

it worked ok and we logged in.

When you ran

iscsiadm -m node --login

we were already logged into the 172.16.1.3 portals (should have told you
to run iscsiadm -m node -u first to logout the other sessions), so we
just tried to login to the 192.168.49.105 ones. That failed because we
could not connect.

But the log output does not look like what you sent.


I think what might be happening is that the iscsi service is auto
logging in for you.

So when you were running the

 iscsiadm -m node -T * -p 172.16.1.3 -l

type of command we were already logged in. iscsiadm just returned success.

If you run

iscsiadm -m session -P 3

do you see us connected?

When you then ran the more general command

iscsiadm -m node --login

we only tried to login to the ones the iscsi/iscsid service did not and
so you only saw that output.

-- 
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com.
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/open-iscsi?hl=en.

Reply via email to