hesela.devNAS gateway
A NAS gateway is a file-serving system that provides network file access to storage supplied by a separate storage system.
Clients send file requests to the gateway; its storage-facing interface accesses the backing devices. SNIA's 2007 example uses IP file I/O on one side and Fibre Channel block I/O on the other. This separates the file-service layer from the external storage array. [1]
Implementation: TR-3461 (May 2019) describes platforms providing CIFS or NFS services using third-party array LUNs as backing storage. The documented platforms could use native disk shelves as well as externally supplied array LUNs, and could expose block protocols too. [2]
Terminology: Gateway identifies the relationship to backing storage; unified storage identifies the access interfaces offered. These describe different architectural properties and can coexist in one system. [1] [2]
Access control: In TR-3461 (May 2019), a FlexArray or V-Series system is itself a host from the backing array's perspective. Array-side LUN masking selects which hosts can access which LUNs; switch zoning controls a different layer. The guide recommends both zoning and host groups for these configurations. [2] File-service permissions do not replace this backing-storage access policy.
Relations
- related
- NAS, SAN, Storage array, Unified storage, File storage, Block storage, NFS, SMB file sharing
Limitations
- The gateway label does not establish support for every external array, path configuration or host protocol. [2]
Citations
- SNIA IP Storage whitepaper (2007), printed p. 6: NAS gateway file I/O and external block storage.
- Michael Peppers, NetApp TR-3461, May 2019: sections 1-2 (p. 5), gateway services; section 11 (p. 15), array-side LUN masking and zoning.
Sources & caveats
- The 2007 SNIA paper explains a file/block architecture, not a requirement for every gateway implementation. [1]
- The May 2019 NetApp FlexArray/V-Series guide is a historical configuration example, not current product-support or interoperability evidence. [2]
- The gateway/unified-storage distinction is editorial synthesis of architectural role and interface coverage, not a measured performance or availability result.
- The file-service versus backing-storage access-control distinction is an editorial inference from the documented architecture, not an operational security test or a complete configuration procedure.