Information technology — Fibre Channel — Part 331: Virtual Interface (FC-VI)

Fibre Channel is a high speed serial interface using either optical or electrical connections (i.e., the physical layer) at data rates currently up to 2 Gbits/s with a growth path to 10 Gbits/s, and provides a general data transport vehicle for Upper Level Protocols (ULPs) such as Intelligent Peripheral Interface (IPI) and Small Computer System Interface (SCSI) command sets, the High-Performance Parallel Interface (HIPPI) data framing, IP (Internet Protocol), ANSI/IEEE 802.2, and others. The topologies supported by Fibre Channel include point-to-point, switched fabric, and arbitrated loop. This part of ISO/IEC 14165 defines an upper-layer protocol within the domain of Fibre Channel, that is designed to permit efficient peer-to-peer or client-server messaging between nodes, and to comply with the Virtual Interface (VI) Architecture. Vendors that wish to implement devices that connect to FC-VI may follow the requirements of this and other normatively referenced standards to manufacture an FC-VI compliant device.

Technologies de l'information — Canal de fibres — Partie 331: Interface virtuelle (FC-VI)

General Information

Status
Published
Publication Date
07-Aug-2007
Current Stage
9093 - International Standard confirmed
Completion Date
13-Jul-2018
Ref Project

Relations

Buy Standard

Standard
ISO/IEC 14165-331:2007 - Information technology -- Fibre Channel
English language
288 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 14165-331
First edition
2007-07
Information technology –
Fibre channel –
Part 331: Virtual interface (FC-VI)
Reference number
ISO/IEC 14165-331:2007(E)

---------------------- Page: 1 ----------------------
THIS PUBLICATION IS COPYRIGHT PROTECTED
Copyright © 2007 ISO/IEC, Geneva, Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester.
If you have any questions about ISO/IEC copyright or have an enquiry about obtaining additional rights to this
publication, please contact the address below or your local IEC member National Committee for further information.
IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: inmail@iec.ch
Web: www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.
About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
ƒ Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
ƒ IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
ƒ Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: csc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00

---------------------- Page: 2 ----------------------
INTERNATIONAL ISO/IEC
STANDARD 14165-331
First edition
2007-07
Information technology –
Fibre channel –
Part 331: Virtual interface (FC-VI)
PRICE CODE
X
For price, see current catalogue

---------------------- Page: 3 ----------------------
14165-331 © ISO/IEC:2007(E) – 3 –
CONTENTS
FOREWORD .10
Introduction.11
1 Scope .12
2 Normative references .12
3 Terms, definitions and abbreviations .12
3.1 FC-VI terms and definitions .12
3.2 VI Definitions .14
3.3 Abbreviations . 15
3.4 Editorial conventions .15
4 Structure and concepts .17
4.1 Fibre channel structure and concepts .17
4.2 FC-VI structure and concepts .17
5 FC-VI protocol overview . 21
5.1 FC-VI information units .21
5.2 FC-VI message transfer operation .21
5.2.1 FC-VI message transfer .21
5.2.2 FC-VI send message transfer operation .22
5.2.3 FC-VI RDMA write message transfer operation .24
5.2.4 FC-VI RDMA read message transfer operation .26
5.2.5 IU reception at an FC-VI edpoint . 27
5.3 FC-VI connection setup operation .29
5.3.1 FC-VI client-server and peer-peer connection setup .29
5.3.2 FC-VI client-server connection setup . 29
5.3.3 FC-VI Peer-to-Peer Connection Establishment .31
5.3.4 FC_VI concurrent peer-to-peer connection setup .33
5.3.5 FC-VI Disconnect Operation . 35
5.4 Exchange ID reuse .36
5.5 Sequence ID reuse .37
5.6 Frame synonym detection .37
5.7 VI message length .38
5.8 FC-FS header usage for FC-VI .39
5.8.1 FC-FS header usage .39
5.8.2 CS_CTL field .39
5.8.3 TYPE field .39
5.8.4 F_CTL field . 39
5.8.5 DF_CTL field .39
5.8.6 SEQ_CNT field .39
5.8.7 Parameter field .40
5.9 FC-VI device_header .40
5.9.1 FC-VI device_header description . 40
5.9.2 FCVI_HANDLE field . 40
5.9.3 FCVI_OPCODE field .41
5.9.4 FCVI_FLAGS field .41
5.9.4.1 FCVI_FLAGS field description .41
5.9.4.2 FCVI_FLAGS for message request IUs.41
5.9.4.3 FCVI_FLAGS for message response IUs .42
5.9.4.4 FCVI_FLAGS for connect request IUs.42
5.9.4.5 FCVI_FLAGS for connect response IUs . 43

---------------------- Page: 4 ----------------------
– 4 – 14165-331 © ISO/IEC:2007(E)
5.9.4.6 FCVI_FLAGS for disconnect IUs .44
5.9.5 Reserved fields .45
5.9.6 FCVI_MSG_ID field .45
5.9.7 FCVI_PARAMETER field .46
5.9.7.1 FCVI_PARAMETER field format.46
5.9.7.2 Connect response reason codes .48
5.9.7.2.1 Connect response non-error reason codes.48
5.9.7.2.2 Connect response error reason codes.48
5.9.7.3 Message response / disconnect reason codes.48
5.9.7.3.1 Descriptor error reason codes.48
5.9.7.3.2 Remote FC-VI port non-descriptor errors.49
5.9.7.3.3 Reserved for future expansion.50
5.9.7.3.4 Vendor unique reason codes .50
5.9.8 FCVI_RMT_VA field .50
5.9.9 FCVI_RMT_VA_HANDLE field .50
5.9.10 FCVI_TOT_LEN field / FCVI_CONNECTION_ID field .50
6 FC-VI Information Unit (IU) formats .51
6.1 FC-VI IU overview .51
6.2 FCVI_SEND_RQST IU .51
6.2.1 FCVI_SEND_RQST IU description .51
6.2.2 FCVI_SEND_RQST Device_Header information .51
6.3 FCVI_SEND_RESP IU .51
6.3.1 FCVI_SEND_RESP IU description .51
6.3.2 FCVI_SEND_RESP Device_Header information .52
6.4 FCVI_WRITE_RQST IU .52
6.4.1 FCVI_WRITE_RQST IU overview .52
6.4.2 FCVI_WRITE_RQST IU Device_Header information .52
6.5 FCVI_WRITE_RESP IU .53
6.5.1 FCVI_WRITE_RESP IU description .53
6.5.2 FCVI_WRITE_RESP IU Device_Header information .53
6.6 FCVI_READ_RQST IU .53
6.6.1 FCVI_READ_RQST IU description .53
6.6.2 FCVI_READ_RQST IU Device_Header information .53
6.7 FCVI_READ_RESP IU .54
6.7.1 FCVI_READ_RESP IU description .54
6.7.2 FCVI_READ_RESP IU Device_Header information .54
6.8 FCVI_CONNECT_RQST IU .55
6.8.1 FCVI_CONNECT_RQST IU description .55
6.8.2 FCVI_CONNECT_RQST Device_Header information .55
6.8.3 FCVI_CONNECT_RQST Payload Information .55
6.9 FCVI_CONNECT_RESP1 IU .57
6.9.1 FCVI_CONNECT_RESP1 IU description .57
6.9.2 FCVI_CONNECT_RESP1 Device_Header information .57
6.9.3 FCVI_CONNECT_RESP1 Payload Information .58
6.10 FCVI_CONNECT_RESP2 IU .59
6.10.1 FCVI_CONNECT_RESP2 IU description .59
6.10.2 FCVI_CONNECT_RESP2 Device_Header information .59
6.11 FCVI_CONNECT_RESP3 IU .59
6.11.1 FCVI_CONNECT_RESP3 IU description .59
6.11.2 FCVI_CONNECT_RESP3 Device_Header information .59
6.12 FCVI_DISCONNECT_RQST IU .60
6.12.1 FCVI_DISCONNECT_RQST IU description .60

---------------------- Page: 5 ----------------------
14165-331 © ISO/IEC:2007(E) – 5 –
6.12.2 FCVI_DISCONNECT_RQST Device_Header information .60
6.13 FCVI_DISCONNECT_RESP IU .61
6.13.1 FCVI_DISCONNECT_RESP IU description . 61
6.13.2 FCVI_DISCONNECT_RESP Device_Header information .61
7 FC-VI Addressing and naming .62
7.1 FC-VI Addressing and naming overview .62
7.2 FCVI_NET_ADDRESS format . 62
7.3 FCVI_ATTRIBUTES format .63
7.4 FC-VI address resolution .65
7.5 FARP ELS .66
7.6 Name server queries .67
7.7 Validation of host address to N_Port Identifier mappings .67
7.7.1 Address mapping overview .67
7.7.2 Point-to-point topology .67
7.7.3 Private loop topology .67
7.7.4 Public loop topology . 68
7.7.5 Fabric topology .68
8 FC-VI Error detection and recovery .69
8.1 FC-VI error detection and recovery overview .69
8.2 FC-VI endpoint states .69
8.3 FCVI_ULP_TIMEOUT definition .69
8.4 Message transfer error detection and recovery rules .70
8.4.1 Message error detection . 70
8.4.2 Message transfer error recovery .70
8.5 Connection setup error detection and recovery rules .71
8.5.1 Connection setup error handling overview .71
8.5.2 Connection setup error detection .71
8.5.3 Connection setup error recovery .71
8.5.4 Connection setup originator retry rules .72
8.6 Disconnect operation error detection and recovery rules .72
8.6.1 Disconnect operation error handling overview .72
8.6.2 Disconnect operation error detection . 72
8.6.3 Disconnect operation error recovery rules .73
Annex A (normative) Concurrent matching peer requests example.74
A.1 Overview.74
A.2 Case 1 .75
A.3 Case 2 .75
A.4 Case 3 .76
A.5 Case 4 .76
A.6 Case 5 .77
A.7 Case 6 .78
Annex B (informative) FC-VI message transfer error handling examples . 79
B.1 Overview.79
B.2 Message transfer error handling operation.79
B.2.1 Message transfer error handling operation overview .79
B.2.2 Message transfer error definitions .79
B.2.3 Error Detection and Recovery Rule Processing .80
B.2.4 Message responder and message originator error recovery actions .80
B.2.5 Message responder error detection actions .81
B.2.6 Message originator Class 2 error detection actions .83
B.2.6.1 Message originator Class 2 error detection overview.83

---------------------- Page: 6 ----------------------
– 6 – 14165-331 © ISO/IEC:2007(E)
B.2.6.2 Message response timeout at message originator.84
B.3 Message transfer error detection and recovery examples.84
B.3.1 Error examples overview .84
B.3.2 Mrcv > Mexp error example .85
B.3.2.1 Mrcv > Mexp example description .85
B.3.2.2 Mrcv > Mexp: In-order fabric and unreliable .85
B.3.2.3 Mrcv > Mexp: In-order fabric and reliable delivery.85
B.3.2.4 Mrcv > Mexp: Out-of-order fabric.86
B.3.3 Mrcv = Mexp error example .86
B.3.3.1 Mrcv = Mexp example description .86
B.3.3.2 Mrcv = Mexp: In-order fabric and unreliable .87
B.3.3.3 Mrcv = Mexp: Out-of-order fabric.87
Annex C (informative) Connection setup error handling examples Overview .89
C.1 Connection setup error handling definitions .89
C.2 Connect request originator and connect request responder rules.89
C.3 Connect request originator rules .89
C.4 Connect request responder rules .91
C.4.1 Connect request responder retry rules .92
C.5 Error detection and recovery examples for connection setup .93
C.5.1 Overview .93
C.5.2 FC-VI connection setup timers .94
C.5.3 VipConnectRequest completion .95
C.5.4 VipConnectAccept completion .95
C.5.5 Enabling message transmission and reception .95
C.5.6 Client timeout of VipConnectRequest .96
C.5.7 Lost FCVI_CONNECT_RQST IU .96
C.5.7.1 Lost FCVI_CONNECT_RQST IU example.96
C.5.7.2 Retried connection setup.97
C.5.8 Lost FCVI_CONNECT_RESP1 IU .98
C.5.9 Lost FCVI_CONNECT_RESP2 IU .99
C.5.9.1 Lost FCVI_CONNECT_RESP2 IU example.99
C.5.9.2 Server timing out connection setup .100
C.5.10 Lost FCVI_CONNECT_RESP3 IU .101
C.5.10.1 Lost FCVI_CONNECT_RESP3 IU example.101
Annex D (informative) Disconnect operation error handling examples .102
D.1 Disconnect operation example description.102
D.2 FC-VI disconnect operation example .103
Annex E (informative) Message streaming for reliable reception .105
Annex F (informative) Enabling Message transmission in the FC-VI NIC .106
Documents for VI Architecture (see Clause 2 for further explanation)
Virtual Interface Architecture Specification, V1.0 (VI-ARCH) .111
Virtual Interface (VI) Architecture Developer’s Guide, V1.0 (VI-DG) .195
Virtual Interface (VI ) Architecture Developer’s Guide Error Table Supplement, V1.0 .291
IP Version 6 Addressing Architecture, RFC 2373, July 1998 (RFC2373) .321

---------------------- Page: 7 ----------------------
14165-331 © ISO/IEC:2007(E) – 7 –
Table 1 – FC-VI Information unit summary.21
Table 2 – Peer B actions based on connect responses from peer A .36
Table 3 – 16-byte FC-VI device_header.40
Table 4 – 32-byte FC-VI device_header.40
Table 5 – FCVI_FLAGS Bit definitions for message request IUs.41
Table 6 – FCVI_FLAGS Bit definitions for message response IUs .42
Table 7 – FCVI_FLAGS Bit definitions for connect request IUs .42
Table 8 – FC-VI connection mode definition .43
Table 9 – FCVI_FLAGS Bit definitions for connect response IUs .43
Table 10 – FCVI_FLAGS Bit definitions for disconnect IUs .44
Table 11 – FCVI_PARAMETER field for connect response and disconnect IUs .46
Table 12 – Reason code for CONN_STS.47
Table 13 – FCVI_CONNECT_RQST IU payload format .56
Table 14 – FCVI_CONNECT_RESP1 IU Payload Format.58
Table 15 – FCVI_NET_ADDRESS Format .63
Table 16 – FCVI_ATTRIBUTES format.63
Table 17 – Format of FCVI_ATTR_FLAGS in FCVI_ATTRIBUTES .64
Table 18 – FCVI_QOS format .64
Table A.1 – Peer B actions based on connect responses from peer A .74

---------------------- Page: 8 ----------------------
– 8 – 14165-331 © ISO/IEC:2007(E)
Figure 1 – FC-VI addressing objects.20
Figure 2 – FC-VI send for Unreliable Delivery or Reliable Delivery.23
Figure 3 – FC-VI send for Reliable Reception.24
Figure 4 – FC-VI RDMA write for Unreliable Delivery or Reliable Delivery .25
Figure 5 – FC-VI RDMA write for Reliable Reception .26
Figure 6 – FC-VI RDMA read for Reliable Reception and Reliable Delivery.27
Figure 7 – Concurrent Receive Streams at a FC-VI Endpoint.28
Figure 8 – FC-VI client-server connection setup .30
Figure 9 – Peer-to-peer connection setup.32
Figure 10 – Peer-to-peer connection setup, concurrent matching peer requests .34
Figure 11 – FC-VI disconnect operation.
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.