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

[Gary Kotzur <GaryKotzur@MaXXan.com>]

I agree with your choice of number one, it is cleaner and the initiator can
"correct" his login after getting the error code.  

Gary Kotzur
Principal Member of Technical Staff
MaXXan Systems, Inc.
GaryKotzur@MaXXan.com
Ph: 832-436-1012
Cl: 281-814-9396
Fx: 832-436-1099

This email message is for the sole use of the intended recipient(s) and may
contain confidential information. Any unauthorized use; review, disclosure
or distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply email to GaryKotzur@MaXXan.com and destroy all
copies of the original message.


-----Original Message-----
From: Jim Hafner [mailto:hafner@almaden.ibm.com]
Sent: Monday, May 21, 2001 11:15 AM
To: ips@ece.cmu.edu
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