FC-4 (FCP) Features
96122 • Revision: F Chapter 5 Fibre Channel Operations 75
TABLE 5-23 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 will 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 will release Exchange information such as the Exchange Status Block
(ESB) after the FCP_CONF is sent. The target will 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.
The following lists each command and its supported usage of requesting an
FCP_CONF:.
TABLE 5-23 FCP_RSP Code
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
No confirm The library will not set the FCP_CONF_REQ bit in the response to the
command. As soon as the response has been transmitted, the exchange is
terminated, and there is no FCP-2 Link Level error recovery possible.
Implicit confirm The library does not set the FCP_CONF_REQ bit in the response to the
command. However, the exchange is not terminated until the same
initiator sends the next command or until the Resource Recovery timer
expires on this exchange. This will allow the initiator to do FCP-2 Link
Level error recovery, if necessary, before sending the next command.
Explicit confirm The library will set the FCP_CONF_REQ bit in the response to a command
if the condition in this column is met. This will allow the initiator to do
FCP-2 Link Level error recovery, if necessary, before sending the
FCP_CONF. If the initiator does not support FCP_CONF, as indicated in its
PRLI payload, then the library will not set the FCP_CONF_REQ bit,
regardless of the condition being met. But the library will treat it as an
Implicit Confirm condition.
To Next Page
Loading...
Need help?
General
