sas-expander · shipping · also expander device, SAS expander device

SAS expander

A SAS expander routes connections among SAS initiators, targets and other expanders, allowing access to more devices than an initiator can attach directly.

Related Observatory article: Read on hesela.com

Direct, table and subtractive routing resolve connections through a SAS domain. SSP carries SCSI traffic, STP tunnels SATA traffic, and SMP supports management. Tunneling is not SCSI-to-ATA command translation. [1] [3] [9]

Early edge/fanout rules belong to SAS-1 history. The 2006 table-to-table proposal discusses the earlier single-fanout and 128-address-per-edge-expander-set restrictions; these are not universal limits for later equipment. [5]

Later expander implementations support self-configuration and table-to-table routing. One documented 12 Gb/s family supports up to 4K SAS addresses. An address count is not a supported-drive count: controller, routing-table and enclosure limits must also be checked. [6]

Host compatibility matters. A 2011 switch firmware release requires a SAS-2 HBA with Allow Table-to-Table Links enabled for its cascaded configuration and excludes SAS-1 HBAs from that arrangement. The requirement is specific to that implementation. [7]

Routing and permission are separate. A zoning expander can restrict communication through PHY zone groups and access permissions. Physical connection alone therefore does not establish host access. [8]

A missing discovery entry is not sufficient evidence of a disconnected device: zoning-hidden PHYs may be reported as 'phy vacant'. The request options and initiator context belong in the diagnostic record. [10]

Relations

related
Serial Attached SCSI (SAS), JBOD, Enterprise SSD, Disk shelf, Serial SCSI Protocol, Serial ATA Tunneled Protocol, Serial Management Protocol, SAS physical PHY, SAS wide port, SAS zoning, SCSI Enclosure Services

Advantages

  • Fan-out allows a host connection to reach multiple storage devices through routed paths. [3]
  • Supporting implementations provide self-configuration and table-to-table routing for larger topologies. [6]
  • Zoning-capable implementations can restrict which hosts may access attached storage. [8]

Limitations

  • Attached devices share upstream link and controller resources; more reachable drives do not imply proportionally higher throughput. [3]
  • Topology and scale limits must be checked for the HBA, expander, firmware and configuration rather than copied from early edge/fanout diagrams. [5, 7]
  • A zoning permission changes access, not encryption, replica count or the independence of power and physical paths. [8]

Citations

  1. Serial Attached SCSI Technical Overview, T10/02-158r1 (Rob Elliott, 6 May 2002; committee slide deck) (accessed 2026-10-16)
  2. Introduction to Serial Attached SCSI, appendix G of an HBA installation guide (vendor documentation, not the T10 standard), Oracle (accessed 2026-10-16)
  3. Microchip SXP 12 Gbps SAS Expander Family, DS00003036A (July 2019), pp. 1-2: table-to-table routing, zoning and address support (accessed 2026-10-20)
  4. LSISAS6160 r201.12.00.00 firmware release notes (November 2011), p. 6: Cascaded Switches with SAS-1 and SAS-2 HBAs (accessed 2026-10-20)
  5. Oracle Sun Blade Storage Module M2 Service Manual (January 2012), pp. 9-10 and 12: zoning, access permissions and dual paths (accessed 2026-10-20)
  6. T10 working drafts: SCSI / ATA Translation scope (accessed 2026-10-20)
  7. Oracle Solaris smp_discover(8), July 2022: --ignore and zoning-hidden PHYs (accessed 2026-10-21)

Further reading

  1. SAS General overview (Rob Elliott, 30 September 2003; slide deck, third-party mirror copy) (accessed 2026-10-16)
  2. T10/04-331r1: SAS-1.1 PHY Definitions and Acronyms update (16 November 2004), working-draft definitions (accessed 2026-10-16)
Sources & caveats
  • Source review, not a hardware benchmark or topology certification. T10/06-189r0 is a historical proposal, not the final SAS-2 standard.
  • The 4K-address example is Microchip SXP 12G, DS00003036A; the cascade constraint is LSISAS6160 r201.12.00.00, November 2011. Neither is a universal SAS limit.
  • Oracle's Sun Blade Storage Module M2 documentation separates host assignments from dual-path hardware. Encryption and failure-domain limits are engineering consequences of permission control, not measured results.

JSON: /data/terms/sas-expander.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. SAS expander. Hesela. 2026-11-03. https://hesela.dev/terms/sas-expander/