News Detail

Industry Insights and Updates

What is a SAN switch? Roles, types, and use cases

A SAN switch connects servers to shared storage within a storage area network. In a Fibre Channel environment, it forwards storage traffic and provides fabric services that help devices communicate. It is one part of a complete storage path, alongside host adapters, cables, storage controllers, software, and access settings.

The term can cause confusion because a SAN describes the storage network, while Fibre Channel describes a technology used to build it. Ethernet can also carry storage traffic, including iSCSI. Choosing equipment therefore starts with identifying the intended protocol and supported connections, rather than looking for an optical port or a particular brand.

This guide explains the device’s role, the main equipment types, and the questions to ask before selecting a configuration. A SAN switch can support a resilient storage design, but the chassis alone does not guarantee application speed, continuous availability, or a trouble-free upgrade.

How a SAN switch fits into the storage path

how a san switch fits into the storage path (1)

Think of the fabric as the connection system between hosts and shared storage. A host runs the application and sends storage requests. In a native Fibre Channel design, a host bus adapter, or HBA, provides the host’s FC connection. The fabric connects that interface to an appropriate storage endpoint.

IBM’s SAN overview explains the relationship between servers, storage, and network infrastructure. Keeping those components separate makes troubleshooting and equipment selection easier: a problem at one layer should not automatically be blamed on another.

Follow a request through the components

Use the following simplified path to identify the equipment in a proposed design:

Host application
 |
Host operating system and supported HBA
 |
FC link and SAN switch fabric
 |
Storage controller and shared storage

This is a conceptual illustration, not a production wiring plan. A real installation may have multiple adapters, switches, controllers, and paths. The operating system, storage software, and supported configuration determine how those paths are used.

When someone requests a SAN switch replacement, first identify which part of this path is changing. Replacing a chassis is different from changing the storage protocol, adding an array, or moving to a new host software release. Each change can introduce different compatibility checks.

Distinguish forwarding from storage access

A switch connects devices and carries traffic; it does not replace the array’s storage controls or the host’s storage configuration. A connected cable is only one condition for a usable service. The intended devices must also have the correct permissions, supported software, and configured paths.

Start an inventory with the host, HBA, switch, and storage identifiers. Add software versions and the intended protocol. This gives an engineer enough information to investigate a connection without relying on vague descriptions such as “the server cannot see the disk.”

Illustrative scenario: A team adds a host and sees an active link on the front panel. The storage volume is still unavailable. Instead of ordering another SAN switch, the team checks the approved connection and access records. The example shows why link status is not the same as an end-to-end service test; it is not a report of a customer incident.

What does a SAN switch do inside a fabric?

A Fibre Channel fabric does more than provide sockets. Its services and configuration help establish communication between attached devices. The exact features and limits depend on the platform and software release, so a feature described for one family should not be assumed on every model.

The Broadcom SAN design guide is a useful reference for fabric design and operation. For a specific installation, use the documentation and support requirements for the actual equipment and releases involved.

Forwarding, discovery, and controlled communication

At an introductory level, distinguish three tasks: moving frames, helping devices identify available fabric services, and controlling which devices may communicate. Those tasks are related, but they are not interchangeable. A forwarding-capable port does not by itself establish the intended storage access.

Zoning is a fabric access-control mechanism. It should be considered alongside, rather than substituted for, the storage array’s access configuration. Use the appropriate vendor procedures when defining or changing that configuration. This article explains the role of a SAN switch; it is not a version-independent set of production commands.

Flow control has operating conditions

Fibre Channel uses credit-based flow control to regulate frame transmission. That mechanism should not be described as a promise that errors, congestion, or application interruptions cannot occur. Cable faults, endpoint behavior, configuration problems, and workload conditions still need investigation.

Likewise, a product’s switching-latency specification does not describe the complete application response time. The host, storage system, links, and workload all contribute to the service. Evaluate a SAN switch within that whole environment instead of translating one hardware figure into a database performance claim.

Diagnostics support investigation

Monitoring and diagnostic features can help operators inspect links and storage traffic. Ask which functions the selected platform provides, which software release is required, and whether additional licensing or management tools apply. Built-in hardware capability is not a complete statement of operating entitlement.

Assign responsibility for reviewing alerts and recording configuration changes. A SAN switch can produce useful operational information only when someone knows how it fits into the service and what action an observation should trigger. Keep that ownership in the handover record.

Equipment types and protocol boundaries

equipment types and protocol boundaries

Separate physical form, architectural role, and protocol support when comparing devices. These are different classification questions. Describing a device as NVMe/FC-capable does not tell you whether it is a fixed switch or a modular director, how many connections are enabled, or what the complete deployment supports.

Fixed switches and modular directors

ClassificationWhat it describesWhat to check
Fixed-configuration switchA platform with a defined chassis and port arrangementEnabled ports, expansion options, and installation needs
Modular directorA chassis with supported modules and larger fabric rolesModule combinations, redundancy, supported limits, and operations
Edge or core roleThe device’s position in an approved topologyTraffic paths, connections, and failure conditions
NVMe/FC capabilitySupport for a particular storage deploymentExact host, adapter, array, switch, and software combination

Avoid assuming that a larger chassis is automatically the right SAN switch for a critical application. Start with the approved architecture, connection requirements, and operating model. A small fabric and an expansion of a large installed fabric can have very different constraints.

Native FC, Ethernet storage, and convergence

TermMeaning in this discussionEquipment implication
Native Fibre ChannelDedicated FC connectivity and fabric operationRequires appropriate FC interfaces and a supported design
iSCSIStorage communication using IP networkingRequires an appropriate Ethernet/IP storage design
FCoEFibre Channel traffic carried over EthernetRequires explicit support across the intended converged path
NVMe/FCNVMe communication over Fibre ChannelRequires a supported end-to-end combination

An Ethernet switch is not a native FC SAN switch simply because both use optical modules. Equally, storage traffic on Ethernet does not mean the network is unsuitable for storage. The correct comparison is between supported designs that meet the actual requirements.

Our data center switch guide explains the Ethernet equipment side. Keep Ethernet and native FC connection plans distinct until the required interfaces and protocols are confirmed. Do not select a transceiver by connector shape alone.

Illustrative scenario: A procurement request says “fiber switch for shared storage.” Before selecting hardware, the team asks whether the array uses native FC or an IP storage connection, then collects host and controller details. That clarification determines which equipment needs evaluation. No savings or performance result is assumed.

Common uses and availability considerations

A SAN switch may be part of a shared-storage design for virtualized hosts, database services, or other enterprise workloads. The application name alone does not determine the correct model or connection speed. What matters is the supported storage architecture and the service requirements.

Shared storage and fabric growth

When adding hosts or storage, identify the new connections and their intended paths. Count ports by fabric and by purpose. Host-facing, storage-facing, and inter-switch connections may consume different parts of the available capacity, while licenses and media affect what can actually be deployed.

For an existing installation, also ask which equipment and software will remain. An expansion introduces a SAN switch into a specific environment; it is not a blank-slate purchase. Record compatibility questions before treating the proposed platform as approved.

Redundancy needs more than duplicate boxes

A dual-fabric design can provide separate storage paths, but the hosts, adapters, controllers, power arrangements, and configuration need to support the intended behavior. The existence of two switches is not evidence that every failure is covered.

Write down the failures the service must tolerate and how the team will verify them. Keep the expected behavior and rollback conditions with the change plan. A SAN switch specification cannot substitute for testing the relevant host and storage paths under an approved procedure.

If you are mapping an existing environment, share the host, storage, and connection details with CREA DAS TECH. State which parts are known and which still need confirmation. This gives the equipment discussion a clearer starting point than a request based only on port speed.

A bounded example: Cisco MDS 9148T

a bounded example cisco mds 9148t

The Cisco MDS 9148T is a useful example of a fixed FC platform. Its official data sheet identifies the DS-C9148T-48PETK9 ordering option with 48 active ports, 48 32G shortwave optics, four fans, two power supplies, and port-side exhaust.

That description is specific to the ordering option. It should not be generalized to every MDS 9148T offer or used as proof of the contents of a supplier’s current shipment. Confirm the quoted part number, supplied components, condition, and applicable support terms.

The MDS 9148T product reference provides a starting point for a configuration discussion. A SAN switch listing is not confirmation of current inventory, software rights, or every function mentioned in a product-family document.

Active ports and feature rights are separate questions

Do not infer that an order with all ports activated includes every software feature or management service. The Cisco MDS licensing guide distinguishes licensing requirements and their applicable platforms or releases. Check the functions you need against the exact supported configuration.

For this reason, a useful SAN switch request names the required capabilities and asks how they are supplied. Avoid blanket descriptions such as “fully licensed,” “no extra software costs,” or “nondisruptive under all conditions” without the evidence and scope needed to support them.

Questions to answer before choosing equipment

Use a short discovery checklist before comparing prices. You do not need a complete engineering design to begin, but unanswered questions should remain visible. They should not become silent assumptions when the proposed SAN switch appears in a quotation.

  1. Which storage protocol and connections are required?
  2. What are the exact host, adapter, array, and software identifiers?
  3. Is this a new fabric, an expansion, or a replacement?
  4. How many connections are needed on each side, including planned growth?
  5. Which failure and maintenance conditions must the service support?
  6. Which media, licenses, management tools, and support arrangements apply?

For the full decision process, use the Fibre Channel switch buying guide. For brand-specific options, consult the Brocade selection guide. Those resources take the next step from understanding the device to comparing complete configurations.

Is every SAN based on Fibre Channel?

No. A storage area network can use different connection technologies. Native FC and IP-based storage designs have different equipment and support requirements. Identify the protocol before deciding what the SAN switch must do; an optical connection alone does not answer that question.

Will a faster switch make storage applications faster?

Not necessarily. First identify the constraint using observations from the host, links, and storage system. A SAN switch upgrade may address a particular requirement, but it does not prove an application outcome. Agree on service measurements before treating speed as the business case.

Can NVMe/FC be enabled on any existing fabric?

Do not assume it. Check the exact switches, software, HBAs, drivers, and storage system against the relevant vendor support information. Protocol capability at one point in the path does not establish compatibility across the entire deployment.

What should I send with an equipment inquiry?

Send the current models, versions, protocol, connection counts, intended change, and support expectations. Include the destination and quantities when requesting an offer. If those details are incomplete, identify the missing fields so they can be resolved before a configuration is approved.

When you are ready, request a configuration-specific discussion. A SAN switch decision starts with a clear storage path and ends with equipment, software, media, and support that match the approved design.

Previous News Fibre Channel switch buying guide: design to procurement