Copies of this document may be purchased from:
Global Engineering, 15 Inverness Way East,
Englewood, CO 80112-5704
Phone: (800) 854-7179 or (303) 792-2181 Fax: (303) 792-2192
INCITS TR-xx-200x
T11/Project 1513-DT
FIBRE CHANNEL
DEVICE ATTACH
(FC-DA)
Revision 2.9
INCITS working draft proposed
Technical Report
June 9, 2004
Secretariat: Information Technology Industry Council
NOTE:
This is a working draft Technical Report of Accredited Standards Committee INCITS. As such, this
is not a completed Technical Report. The T11 Technical Committee or anyone else may modify this
document as a result of comments received anytime, or during a future public review and its eventual approval as a Technical Report. Use of the information contained herein is at your own risk.
Permission is granted to members of INCITS, its technical committees, and their associated task
groups to reproduce this document for the purposes of INCITS standardization activities without
further permission, provided this notice is included. All other rights are reserved. Any duplication
of this document for commercial or for-profit use is strictly prohibited.
POINTS OF CONTACT:
Robert Snively (T11 Chair)
Brocade Communications
1091 Guadalupe Parkway
San Jose, CA 95131
Voice: 408-487-8135
Fax: 408-392-6676
Email: rsnively@brocade.com
Claudio DeSanti (T11 Vice Chair)
Cisco Systems, Inc.
170 W. Tasman Drive
San Jose, CA 95134
Voice: 408-853-9172
Fax: 408-853-9172
Email: cds@cisco.com
Scott Kipp (FC-DA Facilitator)
McDATA Corporation
380 Interlocken Parkway
Broomfield, CO 80021
Voice: 720-558-3452
Fax: 720-558-8999
Email: scott.kipp@mcdata.com
David Peterson (FC-DA Editor)
Computer Network Technology
6000 Nathan Lane North
Plymouth, MN 55442
Phone: 763-268-6139
Fax: 763-268-8818
Email: dap@cnt.com
Craig W. Carlson (T11.3 Chair)
QLogic Corporation
6321 Bury Drive
Eden Prairie, MN 55346
Voice: 952-932-4064
Fax: 952-932-4037
craig.carlson@qlogic.com
ANSI ®
INCITS TR-xx-200x
draft proposed INCITS Technical Report
Fibre Channel —
Device Attach (FC-DA)
Secretariat
Information Technology Industry Council
Approved
,200x
American National Standards Institute, Inc.
Abstract
This technical report selects and restricts logical options from the Fibre Channel Framing and Signaling,
Fibre Channel Protocol for SCSI, Fibre Channel Arbitrated Loop, Fibre Channel Generic Services, and Fibre Channel Single Byte Command Set standards. The intent of this technical report is to facilitate interoperablity between devices whether they are connected in a loop or Fabric topology.
ii
INCITS TR-xx-200x Fibre Channel Device Attach Revision 2.9 June 9, 2004
INCITS
T11
Technical
Report
Series
This technical report is one in a series produced by the American National
Standards Committee, INCITS, Information Technology. The secretariat for
INCITS is held by the Computer and Business Equipment Manufacturers
Association (CBEMA), 1250 Eye Street, NW Suite 200, Washington DC 20005.
As a by-product of the standards development process and the resources of
knowledge devoted to it, INCITS from time to time produces Technical Reports.
Such Technical Reports are not standards, nor are they intended to be used as
such.
INCITS Technical Reports are produced in some cases to disseminate the
technical and logical concepts reflected 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 choice of which depends on the user's particular requirements.
These Technical Reports, thus, provide guidelines, the use of which can result in
greater consistency and coherence of information processing systems.
Patent
Statement
When the draft technical report is completed, the Technical Committee approval
process is the same as for a draft standard. Processing by INCITS is also similar
to that for a draft standard.
CAUTION: The developers of this technical report have requested that holder's of
patents that may be required for the implementation of this technical report disclose
such patents to the publisher. However, 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 and following calls for the
identification of patents that may be required for the implementation of this
technical report, no such claims have been made. No further patent search is
conducted by the developer or the publisher in respect to any technical report it
processes. No representation is made or implied that licenses are not required to
avoid infringement in the use of this technical report.
Published by
American National Standards Institute
11 W. 42nd Street, New York, New York 10036
Copyright © 200x by American National Standards 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
iii
INCITS TR-xx-200x Fibre Channel Device Attach Revision 2.9 June 9, 2004
Foreword
(This Foreword is not part of Technical Report INCITS TR-xx-200x.)
The Fibre Channel Device Attach (FC-DA) Technical Report describes a model for end devices (i.e.,
Nx_Ports), facilitating interoperability in both loop and Fabric environments.
This technical report was developed by Technical Committee T11 of Accredited Standards Committee INCITS during 2001-2003. The final approval process started in 2003.
Requests for interpretation, suggestions for improvements or addenda, or defect reports are welcome. They should be sent to the INCITS Secretariat, Information Technology Industry Council, 1250
Eye Street, NW, Suite 200, Washington, DC 20005-3922.
This technical report was processed and approved for submittal to ANSI by the InterNational Committee for Information Technology Standards (INCITS). Committee approval of the technical report does
not necessarily imply that all committee members voted for approval.
At the time it approved this technical report, INCITS had the following members:
(to be filled in by INCITS)
iv
INCITS TR-xx-200x Fibre Channel Device Attach Revision 2.9 June 9, 2004
Technical Committee T11 on Lower Level Interfaces, that reviewed this technical report, had the following members:
Robert Snively, Chair
Claudio DeSanti, Vice-Chair
Neil Wanamaker, Secretary
(to be filled in by INCITS)
v
INCITS TR-xx-200x Fibre Channel Device Attach Revision 2.9 June 9, 2004
Task Group T11.3 on Fibre Channel Protocols, that developed and reviewed this technical report, had
the following members:
Craig W. Carlson, Chair
George Penokie, Vice-Chair
Bill Martin, Secretary
(to be filled in by INCITS)
vi
INCITS TR-xx-200x Fibre Channel Device Attach Revision 2.9 June 9, 2004
Table of Contents
Page
1 Introduction and scope
............................................................................
1
..............................................................................
2
.......................................................................................
2
2 Normative references
2.1 Overview
2.2 Approved references
.........................................................................
.............................................................
2
.......................................................................
3
.......................................................................................
3
.....................................................................................
3
2.3 References under development
3 Definitions and conventions
3.1 Overview
3.2 Definitions
3.3 Editorial conventions
..........................................................................
3.6 Keywords
5
.................................................................
6
.......................................................................................
6
......................................................................................
6
3.4 Abbreviations and acronyms
3.5 Symbols
2
3.7 Applicability and use of this technical report
................................................
....................................
8
..................................................................................
8
3.8 Feature Set table terms, definitions, and abbreviations
3.8.1 Overview
..................................................................
9
..........................................................................
9
3.9 Feature testing compliance
3.10 Timing Constraints
4 End device model
4.1 Loop behaviors
7
................................................................................
10
..............................................................................
10
4.1.1 Loop initialization
.......................................................................
10
4.1.2 Post initialization
.......................................................................
12
..................................................
13
...................................................................
13
4.1.3 Receipt of CLS in response to OPN
4.1.4 No response to OPN
...............................................................
14
......................................................................
14
4.1.5 Broadcast and multicast
4.1.6 NL_Port operation
...................................................
14
................................................................................
14
4.2 Public Loop and Private Loop behavior
4.2.1 Overview
.......................................
15
................................................
16
........................................................................
18
4.2.2 Public NL_Port and Private NL_Port behavior
4.2.3 Public and Private device addressing
4.3 Nx_Port initialization
............................................................
21
....................................................................
21
................................................................................
22
4.4 Nx_Port node and port naming
4.5 NL_Port login validation
4.6 Nx_Port login
4.6.1 Class of service support
...............................................................
4.6.2 Class of service support for FLOGI and PLOGI
.....................................
22
22
vii
INCITS TR-xx-200x Fibre Channel Device Attach Rev Revision 2.9 June 9, 2004
4.6.3 FLOGI parameters
.....................................................................
23
4.6.4 PLOGI parameters
.....................................................................
24
4.6.5 Nx_Port Class 2 Service Parameters (PLOGI)
.......................................
26
4.6.6 Nx_Port Class 2 Service Parameters (FLOGI)
.......................................
27
4.6.7 Nx_Port Class 3 Service Parameters (PLOGI)
.......................................
29
4.6.8 Nx_Port Class 3 Service Parameters (FLOGI)
.......................................
30
.............................................................
31
4.7 FC-AL-2 features for NL_Ports
.............................................
34
......................................................................
36
.....................................................................
36
4.8 Other Nx_Port FC-FS-2 and FC-LS features
4.9 Nx_Port Link Services
4.9.1 Basic Link Services
.......................................................
37
.........................................................
39
4.9.2 Extended Link Service requests
4.9.3 Extended Link Service replies
...............................
40
.................................................
40
........................................................
42
4.9.4 Link Error Status Block (LESB) support requirements
4.10 Well-known address usage by Nx_Ports
4.11 FC-CT Common Request support
.....................................................
42
...................................................................
43
...............................................................................
43
4.12 Nx_Port Name Server query support
4.13 N_Port_ID Virtualization
4.13.1 Overview
.....................................
44
...........................................
49
......................................................
49
...............................................................................
49
.................................................................................
50
................................................................................
50
4.13.2 N_Port_ID Virtualization acquisition procedure
4.13.3 Buffer-to-buffer flow control management
4.14 CS_CTL/Priority header field usage
4.14.1 Overview
4.14.2 Priority
4.14.3 CS_CTL
4.15 Logout procedure
..........................................................................
.....................................................
51
...............................................................................
51
4.16 Nx_Port management and discovery
4.16.1 Overview
4.16.2 End devices
...........................................................................
5 FC-4 specific behavior
52
...........................................................................
53
......................................................................
53
..........................................................................
53
5.1 FCP Nx_Port behavior
5.1.1 Device binding
51
...................................................................
4.17 Fabric event notification
5.1.2 Registered state change notification
..................................................
5.1.3 FCP Nx_Port Common Service Parameters for PLOGI
5.1.4 FCP Class 2 and Class 3 Service parameters for FLOGI
53
.............................
53
...........................
53
5.1.5 FCP Class 2 Service Parameters for PLOGI - sequential-access devices
viii
50
........
54
INCITS TR-xx-200x Fibre Channel Device Attach Revision 2.9 June 9, 2004
5.1.6 FCP Class 3 Service Parameters for PLOGI
.........................................
...............................
54
............................................
56
..........................................................
57
5.1.7 FCP usage of F_CTL Abort Sequence Condition bits
5.1.8 FCP usage of Process Login parameters
5.1.9 FCP Extended Link Services
.............................
57
.............................................................
58
5.1.10 FC-4 Link Service Requests and Responses for FCP
5.1.11 FCP_RSP payload fields
......................................................
58
................................................................
58
5.1.12 FC-AL-2 requirements for FCP
5.1.13 FCP device discovery
....................................
59
..................................................................
61
5.1.14 FCP Private NL_Port Exchange authentication
5.2 FC-SB-3 N_Port behavior
54
5.2.1 FC-SB-3 Extended Link Services
.....................................................
61
5.2.2 FC-SB-3 Class of Service support
....................................................
61
.........................................
62
........................................................................
62
5.2.3 FC-SB-3 Class Service Parameters support
5.3 IP Nx_Port behavior
Annex A: Discovery and Management: Examples & Rationale . . . . . . . . . . . . . . . . . . . . . . . . . . 63
A.1 Examples & Rationale
A.1.1 Overview
......................................................................
.................................................................................
A.1.2 RNID responses
........................................................................
A.1.3 Platform registration
....................................................................
63
63
63
64
ix
INCITS TR-xx-200x Fibre Channel Device Attach Revision 2.9 June 9, 2004
List of Figures
Page
Figure 1 — Public Loop and Private Loop device coexistence . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 2 — Nx_Port initialization flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 3 — N_Port_ID acquisition flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
x
INCITS TR-xx-200x Fibre Channel Device Attach Revision 2.9 June 9, 2004
List of Tables
Page
Table 1 – ISO and American conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Table 2 – Feature Set table terms and definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Table 3 – Feature Set table key abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Table 4 – Feature testing compliance relationship to definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9
Table 5 – Public and Private NL_Port behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Table 6 – Public and Private Device addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Table 7 – Nx_Port Class of service support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 8 – Nx_Port Class of service support for FLOGI and PLOGI . . . . . . . . . . . . . . . . . . . . . . 22
Table 9 – Nx_Port Common Service Parameters (FLOGI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 10 – Nx_Port Common Service Parameters (PLOGI) . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 11 – Class 2 Service Parameters (PLOGI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 12 – Class 2 Service Parameters (FLOGI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 13 – Class 3 Service Parameters (PLOGI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 14 – Class 3 Service Parameters (FLOGI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Table 15 – FC-AL features for NL_Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Table 16 – Other FC-FS-2 and FC-LS features for Nx_Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Table 17 – Basic Link Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Table 18 – Extended Link Service requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 19 – Extended Link Service replies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Table 20 – LESB support requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Table 21 – ELS requirements for well-known addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Table 22 – FC-CT Common Request support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Table 23 – Nx_Port Name Server query support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Table 24 – CS_CTL field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Table 25 – End device node support summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Table 26 – Platform support summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Table 27 – Nx_Port PLOGI Common Service Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Table 28 – FCP FLOGI Class 2 and Class 3 Service Parameters . . . . . . . . . . . . . . . . . . . . . . . 53
Table 29 – FCP PLOGI Class 2 Service Parameters for sequential-access devices . . . . . . . . . 54
Table 30 – FCP PLOGI Class 3 Service Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Table 31 – FCP Class 2 F_CTL Abort Sequence Condition bits by Sequence Initiator - sequentialaccess device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Table 32 – FCP Class 3 F_CTL Abort Sequence Condition bits by Sequence Initiator . . . . . . . 55
Table 33 – FCP Class 2 F_CTL Abort Sequence Condition bits by Sequence Recipient . . . . . 55
Table 34 – FCP PRLI parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Table 35 – FCP Extended Link Service support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Table 36 – FC-4 Link Service Requests and Responses for FCP . . . . . . . . . . . . . . . . . . . . . . . 57
Table 37 – FCP_RSP payload fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Table 38 – FC-AL features for FCP NL_Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Table 39 – FC-SB-3 Extended Link Service support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
xi
INCITS TR-xx-200x Fibre Channel Device Attach Revision 2.9 June 9, 2004
draft proposed INCITS Technical Report
for Information Technology—
Fibre Channel —
Device Attach (FC-DA)
1
Introduction and scope
This technical report defines a model for end devices (i.e., Nx_Ports). This technical report is intended to serve as an implementation guide whose primary objective is to maximize the likelihood of interoperability between conforming implementations. This technical report prohibits or requires some
features that are in the referenced ANSI/INCITS standards.
This technical report is divided into 5 clauses:
Clause 1 is the introduction and scope of this technical report.
Clause 2 enumerates the normative references that apply to this technical report.
Clause 3 describes the definitions, abbreviations, and conventions used in this technical report.
Clause 4 specifies the end device model consisting of arbitrated loop behaviors (Public and Private), initialization, naming, login and login validation, arbitrated loop features, FC framing and
signaling features, Link Services, well-known address usage, Name Server queries, N_Port_ID
Virtualization, CS_CTL/Priority header field usage, logout, management and discovery, and
Fabric event notification.
Clause 5 specifies applicable FC-4 behavior for an end device. Currently FCP, FC-SB-3, and IP
behaviors are specified.
This technical report has one annex:
Annex A is an informative annex that provides examples and rationale for the discovery and
management processes described in the end device model.
This technical report in combination with technical report FC-MI-2 cover the same scope as, but does
not replace, technical report FC-MI. This technical report includes, corrects, and extends to cover
more recent standards, the guidelines specified by FC-MI for end devices. Technical report FC-MI-2
serves the same purpose for fabric elements.
Another objective of this technical report is to simplify implementations and their associated documentation, testing, and support requirements. As a result there may be some optional features of the
referenced ANSI/INCITS standards that are not mutually exclusive, but are prohibited or required for
the purpose of this simplification. Features that some, but not all, of the referenced ANSI/INCITS
standards require for compliance may be optional in this technical report. Each specification of such
an optional feature in this technical report identifies the referenced ANSI/INCITS standards for which
the feature is required.
Internal characteristics of conformant implementations are not defined by this technical report. This
technical report incorporates features from the standards described in clause 2.
1
INCITS TR-xx-200x Fibre Channel Device Attach Revision 2.9 June 9, 2004
2
2.1
Normative references
Overview
The following standards contain provisions that, through reference in the text, constitute provisions of
this technical report. At the time of publication, the editions indicated were valid. All standards are
subject to revision, and parties to agreements based on this technical report are encouraged to investigate the possibility of applying the most recent editions of the standards listed below.
For electronic copies of INCITS standards and technical reports listed in 2.2, see the INCITS online
store at http://www.incits.org.
2.2
Approved references
ANSI/INCITS 272-1996, Fibre Channel - Arbitrated Loop (FC-AL)
ANSI/INCITS 332-1999/AM1-2003, Fibre Channel - Arbitrated Loop - 2 (FC-AL-2)
ANSI/INCITS 350-2003, Fibre Channel Protocol for SCSI - 2 (FCP-2)
ANSI/INCITS 355-2001, Fibre Channel - Switch Fabric - 2 (FC-SW-2)
ANSI/INCITS 373-2003, Fibre Channel - Framing and Signaling (FC-FS)
ANSI/INCITS TR-30-2002, Fibre Channel - Methodologies for Interconnects (FC-MI)
ANSI/INCITS 352-2002, Fibre Channel - Physical Interface (FC-PI)
ANSI/INCITS 374-2003, Fibre Channel - Single-Byte Command Code Sets Mapping Protocol - 3
(FC-SB-3)
2.3
References under development
At the time of publication, the following referenced standards were still under development. For information about obtaining copies of the following documents or for more information on the current status of these documents, contact INCITS at http://www.incits.org or visit the T11 website at
http://www.t11.org.
ANSI/INCITS xxx-200x, Fibre Channel - Generic Services - 4 (FC-GS-4), T11/Project 1505-D
ANSI/INCITS xxx-200x, Fibre Channel - Methodologies for Interconnects - 2 (FC-MI-2), T11/Project
1599-D
ANSI/INCITS xxx-200x, Fibre Channel - Switch Fabric - 3 (FC-SW-3), T11/Project 1508-D
ANSI/INCITS xxx-200x, Fibre Channel - HBA API (FC-HBA), T11/Project 1568-D
ANSI/INCITS xxx-200x, Fibre Channel Protocol for SCSI - 3 (FCP-3), T10/Project 1560-D
ANSI/INCITS xxx-200x, Fibre Channel - Link Services (FC-LS), T11/Project 1620-D
ANSI/INCITS xxx-200x, Fibre Channel - Framing and Signaling - 2 (FC-FS-2), T11/Project 1619-D
2
INCITS TR-xx-200x Fibre Channel Device Attach Revision 2.9 June 9, 2004
3
Definitions and conventions
3.1
Overview
For this technical report, the following definitions, conventions, abbreviations, acronyms, symbols,
and keywords apply.
3.2
Definitions
3.2.1 address identifier: An address value used to identify source (S_ID) or destination (D_ID) of a
frame.
3.2.2
2).
AL_PA position map: A map that shows device ordering on an Arbitrated Loop (see FC-AL-
3.2.3
Arbitrated Loop time out value (AL_Time): Arbitrated Loop time out value (see FC-AL-2).
3.2.4
Application: An entity that makes requests of a Service.
3.2.5
Arbitrated Loop Physical Address (AL_PA): A one-byte address value (see FC-AL-2).
3.2.6
Area: The second level in a three-level addressing hierarchy (see FC-SW-3).
3.2.7 Directory: A repository of information about objects that may be accessed using the Directory
Service (see FC-GS-4).
3.2.8
Domain: The highest level in a three-level addressing hierarchy (see FC-SW-3).
3.2.9
Error_Detect_Timeout value (E_D_TOV): An error detection time constant (see FC-FS-2).
3.2.10 F_Port: In this technical report, an F_Port always refers to a port to which non-loop N_Ports
are attached to a Fabric, and does not include FL_Ports.
3.2.11 Fabric: An entity that interconnects various Nx_Ports attached to it, and is capable of routing
frames using only the D_ID information in an FC-2 frame header.
3.2.12
Fabric Name: An identifier associated with a Fibre Channel Fabric (see FC-FS-2).
3.2.13 FC-DA-A Compliance: Legacy devices that do not implement LILP and LIRP but are
otherwise compliant with this technical report may claim FC-DA-A Compliance.
3.2.14 FC_Port: A port transmitting or receiving Fibre Channel frames. FC_Port includes any port
type defined in the Fibre Channel family of standards (e.g., N_Port, F_Port, FL_Port, E_Port).
3.2.15 FL_Port: An L_Port that performs the function of an F_Port when attached to one or more
NL_Ports in an Arbitrated Loop topology (see FC-AL-2). The AL_PA of an FL_Port is 00h. In this
technical report, an FL_Port always refers to a port to which NL_Ports are attached to a Fabric, and
does not include F_Ports.
3.2.16
Fx_Port: A Switch Port capable of operating as an F_Port or FL_Port.
3.2.17
Hub: A device that interconnects L_Ports (see FC-FS-2).
3
INCITS TR-xx-200x Fibre Channel Device Attach Revision 2.9 June 9, 2004
3.2.18 L_Port: A port that contains Arbitrated Loop functions associated with the Arbitrated Loop
topology (see FC-AL-2).
3.2.19 Loop Fabric Address (LFA): An address identifier used to address an FL_Port (see FCSW-3) for the purpose of loop management (see FC-LS).
3.2.20 Name_Identifier: A Fibre Channel Service that allows registration of various attributes (see
FC-GS-4).
3.2.21 Name Server: A Fibre Channel Service that allows registration of various attributes (see FCGS-4).
3.2.22 N_Port: In this technical report, an N_Port always refers to a direct Fabric-attached port, and
does not include NL_Ports (see FC-FS-2).
3.2.23 N_Port Identifier: A Fabric unique address identifier by which an Nx_Port is uniquely
known. The identifier is used in the S_ID and D_ID fields of a frame.
3.2.24 NL_Port: An L_Port that is able to perform the function of an N_Port when attached to one
or more NL_Ports and zero or more FL_Ports in an Arbitrated Loop topology. In this technical report,
an NL_Port always refers to a loop-attached port including both Private NL_Ports and Public
NL_Ports, and does not include N_Ports.
3.2.25
Node: A collection of one or more Nx_Ports controlled by a level above FC-2 (see FC-FS-2).
3.2.26
Node_Name: A Name_Identifier (see 3.2.20) associated with a Node (see FC-FS-2).
3.2.27 Non-Participating mode: The operational mode of an L_Port that does not have an AL_PA,
but is enabled into the Loop (see FC-AL-2).
3.2.28
Nx_Port: A Port operating as an N_Port or NL_Port.
3.2.29 OLD-PORT: The state of a pair of ports where two devices operate in a point-to-point mode
utilizing FC-FS-2 protocols instead of FC-AL-2 protocols (see FC-AL-2 and FC-FS-2).
3.2.30
OPEN_INIT: A state in the LPSM (see FC-AL-2).
3.2.31 Participating mode: The operational mode of an L_Port that has an AL_PA and is enabled
into the Loop (see FC-AL-2).
3.2.32 Platform: An association of one or more Nodes for the purpose of discovery and
management.
3.2.33
Port: The lowest level in a three-level addressing hierarchy (see FC-SW-3).
3.2.34 Port Identifier: A Name Server object containing the Fibre Channel address identifier
assigned to an N_Port or NL_Port (see FC-GS-4).
3.2.35
N_Port_Name: An Name_Identifier (see 3.2.20) associated with an FC_Port (see FC-FS-2).
3.2.36
2).
Private NL_Port: An NL_Port that observes the rules of private loop behavior (see FC-AL-
4
INCITS TR-xx-200x Fibre Channel Device Attach Revision 2.9 June 9, 2004
3.2.37 Public NL_Port: An NL_Port that attempts a fabric login and is permitted to open
AL_PA=00h. A Public NL_Port observes the rules of either public or private loop behavior (see FCAL-2).
3.2.38 Receiver_Transmitter_Timeout value (R_T_TOV): A receiver/transmitter time constant
(see FC-FS-2).
3.2.39 Resource_Allocation_Timeout value (R_A_TOV): A resource allocation time constant
(see FC-FS-2).
3.2.40 Resource_Recovery_Timeout value (RR_TOV): A resource recovery time constant (see
FCP-2).
3.2.41 Service: A Service is provided by a Node, accessible through an N_Port that is addressed
by a Well-Known Address or an N_Port Identifier (e.g., the Directory Service) (see FC-GS-4).
3.2.42 Speed Negotiation: A process that determines a common operating speed between an
FC_Port capable of multiple operating speeds that is connected by a common FC infrastructure to
another FC_Port that may also be capable of multiple operating speeds (see FC-FS-2).
3.2.43
Switch: An element that makes up the switching portion of the Fabric (see FC-SW-3).
3.2.44
Switch Port: An E_Port, F_Port, or FL_Port.
3.2.45
Well-Known Address: An address identifier defined to access a Service (see FC-FS-2).
3.3
Editorial conventions
In this technical report a number of conditions, mechanisms, sequences, parameters, events, states,
or similar terms are printed with the first letter of each word in uppercase and the rest lowercase (e.g.,
Exchange, Class). Any lowercase uses of these words have the normal technical English meanings.
Lists sequenced by letters (e.g., a-red, b-blue, c-green) show no priority relationship between the listed items. Numbered lists (e.g., 1-red, 2-blue, 3-green) show a priority ordering between the listed
items.
The ISO convention of numbering is used (i.e., the thousands and higher multiples are separated by
a space and a comma is used as the decimal point.) A comparison of the American and ISO conventions are shown in table 1.
Table 1 – ISO and American conventions
ISO
American
0,6
0.6
1 000
1,000
1 323 462,9
1,323,462.9
In case of any conflict between figure, table, and text, the text, then tables, and finally figures take
precedence. Exceptions to this convention are indicated in the appropriate sections.
In all of the figures, tables, and text of this document, the most significant bit of a binary quantity is
shown on the left side. Exceptions to this convention are indicated in the appropriate sections.
5
INCITS TR-xx-200x Fibre Channel Device Attach Revision 2.9 June 9, 2004
If a field or a control bit in a frame is specified as not meaningful, the entity that receives the frame
shall not check that field or control bit.
Numbers that are not immediately followed by lower-case b or h are decimal values.
Numbers immediately followed by lower-case b (xxb) are binary values.
Numbers or upper-case letters immediately followed by lower-case h (xxh) are hexadecimal values.
To indicate a bit field, the convention (MSB bit number: LSB bit number) is used (e.g., 7:0).
3.4
Abbreviations and acronyms
Abbreviations and acronyms applicable to this technical report are listed.
ELS
Extended Link Service
FC
Fibre Channel
FC-CT
Common Transport for Fibre Channel Service
FCP
Fibre Channel Protocol for SCSI
IP
Internet Protocol
IU
Information Unit
LFA
Loop Fabric Address
LIP
Loop Initialization Primitive Sequence
LIPr
Loop Initialization - reset L_Port
LSB
Least Significant Bit
MSB
Most Significant Bit
NFS
Network File Server
NPIV
N_Port_ID Virtualization
ULP
Upper Level Protocol
2xR_A_TOV
two times R_A_TOV
3.5
Symbols
Unless indicated otherwise, the following symbols have the listed meaning.
||
=
!=
>
