ALUA
Asymmetric Logical Unit Access is the SCSI mechanism for reporting logical-unit access states through target port groups.
REPORT TARGET PORT GROUPS describes access to a logical unit through target port groups. Active/optimized and active/non-optimized are states, not latency measurements. Linux v6.12 stores the current state, preferred (PREF) flag and supported-state mask separately. [5]
Topology: A local-active configuration can mark owning-node paths optimized and partner paths non-optimized. An active-active configuration can expose optimized paths through both nodes of an HA pair. An extra controller hop is not a universal property of ALUA. [6]
Transitions: Implicit transitions occur without a SET TARGET PORT GROUPS request; explicit transitions use that command when supported. After issuing that command, Linux v6.12 requests another REPORT TARGET PORT GROUPS evaluation. Re-observation is distinct from merely requesting a change. [5]
Host policy: The documented multibus setting combines differently prioritized paths into one group. The example priorities 50 and 10 are host values, not SCSI access-state codes. [3]
Protocol: NVMe uses the separate ANA mechanism. Linux native NVMe multipath prefers an available optimized path before applying its path-selection policy. [4]
Relations
- related
- Multipath I/O, SAN, iSCSI, Fibre Channel, SCSI, NVMe multipath, NVMe over Fabrics, FCoE, Dual-port drive, Asymmetric Namespace Access, I/O fencing
Advantages
- Target-side information helps multipath software adapt routing when controller access changes. [5]
Limitations
- An optimized route does not establish exclusive application-writer ownership. [5]
- Transport faults, host recovery policy and array configuration still affect service restoration. [5, 6]
Citations
- How to setup preferred path with multipath (Red Hat Customer Portal)
- Linux NVMe multipath (Linux kernel documentation)
- Linux v6.12: scsi_dh_alua.c, alua_rtpg and alua_stpg state handling
- NetApp ONTAP: SAN multipathing configurations and automatic LIF failover
Further reading
- Linux SCSI Target - Asymmetric Logical Unit Assignment
- Why are there Active/Optimized and Active/Unoptimized paths on Windows Server LUNs? (NetApp KB)
Sources & caveats
- Source synthesis, not an array failover experiment. Linux v6.12 lines 658-670 separate state, PREF and support; alua_stpg lines 742-787 checks explicit support and requests state re-evaluation. [5]
- NetApp configuration support varies with platform, release and protocol; the local-active and active-active examples do not define all ALUA implementations. [6]
- Red Hat's diagnostic example concerns RHEL 7 device-mapper-multipath; its priorities are not standardized wire values. [3]
- Writer-ownership and latency limits are engineering inferences from the scope of access-state reporting, not measured performance results.