Re: iSCSI Target Reset

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

Absolutely not,  Why would we think that impacting 32 different other
initiators is an OK thing to do.  By the way there are lots more Initiators
possible with FC on Shark, and would hope that there would be even more
with iSCSI.

I have been told that these large Storage Controllers do not support Target
Reset today.  So I see no loss in not supporting such an item in iSCSI
especially since many Initiators will be beyond even the distances and
mischief that is possible with FC.

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


Santosh Rao <santoshr@cup.hp.com>@ece.cmu.edu on 04/23/2001 01:24:02 PM

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


To:   ips@ece.cmu.edu
cc:
Subject:  Re: iSCSI Target Reset



"Dillard, David" wrote:
>
> When will STORPORT be generally available?  The latest STORPORT document
> that I found on the MS web site is version 0.6a, dated March 18, 2001.
> Given this it seems like STORPORT might not be available soon.  In that
case
> do you know what happens with the current drivers?  Are we going to be
> telling customers that if they want to use iSCSI and NT clustering they
have
> to update to Whistler?


[One would hope that this list does not turn into a Microsoft
release/product discussion mailing list (?) ]

Without going into specifics of A certain O.S., does it suffice to
require that iSCSI not break existing legacy SCSI applications ?

If the above is a valid requirement, then, knowing that legacy
applications continue to use SCSI-2 Reserve/Release and the target reset
as a mechanism of breaking SCSI-2 reservations, should'nt iSCSI continue
to support the target reset ?

- Santosh