Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 14165-241-06: Fibre Channel Backbone-2 (FC-BB-2) Standard – Technical Overview
Understanding the ISO/IEC Standard for Fibre Channel over Ethernet and Backbone Connectivity
Scope and Introduction
The IEC 14165-241-06 standard, formally titled Fibre Channel – Part 241-06: Backbone – 2 (FC-BB-2), defines the second generation of the Fibre Channel Backbone specification. Published jointly by ISO and IEC as ISO/IEC 14165-241-06, this standard extends the Fibre Channel (FC) architecture to enable transport of FC frames over Ethernet networks using Fibre Channel over Ethernet (FCoE) and to support multi-hop backbone topologies. FC-BB-2 introduced enhancements for better scalability, resilience, and interoperability with existing Ethernet infrastructure.
The scope of IEC 14165-241-06 encompasses the mapping of Fibre Channel frames onto Lossless Ethernet (using Priority Flow Control, PFC), the encapsulation format, addressing schemes, and the behavior of backbone elements such as FCoE switches and End Nodes (ENodes). It also defines the FC-BB-2 Backbone Network, which interconnects multiple Fibre Channel fabrics via an Ethernet backbone while preserving native Fibre Channel semantics.
Tip: IEC 14165-241-06 was the first international standard to formalize FCoE, replacing earlier proprietary implementations. It remains a foundational reference for lossless Ethernet storage networks.
Technical Requirements
Frame Formats and Encapsulation
FC-BB-2 specifies a two-layer encapsulation model. Native Fibre Channel frames are first encapsulated into FCoE frames using a dedicated Ethertype (0x8906). The FCoE frame header includes a Version field (currently 0), an Ordered Set flag, and a 24-bit FCoE Parameter field used for optional functions like spoofing prevention. The encapsulated FC frame follows the FCoE header, typically up to 2148 bytes total (FC frame plus header).
| Field | Size (Bytes) | Description |
|---|---|---|
| Ethernet MAC Header | 14 | Destination/Source MAC (may include FCoE mapped addresses) |
| FCoE Ethertype | 2 | 0x8906 – FCoE type |
| FCoE Header | 8 | Version, Ordered Sets, Parameters |
| Fibre Channel Frame | 28–2148 | SOF, FC Header, Payload, CRC, EOF |
| Ethernet FCS | 4 | Standard CRC32 |
To ensure lossless behavior, the standard mandates the use of IEEE 802.1Qbb (Priority Flow Control) on all backbone links, maintaining per-priority pause to prevent frame drops for FCoE traffic.
Topology and Addressing
FC-BB-2 supports two backbone topologies: Single-Hop (point-to-point between an ENode and a Fibre Channel Forwarder, FCF) and Multi-Hop (multiple FCFs interconnected via an Ethernet backbone). Addressing relies on a combination of MAC addresses derived from the FC World Wide Name (WWN) and the FC Fabric Assigned Port Identifier (FPIN). The standard defines a mapping for FC Domain_IDs and Switch_Name into MAC address ranges to simplify discovery and routing.
Important: When implementing Multi-Hop FC-BB-2, careful design of the Ethernet backbone is required. All intermediate Ethernet bridges must support jumbo frames (≥2500 bytes MTU) and PFC, otherwise performance degradation or frame loss may occur.
Service Classes and Flow Control
FC-BB-2 retains support for the three classic Fibre Channel service classes (Class 2, Class 3, and Class F) over the backbone. However, due to the Ethernet infrastructure, only Class 3 (datagram) and Class F (fabric control) are widely deployed. Class 2 (connectionless with acknowledgment) is optional. The standard relies on the FC end-to-end credit model, but introduces a Backbone Credit scheme to manage buffer-to-buffer credits across the lossless Ethernet segment.
Implementation Highlights
Implementers of IEC 14165-241-06 must pay special attention to the following areas:
- Lossless Ethernet Configuration: All ports participating in the FCoE backbone must enable PFC (IEEE 802.1Qbb) for the FCoE priority class and ensure no other traffic interferes with that priority.
- FCF Discovery: The standard specifies two mechanisms: FIP (FCoE Initialization Protocol) snooping used by Ethernet switches, and explicit FCF advertisement via multicast FIP frames.
- Virtual Links (VN_Port to VN_Port): FC-BB-2 defines virtual point-to-point links over the Ethernet backbone, requiring each ENode to map its Fibre Channel sessions to Ethernet MAC addresses.
- Interoperability: Equipment labeled as “FC-BB-2 compliant” must pass a set of conformance tests defined in the Fibre Channel Interoperability Test Suite (FC-ITS).
Best Practice: Deploy dedicated FCoE VLANs and separate them from LAN traffic to simplify troubleshooting and guarantee bandwidth for storage traffic. Many designs use a separate VLAN for FCoE (commonly VLAN 1002) and ensure PFC is enabled only on that VLAN.
Compliance and Testing
Compliance with IEC 14165-241-06 is typically verified through both protocol conformance testing and interoperability testing. The standard references the Fibre Channel Backbone Test Specification (FC-BB-TS) issued by the T11 technical committee. Required verifications include:
- Correct FCoE frame encapsulation and Ethertype filtering.
- Proper handling of Ordered Sets for primitive sequences.
- Accurate FIP operation during login and discovery.
- Backbone credit management under congestion.
- Seamless switchover between FC and FCoE paths.
| Test Category | Key Checkpoints | Reference Document |
|---|---|---|
| Encapsulation | Correct header fields, CRC coverage, maximum frame size | FC-BB-2 Clause 6 |
| Discovery | FIP advertisement intervals, multicast address (01-10-18-01-00-02) | FC-BB-2 Annex A |
| Flow Control | PFC reaction times, credit return upon Data_Out | IEEE 802.1Qbb / FC-BB-2 Clause 9 |
| Forwarding | MAC address mapping, Domain_ID consistency | FC-BB-2 Clause 11 |
Caution: Devices that only implement earlier FC-BB-1 or proprietary FCoE may not be interoperable with FC-BB-2 compliant equipment. Always check the specific version revision when designing multi-vendor storage networks.
Frequently Asked Questions
Q: What is the main difference between FC-BB-1 and FC-BB-2?
A: FC-BB-2 introduced multi-hop FCoE backbone support, standardized the FCoE Initialization Protocol (FIP) for discovery and login, and mandated Priority Flow Control for lossless operation. FC-BB-1 was limited to single-hop connections between an ENode and an FCF.
A: FC-BB-2 introduced multi-hop FCoE backbone support, standardized the FCoE Initialization Protocol (FIP) for discovery and login, and mandated Priority Flow Control for lossless operation. FC-BB-1 was limited to single-hop connections between an ENode and an FCF.
Q: Is IEC 14165-241-06 still relevant given newer FC-BB standards?
A: Yes, many current FCoE deployments are based on FC-BB-2 (or its successor FC-BB-3). IEC 14165-241-06 remains the baseline for backbone connectivity and is widely referenced in certification programs.
A: Yes, many current FCoE deployments are based on FC-BB-2 (or its successor FC-BB-3). IEC 14165-241-06 remains the baseline for backbone connectivity and is widely referenced in certification programs.
Q: Are there any mandatory licensing or copyright restrictions for implementing this standard?
A: The standard is available from national standards bodies (e.g., ANSI, CSA) and must be purchased. However, the technical specifications can be implemented freely once licensed – check with the relevant copyright office.
A: The standard is available from national standards bodies (e.g., ANSI, CSA) and must be purchased. However, the technical specifications can be implemented freely once licensed – check with the relevant copyright office.
Q: What are the minimum Ethernet MTU requirements for FC-BB-2?
A: The standard recommends a minimum MTU of 2500 bytes on the backbone to accommodate the encapsulated FC frame (up to 2148 bytes) plus headers. Smaller MTUs will cause fragmentation or frame discard.
A: The standard recommends a minimum MTU of 2500 bytes on the backbone to accommodate the encapsulated FC frame (up to 2148 bytes) plus headers. Smaller MTUs will cause fragmentation or frame discard.
Article prepared for technical reference purposes. Standard number: IEC 14165-241-06. Year of publication: 2006. This article was last updated in 2026.