How FCoE Unifies LAN and SAN: Design Benefits and Deployment Strategies

Why converge IP SAN and FC SAN with FCoE?

Before convergence, data‑center networks required separate LAN and SAN fabrics. Each server typically needed 4‑6 NICs/HBAs, resulting in complex cabling, difficult scaling, and high power consumption. FCoE (Fibre Channel over Ethernet) allows a single converged network, reducing cabling, hardware count, and total cost of ownership. Servers use a CNA (Converged Network Adapter) that presents both an Ethernet NIC and an FC HBA to the operating system.

Key Benefits of a Unified Architecture

Reduced hardware and simplified management: One pair of redundant NICs per server replaces separate NICs and FC HBAs; a single set of switches replaces parallel LAN and SAN switches.

Higher flexibility and reliability: The converged fabric can dynamically allocate servers, storage, and other resources without physical re‑cabling, supporting virtualized and automated data‑center designs.

Lower power consumption: Halving the number of NICs, cables, and switches cuts energy use significantly.

FCoE Deployment Modes

Access‑layer / core‑layer deployment, where servers connect to an FCoE access switch and the switch uplinks to existing LAN and SAN fabrics.

VN2VN (virtual‑node‑to‑virtual‑node) deployment, where servers and storage connect directly via CNA cards without an FCoE switch.

In practice, most deployments limit FCoE to the server access layer. Servers use 10 GbE CNAs that connect to an FCoE access switch (FCF or NPV). The access switch forwards traffic to the LAN and SAN fabrics over separate 10 GbE and FC links.

Access‑Layer FCoE Design

FCoE encapsulates Fibre Channel frames inside Ethernet frames, allowing LAN and SAN traffic to share the same physical network. The design should address the five elements of a network model, starting with topology.

Topology: Each server installs a 10 GE/CEE CNA that appears to the OS as both an Ethernet NIC and an FC HBA. The OS therefore does not need to be aware of FCoE.

The FCoE switch ports must carry three VLANs:

Server VLAN: Untagged ordinary Ethernet traffic.

Storage VLAN: Tagged FCoE data frames.

FIP VLAN: Untagged FCoE Initialization Protocol (FIP) frames.

Configure the switch ports as Hybrid so that storage VLAN frames are transmitted with a VLAN tag while server and FIP frames are untagged. Set the port PVID to the Server VLAN ID. The FIP VLAN operates in “protocol VLAN mode” to allow FIP to complete initialization before the storage VLAN ID is assigned.

High‑Availability Design

Ethernet HA typically relies on full mesh and link redundancy, whereas FC SAN HA uses multiple independent vertical paths for load‑balancing and failover. In an FCoE network, SAN and LAN HA must be designed separately.

Typical HA scenarios:

Normal operation: Each server’s two CNA ports connect to two separate FCoE access switches, registering with two SAN fabrics (SAN A and SAN B). Multipath software on the host distributes traffic across the paths.

Node failure: If one FCoE access switch fails, the server continues to communicate with the SAN via the remaining CNA and switch.

Link failure: If a link between a server and an access switch fails, traffic automatically switches to the alternate path. Multiple uplinks from the access switch to the FC SAN further increase resilience.

From the LAN perspective, the two server NICs are teamed (NIC‑Teaming) and connect to the two access switches. The switches use MSTP + VRRP to provide redundant uplinks to the aggregation layer.

When the access layer is virtualized (e.g., H3C IRF), the two switches appear as a single logical device. CNA Ethernet ports may be aggregated, but FCoE ports must remain separate because SAN HA requires vertical isolation.

Transport Reliability

Traditional Ethernet is a best‑effort network and can drop packets under congestion. FC SAN uses BB‑Credit flow control to guarantee lossless delivery. Because FCoE carries FC frames over Ethernet, the Ethernet segment must also provide lossless transport. The IEEE 802.1 working group and IETF defined the CEE (Converged Enhanced Ethernet) standard for end‑to‑end lossless Ethernet. Enable CEE features on all ports that carry SAN traffic.

Network Services

FCoE services are divided into LAN‑side and SAN‑side categories:

LAN services: firewalls, server load balancing, traffic analysis – typically provided by aggregation‑layer devices.

SAN services: DNS, RSCN, FDMI – normally offered by core FC SAN switches. In an access‑layer‑only FCoE deployment these services can be ignored for the design.

Traffic Model

In an FCoE network, SAN traffic flows primarily vertically—from servers to storage devices. Designers should calculate the convergence ratio of SAN uplink ports on the FCoE access switch based on the number of servers and required bandwidth to ensure adequate SAN performance.

Further Reading

FCoE Series – Enhanced Ethernet Technology: http://mp.weixin.qq.com/s?__biz=MzAxNzU3NjcxOA==∣=2650716686&idx=1&sn=7db792cae0d56c8a8768ec3e9d739cb8

FCoE Series – Network Convergence Switch Types: http://mp.weixin.qq.com/s?__biz=MzAxNzU3NjcxOA==∣=2650716708&idx=1&sn=f34bd913ebebbbc1ffc79a4a02393202