Re: ISCSI: Error Recovery Level 0

["John Hufferd" <hufferd@us.ibm.com>]

Kevin,
What you are asking for is Level 2, connection level recovery.  We agreed
on these levels at a Face to Face meeting, since folks ask us to make the
spec. simpler.   We all agreed on only having official levels 0,1 & 2.

Level 2 has all you want, even if you do not want to have anything to do
with level 1 (within command recovery) you can always terminate and recover
the connection.

If you attempt to make level 1 a "no-op" level, you still have to field the
SNACK on the Target Side, but you can decide to react with a connection
recovery.   Likewise on the Initiator side, you can decide to Logout the
connection instead of sending a SNACK.  Everything will work, but for the
sake of your customers you need to state that you do not do within command
recovery, even if you generally act at recovery level 2.

In any event, within command-recovery is fairly simple, and you should try
your best, then punt with a connection logout.



.
.
.
John L. Hufferd
Senior Technical Staff Member (STSM)
IBM/SSG San Jose Ca
Main Office (408) 256-0403, Tie: 276-0403,  eFax: (408) 904-4688
Home Office (408) 997-6136, Cell: (408) 499-9702
Internet address: hufferd@us.ibm.com


"LEMAY,KEVIN (A-Roseville,ex1)" <kevin_lemay@agilent.com>@ece.cmu.edu on
05/29/2002 12:14:30 PM

Sent by:    owner-ips@ece.cmu.edu


To:    "'ips@ece.cmu.edu'" <ips@ece.cmu.edu>
cc:    Julian Satran/Haifa/IBM@IBMIL
Subject:    ISCSI: Error Recovery Level 0



I have the following question on error Recovery level 0.

On page 105, v12, it says that error recovery level 0 must perform Session
recovery as described in 6.12.4.

This seems to imply that:
If I have a multi-connection session were one connection experiences a
digest error, then I must close all connections on the session, even
killing IOs over the good connection.

This is absurd! Why not just close the one connection that has a problem
and allow the IO to be restarted on one of the other live connections?
There is nothing wrong with the session, only a single connection.

I guess I am calling for a level 0.5, so that I can abort only the
troublesome connection. This would allow for a much faster IO recovery
without adding hardly any coding complexity that is required for level 1.

Comments?

Kevin Lemay