|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: iSCSI - Response/StatusThanks Elliot - I am not sure that we have it closed we may have to rearrange things. There is nothing to convey the fact that this was an error originated in iSCSI at the target and the detailed nature of the error (we had this in the iSCSI response, now we might have to add this information to sense. Julo "Elliott, Robert" <Robert.Elliott@compaq.com>@ece.cmu.edu on 10-08-2001 13:03:57 Please respond to "Elliott, Robert" <Robert.Elliott@compaq.com> Sent by: owner-ips@ece.cmu.edu To: ips@ece.cmu.edu cc: Subject: RE: iSCSI - Response/Status I would call out those additional sense codes by name rather than number (perhaps both). The sense key(s) to be used also need to be listed. Status=CHECK CONDITION Sense Key= additional sense code (ASC+ASCQ)= -- Robert.Elliott@compaq.com Compaq Computer Server Storage -----Original Message----- From: Julian Satran [mailto:Julian_Satran@il.ibm.com] Sent: Thursday, August 09, 2001 6:34 PM To: ips@ece.cmu.edu Subject: iSCSI - Response/Status According to the discusions on the list 2.4.2 & 2.4.3 have been fixed to read: 1.1.1 Status The Status field is used to report the SCSI status of the command (as specified in [SAM2]) and is valid only if the Response Code is Command Completed at target. If a SCSI device error is detected while data from the initiator is still expected (the command PDU did not contain all the data and the target has not received a Data PDU with the final bit Set) the target MUST wait until it receives the a Data PDU with the F bit set, in the last expected sequence, before sending the Response PDU. 1.1.2 Response This field contains iSCSI service response. Valid iSCSI service response codes are: 0x00 - Command Completed at Target 0x01 - Target Failure 0x02 - Delivery Subsystem Failure 0x80-0xff - Reserved for Vendor-Unique Responses The Response is used to report a Service Response. The exact mapping of the iSCSI response codes to SAM service response symbols is outside the scope of this document. Certain iSCSI conditions result in the command being terminated at the target (response Command Completed at Target) with a SCSI Check Condition Status as outlined in the next table: +------------------------------+---------------------------+ | Reason | with SCSI CHECK CONDITION | +------------------------------+---------------------------+ | Unsolicited data rejected | ASC = 0x49 ASCQ = 0x00 | +------------------------------+---------------------------+ | Not enough unsolicited | ASC = 0x4B ASCQ = 0x00 | +------------------------------+---------------------------+ | SNACK rejected | ASC = 0x47 ASCQ = 0x03 | +------------------------------+---------------------------+ N.B. Unsolicited data rejected condition is reported used by the target only if it does not support output (write) operations in which the total data length is higher than FirstBurstSize but the initiator sent less than first burst size and out-of-order R2Ts can't be used. Julo
Home Last updated: Tue Sep 04 01:04:02 2001 6315 messages in chronological order |