FCP-2草案：SCSI协议的Fibre Channel标准修订版

2星需积分: 18 5 浏览量更新于2024-07-20 收藏 1004KB PDF 举报

FCP (Fibre Channel Protocol) 是一种在SCSI（Small Computer System Interface, 小型计算机系统接口）环境中使用的高速通信协议，其第三版（FCP-3）是针对SCSI标准的草案提案，由美国国家标准技术研究所（NCITS）的技术委员会T10制定。FCP旨在提供光纤通道（Fiber Channel）技术与SCSI设备间的高效、可靠的数据传输，以支持存储区域网络（SAN, Storage Area Network）中的设备通信。 FCP-2 Revision 8是在2002年9月23日发布的草案，作为一项美国国家标准，但强调它并非完成的标准，而是处于公开征求意见阶段。用户在使用其中提供的信息时需自行承担风险，因为可能会根据公众反馈和标准化进程进行修改。 NCITS成员和技术委员会及其相关的任务组被允许在NCITS标准化活动中复制这份文档，但必须保留此通知，并且商业或盈利性的复制是严格禁止的。该文档参考了ISO/IECxxxxx:2001和ANSINCITS.xxx:2001的相关标准。技术编辑罗伯特·斯内维利（Robert Snively）来自Brocade Communications Systems, Inc.，地址位于加利福尼亚州圣何塞市。他的联系方式包括电话和电子邮件，这表明他在这个标准制定过程中起到了关键作用。 FCP-2 Revision 8文档包含了关于光纤通道物理层、逻辑层以及与SCSI交互的详细规定，涵盖了帧结构、错误检测与恢复、事务处理、服务质量（QoS）管理等内容。该版本旨在提升数据传输的性能，包括带宽效率、延迟时间和可靠性，以满足不断增长的存储需求和业务应用对存储解决方案的高要求。 FCP-3作为SCSI标准的重要补充，对于理解现代数据中心内的高速存储架构和优化数据传输至关重要，是技术人员和系统管理员必备的参考资料。随着技术的发展和标准化进程的推进，后续修订可能会包含更多先进的特性和技术细节。

NCITS T10, Project 1144D, Revision 08 10/23/02

2 Working Draft, FCP-2

NCITS Project 1157D, SCSI Architecture Model - 2 (SAM-2)

INCITS Project 1561D, SCSI Architecure Model - 3 (SAM-3)

NCITS Project 1236D, SCSI Primary Commands - 2 (SPC-2)

NCITS Project 1416D, SCSI Primary Commands - 3 (SPC-3)

Copies of these NCITS T10 and T11 draft standards are available for purchase from Global Engineering

Documents. For further information, contact Global Engineering Documents at 800-854-7179 (phone) or 303-

792-2181 (phone) or by mail at 15 Inverness Way East, Englewood, CO 80122-5704. The NCITS T10 draft

standards are also available on the web site www.t10.org. The NCITS T11 draft standards are also available on

the web site www.t11.org.

2.4 Other references

The following references are the product of the SFF committee. For information on the current status and

availability of the documents, contact the SFF committee at 408-867-6630 (phone) or by mail at 14426 Black

Walnut Court, Saratoga, CA 95070.

SFF document SFF-8067, 40-pin SCA-2 Connector w/Bidirectional ESI

3 Definitions, abbreviations and conventions

3.1 Definitions

3.1.1 access controls: Mechanisms allowing a managing application client to control the set of initiators that

have access to a target. The access control is enforced by the target. See SPC-3.

3.1.2 access controls data: Information sent to the target by the managing application client that is used by

the target to control the set of initiators that have access to the target. See SPC-3.

3.1.3 access controls enrollment state: A state established in the target by the managing application client.

The state governs the behavior of the target in controlling the set of initiators that have access to the target. See

SPC-3.

3.1.4 acknowledged class: Any class of service that acknowledges transfers. Acknowledged classes of

service include Class 1, Class 2, and Class 4 service. See FC-FS.

3.1.5 address identifier: An address value used to identify source (S_ID) or destination (D_ID) of a frame.

See FC-FS.

3.1.6 application client: An object that is the source of SCSI commands. See SAM-2.

3.1.7 application client buffer offset: Offset in bytes from the beginning of the application client’s buffer

(data-in or data-out) to the location for the transfer of the first byte of a data delivery service request. See SAM-2.

3.1.8 autosense data: Sense data (see 3.1.51) that is returned in the FCP_RSP IU payload. See SAM-2.

3.1.9 command: A request describing a unit of work to be performed by a device server. See SAM-2.

3.1.10 command descriptor block: A structure used to communicate a command from an application client

to a device server. See SAM-2.

3.1.11 data buffer size: Upper limit on the extent of the data (data-in or data-out) to be transferred by the SCSI

command. See SAM-2.

3.1.12 data in delivery service: A confirmed service used by the device server to request the transfer of data

to the application client. See SAM-2.

3.1.13 data out delivery service: A confirmed service used by the device server to request the transfer of data

10/23/02 NCITS T10, Project 1144D, Revision 08

Working Draft, FCP-2 3

from the application client. See SAM-2.

3.1.14 data overlay: The use of random buffer access capability where data is transmitted using the same

application client buffer offset more than one time during the set of delivery actions performed by a single

command. See SAM-2.

3.1.15 Destination_Identifier: The address identifier used to indicate the destination of the transmitted frame.

See FC-FS.

3.1.16 device server: An object within the logical unit that executes SCSI tasks and enforces the rules for task

management. See SAM-2.

3.1.17 discard: The term used in FC-FS to describe removing a frame or sequence from the destination buffer

without making use of the frame or sequence and without notifying upper layers of the receipt of the frame or

sequence. See FC-FS.

3.1.18 Exchange: The basic mechanism which transfers information consisting of one or more related non-

concurrent Sequences which may flow in the same or opposite directions. The Exchange is identified by an

Originator Exchange_ID (OX_ID) and a Responder Exchange_Identifier (RX_ID). See FC-FS.

3.1.19 Execute Command service: A peer-to-peer, confirmed service requested by the application client to

perform a SCSI Command. See SAM-2.

3.1.20 FCP Exchange: A SCSI I/O Operation for the Fibre Channel FC-2 layer. The SCSI I/O Operation for

Fibre Channel is contained in a Fibre Channel Exchange. See FC-FS and 4.1.

3.1.21 FCP I/O operation: A SCSI I/O Operation for the Fibre Channel FC-4 layer, as defined in this standard.

3.1.22 FCP_Port: An N_Port or NL_Port that supports the SCSI Fibre Channel Protocol.

3.1.23 fully qualified exchange identifier: A set of addresses and values used to uniquely identify an FCP

I/O operation. See 5.1.

3.1.24 image pair: The originating and responding processes related by a Process Login operation. For the

Fibre Channel protocol, the image pair is composed of one initiator and one target. See FC-FS.

3.1.25 I_T nexus loss: A condition resulting from the events defined by SAM-3 in which the SCSI device

performs the operations described in SAM-3 and this standard.

3.1.26 I_T nexus loss event: A SCSI transport protocol specific event that triggers I_T nexus loss as

described in SAM-3.

3.1.27 Information Unit: An organized collection of data specified by the Fibre Channel protocol to be

transferred as a single Sequence by the Fibre Channel service interface. See FC-FS.

3.1.28 initiator: A SCSI device containing application clients that originate device service requests and task

management functions to be processed by a target SCSI device. In this standard, the word “initiator” also refers

to an FCP_Port using the Fibre Channel protocol to perform the SCSI initiator functions defined by SAM-2.

3.1.29 initiator identifier: Address a target uses to identify the initiator device. See SAM-2.

3.1.30 interconnect tenancy: The period of time that an FCP device owns or may access a shared Fibre

Channel link such as an FC-AL loop. See 10.2.1.

3.1.31 logical unit: A target resident entity that implements a device model and processes SCSI commands

sent by an application client. See SAM-2.

3.1.32 logical unit number: An encoded 64-bit identifier for a logical unit. See SAM-2.

3.1.33 loop initialization primitive: A primitive used in Fibre Channel arbitrated loops to start loop

NCITS T10, Project 1144D, Revision 08 10/23/02

4 Working Draft, FCP-2

initialization. See FC-AL-2.

3.1.34 Name_Identifier: A 64-bit identifier, with a 60-bit value preceded with a 4 bit Network_

Address_Authority Identifier, used to identify entities in Fibre Channel such as N_Port, Node, F_Port, or Fabric.

See FC-FS.

3.1.35 Name Server: A Fibre Channel service accessed through a well-known address identifier that uses the

Common Transfer (CT) protocol as defined in FC-GS-3 to allow a client to determine the address identifier and

properties of devices attached to a Fibre Channel switching fabric. See FC-GS-3.

3.1.36 Node_Name: A Name_Identifier associated with a Node. See FC-FS.

3.1.37 NL_Port: An N_Port that contains arbitrated loop functions associated with the Fibre Channel arbitrated

loop topology. See FC-AL-2.

3.1.38 N_Port: A hardware entity that supports the FC-FS FC-2 layer. It may act as an Originator, a

Responder, or both. See FC-FS.

3.1.39 Originator: The logical function associated with an N_Port responsible for originating an Exchange.

See FC-FS.

3.1.40 Originator Exchange Identifier: An identifier assigned by an Originator to identify an Exchange

(see 3.1.50). See FC-FS.

3.1.41 Port Identifier: An address identifier, assigned to an N_Port or NL_Port during implicit or explicit Fabric

3.1.42 Port (N_Port) Login (PLOGI): The Fibre Channel Extended Link Service (ELS) that exchanges

identification and operation parameters between an originating N_Port and a responding N_Port. See FC-FS.

3.1.43 Port_Name: A Name_Identifier associated with an N_Port or an NL_Port.

3.1.44 private loop: A loop operating with no attached fabric loop ports. See FC-PLDA.

3.1.45 public loop: A loop operating with an attached fabric loop port. See FC-FLA.

3.1.46 random buffer access: The occurrence of device server data transfer requests that request data

transfers to or from segments of the application client’s buffer with an arbitrary offset and extent. See SAM-2.

3.1.47 recovery abort: An FC-FS protocol that recovers FCP_Port resources by terminating the Exchange

and FCP I/O operation. See 12.3.

3.1.48 request byte count: The number of bytes to be moved by a data delivery service request. See SAM-2.

3.1.49 Responder: The logical function in an N_Port responsible for supporting the Exchange initiated by the

Originator in another N_Port. See FC-FS.

3.1.50 Responder Exchange Identifier: An identifier assigned by a Responder to identify an Exchange and

meaningful only to the Responder. See FC-FS.

3.1.51 sense data: Data returned to an application client as a result of an autosense operation, asynchronous

event report, or REQUEST SENSE command. See SPC-2.

3.1.52 Sequence: A set of one or more Data frames with a common Sequence_ID (SEQ_ID), transmitted

unidirectionally from one N_Port to another N_Port with a corresponding response, if applicable, transmitted in

response to each Data frame. See FC-FS.

3.1.53 Source_Identifier: The address identifier used to indicate the source port of the transmitted frame. See

FC-FS.

10/23/02 NCITS T10, Project 1144D, Revision 08

Working Draft, FCP-2 5

3.1.54 SCSI device: A device that originates or services SCSI commands. See SAM-2.

3.1.55 SCSI I/O operation: An operation defined by a SCSI command, a series of linked SCSI commands or

a task management function. See SAM-2.

3.1.56 status: A single byte returned by the device server to the application client to indicate the completion

and completion state of a command. See SAM-2.

3.1.57 tag: The initiator-specified component of a task identifier that uniquely identifies one task among the

several tasks coming from an initiator to a logical unit. The fully qualified exchange identifier performs the

function of the SCSI tag in this standard. See 5.1 and SAM-2.

3.1.58 target: A SCSI device that receives SCSI commands and directs such commands to one or more

logical units for execution. In this standard, the word “target” also refers to an FCP_Port using the Fibre Channel

protocol to perform the SCSI target functions defined by SAM-2.

3.1.59 target identifier: Address of up to 64-bits that identifies a target. See SAM-2.

3.1.60 task: An object within the logical unit representing the work associated with a command or group of

linked commands. See SAM-2.

3.1.61 task attribute: The queuing specification for a task (SIMPLE, ORDERED, HEAD OF QUEUE, ACA).

See SAM-2.

3.1.62 task identifier: The information uniquely identifying a task. See SAM-2.

3.1.63 task management function: A peer-to-peer confirmed service provided by a task manager that may

be invoked by an application client to affect the execution of one or more tasks. See SAM-2.

3.1.64 Worldwide_Name: A Name_Identifier which is worldwide unique, and represented by a 64-bit

unsigned binary value. (FC-FS)

3.2 Abbreviations

CRN Command Reference Number (See 9.1.2.2.)

D_ID Destination_Identifier (See FC-FS.)

ELS Extended Link Service (See FC-FS.)

FC Fibre Channel (See FC-FS.)

FC-AL-2 NCITS 332:1999, Fibre Channel Arbitrated Loop - 2 (See 2.2.)

FC-FLA NCITS TR-20, Fibre Channel Fabric Loop Attachment (See 2.2.)

FC-FS NCITS Project 1311D, Fibre Channel Framing and Signaling Interface (See 2.3.)

FC-GS-3 NCITS Project 1356D, Fibre Channel Generic Services - 3 (See 2.3.)

FC-PLDA NCITS TR-19, Fibre Channel Private Loop, SCSI Direct Attach (See 2.2.)

FC-TAPE NCITS TR-24:1999, Fibre Channel - Tape Technical Report (See 2.2.)

FCP X3.269-1996, Fibre Channel Protocol for SCSI (See 2.2.)

Also: referring both to FCP and to this standard

FCP-2 This standard (Fibre Channel Protocol for SCSI, second version.)

FC-4 Fibre Channel Layer 4 mapping layer. (See FC-FS.)

NCITS T10, Project 1144D, Revision 08 10/23/02

6 Working Draft, FCP-2

FLOGI Fabric Login Extended Link Service. (See FC-FS.)

FQXID fully qualified exchange identifier (See 3.1.23.)

ID identifier

IU Information Unit (See FC-FS.)

LIFA loop initialization fabric assigned, a step of the loop initialization sequence

(See FC-AL-2.)

LIHA loop initialization hard assigned, a step of the loop initialization sequence

(See FC-AL-2.)

LIP loop initialization primitive (See FC-AL-2.)

LIPA loop initialization previously assigned, a step of the loop initialization sequence

(See FC-AL-2.)

LISA loop initialization soft assigned, a step of the loop initialization sequence

(See FC-AL-2.)

LISM loop initialization select master, a step of the loop initialization sequence

(see FC-AL-2.)

LOGO Log Out Extended Link Service (See FC-FS.)

NA Not Applicable

OX_ID Originator Exchange Identifier (See FC-FS.)

PLOGI Port (N_Port) Login Extended Link Service (See FC-FS.)

RX_ID Responder Exchange Identifier (See FC-FS.)

SAM-2 NCITS Project 1157D, SCSI Architecture Model - 2 (See 2.3.)

SAM-3 INCITS Project 1561D, SCSI Architecture Model - 3 (See 2.3.)

SCSI Small Computer System Interface, any revision.

SCSI-3 Small Computer System Interface-3, the SCSI architecture specified by SAM-2

and extended by the companion standards referenced in SAM-2.

S_ID Source_Identifier (See FC-FS.)

SPC-2 NCITS Project 1236D, revision 14, SCSI Primary Commands - 2 (See 2.3.)

ULP upper layer protocol (See FC-FS.)

3.3 Keywords

3.3.1 expected: A keyword used to describe the behavior of the hardware or software in the design models

assumed by this standard. Other hardware and software design models may also be implemented.

3.3.2 invalid: A keyword used to describe an illegal or unsupported bit, byte, word, field or code value.

Receipt of an invalid bit, byte, word, field or code value shall be reported as error.

3.3.3 ignored: A keyword used to describe a bit, byte, word, field or code value that shall not be examined

by the receiving SCSI device. The bit, byte, word, field or code value has no meaning in the specified context.

3.3.4 mandatory: A keyword indicating an item that is required to be implemented as defined in this standard.

3.3.5 may: A keyword that indicates flexibility of choice with no implied preference (equivalent to “may or may

剩余146页未读，继续阅读

laiwg1234

粉丝: 0
资源: 5

FCP-2草案：SCSI协议的Fibre Channel标准修订版

FCP-3: Fibre Channel Protocol for SCSI详细规范

FCP-3：SCSI标准的光纤通道协议第三版草案

详述光纤接口硬盘通信：SCSI3协议解析

Fibre Channel Protocol for SCSI, Third Version

Design and Implementation of a Fibre Channel Target

NetBackup 52xx and 5330 Appliance Fibre Channel Guid

NetBackup_Appliance_Fibre_Channel_Guide_511.pdf

NetBackup_Appliance_Fibre_Channel_Guide_50.pdf

zfcp_scsi.rar_interface_scsi

vnic_scsi.rar_V2

最新资源