fibre-channel · shipping · also FC

Fibre Channel

Fibre Channel is a frame-based networking architecture used to carry storage protocols between node ports, directly or through a fabric.

Related Observatory article: Read on hesela.com

FC-2 handles framing and transport control; FC-4 maps upper-layer protocols. In a switched fabric, FLOGI establishes fabric parameters and obtains a fabric address, while PLOGI establishes peer-port parameters. These logins can be implicit. [5] Linux libfc also handles FLOGI for direct point-to-point attachments, so a switch is not a universal prerequisite. [11]

Frames belong to sequences and sequences belong to exchanges. Keep source/destination port identity, OX_ID/RX_ID and sequence context together when correlating traces. An exchange identifier is scoped protocol state, not a permanent global request ID. [9]

Linux v6.12 defines a 24-byte header and a maximum 2112-byte data field. Its 2136-byte FC_MAX_FRAME excludes CRC and delimiters. [6] FC-NVMe I/O can reuse FCP transport TYPE 08h, so header TYPE alone is not a reliable SCSI-versus-NVMe classifier. [9]

Buffer-to-buffer credits govern a link's receive-buffer capacity, independently in each direction. A frame uses one credit; basic R_RDY flow control returns it when buffer space becomes available. [7] SCSI status resides separately in an FCP response. A returned credit therefore cannot prove successful command execution or persistent storage. [8]

Fibre Channel zoning controls fabric-port relationships; LUN masking controls logical-unit presentation to initiators. Check both layers when a reachable target does not expose the expected volume. [12]

The 1996 topology model assumes uniform terminal-to-terminal traffic and idealized buffering. Its deadlock-free rerouting example can still concentrate traffic on central links. These are historical analytical assumptions, not measured application throughput or a current fabric-design recommendation. [13]

Relations

related
SAN, Serial Attached SCSI (SAS), SCSI, ALUA, SCSI initiator and target, FICON, NVMe/FC, Fibre Channel frame, Fibre Channel sequence, Fibre Channel exchange, Buffer-to-buffer credit, Fibre Channel over TCP/IP, Fibre Channel zoning, LUN masking, World Wide Name (Fibre Channel)

Advantages

  • A fabric can carry different upper-layer protocol mappings when endpoints support them. [6]

Limitations

  • Flow control is not an end-to-end durability guarantee; credits and command status describe different protocol layers. [7, 8]
  • Negotiated frame sizes and implementation support must be checked for the actual path. [5]

Citations

  1. RFC 4338 (January 2006), sections 2.1-2.4: Fibre Channel architecture summary (accessed 2026-10-19)
  2. Linux v6.12: fc_fs.h frame layout, identifiers and protocol types (accessed 2026-10-19)
  3. Cisco MDS 9000 Interfaces Configuration Guide, Release 9.x: Buffer-to-Buffer Credits and Credit Recovery (accessed 2026-10-19)
  4. Linux v6.12: fc_fcp.h, fcp_resp and SCSI status (accessed 2026-10-19)
  5. FCIA: Inside a Modern Fibre Channel Architecture, Part 2 (2021), slides 7, 19, 23-31, 35 and 38 (accessed 2026-10-19)
  6. Linux v6.12: libfc fc_lport.c, direct point-to-point FLOGI handling (accessed 2026-10-19)
  7. Cisco: Enabling Cisco HyperFlex Systems to Coexist with Fibre Channel Shared Storage, Cisco MDS multilayer switches (accessed 2026-11-03)
  8. Cherkasova, Kotov and Rokicki. Fibre Channel Fabrics: Evaluation and Design. HICSS 1996, sections 2.1 and 3, pp. 54 and 58. DOI 10.1109/HICSS.1996.495447 (accessed 2026-11-03)

Further reading

  1. Fibre Channel (accessed 2026-03-26)
  2. RFC 4338: Transmission of IPv6, IPv4, and Address Resolution Protocol (ARP) Packets over Fibre Channel (IETF Standards Track, January 2006), sections 2.1 to 2.4 (accessed 2026-10-16)
  3. RFC 3643: Fibre Channel (FC) Frame Encapsulation (IETF Standards Track, December 2003) (accessed 2026-10-16)
  4. include/uapi/scsi/fc/fc_fs.h and include/scsi/scsi_transport_fc.h, Linux kernel source (open source; fc_fs.h derived from T11 FC-FS-2 Rev 0.90, 9 August 2005) (accessed 2026-10-16)
  5. RFC 3643 (December 2003), section 5: frame content and delimiter representation (accessed 2026-10-19)
Sources & caveats
  • Architectural source review, not a benchmark. Linux references are pinned to v6.12; the RFCs describe older foundational behavior.
  • Cisco configuration and credit-recovery details apply to the cited MDS 9.x guide. No universal maximum rate or current market-share claim is made.
  • Earlier c1-c4 citation IDs are retained for compatibility; inline claims now point to the scoped sources listed here.

JSON: /data/terms/fibre-channel.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Fibre Channel. Hesela. 2026-11-03. https://hesela.dev/terms/fibre-channel/