RE: iSCSI: Response codes in SCSI Response Command

["Elliott, Robert" <Robert.Elliott@compaq.com>]

SPI-4, FCP-2, SRP, and SST do agree on these values:
0 - task management function complete
1 - FCP specific
2 - command IU/request fields invalid
3 - FCP specific
4 - task management function not supported
5 - task management function failed
6+ - protocol specific

It's too late to try to force any more commonality, as those standards
already exist.

iSCSI has separate command response and task management response IUs (PDUs),

making it a bit different from the other protocols.
 
---
Rob Elliott, Compaq Server Storage
Robert.Elliott@compaq.com




-----Original Message-----
From: Sanjeev Bhagat (TRIPACE/Zoetermeer) [mailto:sbhagat@tripace.com]
Sent: Monday, June 11, 2001 11:10 AM
To: 'Julian Satran'; 'ISCSI'; 'Mark Bakke'; 'Ralph Weber'
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