Thanks, Mike.   I'll look into this on our end.  Off the bat, it looks  
like "0" would be an invalid value for this key.

I'll reply to this thread if anything further comes up.  My guess is  
it's just a bug on our end.

/jb


On Sep 16, 2009, at 11:51 AM, Mike Christie wrote:

>
> Mike Berg wrote:
>> I see:
>>
>> iscsid: Login negotiation failed, couldn't recognize text
>> MaxOutstandingUnexpectedPDUs=0
>>
>> in /var/log/messages.
>>
>> Is the initiator getting MaxOutstandingUnexpectedPDUs=0 from the  
>> target?
>
> Yeah, the target is sending the initaitor that string during login
> negotiation. We have no idea what it is (is it a iser value?) and do  
> not
> know how to handle it so we fail the login process.
>
>>
>>
>> On Sep 16, 2009, at 11:02 AM, Mike Christie wrote:
>>
>>> Jesse Butler wrote:
>>>> I am attempting to login to a Solaris iSER target w/ a Linux
>>>> machine,  and am seeing this error:
>>>> #   iscsiadm -m node -T
>>>> iqn.1986-03.com.sun:02:d8e2ebc9-6886-46dd-91f6- e80b7400948d -p
>>>> 10.0.0.2:3260,1 -l
>>>> Logging in to [iface: default, target: iqn.1986-03.com.sun:
>>>> 02:d8e2ebc9-6886-46dd-91f6-e80b7400948d, portal: 10.0.0.2,3260]
>>>> iscsiadm: Could not login to [iface: default, target: iqn.
>>>> 1986-03.com.sun:02:d8e2ebc9-6886-46dd-91f6-e80b7400948d, portal:
>>>> 10.0.0.2,3260]:
>>>> iscsiadm: initiator reported error (5 - encountered iSCSI login  
>>>> failure)
>>>> #
>>>> I think I have everything configured properly (see below), so I'm
>>>> just  wondering what that "5" means so I can try to troubleshoot
>>>> this.  I
>>>
>>> 5 actually just means the error "encountered iSCSI login failure".  
>>> It
>>> is just a generic error value to cover all login problems.
>>>
>>> There is normally more error info in /var/log/messages like if it  
>>> was
>>> a chap error or a login pdu error and what the status/class values
>>> were or if it was just a connection problem. Look for something from
>>> iscsiadm or iscsid in there.
>>>
>>>
>>>> looked at the code, but it's a bit difficult to track all the way
>>>> into  the specific error codes.
>>>> My Linux Kung Fu is weak, so if version/rev info is needed, please
>>>> let  me know what and how to retrieve it.
>>
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to