Sun Oracle Storage Tek T10000, Reference Manual

Page: 70 / 296

FCP Information Units
52 T10000: Interface Reference Manual • January 2011 • E20425-01
• Table 29 indicates the result of a Task Management function in the
RSP_CODE of the FCP_RSP_INFO fields.
The FCP_CONF IU is used by the Target to confirm reception of an FCP_RSP
IU at the initiator. Support for the FCP_CONF IU is negotiated via PRLI. A
Target request for an FCP_CONF IU from the initiator is indicated by the
Target setting the FCP_CONF_REQ bit in the FCP_STATUS field contained in
the FCP_RSP. If the initiator does not need to perform any error detection or
recovery procedure, the initiator shall send an FCP_CONF IU if an FCP_RSP
is received with the FCP_CONF_REQ bit set in the FCP_STATUS field.
The initiator shall release Exchange information such as the Exchange Status
Block (ESB) after the FCP_CONF is sent. The Target shall retain Exchange
information and associated data until an FCP_CONF is received. See FCP-2
(4.4 Confirmed Completion of FCP-2 SCSI Commands) for a description of
the FCP_CONF_REQ bit and FCP_CONF usage.
If the initiator supports FCP_CONF as indicated in it’s PRLI page load, the
drive will always set the FLP_CONF_REG bit.
Task Management Flags and Information Units
All SCSI Initiators send Task Management functions using T1.
All SCSI Targets return FCP_RSP to Task Management functions using I4.
The RSP_CODE in the FCP_RSP_INFO field indicates the result of the Task
Management function. The SCSI Status byte and FCP_SNS_INFO are
ignored for I4 information units sent in response to a Task Management
function.
Table 29. FCP_RSP Codes
RSP_CODE Description
00 No failure or Task Management complete
01 FCP_DATA length different than BURST_LEN
02 FCP_CMND fields invalid
03 FCP_DATA RO mismatch with FCP_XFER_RDY DATA_RO
04 Task Management function not performed or supported
05 Task Management function supported but not performed
06–FF Reserved