IBM i FlashSystem Attachment: VIOS, NPIV, and Software Compatibility Requirements

Two different attachment paths, and they are not interchangeable

Native attach connects an IBM i partition directly to external SAN storage over its own Fibre Channel adapter, with no VIOS layer involved. VIOS with NPIV instead routes the connection through a Virtual I/O Server partition, which presents a virtual Fibre Channel port to the IBM i client partition using N_Port ID Virtualization. Both reach the same FlashSystem array, but they are configured differently, have different adapter and licensing implications, and are not always both available on a given Power server and IBM i release combination.

What VIOS and NPIV actually require

NPIV support is a chain, not a single setting. Historically, IBM has required IBM i 6.1 or later and Power6 or later server technology for VIOS support, with NPIV specifically requiring IBM i Licensed Internal Code 6.1.1 or later, NPIV-capable physical Fibre Channel adapters, and SAN switches that support NPIV. A project that confirms IBM i and VIOS software levels but overlooks the adapter or switch fabric will still fail to attach.

• IBM i and VIOS software levels support NPIV
• The physical Fibre Channel adapter in the Power server is NPIV-capable, not just Fibre Channel capable
• The SAN switch fabric between the Power server and the FlashSystem array supports NPIV zoning
• The target FlashSystem array is configured for IBM i host attachment specifically

FlashSystem-side firmware also has a floor

On the array side, FlashSystem storage runs on IBM Storage Virtualize (the software layer covered in the Storage Virtualize licensing guide), and that software has its own minimum firmware level for supported IBM i attachment. Historical baselines have cited Storage Virtualize/SVC firmware 6.4.1.5 or higher as a floor for FlashSystem-based external storage attachment; current FlashSystem generations expect a materially newer firmware level than that baseline. Confirm the current minimum against IBM's published documentation for the specific FlashSystem model and FlashCore Module generation in the quote, rather than assuming an older baseline still applies.

Newer Fibre Channel speeds change the protocol conversation too

32Gb and 64Gb Fibre Channel adapters support NVMe over Fibre Channel (NVMe-oF) in addition to traditional SCSI-based FC, and 25/100Gb RoCE Ethernet supports NVMe over RDMA. This matters for planning because it means the host adapter generation, not just its raw link speed, determines whether an environment can eventually take advantage of NVMe-based attachment protocols as IBM's storage software stack extends support for them, separate from the FlashCore Module generation running inside the array itself.

Build the compatibility check into the project plan, not the punch list

The software and firmware compatibility question should be answered before hardware is ordered, not discovered during installation. Confirm the Power server's supported attachment path (native, VIOS/NPIV, or both), the IBM i and VIOS version minimums for that path, the SAN adapter and switch NPIV support if applicable, and the FlashSystem array's minimum Storage Virtualize firmware level for IBM i attachment, all against IBM's current published support matrix for the exact hardware in the quote.

Common questions about this Storage Software Licensing topic.

Does every IBM i partition need VIOS to reach FlashSystem storage?

No. Some Power server and IBM i release combinations support native direct or SAN Fibre Channel attach without a VIOS layer. VIOS with NPIV becomes necessary when the design calls for virtualized, shared Fibre Channel adapters across multiple client partitions rather than a dedicated adapter per partition.

What is NPIV and why does it matter for FlashSystem attachment?

N_Port ID Virtualization (NPIV) lets a single physical Fibre Channel adapter present multiple virtual Fibre Channel ports, each with its own worldwide port name, so a VIOS partition can share adapters across several IBM i, AIX, or Linux client partitions while each client still appears as its own distinct host to the FlashSystem array. It requires NPIV support at the IBM i, VIOS, physical adapter, and SAN switch level simultaneously.

Where do I find the current minimum IBM i, VIOS, and Storage Virtualize firmware levels for FlashSystem attachment?

IBM publishes an IBM i external storage support matrix and per-model FlashSystem hardware interoperability matrices. Because minimums move forward across IBM i releases and FlashSystem generations, confirm the current figures against IBM's published documentation for the specific Power server, IBM i release, and FlashSystem model in the project rather than relying on a fixed number.