Re: iSCSI-related conclusions from Orlando interim Meeting

[julian_satran@il.ibm.com]

I'll think about it.

Julo

Santosh Rao <santoshr@cup.hp.com> on 22/01/2001 19:32:43

Please respond to Santosh Rao <santoshr@cup.hp.com>

To:   Julian Satran/Haifa/IBM@IBMIL
cc:   ips@ece.cmu.edu
Subject:  Re: iSCSI-related conclusions from Orlando interim Meeting




> I am reluctant to consider any procedure that originates a command at the
> target.

Julian,

iSCSI targets are already allowed to originate Async Messages. This is not
a new procedure being proposed.

>
> Note however that a target in trouble may drop a TCP connection and force
> an initiator to recover.

This does not communicate to the initiator the reason for the connection
close. It is better to use an Async Message for this purpose than
abruptly terminate the connection, for the same reason that one would
rather use a Lgout than close a connection. [in the case where a Logout
is sent on the same connection that is being cleaned up.]

Regards,
Santosh

>
> Santosh Rao <santoshr@cup.hp.com> on 21/01/2001 21:21:46
>
> Please respond to Santosh Rao <santoshr@cup.hp.com>
>
> To:   Julian Satran/Haifa/IBM@IBMIL
> cc:   ips@ece.cmu.edu
> Subject:  Re: iSCSI-related conclusions from Orlando interim Meeting
>
>
> On the subject of Async Message "Target requests a logout", which is a
> ping-pong procedure to achieve a logout, it may be worth considering an
> alternate Async Message in its place that indicates "Target is logging
out
> for error recovery" and allow the target to follow up the Async Message
> with a connection close.
>
> This will simplify target driven connection level error recovery.
>
> Regards,
> Santosh
>


--
#################################
Santosh Rao
Software Design Engineer,
HP, Cupertino.
email : santoshr@cup.hp.com
Phone : 408-447-3751
#################################