FIBRE CHANNEL - T11
FIBRE CHANNEL - T11
FIBRE CHANNEL - T11
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
TR-xx-1998 Fibre Channel Tape Rev 1.07 August 7, 1998<br />
8.2 FCP Information Units<br />
From a SCSI Initiator to a SCSI Target, the T1 (CMD/Task Mgmt with SI transferred), and T6 (Write<br />
Data with SI transferred) are required and the T12 (Confirm with SI held) is optional. Devices that implement<br />
linking shall also support the T3 (CMD/Task Mgmt) Information Unit. All other SCSI Initiator<br />
to SCSI Target IUs are prohibited.<br />
From a SCSI Target to a SCSI Initiator, the I1 (FCP_XFER_RDY on Write), I3 (Read Data), I4<br />
(FCP_RSP) are required. Devices that implement SCSI linking shall also support the I5 (FCP_RSP)<br />
Information Unit. All other SCSI Target to SCSI Initiator IUs are prohibited. SCSI Targets shall respond<br />
to Task Management functions using I4. Examples of write and read type operations are<br />
shown in Figure 2.<br />
WRITE CMD<br />
READ CMD<br />
T1<br />
FCP_CMND<br />
T1<br />
FCP_CMND<br />
FCP_XFER_RDY<br />
I1<br />
DATA<br />
T6<br />
T6<br />
Single Sequence<br />
Single Sequence<br />
T12<br />
DATA<br />
DATA<br />
DATA<br />
FCP_XFER_RDY<br />
DATA<br />
DATA<br />
DATA<br />
FCP_RSP<br />
FCP_CONF<br />
(optional)<br />
I1<br />
I4<br />
DATA<br />
DATA<br />
DATA<br />
DATA<br />
DATA<br />
FCP_RSP<br />
FCP_CONF<br />
(optional)<br />
Single or Multiple Sequences<br />
I3<br />
I3<br />
I4<br />
T12<br />
8.2.1 FCP_CMND IU (T1/T3)<br />
Figure 2 — FCP Read/Write IU Examples<br />
The T1/T3 Information Unit shall be a Single-Frame Sequence.<br />
SCSI Targets that report a peripheral device type of Array Controller (hex ’C’) shall conform to the SCC defined<br />
LUN addressing mechanism. Other SCSI Targets shall address the LUNs using the “first level addressing”<br />
field of SCC (reference [9]) with “peripheral device addressing method” (00b) as shown in figure 3, unless<br />
they report a different LUN addressing mechanism in response to a Report LUN command. For example:<br />
Figure 3 — FCP 8-byte LUN<br />
Byte 0 Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7<br />
00 LUN 00 00 00 00 00 00<br />
35