RE: iSCSI: Logout needs ISID

[julian_satran@il.ibm.com]

Josh,

No command, including logout, can be sent without a login.
The complete scenario is:

-open a new connection
-login in the same session as the old connection (this has the ISID & TSID)
-logout the old connection
-recover commands

You are not supposed to be able to kill a session from outside (at least
not an iSCSI defined mode).
You will need management support for that (SNMP?)

Regards,
Julo

Joshua Tseng <jtseng@NishanSystems.com> on 14/03/2001 17:09:48

Please respond to Joshua Tseng <jtseng@NishanSystems.com>

To:   Julian Satran/Haifa/IBM@IBMIL, ips@ece.cmu.edu
cc:
Subject:  RE: iSCSI: Logout needs ISID




Julian,

In 2.14, you state that a logout command can be
sent on a different connection to destroy a single-
connection iSCSI session.  If you have multiple
sessions ongoing, and the logout command is sent
on a different connection than the one used
to support the session that is to be killed, then
you will need ISID to distinguish the session that
you want killed.

Regards,
Josh

> -----Original Message-----
> From: julian_satran@il.ibm.com [mailto:julian_satran@il.ibm.com]
> Sent: Tuesday, March 13, 2001 9:57 PM
> To: ips@ece.cmu.edu
> Subject: Re: iSCSI: Logout needs ISID
>
>
>
>
> Josh,
>
> There is something I am missing. The Logout can be issued
> only after Login
> (authentication and the rest).
> The session is then implied.
>
> Regards,
> Julo
>
> Joshua Tseng <jtseng@NishanSystems.com> on 14/03/2001 03:56:45
>
> Please respond to Joshua Tseng <jtseng@NishanSystems.com>
>
> To:   Julian Satran/Haifa/IBM@IBMIL
> cc:   ips@ece.cmu.edu
> Subject:  iSCSI:  Logout needs ISID
>
>
>
>
> Julian,
>
> Section 2.14 states that the logout command may
> be sent on a second connection to clean up the
> a single connection iSCSI session.  If the reason
> code is 0 (close the session), then ISID is needed
> to identify the iSCSI session to close.
>
> Josh
>
>
>