FC vs iSCSI vs NVMe-oF: Choosing a Storage Network Protocol

Block storage for virtualization clusters and databases travels over one of three fabrics - dedicated Fibre Channel, Ethernet-based iSCSI, or the newer NVMe-over-Fabrics family - and the choice shapes both your latency budget and your day-2 operations for years. The common trap is treating the decision as "FC is old, NVMe is new, so NVMe wins": each protocol optimizes a different constraint. This article compares FC, iSCSI and NVMe-oF (including NVMe/TCP, NVMe/RoCE and FC-NVMe) so the transport matches the workload.

Protocols at a Glance

iSCSI: The Pragmatic Workhorse

iSCSI wraps SCSI in TCP/IP, so the entire Ethernet toolkit applies: standard switches, jumbo frames, multipathing, existing monitoring. It is the right answer for small/medium virtualization, VM file services, backups and test environments - and it can serve databases if traffic is isolated on a dedicated VLAN or network. The costs are CPU per I/O (TCP processing and SCSI translation) and latency that depends heavily on network tuning; vendor tests consistently show iSCSI delivering the lowest IOPS and highest host CPU of the common transports.

Fibre Channel: Isolation as a Feature

FC is a purpose-built lossless SAN with its own switches, HBAs and terminology (WWPN, zoning, fabric). Because nothing else shares the network, latency is predictable and operational surprises are fewer in large, critical environments - finance, healthcare, dense VDI. The price is a separate infrastructure to buy and skills to keep; FC's bandwidth roadmap (32GFC mainstream, 64GFC arriving) also trails Ethernet.

NVMe-oF: Native Flash Semantics over a Network

NVMe-oF keeps the NVMe command set end to end, avoiding the SCSI translation every iSCSI or FCP I/O pays. The three transports answer different questions:

• NVMe/TCP - lowest barrier: standard Ethernet and NICs, routable, troubleshot with familiar tools. Measurably better IOPS and CPU than iSCSI on the same network.
• NVMe/RoCE (RoCEv2) - RDMA moves data between host and target memory directly; lowest Ethernet latency, but requires RDMA NICs and a lossless fabric tuned with PFC and ECN. Published tests put 25G RoCE near 32GFC on IOPS and latency.
• FC-NVMe - NVMe over existing FC infrastructure; deterministic and low-risk for shops that already run FC well, letting them adopt NVMe semantics without ripping out the SAN.

How to Decide

• Fast start on familiar Ethernet, cost-sensitive, medium scale - start with iSCSI (segmented, redundant, validated), and treat NVMe/TCP as the natural next step.
• Maximum predictability, isolation and zero-tolerance downtime - Fibre Channel (or FC-NVMe) if you already operate FC.
• Very fast all-flash arrays with latency-critical workloads (high-load databases, analytics, AI) - NVMe-oF, picking the transport by your team's ability to run lossless Ethernet (RoCE) or by existing FC practice (FC-NVMe).
• Most shops run a mix: NVMe/TCP for general workloads, RoCE islands for the latency-critical tier, FC-NVMe for the legacy SAN - matching transport to workload rather than standardizing on one fabric.

Whichever protocol you pick, the fabric side needs the same discipline: two independent paths, redundant switches and cabling. See our Brocade FC zoning CLI guide for FC fabrics, HPE 3PAR administration commands for array-side operations, and the NetApp ONTAP NFS export policy guide when the workload prefers file (NFS) semantics over block.

原文链接：https://gse.kz/en/blog/storage-network-for-san-iscsi-fc-nvme-of