Re: iSCSI: Response codes in SCSI Response Command

[julian_satran@il.ibm.com]

Unfortunately there is no such standard and every OS has it's own way of
handling response codes.

Julo

"Sanjeev Bhagat (TRIPACE/Zoetermeer)" <sbhagat@tripace.com> on 11-06-2001
19:10:26

Please respond to "Sanjeev Bhagat (TRIPACE/Zoetermeer)"
      <sbhagat@tripace.com>

To:   Julian Satran/Haifa/IBM@IBMIL, "'ISCSI'" <ips@ece.cmu.edu>, "'Mark
      Bakke'" <mbakke@cisco.com>, "'Ralph Weber'"
      <ralphoweber@compuserve.com>
cc:
Subject:  iSCSI: Response codes in SCSI Response Command




Current definition states

2.4.2 Status/Response

The Status field is used to report the SCSI status of the command (as
specified in [SAM2]). 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. 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 before sending the Response PDU.

Valid iSCSI Response codes are:

0x01 - Target Failure

0x02 - Delivery Subsystem Failure

0x03 - Unsolicited data rejected

0x04 - SNACK rejected

0x80-0xff - Reserved for Vendor-Unique Responses



DONT YOU THINK that these response codes be actually mapped in SAM document
and be made as standard to be followed by any protocol. So iSCSI should
also
report the same responses as defined in SAM document.

Regards,

Sanjeev




 - att1.htm