ANSI INCITS TR-16-1997 Information Technology SCSI-3 Generic Packetized Protocol (SCSI-GPP)《信息技术.SCSI-3通用封包化协议(SCSI-GPP)》.pdf

1、INCITS TR-16-1997Information Technology SCSI-3 Generic Packetized Protocol (SCSI-GPP)Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-X3/TR-16-1997 Revision 9 of X3-991 D X3 Techn

2、ical Report - Small Computer System Interface - 3 Generic Packetized Protocol (SCSI-GPP) Secretariat Computer and Business Equipment Manufacturers Association Abstract SCSI-3 Generic Packetized Protocol (SCSI-3 GPP) defines a transport protocol that per- mits an inter-operable common mapping of the

3、Small Computer System Interface - 3 (SCSI-3) functions to several physical interfaces that do and do not have a native SCSI-3 protocol mapping. In support of such heterogeneous sytems environments (e.g., SCSI-3 parallel interface, Fibre Channel, and Internet), some implementors may choose to use GPP

4、 as an alternate protocol to provide common software and transportation services across several interfaces. Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-X3s Technical Report S

5、eries This Technical Report is one in a series produced by the Accredited Standards Committee, X3, Information Technology. The Secretariat for X3 is held by the Information Technology Industry Council (ITI), 1250 Eye Street, NW, Suite 200, Washington, DC 20005. As a by-product of the standards devel

6、opment process and the resources of knowledge devoted to it, X3 from time to time produces Technical Reports. Such Technical Reports are not standards, nor are they intended to be used as such. X3 Technical Reports are produced in some cases to disseminate the technical and logical con- cepts reflec

7、ted in standards already published or under development. In other cases, they derive from studies in areas where it is found premature to develop a standard due to a still-changing technology, or inappropriate to develop a rigorous standard due to the existence of a number of viable options, the cho

8、ice of which depends on the users particular requirements. These Technical Reports, thus, provide guidelines, the use of which can result in greater consistency and coherence of information processing systems. When the draft Technical Report is completed, the Technical Committee approval process is

9、the same as for a draft standard. Processing by X3 is also similar to that for a draft standard. CAUTION: The developers of this technical report have requested that holders of patents that may be required for the implementation of the technical report disclose such patents to the publisher. However

10、, neither the developers nor the publisher have undertaken a patent search in order to identify which, if any, patents may apply to this technical report. As of the date of publication of this technical report, following calls for the identification of patents that may be required for the implementa

11、tion of the technical report, notice of one or more such claims has been received. By publication of this technical report, no position is taken with respect to the validity of this claim or of any rights in connection therewith. The known patent holder(s) has (have), however, filed a statement of w

12、illingness to grant a license under these rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain such a license. Details may be obtained from the publisher. No further patent search is conducted by the developer or publisher in respect to any technical repor

13、t it processes. No representation is made or implied that this is the only license that may be required to avoid infringement in the use of this technical report. Published by American National Standards Institute 11 West 42nd Street, New York, New York 10036 Copyright 01 997 by American National St

14、andards Institute All rights reserved. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without prior written permission of the publisher. Printed in the United States of America Copyright American National Standards Institute Provided by IHS

15、 under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SCSI-3 GPP REV 9. January 12. 1995 Contents Page Foreword ix Introduction . 1 Scope 1 1.1Application 1 1.2 Structure . 2 1.3 Relationship to standards 2 2References 5 5 3 Definitions. abbreviat

16、ions and symbols 7 3.1 Definitions 7 3.2 Abbreviations and symbols 9 4General 12 4.1Overview 12 4.2Convention.s . 12 4.3 Logical system description 13 4.4 Description of logical operations . 13 4.5 Statement of support for SAM requirements 16 4.6 Logical system model 16 I Copyright American National

17、 Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SCSI-SCSI-3 GPP REV 9. January 12.1995 4.7 Mandatory requirements 20 5 GPP Tasks and Task management . 22 5.1.1 Parameter requirements (mandatory) . 22 5.1.2

18、 Task sense data (mandatory) 23 5.1.3 GPP identification (mandatory) . 23 5.1.3.2 Target identification (mandatory) 24 5.1 -3.4 GPP port number (mandatory) 24 5.1.4 Commands (mandatory) 24 5.1.5 Status (mandatory) . 25 5.2 Task Set management (mandatory) 26 5.3 Task termination (mandatory) . 27 5.3.

19、1 Normal Task termination 28 5.3.2 Abnormal Task termination 28 5.3.2.1 Initiator-caused Task termination 28 5.3.2.2 Target-caused Task termination . 28 5.4 Assignment termination (mandatory) . 28 5.5 Path group operations . 28 5.5.1 Single path mode (mandatory) . 28 5.5.2 Multiple path mode (option

20、al) . 29 5.5.3 Single path status (mandatory) . 29 5.5.4 Multiple path status (optional) 29 5.5.5 Path group disbanding (optional) 29 5.1Tasks 22 5.1.3.1 Initiator identification (mandatory) . 23 5.1.3.3 GPP address for a port (mandatory) . 24 5.1.3.5 Logical unit identification (mandatory) 24 5.1.6

21、 Asynchronous Event Notification (mandatory) . 25 5.1.7 Auto-Contingent Allegiance (mandatory) . 26 6 GPP Information Packet structure . 30 6.1 Information Packet layout 30 6.2 Interface control prefix . 31 6.3.1 Message ILE 36 6.3 Interface Logical Elements (ILEs) 35 6.3.2 Command descriptor block

22、ILE . 36 6.3.3 Command parameter data ILE . 37 6.3.4 Command response data ILE 37 6.3.5 Logical data ILE . 37 6.3.6 Status ILE 37 6.3.7 Autosense ILE 37 7 GPP task control 39 7.1 Message structure 40 7.2 GPP primary messages 43 7.2.1 ABORT TASK . 43 7.2.2 ABORT TASK SET . 43 7.2.3ASSlGN 43 ii Copyri

23、ght American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SCSI-3 GPP REV 9. January 12. 1995 7.2.3.1 Extent assignment 46 7.2.3.2 Element assignment 48 7.2.3 CLEAR ACA 49 7.2.4 CLEAR TASK SET .

24、49 7.2.5 CONTROL ACCESS 50 7.2.6 EXTENDED MESSAGE REJECT . 52 7.2.7 INVALID INFORMATION PACKET 54 7.2.8 LINKED COMMAND COMPLETE . 55 7.2.9 LINKED COMMAND COMPLETE (WITH FLAG) . 55 7.2.10 MODIFY DATA POSITION 55 7.2.1 1 PACKET TRANSFER REQUEST 56 7.2.12 REPORT PATH STATUS . 58 7.2.1 4 RESEND PREVIOUS

25、 INFORMATION PACKET 60 7.2.1 5 SET WWN . 61 7.2.1 6 TARGET RESET 64 7.2.1 7 TASK COMPLETE 65 7.2.1 8 TASK WAITING . 65 7.2.1 9 TERMINATE TASK 66 7.2.20 UNASSIGN 67 8 GPP services for a logical element 70 8.1 GPP services introduction 70 8.1.1 Logical element-to-GPP services introduction . 70 8.1.2 G

26、PP services-to-SDS introduction . 70 8.2 GPP-device-to-GPP services 71 8.2.1 GPP-TASK.reque.9 72 8.2.1.1 Semantics . 72 8.2.1.2 When generated . 74 8.2.1.3 Effect of receipt 74 8.2.1.4 GPP-TASK.request parameter usage 75 8.2.1.5 Task-Element-List parameter usage . 76 8.2.1.6 Element-Descriptor param

27、eter usage 78 8.2.1.7 ScatterIGather List (SG-LIST) parameter usage 82 8.2.2 GPP-TASK-TAG.indication 82 8.2.2.1 Semantics . 82 8.2.2.2 When generated . 83 8.2.2.3 Effect of receipt 83 8.2.2.4 GPP services managed parameters 83 8.2.3 GPP-TASK.indication . 83 8.2.3.1 Semantics . 83 8.2.3.2 When genera

28、ted . 84 8.2.3.4 Effect of receipt 84 8.2.3.5 GPP services managed parameters 84 8.2.3.6 GPP-TASK.indication semantics 85 8.2.4 GPP-TASK.confirmation 87 8.2.4.1 Semantics . 87 8.2.4.2 When generated . 87 8.2.4.3 Effect of receipt 87 8.2.4.4 GPP services managed parameters 87 8.3 GPP services-to-SDS

29、88 ANNEXA 89 A.l Fibre Channel definitions for GPP 89 A.2 Fibre Channel specific messages 91 A.3 Fibre Channel physical description for GPP 92 A.4 FC-PH encapsulation of an Information Packet . 93 iii Copyright American National Standards Institute Provided by IHS under license with ANSINot for Resa

30、leNo reproduction or networking permitted without license from IHS-,-,-SCSI-SCSI-3 GPP REV 9. January 12. 1995 A.4.1 Information unit 93 A.4.2 FC-PH Information Unit management 94 A.4.3 GPP FC-PH responses and signals . 94 AS GPP services to FC-PH Information Unit services . 95 A.5.1 FC-PH-SEQUENCE.

31、request 96 A.5.1.1 Semantics 96 A.5.1.2 When generated . 96 A.5.1.3 Effect of receipt 96 A.5.1.4 Function parameter usage . 97 A.5.1.5 FC-PH managed parameters . 99 A.5.2 FC-PH-SEQUENCETAG.indication . 99 A.5.2.1 Semantics 99 A.5.2.2 When generated 100 A.5.2.3 Effect of receipt . 100 A.5.2.4 FC-PH m

32、anaged parameters 100 A53 FC-PH-SEQUENCE.indication . 100 A.5.3.1 Semantics . 100 A.5.3.2 When generated 101 A.5.3.3 Effect of receipt . 101 A.5.3.4 FC-PH managed parameters 102 A.5.4 FC-PH-SEQUENCE.confirmation . 103 A.5.4.1 Semantics . 103 A.5.4.2 When generated 103 A.5.4.3 Effect of receipt . 103

33、 A.5.4.4 FC-PH managed parameters 103 A.6FC-PHevents . 104 A.6.1 FC-PH unexpected disconnect event . 104 A.6.2 FC-PH unsuccessful Information Unit transfer event . 104 A.6.3 FC-PH unsuccessful Information Packet transfer condition . 104 ANNEXB . 106 B.l Introduction to the GPP FC-4 Exchange protocol

34、 106 B.2 GPP FC-PH Exchange protocol 108 8.2.1 FC-PH Information Units . 108 8.2.2FC-PHExchanges 108 8.2.3 Transport layer independence 109 ANNEXC . 111 C.l SPI physical description 111 C.2 SPI specific messages . 112 C.2.1 INVALID BUS PHASE DETECTED 113 C.2.2 PARITY ERROR . 114 C.2.3 SYNCHRONOUS DA

35、TA TRANSFER REQUEST . 115 C.3 GPP services to SPI information tra.nsfer services . 116 C.3.1 SPlSEQUENCE.request 117 C.3.1.1 Semantics . 117 C.3.1.2 When generated 118 C.3.1.3 Effect of receipt . 118 C.3.1.4 Function parameter usage 118 C.3.1.5 SPI managed parameters 119 C.3.2 SPI-SEQUENCETAG.indica

36、tion 119 C.3.2.1 Semantics . 119 C.3.2.2 When generated 119 C.3.2.3 Effect of receipt . 119 C.3.2.4 SPI managed parameters 119 C.3.3 SPI-SEQUENCE.indication 119 iv Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permi

37、tted without license from IHS-,-,-SCSI-3 GPP REV 9. January 12.1995 C.3.3.1 Semantics . 120 C.3.3.2 When generated . 120 C.3.3.3 Effect of receipt . 120 C.3.3.4 SPI managed parameters . 120 C.3.4 SPI-SEQUENCE.confirmation 121 C.3.4.1 Semantics . 121 C.3.4.1 When generated 121 C.3.4.2 Effect of recei

38、pt . 121 C.3.4.3 SPI managed parameters . 121 C.4.1 SPI BUS FREE phase . 122 C.4.2 SPI ARBITRATION phase 122 C.4.3 SPI SELECTION phase 122 C.4.4 SPI SELECTION time-out procedure . 123 C.4.4.1 SPI asynchronous information transfer (mandatory) 123 C.4.4.2 SPI synchronous data transfer (mandatory) 123

39、C.4.4.3 SPI wide data transfer (mandatory) . 123 C.4.5 SPI DATA OUT information transfer phase 123 C.4.6 GPP versus SIP operating mode . 124 C.4 GPP implemented SPI bus phases 122 C.5 SPI events . 125 C.5.1 SPI attention event 125 C.5.2 SPI reset event . 126 C.5.3 SPI disconnect event 126 ANNEXD . 1

40、28 D.l Operation notes . 128 D.2 Application examples . 128 D.2.1 Migration to new interfaces . 129 D.2.2 High availability environments . 129 D.2.3 Processor-type clusters 129 D.2.4 Third-party operations . 129 AnnexE 130 E.l IP specific messages . 130 E.3 TCP/IP services . 131 E.4 TCP/IP support o

41、f SAM . 131 E.4.1 IP header 132 E.4.2 TCP header 132 E.4.3 TCP/IP header overhead 133 E.5 Service interface from GPP to TCP/IP 133 E.2 Encapsulation of an information packet 131 AnnexF 134 F.1 Error Management . 134 F.2 The value of the sliding window . 135 F.3Performance 136 Annex G 137 G.l HIC def

42、initions for GPP . 137 (3.2 HIC specific messages . 138 G.3 HIC physical description for GPP . 138 G.3.1 Destination ID assignment and Destinations . 138 G.3.2 No acknowledgement of packet delivery 139 (3.3.3 Order of delivery of packet contents 139 G.3.4 Order of delivery of independent packets 139

43、 G.3.5 Relationship of a packet to an Information Packet . 140 V Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-SCSI-SCSI-3 GPP REV 9. January 12. 1995 G.3.6 Managing the order

44、of execution of commands with HIC . 140 G.3.7 Simple GPP service delivery subsystem with HIC 141 G.4 HIC encapsulation of an Information Packet 142 G.4.1 HIC packet 142 G.4.2 Information Packet management 143 G.5 GPP services to HIC Link Level services . 143 G.5.1 HIC-PACKET.request . 143 G.5.1.1 Se

45、mantics . 144 G.5.1.2 When generated 144 (3.5.1.3 Effect of receipt . 144 G.5.1.4 Function parameter usage 144 G.5.1.5 LL managed parameters . 145 G.5.2 HIC-PACKET.indication . 145 G.5.2.1 Semantics . 145 G.5.2.2 When generated 145 G.5.2.3 Effect of receipt . 145 G.5.2.4 LL managed parameters . 146

46、G.5.3 HIC-PACKET.confirmation . 146 G.5.3.1 Semantics . 146 G.5.3.2 When generated 146 G.5.3.3 Effect of receipt . 146 G.5.3.4 LL managed parameters . 146 G.6 HIC events . 147 G.6.2 LL unexpected disconnect event 147 66.3 LL unsuccessful Information Packet transfer condition . 147 G.4.3 HIC response

47、s and signals . 143 AnnexH 148 H.l Introduction to the GPP HIC packet protocol 148 H.2 GPP transaction protocol . 149 H.2.2 Transport layer independence 149 H.2.1 HIC packets . 149 Annex1 . 150 1.1 ATM specific messages . 150 1.3 ATM error control . 151 1.4ATMservices 151 1.5 ATM support of SAM 152

48、1.6 Service interface from GPP to ATM 152 1.2 ATM encapsulation of an information packet . 151 AnnexJ 154 J.l GPP use of ATM . 154 J.2 Error Management . 155 vi Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitte

49、d without license from IHS-,-,-SCSI-3 GPP REV 9. January 12. 1995 Tables Page Table 1 . Information Packet Structure . 30 Table 2 . Interface Control Prefix Fields 31 Table 3 . Interface Logical Element (ILE) . 35 Table 4 . Element Type Codes . 36 Table 6 . Message Format Codes 40 Table 7 . Extended Message Format 41 Table 8 . Extended Message Codes 42 Table 9 . ASSIGN message format . 45 Table 10 . Exten