FC vs iSCSI SAN: Choosing the Right Storage Protocol

When you design a storage network, the first fork in the road is FC or iSCSI. Fibre Channel has been the enterprise SAN standard for two decades with dedicated switches and guaranteed performance; iSCSI runs storage traffic over standard Ethernet, cutting cost at the expense of tuning effort. Both are alive and well in 2026 - all-flash arrays like NetApp AFF, Dell PowerStore and HPE Alletra support both. This article compares them honestly across the metrics that matter - speed, latency, cost, cabling, skills and management - and gives you a decision framework instead of a religious debate.

Protocol Fundamentals

• FC: dedicated Fibre Channel fabric, SCSI commands over FC frames, own addressing (WWNs), own zoning and LUN masking model.
• iSCSI: SCSI commands encapsulated in TCP/IP over Ethernet, uses IP addresses, VLANs and standard switches.

Performance and Latency Comparison

On modern all-flash arrays with NVMe, both protocols reach tens of thousands of IOPS; FC Gen 6/7 retains an edge in consistent low latency, while 100G iSCSI can match or exceed older FC generations in raw throughput.

Cost Comparison

• FC: FC switches (Brocade/Cisco) cost more per port, plus FC HBAs and optics. Small deployments rarely justify a dedicated fabric.
• iSCSI: reuses existing Ethernet switches (with care), standard NICs and copper/optical DACs; software initiators are free.
• Storage array license differences: many arrays price FC and iSCSI ports identically; the real cost is in the fabric.

Management and Skills

• FC management: zoning (soft/hard), WWN-based LUN masking, fabric monitoring (Brocade Network Advisor / Cisco DCNM).
• iSCSI management: VLANs, IP SAN subnets, CHAP authentication, MPIO configuration on the host.
• Skills: FC expertise is scarcer and more expensive; iSCSI skills overlap with general networking.

Decision Guide

• Choose FC when: mission-critical databases, lowest consistent latency, dedicated storage team, existing FC fabric, regulatory environments that expect FC.
• Choose iSCSI when: budget-sensitive, small/medium environments, converged networks, staff already strong in Ethernet, ROBO/edge sites.
• Many enterprises run both: FC for primary databases, iSCSI for backups, file services and DR replication traffic.

Practical Considerations

• iSCSI over shared Ethernet: isolate storage VLANs, enable PFC/ETS if the switch supports DCB, avoid oversubscribed ToR switches for latency-critical workloads.
• Always configure MPIO (multipath) for iSCSI - single-path iSCSI is a SPOF and performs poorly.
• FC Gen 7 (64G) and NVMe-oF (FC-NVMe) keep FC relevant for all-flash and NVMe arrays.

Related: Dell PowerStore best practices and NetApp ONTAP network configuration best practices.

原文链接：https://www.netapp.com/blog/