ANSI INCITS 296-1997 Information Technology - Single-Byte Command Code Sets Connection (SBCON) Architecture.pdf

1、I ANSI INCITS 296-1 997 (R2002) (formerly ANSI X3.296-1997) for Information Technology - Single-Byte Command Code Sets CONnection (SBCON) Architecturt ? Developed by Where IT all begins ANSI X3.296-1997 American National Standard for Information Technology - Sngle-Byte Command Code Sets CON nection

2、(SBCON) Architect u re Secretariat Information Technology Industry Council Approved March 12, 1997 American National Standards Institute, Inc. Abstract This standard describes an input/output (/O) and interconnection architecture including specification of fiber optic links, switched point-to-point

3、topology, and /O protocols for high bandwidth, high perfor- mance and long distance information exchange. Approval of an American National Standard requires review by ANSI that the requirements for due process, consensus, and other criteria for approval have been met by the standards developer. Cons

4、ensus is established when, in the judgment of the ANSI Board of Standards Review, substantial agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and o

5、bjections be considered, and that a concerted effort be made toward their resolution. The use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or u

6、sing products, processes, or procedures not conforming to the standards. The American National Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an inter

7、pretation of an American National Standard in the name of the American National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or

8、 withdrawn at any time. The procedures of the American National Standards Institute require that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards may receive current information on all standards by calling or writing the American

9、National Standards Institute. American National CAUTION: The developers of this standard have requested that holders of patents that may be required for the implementation of the standard disclose such patents to the publisher. However, neither the developers nor the publisher have undertaken a pate

10、nt search in order to identify which, if any, patents may apply to this standard. As of the date of publication of this standard, following calls for the identification of patents that may be required for the implementation of the standard, notice of one or more such claims has been received. By pub

11、lication of this standard, 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 willingness to grant a license under these rights on reasonable and nondiscriminatory terms and co

12、nditions 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 standard it processes. No representation is made or implied that this is the only license that may be required t

13、o avoid infringement in the use of this standard. Published by American National Standards Institute 11 West 42nd Street, New York, New York 10036 Copyright O1 997 by Information Technology Industry Council (ITI) All rights reserved. No part of this publication may be reproduced in any form, in an e

14、lectronic retrieval system or otherwise, without prior written permission of ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of America Contents Page Foreword . Introduction . xv 1 Scope . 1 2.1 Approved references . 1 2 Normative references . 1 2.2 Other References 3 3 D

15、efinitions and conventions . 3 3.1 Definitions 3 3.2 Editorial conventions 10 3.2.1 Binary notation 11 3.2.2 Hexadecimal notation 11 Abbreviations, acronyms and symbols 11 3.3.1 Acronyms and other abbreviations 11 3.3.2 Symbols 12 4 I/O interface overview . 13 4.1 Channel-path elements . 13 4.1.1 Ch

16、annel 13 4.1.3 Control unit . 14 4.1.4 Dynamic switch 14 4.1.5 pynamic-switch control unit . 15 4.1.6 Link-level facility 16 4.2 Channel-path configurations 16 4.2.1 Point-to-point configuration . 16 4.2.2 Switched-point-to-point configuration 17 4.2.3 Physical path . 18 4.2.4 Logical path . 18 4.3

17、Information formats . 19 4.4 Protocols 19 4.4.1 Link-level . 20 4.4.2 Device-level . 21 4.4.3 Addressing 21 5 SBCON physical layer definition 23 5.1 Physical interface . 23 5.1.1 Fiber optic information transfer . 23 5.1.2 Data transmission : 24 5.1.3 Link, trunk cable, and jumper cable specificatio

18、ns 24 5.2 Multimode physical layer . 24 5.2.1 Multimode output interface 25 5.2.2 Multimode input interface 25 5.2.3 Multimode link specifications . 25 5.2.4 62.5 prn multimode cable specifications . 25 5.2.4.1 62.5 pm multimode trunk cable optical specifications 25 5.2.4.2 62.5 prn multimode duplex

19、 jumper cable specifications . 27 5.2.5 50 prn multimode trunk cable optical specifications . 27 3.3 4.1.2 Link . 13 i Page 5.2.6 5.2.7 5.3.1 5.3.2 5.3.3 5.3.4 Multimode duplex connector 28 Multimode duplex receptacle . 28 Single-mode physical layer 28 Single-mode output interface . 28 Single-mode i

20、nput interface . 30 Single-mode link specifications 30 Single-mode cable specifications 30 Single-mode trunk cable optical specifications . 30 Single-mode duplex jumper cable specifications 30 5.3.5 Single-mode connector 30 5.3.6 Class 1 laser safety 30 5.4 Bit-error-rate thresholding 30 5.4.1 Types

21、 of link errors caused by bit errors 32 5.4.2 Error bursts 32 5.4.3 Bit-error-rate-thresholding measurement 32 6 Transmission code 33 6.1 Notation conventions 33 6.2 8B/1 OB transmission code 34 6.2.1 Transmission order 34 6.2.2 Valid and invalid transmission characters 34 5.3 5.3.4.1 5.3.4.2 6.2.2.

22、1 6.2.2.2 Generating transmission characters . 35 Checking the validity of received transmission characters 35 6.3 Special character combinations 39 7 Link transmission and reception characteristics . 40 7.1.1 Conditions that cause loss of synchronization . 40 7.1.1.2 Transition to power on . 41 7.1

23、.1.3 7.1.2 Acquisition of synchronization . 41 7.1.3 7.2 Idle character 42 7.4 Sequence transmission and reception . 43 7.4.1 Sequence reception . 43 7.1 Synchronization 40 7.1.1.1 Loss-of-synchronization procedure . 40 Detection of loss of signal . 41 Synchronization state diagram 42 7.3 Ordered-se

24、t reception 42 7.4.2 Not-operational sequence 44 7.4.3 Unconditional-disconnect sequence 44 7.4.4 Unconditional-disconnect-response sequence 44 7.4.5 Offline sequence 44 8 Frame structure . 46 8.1 Link header . 47 8.1.1 Start-of-frame delimiter 47 8.1.2 Destination-address field . 47 8.1.2.1 Destina

25、tion link address 48 8.1.2.2 Destination logical address . 48 8.1.3 Source-address field 48 8.1.3.1 Source link address . 48 8.1.3.2 Source logical address 49 ii Page 8.1.4 Logical path identifier 49 8.1.5 Link-control field 49 8, 2 Information field . 49 8.3 Link trailer 49 8.3.1 Cyclic-redundancy-

26、check field 50 8.3.2 End-of-frame delimiter . 51 8.3.3 Abort delimiter . 51 Frame transmission and reception 51 8.4.1 Frame transmission . 51 8.4.2 Frame reception 52 8.5 Link-interval duration . 53 8.6 Connection-recovery-interval duration . 53 9 Link-level-control functions . 54 9.1 Link-control f

27、rames 54 9.1.1 Establish-logical-path 58 8.4 9.1.2 Remove-logical-path . 60 9.1.3 Logical-path-established . 61 9.1.4 Logical-path-removed . 61 9.1.5 Link-level-acknowledgment . 61 9.1.6 Test-initialization . 62 9.1.7 Test-initialization-result . 62 9.1.8 Link-level-reject . 62 9.1.9 Port-reject 64

28、9.1.1 O Link-level-busy 65 9.1.1 1 POrt-buSy . 65 Source-port-busy monolog-D . 66 Multiple port-reject and port-busy conditions 67 9.1.1 3 State-change-notification 67 9.1.14 Acquire-link-address . 68 9.1.1 5 Request-node-identifier . 69 9.1.1 6 Identifier-response 69 9.1.17 Link-incident-notificati

29、on 70 9.1.1 8 Request-incident-record 70 9.1 . 19 Link-incident-data 70 9.2 Functions and protocols for device frames 70 10 Link-level-facility and dynamic-switch-port states and protocols 72 10.1 Initialization 72 10.1.1 Link-initialization procedure 74 10.1.2 Initialization for channel link-level

30、facility . 74 10.1.2.1 Channel link-address acquisition 75 10.1.2.2 Channel node-identifier acquisition 76 10.1.2.3 Establishment of logical paths by the channel 77 10.1.3 Initialization process for control-unit link-level facility 78 10.1.3.1 Control-unit link-address acquisition . 79 10.1.3.2 Cont

31、rol-unit node-identifier acquisition . 79 10.1.3.3 Establishment of logical paths by the control unit . 80 10.2 Link-incident reporting . 81 9.1.1 1.1 9.1.1 1.2 Source-port-busy-unconnected 66 9.1.1 1.3 Destination-port-busy . 66 9.1.12 iii Page 10.2.2 Link-incident-reporting procedure 83 10.3 Offli

32、ne procedures . c84 10.3.1 Conditions that cause the off line procedure 84 10.3.2 Offline states 85 10.3.2.1 Off line-transmission state 85 10.3.2.2 Off line-reception state . 86 10.3.2.3 Wait-for-offline-sequence state . 86 10.4 Connection recovery 86 Conditions that cause connection recovery . 87

33、10.4.2 Connection-recovery procedure 88 10.4.2.1 UD-transmission state . 88 10.4.2.2 UD-reception state 89 10.4.2.3 UDR-reception state 89 10.5 Link failure 90 10.5.1 Conditions that cause link failure . 90 10.5.2 Link-failure procedure . 90 10.5.2.1 Transmit-OLS state . 90 10.5.2.2 Transmit-NOS sta

34、te 91 10.6 Link abort 91 10.7 Connection . 92 10.8 Link-level-facility states 92 10.8.1 Link-level facility inactive . 93 10.8.2 Link-level facility working . 93 10.8.3 Link-level-facility link failure . 94 10.8.4 Link-level-facility connection recovery . 94 10.8.5 Link-level-facility offline 94 10.

35、9 Dynamic-switch-port states 94 10.9.1 Port inactive . 95 10.9.2 Port link busy . 95 10.9.3 Port connection 95 10.9.3.2 Monolog-D . 96 10.9.3.3 Dialog-2 . 97 10.9.3.4 Dialog-1 . 97 10.9.4 Port link failure . 98 10.9.5 Port connection recovery . 98 10.9.6 Port-offline state . 99 10.9.7 Static state .

36、 99 10.9.7.1 Static-transmit-OLS state 100 10.9.7.2 Static-pass-through state 100 10.1 O Link timeout 100 10.1 1 Link-busy condition . 100 11 Link and dynamic-switch-port error conditions 102 11.1 Link errors 102 1 1.1.1 Connection error 103 1 1.1.2 Link-signal error . 104 1 1.1.3 Code-violation err

37、or . 105 1 1 -1.4 Sequencing error . 105 1 1.1.5 CRC error 106 10.2.1 Link-incident record . 81 10.4.1 10.9.3.1 Monolog-S . 96 iv Page 11.1.6 Destination-address-invalid error 106 11.1.7 Link-protocol error . 106 . 1 1.1.8 Logical-path-not-established error 108 1 1.2 Dynamic-switch-pori errors 108 1

38、1.2.1 Address-invalid error . 109 1 1.2.2 Undefined-destination-address error . 109 11.2.3 Destination-port malfunction . 109 1 1.2.4 Dynamic-switch-port intervention required 109 12 Device-frame format . 110 12.1 Device-header . 110 12.1.1 Information-field identifier 110 12.1.1.1 Address-specific

39、(AS) . 110 12.1.1.2 Supplemental-status (ES) . 111 12.1.1.3 Device-frame type (T2, T1) 111 12.1.2 Device-address . 111 12.1.3 Device-header-flag field 112 12.1.3.1 End (E) . 112 12.1.3.2 End-block (EB) . 112 12.1.3.3 Ready (RDY) 112 12.1.3.4 Chaining (CH) . 113 12.1.3.5 Data-request (DR) 113 12.2 De

40、vice-information block . 114 12.2.1 Data-frame DIB structure 114 12.2.2 Command-frame DIB structure . 114 12.2.2.1 Command-flag field . 114 12.2.2.1.1 Chain-data (CD) . 116 12.2.2.1.2 Chain-command (CC) 116 12.2 2. 1.3 Data-chaining-update flag (DU) . 116 12.2.2.2 Command field . 116 12.2.2.2.1 Sens

41、e . 117 12.2.2.2.2 Read-backward 117 12.2.2.2.3 Read 117 12.2.2.2.4 Write . 117 12.2.2.2.5 Control . 117 12.2.2.3 Count field 117 12.2.3 Status-frame-DIB structure . 118 12.2.3.1 Status-flag field . 119 12.2.3.2 Status-byte . 120 12.2.3.2.1 Attention . 120 12.2.3.2.2 Status-modifier . 121 12.2.3.2.3

42、 Control-unit-end 121 12.2.3.2.4 Busy . 123 12.2.3.2.5 Channel-end 123 12.2.3.2.6 Device-end . 124 12.2.3.2.7 Unit-check 125 12.2.3.2.8 Unit-exception 126 12.2.3.3 Status-parameter field 126 12.2.3.4 Supplemental-status DIB structure . 128 12.2.3.5 Sense information . 128 12.2.3.5.1 Command-reject 1

43、29 V Page 12.2.3.5.2 Intervention-required 129 12.2.3.5.3 Bus-out-check . 129 12.2.3.5.4 Equipment-check 129 12.2.3.5.5 Data-check . 129 Control-frame DIB structure . 130 Multipurpose device-control function . 130 1 2.2.4.1.1 Accept-command-response 132 12.2.4.1.2 Accept-connection 132 12.2.4.1.3 De

44、ny-connection . 132 12.2.4.1.4 Rescind-connection 132 12.2.4.1.5 Data-request . 132 12.2.4.2 Command-response frame . 132 CMR frame for write operation . 133 CMR frame for read operation 133 12.2.4.2.3 Pacing-count . 133 12.2.4.2.5 Number-of-data-requests (NDR-R-count) 133 12.2.4.3 Stack-status fram

45、e 134 12.2.4.5 System-reset frame 134 12.2.4.6 Selective-reset frame 134 12.2.4.7 Request-connection frame 135 12.2.4.8 Request-status frame 135 12.2.4.9 Device-level-exception frame 135 Status-accepted frame 136 Device-level-acknowledgment frame 136 12.3 Device-frame delimiters 136 Device-level fun

46、ctions and protocols 138 13.1 Device-level operations 138 Initiating an I/O operation . 138 13.1.2 Data-transfer protocol 140 13.1.2.1 Write operation 143 13.1.2.2 Read operation 144 13.1.2.3 Data-chaining 145 Ending an I/O operation . 147 Ending an I/O operation using a status frame . 147 13.1.3.2

47、Supplemental-status . 148 13.1.4 Command-chaining 149 13.2 Device-level controls 151 13.2.3 System-reset function 153 1 2.2.3.5.6 Overrun . 129 12.2.4 12.2.4.1 12.2.4.2.1 12.2.4.2.2 12.2.4.2.4 Data-request-count . 133 12.2.4.4 Cancel frame . 134 12.2.4.1 O 12.2.4.1 1 13 13.1.1 13.1.2.4 Pacing . 146

48、13.1.2.5 Zero CCW count . 146 13.1.3.1 13.1.3.3 Transfer-count checking 148 13.1.3 13.2.1 Stack-status function . 151 13.2.2 Cancel function 152 13.2.4 Selective-reset function . 154 13.2.5 Request-connection function . 156 13.2.6 Request-status function . 157 13.2.7 Device-level-exception function

49、. 158 vi Page 13.2.8 Status-acceptance function . 158 13.2.9 Device-Ievel-acknowledgment function . 159 13.2.9.1 Control-unit-busy condition . 159 Error handling at the device level 159 13.3.1 Device-level errors 159 13.3.1.1 Device-level-connection errors . 160 13.3.1.2 Device-level-protocol errors 160 13.3.2 Command-retry . 160 Channel-initiated recovery procedures . 161 13.3.3.2 Channel-initiated-unit-check request 163 Channel request for unit-check without overrun 164 Channel request for unit-check with overrun . 164 13.3.4 Address-exception condition . 164 13.3.5 Device-level timeou