Why Enhanced Ethernet (CEE/DCE) Is Essential for FCoE in Modern Data Centers
The article explains how Enhanced Ethernet (CEE/DCE) adds loss‑less, priority‑based flow control and bandwidth management to traditional Ethernet, enabling Fibre Channel over Ethernet (FCoE) to meet strict storage reliability requirements and simplify data‑center cabling and topology.
What is FCoE
FCoE (Fibre Channel over Ethernet) maps the Fibre Channel protocol stack onto Ethernet frames. It enables storage traffic to use the high‑speed, rapidly evolving Ethernet infrastructure while preserving existing Fibre Channel investments and reducing the number of adapters and cables required.
Enhanced Ethernet (DCB/CEE/DCE)
Enhanced Ethernet is not a new frame format; it is a set of extensions defined by the IEEE Data Center Bridging (DCB) working group that make Ethernet loss‑less and suitable for storage‑class traffic. The extensions allow multiple traffic classes (storage, server, regular Ethernet) to share a single physical link with guaranteed reliability.
Integrates three network types on a single Ethernet fabric.
Provides loss‑less transmission to satisfy services with extremely high reliability demands.
FCoE Standards and Origins
T11.3‑FC‑BB‑5 (June 2009) – first FCoE standard ratified.
T11.3‑FC‑BB‑6 (August 2009) – defines point‑to‑point, end‑to‑end FCoE models.
The FC‑BB‑5 standard requires an FC Forwarder (FCF), which functions as an FCoE switch. Early Fibre Channel deployments used host HBAs directly connected to storage controllers; in FCoE the FCF sits between servers and storage. An optional FIP Snooping Bridge (FSB) can be added to expand ports for the FCoE Initialization Protocol (FIP).
Why FCoE Requires Loss‑less Ethernet
Standard Ethernet discards packets under congestion, which is unacceptable for Fibre Channel traffic that cannot tolerate loss or interruption. Enhanced Ethernet introduces loss‑less mechanisms—Priority‑based Flow Control (PFC), Enhanced Transmission Selection (ETS), Data Center Bridging Exchange (DCBX), and Congestion Notification (CN)—to guarantee that no FCoE frames are dropped.
Key DCB Extensions
PFC (Priority‑based Flow Control, IEEE 802.1Qbb) – pause frames are applied per traffic class, allowing a congested class to pause without starving other classes.
ETS (Enhanced Transmission Selection, IEEE 802.1Qaz) – allocates bandwidth among the virtual lanes created by PFC, ensuring each class receives its configured share of the link.
DCBX (Data Center Bridging Exchange Protocol) – automatically exchanges DCB capabilities and configuration between switches and endpoints, detecting misconfigurations and synchronizing parameters.
CN (Congestion Notification, IEEE 802.1Qau) – when a switch detects congestion it sends a CN frame toward the edge, prompting upstream devices to throttle traffic and protect the core network.
Required Ethernet Capabilities for FCoE
Full‑duplex operation.
Ordered delivery of frames.
Jumbo frames with a minimum payload of 2.5 KB.
FCoE Protocol Model
The FCoE model retains the upper Fibre Channel layers (FC‑4, FC‑3, FC‑2) while the physical (FC‑0) and link (FC‑1) layers are replaced by Ethernet’s PHY and MAC layers. FCoE provides the mapping between FC frames and Ethernet frames.
Three virtual connection types are defined:
VN2VN – ENODE to ENODE.
VN2VF – ENODE to FCF.
VE2VE – FCF to FCF.
Typical Topologies
VN2VF – each ENODE (server) creates one or more VN ports that connect to VF ports on an FCF, forming virtual links over the loss‑less Ethernet fabric.
VE2VE – multiple FCFs interconnect via VE ports, creating a mesh of virtual Ethernet links that emulate a traditional Fibre Channel fabric.
VN2VN – ENODEs connect directly to each other using inexpensive FDF devices, forming point‑to‑point virtual links.
Port Naming Mapping
N_Ports (HBA and storage FC front‑end) → VN_Ports (CNA and storage FCoE port).
F_Ports (Fabric ports) → VF_Ports (FCoE switch ports).
E_Ports (FC switch‑to‑switch) → VE_Ports (FCoE inter‑switch ports).
Performance Characteristics
FCoE operates over 10 Gbps loss‑less Ethernet. The encapsulation sequence is SCSI → FC frame → FCoE header → Ethernet frame, eliminating TCP/IP overhead and preserving Fibre Channel latency characteristics.
Future Outlook
With the rise of software‑defined networking and fully IP‑based cloud data centers, native Fibre Channel and FCoE are being superseded. Enhanced Ethernet (also called Converged Enhanced Ethernet, CEE) continues to evolve as the foundation for converged data‑center networking, enabling multiple traffic types to share a single physical link while reducing cable count, power consumption, and cost.
Architects' Tech Alliance
Sharing project experiences, insights into cutting-edge architectures, focusing on cloud computing, microservices, big data, hyper-convergence, storage, data protection, artificial intelligence, industry practices and solutions.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
