Re: iSCSI connection recovery

["Julian Satran" <Julian_Satran@il.ibm.com>]

Sandeep,

Retry over any connection was always the case.
Commands can change allegiance only after a logout.
The commands get quiesced anyway and you have to mark them ready for a
retry anyhow (you don't want retry at arbitrary times to hit unpunished the
target). After that it doesn't matter where you retry (same connection,
another old one, a new one).

The only new thing is command replay (after status was sent but before it
is acked).

Regards,
Julo

sandeepj@research.bell-labs.com (Sandeep Joshi) on 28-07-2001 06:37:33

Please respond to sandeepj@research.bell-labs.com (Sandeep Joshi)

To:   ips@ece.cmu.edu
cc:
Subject:  iSCSI connection recovery




I had a "big-picture" question about the connection
recovery model.

The current draft suggests that, once the broken connection
is logged out, the commands allegiant to the old connection
can now be retried over *any* connection. (See Section 7.11.3
bullet 1 and also Appendix F Session Recovery algo for
initiator.)

I may be mistaken, but in previous drafts, this was not
the case and commands always stayed allegiant to a CID.

So the question is.. how does one use a Status cache
belonging to the old connection in this new model (now that
the commands are going to be retried over any connection)
Doesnt this become more complex ?

Secondly, this also means that one must walk the command
list at the target and quiesce connection allegiance during
logout - which may not be required if the commands were to be
retried over the same connection always.

Comments  ?

-Sandeep