I took a peek at the code and 2/2 is returned when login_set_auth() return LOGIN_DROP. Now, it's strange that a login is even going through the authentication phase in the first place unless the initiator was specifically enabled to request authentication. It's possible the initiator code has changed.
LOGIN_DROP is returned if the initiator doesn't send a TargetName during a normal login with authentication requested. This value is also returned if there's an internal error in the configuration database (it probably should have returned a different error here). Finally, the code will return this error if the target has an ACL list and the initiator isn't found in that list. Given the information provided the target doesn't appear to have an ACL so either the initiator is sending a NULL value or no TargetName or there's an internal configuration error with the target. As Nigel requests, have a network snoop during the login would help a lot. On 9/25/07, Nigel Smith <[EMAIL PROTECTED]> wrote: > It looks like the initiator is failing in the login to the target as it's > reporting "Connections: 0". > I think it would be useful to get a capture of the network traffic using > the 'snoop' program. > See this thread for more advice: > http://www.opensolaris.org/jive/thread.jspa?messageID=153729 > Regards > Nigel Smith > > > This message posted from opensolaris.org > _______________________________________________ > storage-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/storage-discuss > -- Rick McNeal A good friend will come and bail you out of jail ... but, a true friend will be sitting next to you saying, "Damn .. that was fun!" _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
