san · shipping · also storage area network

SAN

A storage area network (SAN) is a network primarily used for data transfer between computers and storage devices, or among storage devices.

Block services are common on a SAN, but the term is not restricted to them. [8] Fibre Channel, iSCSI over TCP/IP and NVMe over Fabrics are different ways to provide networked storage access; a SAN is not a file-sharing protocol [2] [4] [5].

A volume can serve one host or a storage-aware cluster. Giving several hosts access does not coordinate file-system metadata or caches. Concurrent writers require a shared-disk file system or an application designed for common block storage, plus its required recovery controls [6].

Discovery, permission and live connectivity are separate observations. iSNS discovery domains limit which nodes learn about each other, and targets can use authorised-initiator information for login control. A state-change notification reports a database change, not proof that a peer is reachable [3].

Fibre Channel zoning controls fabric-port relationships; LUN masking controls logical-unit presentation to initiators. Check both layers when a reachable target does not expose the expected volume. [9]

Relations

related
Fibre Channel, iSCSI, NVMe over Fabrics, Block storage, ALUA, All-flash array, SCSI initiator and target, Logical unit number (LUN), SNIA, File storage, Shared-disk file system, I/O fencing, Direct-attached storage, Unified storage, NAS gateway, Fibre Channel zoning, LUN masking

Advantages

  • iSCSI permits the SCSI command model to operate across TCP/IP networks rather than requiring a locally attached bus. [2]
  • Administrators can group storage nodes into discovery domains to reduce irrelevant logins and narrow target visibility. [3]

Limitations

  • Ordinary local file systems do not become safe for simultaneous read-write mounts merely because the volume is presented to several machines. [7]
  • Storage-service resilience still depends on the shared devices and paths; attaching more hosts does not create additional copies of the stored data. [7]

Citations

  1. RFC 7143: Internet Small Computer System Interface (iSCSI) Protocol (Consolidated), IETF, April 2014 (accessed 2026-10-16)
  2. RFC 4171: Internet Storage Name Service (iSNS), IETF, September 2005 (accessed 2026-10-16)
  3. RFC 4338: Transmission of IPv6, IPv4, and Address Resolution Protocol (ARP) Packets over Fibre Channel, IETF, January 2006 (accessed 2026-10-16)
  4. NVM Express Base Specification, Revision 2.4 (NVM Express, Inc.; open standard) (accessed 2026-10-16)
  5. Red Hat Enterprise Linux 8: Overview of available file systems, local, network and shared-storage categories (accessed 2026-10-19)
  6. Amazon EBS: Multi-Attach considerations and limitations (service-specific documentation) (accessed 2026-10-19)
  7. SNIA dictionary: Storage Area Network (accessed 2026-10-25)
  8. Cisco: Enabling Cisco HyperFlex Systems to Coexist with Fibre Channel Shared Storage, Cisco MDS multilayer switches (accessed 2026-11-03)

Further reading

  1. SAN (accessed 2026-03-26)
Sources & caveats
  • Transport descriptions retain the earlier RFC and NVMe references; this revision adds filesystem-sharing boundaries, not a transport performance comparison.
  • The EBS Multi-Attach guidance supplies a concrete shared-volume example; its service limits are not general SAN limits [7].

JSON: /data/terms/san.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. SAN. Hesela. 2026-11-03. https://hesela.dev/terms/san/