Re: iSCSI: Out Of Sequence due to null sequence with multiple connections.

[Matt Wakeley <matt_wakeley@agilent.com>]

In simple terms, what Doug is asking for in (B) is an "immediate" command that
will go and abort all pending commands in the iSCSI queue that have not yet
been delivered to the SCSI layer due to missing commands sequence numbers.

I'm wondering how useful this is.  The initiator could simply look at the
ExpCmdSN from the target and resend the missing command(s) if the target
appears to be "stuck".  Given the way TCP works, the only time the target
could get "stuck" is if a TCP connection fails.  In which case the connection
would be re-established and the missing commands resent.

-Matt