fcoe · limited · also Fibre Channel over Ethernet

FCoE

Fibre Channel over Ethernet (FCoE) carries unmodified Fibre Channel frames inside Ethernet frames, with a separate discovery and login protocol, FIP, and no TCP/IP layer.

Related Observatory article: Read on hesela.com

FCoE is specified in FC-BB-5 (ANSI INCITS 462, 2010) and has two parts, the FCoE Initialization Protocol (FIP) and the encapsulation; the entire Fibre Channel frame is carried unchanged. Unlike FCIP and iFCP there is no TCP, which confines FCoE to the enterprise data center and aims to converge it on one fabric. [2][4] The EtherType is 0x8906 for FCoE and 0x8914 for FIP, and start-of-frame and end-of-frame codes surround the frame. [2][3]

FIP handles discovery, fabric login and logout; only the ENode and the Fibre Channel Forwarder (FCF) use it, and it sets up virtual ports corresponding to N_Port, F_Port and E_Port. An ENode sends a discovery solicitation and an FCF answers within D_A_TOV, default 5 s, then sends periodic advertisements as a heartbeat every D_A_TOV x 10, 50 s at the default. [2] An FCF forwards on the Fibre Channel destination ID, rewrites MAC addresses hop by hop, enforces zoning and typically has native Fibre Channel ports to reach arrays. [4]

The Linux kernel defines an FCoE header of 14 bytes, a trailer of 8 bytes and an FCoE MTU of 2158 bytes, with a source comment reading 14 + 24 + 2112 for header, Fibre Channel header and maximum payload. [3] Arithmetic: 14 + 24 + 2112 = 2150, and the 8-byte trailer gives 2158, about 1.44 times a 1500-byte Ethernet payload. Switches carrying FCoE would likely implement data center bridging protocols to avoid frame loss from queue overflow. [4]

Transport boundary: FCIP connects Fibre Channel fabric islands over TCP/IP; it is not FCoE or an iSCSI session. [6] FIP setup, priority-based flow control and DCB capability exchange address separate parts of an FCoE path. A physical Ethernet link being up does not prove a usable FC virtual link. [5]

Relations

related
Fibre Channel, iSCSI, ALUA, SAN, SCSI, FCoE Initialization Protocol (FIP), Priority-based Flow Control (PFC), Data Center Bridging (DCB)

Advantages

  • SCSI tools and Fibre Channel zoning and login semantics keep working over an Ethernet fabric because the stack above the frame is unchanged. [2][4]

Limitations

  • Without TCP the protocol is not suited to wide-area transport. [2]
  • Every link on the path must carry frames larger than the classic 1500-byte payload. [3]
  • A separate FIP control plane with virtual ports must be operated alongside the data path. [2]

Citations

  1. FCoE Tutorial, based on FC-BB-5 1.01, 10 June 2008 (UNH InterOperability Laboratory, Fibre Channel Consortium) (accessed 2026-10-16)
  2. Linux kernel: include/uapi/linux/if_ether.h, include/scsi/fc/fc_fcoe.h and include/scsi/libfcoe.h (accessed 2026-10-16)
  3. RFC 6847: Fibre Channel over Ethernet (FCoE) over Transparent Interconnection of Lots of Links (TRILL), January 2013 (accessed 2026-10-16)
  4. Cisco MDS 9000 FCoE Configuration Guide, Release 8.x: FCoE, FIP and frame formats (accessed 2026-11-02)
  5. RFC 3821: Fibre Channel Over TCP/IP (FCIP), sections 4-5 (accessed 2026-11-02)

Further reading

  1. FCoE (accessed 2026-03-26)
Sources & caveats
  • The FC-BB-5 standard text could not be retrieved (the T11 server did not answer), so the description rests on a university test-lab tutorial of an earlier revision (1.01, June 2008), the kernel definitions and an IETF RFC.
  • A later FC-BB-5 revision may differ in detail from the 2008 tutorial, and the standard requirements on Ethernet flow control were not read.
  • RFC 6847 is an Informational independent submission by authors affiliated with network-equipment makers and concerns FCoE over TRILL; only its background description of FCoE is used.
  • The kernel file is a master-branch snapshot on the access date; the header notes that non-FIP use with a fixed fabric-login MAC address is deprecated.
  • Arithmetic: 14 + 24 + 2112 = 2150, plus the 8-byte trailer 2158; 2158 / 1500 is about 1.44; adding a 14-byte Ethernet header and 4-byte frame check sequence gives about 2176 bytes on the wire.
  • No throughput, cost or adoption figures are given.

JSON: /data/terms/fcoe.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. FCoE. Hesela. 2026-11-02. https://hesela.dev/terms/fcoe/