You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 3.85.0.0/16 has been blocked (disabled) by ‪ST47‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider. To prevent abuse, web hosts may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a web host's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and they should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 21:48, 22 February 2026.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪Jon Kolbert‬. The reason given is Open proxy/Webhost: See the help page if you are affected .
- Start of block: 05:35, 21 February 2024
- Expiry of block: 05:35, 21 February 2029
Your current IP address is 3.85.235.113. The blocked range is 3.85.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((short description|Network which provides access to consolidated, block-level data storage))
((Distinguish|network-attached storage))
((Use dmy dates|date=May 2022))
((Use American English|date=July 2020))

((Area networks))
((Fibre Channel))

A '''storage area network''' ('''SAN''') or '''storage network''' is a [[computer network]] which provides access to consolidated, [[block device|block-level data storage]]. SANs are primarily used to access [[Computer data storage|data storage]] devices, such as [[disk array]]s and [[Tape library|tape libraries]] from [[Server (computing)|server]]s so that the devices appear to the [[operating system]] as [[direct-attached storage]]. A SAN typically is a dedicated network of storage devices not accessible through the [[local area network]] (LAN).

Although a SAN provides only block-level access, [[file systems]] built on top of SANs do provide file-level access and are known as [[shared-disk file system]]s.

Newer SAN configurations enable hybrid SAN<ref>((Cite web |title=Water Panther Expanse SAN Series ((!)) Enterprise Data Center Hard Drives & SSDs |url=https://waterpanther.com/collections/expanse-san-drives |access-date=2022-07-18 |website=Water Panther |language=en-US |archive-date=18 July 2022 |archive-url=https://web.archive.org/web/20220718191845/https://waterpanther.com/collections/expanse-san-drives |url-status=live ))</ref> and allow traditional block storage that appears as local storage but also object storage for web services through APIs.

== Storage architectures==
[[File:Fibre Channel Storage Area Network.png|left|thumb|The Fibre Channel SAN connects servers to storage via Fibre Channel switches.]]

Storage area networks (SANs) are sometimes referred to as ''network behind the servers''<ref name="Tate">((Cite web|title= Introduction to Storage Area Networks|author=Jon Tate |author2=Pall Beck |author3=Hector Hugo Ibarra |author4=Shanmuganathan Kumaravel |author5=Libor Miklas |publisher= Red Books, IBM|year= 2017|url= https://www.redbooks.ibm.com/redbooks/pdfs/sg245470.pdf|access-date= 15 September 2011|archive-date= 1 January 2020|archive-url= https://web.archive.org/web/20200101200125/http://www.redbooks.ibm.com/redbooks/pdfs/sg245470.pdf|url-status= live))</ref>((rp|11)) and historically developed out of a [[centralized data storage]] model, but with its own [[data network]]. A SAN is, at its simplest, a dedicated network for data storage. In addition to storing data, SANs allow for the automatic [[backup]] of data, and the monitoring of the storage as well as the backup process.<ref name="NIIT">((Cite book|title= Special Edition: Using Storage Area Networks |publisher= Que Publishing|year=2002 |isbn=  978-0-7897-2574-5))</ref>((rp|16–17)) A SAN is a combination of hardware and software.<ref name="NIIT"/>((rp|9)) It grew out of data-centric [[Mainframe computer|mainframe architectures]], where clients in a network can connect to several [[server (computing)|server]]s that store different types of data.<ref name="NIIT"/>((rp|11)) To scale storage capacities as the volumes of data grew, [[direct-attached storage]] (DAS) was developed, where [[disk array]]s or [[just a bunch of disks]] (JBODs) were attached to servers. In this architecture, storage devices can be added to increase storage capacity. However, the server through which the storage devices are accessed is a [[single point of failure]], and a large part of the LAN network bandwidth is used for accessing, storing and backing up data. To solve the single point of failure issue, a ''direct-attached shared storage'' architecture was implemented, where several servers could access the same storage device.<ref name="NIIT"/>((rp|16–17))

DAS was the first network storage system and is still widely used where data storage requirements are not very high. Out of it developed the [[network-attached storage]] (NAS) architecture, where one or more dedicated [[file server]] or storage devices are made available in a LAN.<ref name="NIIT"/>((rp|18)) Therefore, the transfer of data, particularly for backup, still takes place over the existing LAN. If more than a terabyte of data was stored at any one time, LAN bandwidth became a bottleneck.<ref name="NIIT"/>((rp|21–22)) Therefore, SANs were developed, where a dedicated storage network was attached to the LAN, and terabytes of data are transferred over a dedicated high speed and bandwidth network. Within the SAN, storage devices are interconnected. Transfer of data between storage devices, such as for backup, happens behind the servers and is meant to be transparent.<ref name="NIIT"/>((rp|22)) In a NAS architecture data is transferred using the [[Transmission Control Protocol|TCP]] and [[Internet Protocol|IP]] protocols over [[Ethernet]]. Distinct protocols were developed for SANs, such as [[Fibre Channel]], [[iSCSI]], [[InfiniBand|Infiniband]]. Therefore, SANs often have their own network and storage devices, which have to be bought, installed, and configured. This makes SANs inherently more expensive than NAS architectures.<ref name="NIIT"/>((rp|29))

== Components ==
[[File:QLogic QLE2562 8Gb FC HBA.jpg|thumb|200px|Dual port 8&nbsp;Gb FC host bus adapter card]]
SANs have their own networking devices, such as SAN switches. To access the SAN, so-called SAN servers are used, which in turn connect to SAN [[host adapter]]s. Within the SAN, a range of data storage devices may be interconnected, such as SAN-capable disk arrays, JBODS and [[tape libraries]].<ref name="NIIT"/>((rp|32,35–36))

=== Host layer ===
Servers that allow access to the SAN and its storage devices are said to form the ''host layer'' of the SAN. Such servers have host adapters, which are cards that attach to slots on the server [[motherboard]] (usually PCI slots) and run with a corresponding [[firmware]] and [[device driver]].  Through the host adapters the [[operating system]] of the server can communicate with the storage devices in the SAN.<ref name="Dummies">((Cite book|title= Storage Area Networks For Dummies|editor1=Christopher Poelker |editor2=Alex Nikitin |publisher= John Wiley & Sons|year=2009 |isbn=978-0-470-47134-0))</ref>((rp|26))

In Fibre channel deployments, a cable connects to the host adapter through the [[gigabit interface converter]] (GBIC). GBICs are also used on switches and storage devices within the SAN, and they convert digital bits into light impulses that can then be transmitted over the Fibre Channel cables. Conversely, the GBIC converts incoming light impulses back into digital bits. The predecessor of the GBIC was called gigabit link module (GLM).<ref name="Dummies"/>((rp|27))

=== Fabric layer ===
[[File:ML-QLOGICNFCCONN.JPG|thumb| [[Qlogic]] SAN-[[Fibre Channel switch|switch]] with optical Fibre Channel connectors installed]]

The fabric layer consists of SAN networking devices that include [[SAN switch]]es, routers, protocol bridges, gateway devices, and cables. SAN network devices move data within the SAN, or between an ''initiator'', such as an HBA port of a server, and a ''target'', such as the port of a storage device.

When SANs were first built, hubs were the only devices that were Fibre Channel capable, but Fibre Channel switches were developed and hubs are now rarely found in SANs. Switches have the advantage over hubs that they allow all attached devices to communicate simultaneously, as a switch provides a dedicated link to connect all its ports with one another.<ref name="Dummies"/>((rp|34)) When SANs were first built, Fibre Channel had to be implemented over copper cables, these days multimode [[Optical fiber|optical fibre cables]] are used in SANs.<ref name="Dummies"/>((rp|40))

SANs are usually built with redundancy, so SAN switches are connected with redundant links. SAN switches connect the servers with the storage devices and are typically non-blocking allowing transmission of data across all attached wires at the same time.<ref name="Dummies"/>((rp|29)) SAN switches are for redundancy purposes set up in a [[Mesh networking|meshed topology]]. A single SAN switch can have as few as 8 ports and up to 32 ports with modular extensions.<ref name="Dummies"/>((rp|35)) So-called director-class switches can have as many as 128 ports.<ref name="Dummies"/>((rp|36))

In switched SANs, the Fibre Channel switched fabric protocol FC-SW-6 is used under which every device in the SAN has a hardcoded [[World Wide Name]] (WWN) address in the host bus adapter (HBA). If a device is connected to the SAN its WWN is registered in the SAN switch name server.<ref name="Dummies"/>((rp|47)) In place of a WWN, or worldwide port name (WWPN), SAN Fibre Channel storage device vendors may also hardcode a worldwide node name (WWNN). The ports of storage devices often have a WWN starting with 5, while the bus adapters of servers start with 10 or 21.<ref name="Dummies"/>((rp|47))

=== Storage layer ===
[[File:Fibre Channel layers.svg|thumb|300px|Fibre Channel is a layered technology that starts at the physical layer and progresses through the protocols to the upper-level protocols like SCSI and SBCCS.]]

The serialized [[Small Computer Systems Interface]] (SCSI) protocol is often used on top of the Fibre Channel switched fabric protocol in servers and SAN storage devices. The [[Internet Small Computer Systems Interface]] (iSCSI) over Ethernet and the [[Infiniband]] protocols may also be found implemented in SANs, but are often bridged into the Fibre Channel SAN. However, Infiniband and iSCSI storage devices, in particular, disk arrays, are available.<ref name="Dummies"/>((rp|47–48))

The various storage devices in a SAN are said to form the ''storage layer''. It can include a variety of [[hard disk]] and [[magnetic tape]] devices that store data. In SANs, disk arrays are joined through a [[RAID]] which makes a lot of hard disks look and perform like one big storage device.<ref name="Dummies"/>((rp|48)) Every storage device, or even partition on that storage device, has a [[logical unit number]] (LUN) assigned to it. This is a unique number within the SAN. Every node in the SAN, be it a server or another storage device, can access the storage by referencing the LUN. The LUNs allow for the storage capacity of a SAN to be segmented and for the implementation of access controls. A particular server, or a group of servers, may, for example, be only given access to a particular part of the SAN storage layer, in the form of LUNs. When a storage device receives a request to read or write data, it will check its access list to establish whether the node, identified by its LUN, is allowed to access the storage area, also identified by a LUN.<ref name="Dummies"/>((rp|148–149)) LUN masking is a technique whereby the host bus adapter and the SAN software of a server restrict the LUNs for which commands are accepted. In doing so LUNs that should never be accessed by the server are masked.<ref name="Dummies"/>((rp|354)) Another method to restrict server access to particular SAN storage devices is fabric-based access control, or zoning, which is enforced by the SAN networking devices and servers. Under zoning, server access is restricted to storage devices that are in a particular SAN zone.<ref>((Cite book|title= Storage Area Network Essentials: A Complete Guide to Understanding and Implementing SANs|url= https://archive.org/details/storageareanetwo00bark|url-access= limited|author1=Richard Barker |author2=Paul Massiglia |publisher= John Wiley & Sons|year=2002 |isbn=978-0-471-26711-9|page=[https://archive.org/details/storageareanetwo00bark/page/n228 198]))</ref>

== Network protocols ==
A mapping layer to other protocols is used to form a network:
* [[ATA over Ethernet]] (AoE), mapping of [[AT Attachment]] (ATA) over Ethernet
* [[Fibre Channel Protocol]] (FCP), a mapping of SCSI over Fibre Channel
* [[Fibre Channel over Ethernet]] (FCoE)
* [[ESCON]] over Fibre Channel ([[FICON]]), used by [[mainframe computer]]s
* [[HyperSCSI]], mapping of SCSI over Ethernet
* [[iFCP]]<ref>((cite web |url=http://www.techweb.com/encyclopedia/defineterm.jhtml?term=IPstorage |title=TechEncyclopedia: IP Storage |access-date=2007-12-09 |archive-date=9 April 2009 |archive-url=https://web.archive.org/web/20090409174610/http://www.techweb.com/encyclopedia/defineterm.jhtml?term=IPstorage |url-status=live ))</ref> or [[SANoIP]]<ref>((cite web |url=http://www.techweb.com/encyclopedia/defineterm.jhtml?term=SANoIP |title=TechEncyclopedia: SANoIP |access-date=2007-12-09 |archive-date=9 April 2009 |archive-url=https://web.archive.org/web/20090409174616/http://www.techweb.com/encyclopedia/defineterm.jhtml?term=SANoIP |url-status=live ))</ref> mapping of FCP over IP
* [[iSCSI]], mapping of SCSI over [[TCP/IP]]
* [[iSCSI Extensions for RDMA]] (iSER), mapping of iSCSI over [[InfiniBand]]
* [[Network block device]], mapping [[device node]] requests on [[UNIX-like|UNIX-like systems]] over [[stream socket]]s like TCP/IP
* [[SCSI RDMA Protocol]] (SRP), another SCSI implementation for [[remote direct memory access]] (RDMA) transports

Storage networks may also be built using [[Serial Attached SCSI]] (SAS) and [[Serial ATA]] (SATA) technologies. SAS evolved from SCSI direct-attached storage. SATA evolved from [[Parallel ATA]] direct-attached storage. SAS and SATA devices can be networked using [[Serial Attached SCSI#SAS expanders|SAS Expanders]].

{| class="wikitable" style="text-align:center"
|+ Examples of stacked protocols using SCSI
| colspan="7" | Applications
|-
| colspan="7" | [[SCSI]] Layer
|-
| rowspan="4" | [[Fibre Channel Protocol|FCP]]
| rowspan="3" | [[Fibre Channel Protocol|FCP]]
| [[Fibre Channel Protocol|FCP]]
| [[Fibre Channel Protocol|FCP]]
| rowspan="2" | [[iSCSI]]
| rowspan="2" | [[iSCSI Extensions for RDMA|iSER]]
| rowspan="2" | [[SCSI RDMA Protocol|SRP]]
|-
| [[Fibre Channel over IP|FCIP]]
| [[Internet Fibre Channel Protocol|iFCP]]
|-
| colspan="3" | [[Transmission Control Protocol|TCP]]
| colspan="2" | [[Remote direct memory access|RDMA]] Transport
|-
| [[Fibre Channel over Ethernet|FCoE]]
| colspan="3" | [[Internet Protocol|IP]]
| colspan="2" | [[Internet Protocol|IP]] or [[InfiniBand]] Network
|-
| [[Fibre Channel|FC]]
| colspan="4" | [[Ethernet]]
| colspan="2" | [[Ethernet]] or InfiniBand Link
|}

== Software ==
The [[Storage Networking Industry Association]] (SNIA) defines a SAN as "a network whose primary purpose is the transfer of data between computer systems and storage elements". But a SAN does not just consist of a communication infrastructure, it also has a software ''management layer''. This software organizes the servers, storage devices, and the network so that data can be transferred and stored. Because a SAN does not use [[direct attached storage]] (DAS), the storage devices in the SAN are not owned and managed by a server.<ref name="Tate"/>((rp|11)) A SAN allows a server to access a large data storage capacity and this storage capacity may also be accessible by other servers.<ref name="Tate"/>((rp|12)) Moreover, SAN software must ensure that data is directly moved between storage devices within the SAN, with minimal server intervention.<ref name="Tate"/>((rp|13))

SAN management software is installed on one or more servers and management clients on the storage devices. Two approaches have developed in SAN management software: in-band and out-of-band management. In-band means that management data between server and storage devices is transmitted on the same network as the storage data. While out-of-band means that management data is transmitted over dedicated links.<ref name="Tate"/>((rp|174)) SAN management software will collect management data from all storage devices in the storage layer. This includes info on read and write failures, storage capacity bottlenecks and failure of storage devices. SAN management software may integrate with the [[Simple Network Management Protocol]] (SNMP).<ref name="Tate"/>((rp|176))

In 1999 Common Information Model (CIM), an open standard, was introduced for managing storage devices and to provide interoperability, The web-based version of CIM is called Web-Based Enterprise Management (WBEM) and defines SAN storage device objects and process transactions. Use of these protocols involves a CIM object manager (CIMOM), to manage objects and interactions, and allows for the central management of SAN storage devices. Basic device management for SANs can also be achieved through the [[Storage Management Interface Specification]] (SMI-S), were CIM objects and processes are registered in a directory. Software applications and subsystems can then draw on this directory.<ref name="Tate"/>((rp|177)) Management software applications are also available to configure SAN storage devices, allowing, for example, the configuration of zones and LUNs.<ref name="Tate"/>((rp|178))

Ultimately SAN networking and storage devices are available from many vendors and every SAN vendor has its own management and configuration software. Common management in SANs that include devices from different vendors is only possible if vendors make the [[application programming interface]] (API) for their devices available to other vendors. In such cases, upper-level SAN management software can manage the SAN devices from other vendors.<ref name="Tate"/>((rp|180))

== Filesystems support ==
In a SAN, data is transferred, stored and accessed on a block level. As such, a SAN does not provide [[data file]] abstraction, only [[block-level storage]] and operations. Server operating systems maintain their own [[file system]]s on their own dedicated, non-shared LUNs on the SAN, as though they were local to themselves. If multiple systems were simply to attempt to share a LUN, these would interfere with each other and quickly corrupt the data. Any planned sharing of data on different computers within a LUN requires software. [[File systems]] have been developed to work with SAN software to provide [[file-level access]]. These are known as [[shared-disk file system]].

== In media and entertainment ==
[[Video editing]] systems require very high data transfer rates and very low latency. SANs in media and entertainment are often referred to as serverless due to the nature of the configuration which places the video workflow (ingest, editing, playout) desktop clients directly on the SAN rather than attaching to servers. Control of data flow is managed by a distributed file system. Per-node bandwidth usage control, sometimes referred to as [[quality of service]] (QoS), is especially important in video editing as it ensures fair and prioritized bandwidth usage across the network.

== Quality of service ==
SAN Storage QoS enables the desired storage performance to be calculated and maintained for network customers accessing the device. Some factors that affect SAN QoS are:
* [[Bandwidth (computing)|Bandwidth]]((snd)) The rate of data throughput available on the system.
* [[Latency (engineering)|Latency]]((snd)) The time delay for a read/write operation to execute.
* Queue depth((snd)) The number of outstanding operations waiting to execute to the underlying disks (traditional or [[solid-state drive]]s).

Alternatively, [[over-provisioning]] can be used to provide additional capacity to compensate for peak network traffic loads. However, where network loads are not predictable, over-provisioning can eventually cause all bandwidth to be fully consumed and latency to increase significantly resulting in SAN performance degradation.

== Storage virtualization ==
[[Storage virtualization]] is the process of abstracting logical storage from physical storage. The physical storage resources are aggregated into storage pools, from which the logical storage is created. It presents to the user a logical space for data storage and transparently handles the process of mapping it to the physical location, a concept called [[location transparency]]. This is implemented in modern disk arrays, often using vendor-proprietary technology. However, the goal of storage virtualization is to group multiple disk arrays from different vendors, scattered over a network, into a single storage device.  The single storage device can then be managed uniformly.<ref>((cite web|last1=PC Magazine|title=Virtual Storage|url=https://www.pcmag.com/encyclopedia/term/53951/virtual-storage|website=PC Magazine Encyclopedia|access-date=17 October 2017|archive-date=30 August 2019|archive-url=https://web.archive.org/web/20190830110653/https://www.pcmag.com/encyclopedia/term/53951/virtual-storage|url-status=live))</ref>

== See also ==
* [[List of networked storage hardware platforms]]
* [[List of storage area network management systems]]
* [[Massive array of idle disks]] (MAID)
* [[Storage hypervisor]]
* [[Storage resource management]] (SRM)
* [[Converged storage]]

== References ==
<references/>

== External links ==
<!-- ATTENTION! Please do not add links without discussion and consensus on the talk page. Undiscussed links will be removed. -->
* [https://www.snia.org/education/storage_networking_primer/san/what_san What Is a Storage Area Network (SAN)?]
* [https://www.redbooks.ibm.com/redbooks/pdfs/sg245470.pdf Introduction to Storage Area Networks Exhaustive Introduction into SAN], [[IBM Redbooks|IBM Redbook]]
* ((webarchive |url=https://web.archive.org/web/20111030172419/http://capitalhead.com/articles/san-vs-das-a-cost-analysis-of-storage-in-the-enterprise.aspx |title=SAN vs. DAS: A Cost Analysis of Storage in the Enterprise))
* [http://searchstorage.techtarget.co.uk/generic/0,295582,sid181_gci1516893,00.html SAS and SATA, solid-state storage lower data center power consumption] ((Webarchive|url=https://web.archive.org/web/20101018190550/http://searchstorage.techtarget.co.uk/generic/0,295582,sid181_gci1516893,00.html |date=18 October 2010 ))
* [https://www.youtube.com/playlist?list=PLivYD7W2z2HMGGRIwRoRcqLL4HMpR1dIe SAN NAS Videos]

((Authority control))

((DEFAULTSORT:Storage Area Network))
[[Category:Data management]]
[[Category:Telecommunications engineering]]
[[Category:Storage area networks| ]]

Pages transcluded onto the current version of this page (help):

Storage area network (edit)
Template:Area networks (edit)
Template:Authority control (view source) (template editor protected)
Template:Cite book (view source) (protected)
Template:Cite web (view source) (protected)
Template:DMCA (view source) (template editor protected)
Template:Dated maintenance category (view source) (template editor protected)
Template:Dated maintenance category (articles) (view source) (template editor protected)
Template:Distinguish (view source) (template editor protected)
Template:FULLROOTPAGENAME (view source) (template editor protected)
Template:Fibre Channel (edit)
Template:Hlist/styles.css (view source) (protected)
Template:Infobox (view source) (template editor protected)
Template:Main other (view source) (protected)
Template:Ns has subpages (view source) (protected)
Template:Pagetype (view source) (protected)
Template:R/superscript (view source) (template editor protected)
Template:R/where (view source) (template editor protected)
Template:Rp (view source) (template editor protected)
Template:SDcat (view source) (protected)
Template:Short description (view source) (protected)
Template:Short description/lowercasecheck (view source) (protected)
Template:Sidebar (view source) (template editor protected)
Template:Snd (view source) (template editor protected)
Template:Spaced en dash (view source) (template editor protected)
Template:Template other (view source) (protected)
Template:Use American English (view source) (template editor protected)
Template:Use dmy dates (view source) (template editor protected)
Template:Webarchive (view source) (template editor protected)
Module:Arguments (view source) (protected)
Module:Authority control (view source) (template editor protected)
Module:Authority control/config (view source) (template editor protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:DecodeEncode (view source) (template editor protected)
Module:Disambiguation/templates (view source) (protected)
Module:Distinguish (view source) (template editor protected)
Module:EditAtWikidata (view source) (protected)
Module:Format link (view source) (template editor protected)
Module:GetParameters (view source) (template editor protected)
Module:Hatnote (view source) (template editor protected)
Module:Hatnote/styles.css (view source) (template editor protected)
Module:Hatnote list (view source) (template editor protected)
Module:Infobox (view source) (template editor protected)
Module:Infobox/styles.css (view source) (template editor protected)
Module:Navbar (view source) (protected)
Module:Navbar/configuration (view source) (protected)
Module:Navbar/styles.css (view source) (protected)
Module:Navbox (view source) (template editor protected)
Module:Navbox/configuration (view source) (template editor protected)
Module:Navbox/styles.css (view source) (template editor protected)
Module:Ns has subpages (view source) (protected)
Module:Pagetype (view source) (protected)
Module:Pagetype/config (view source) (protected)
Module:Pagetype/disambiguation (view source) (protected)
Module:Pagetype/setindex (view source) (protected)
Module:Pagetype/softredirect (view source) (protected)
Module:Plain text (view source) (template editor protected)
Module:SDcat (view source) (protected)
Module:Sidebar (view source) (template editor protected)
Module:Sidebar/configuration (view source) (template editor protected)
Module:Sidebar/styles.css (view source) (template editor protected)
Module:String (view source) (protected)
Module:String2 (view source) (template editor protected)
Module:TableTools (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Webarchive (view source) (template editor protected)
Module:Webarchive/data (view source) (template editor protected)
Module:Wikitext Parsing (view source) (protected)
Module:Yesno (view source) (protected)

Return to Storage area network.

Retrieved from "https://en.wikipedia.org/wiki/Storage_area_network"