Re: iSCSI: response to second login (with same ISID)

["Sanjeev Bhagat \(TRIPACE/Zoetermeer\)" <sbhagat@tripace.com>]

Hello,

Before we decide one of the given 2 options we must analyze under which
conditions will initiator send the same ISID in two login.

If initiator sends the same ISID because of programattic error then in that
case option no 1 is more relevant in which target rejects the login with
some error code.

But if the initiator sends because of some digest error or it is trying to
open the same session which was ended because of some error before and
target is still in recovery stage then option no. 2 is more relevant where
target closes the pre-existing session and then proceeds for fresh login.

Regards,
Sanjeev


----- Original Message -----
From: "Jim Hafner" <hafner@almaden.ibm.com>
To: <ips@ece.cmu.edu>
Sent: Monday, May 21, 2001 6:15 PM
Subject: iSCSI: response to second login (with same ISID)


> Folks,
>
> Santosh has requested a response to this question and I don't think I've
> noticed an answer.  It's one of those "dot the i" things that we need to
> complete.
>
> The current thinking is that an iSCSI initiator must use a different ISID
> for each session it opens with a specific iSCSI target.
>
> We need to decide on the iSCSI target's response when the iSCSI initiator
> attempts to break this rule.  The choices are:
> 1) REJECT the login with some error code (that the iSCSI initiator can
> understand or infer to mean "ISID in use") and leave the pre-existing
> session alone
> 2) CLOSE the pre-existing session (and abort all it's tasks) and then
> process the new login fresh.
>
> Personally, I have no strong feeling either way, but lean towards option
> (1).  It's simple, clean and doesn't involve any interruption.
>
> Anybody else got any opinions?
>
> Jim Hafner
>