Re: Target Reset handling

["Mallikarjun C." <cbm@rose.hp.com>]

Julian,

I was thinking that the C-bit would go into bytes 2/3 (currently
reserved) of the SCSI Task Management Command PDU (as defined in 
section 3.7 of draft-satran-iscsi-01.txt) - which does not have
a CDB.  So, I guess it's part of the iSCSI protocol headers, as
you were suggesting.

Thanks.
--
Mallikarjun 
M/S 5601			
Networked Storage Architecture
HP Storage Organization
Hewlett-Packard, Roseville.
cbm@rose.hp.com


>Mallikarjun,
>
>Is the C bit hidden in the CDB? We as a rule avoided examining the CDB
>(iSCSI never has to). If we can make it external then we are in wild
>agreement.
>
>Regards,
>Julo
>
>"Mallikarjun C." <cbm@rose.hp.com> on 05/09/2000 20:03:56
>
>Please respond to cbm@rose.hp.com
>
>To:   ips@ece.cmu.edu
>cc:    (bcc: Julian Satran/Haifa/IBM)
>Subject:  Re: Target Reset handling
>
>
>
>
>Julian,
>
>Thanks for the suggestion.
>
>I am in broad agreement with this kind of definition, if the
>rest of the folks accept it.  I would however suggest a single
>Target Reset task management function (in accordance with SAM-2),
>and provide the choice of a "cold-reset" with a "C" bit in the
>Task Management Command PDU.  Assuming that we do this, let me
>try to summarize our tentative agreement:
>
>o Target Reset task management requires a response, unless the
>  the C-bit is set in which case the sessions would be terminated
>  as well and no response can be expected.
>
>o A Unit Attention AER shall be reported to all currently logged-in
>  initiators, in accordance with the provisions contained in clauses
>  7.9 and 8.3.6 of SPC-2 (basically, to be reported only if agreed
>  in advance between the initiator and the LU).
>
>Regards.
>--
>Mallikarjun
>M/S 5601
>Networked Storage Architecture
>HP Storage Organization
>Hewlett-Packard, Roseville.
>cbm@rose.hp.com
>
>
>
>>Mallikarjun,
>>
>>How about having two different function:
>>
>>target warm-reset (connections stay) and target cold-rest (connections get
>>also reset)?
>>
>>Julo
>>