FlashArray Compatibility Matrix
FlashArray Compatibility Matrix
The compatibility matrix lists third-party products that have been fully tested and qualified for use with the Pure Storage
FlashArray.
This Matrix is for FC/iSCSI only. For NVMe/RoCE support, please go here -- https://support.purestorage.com/Solutions/
SAN/SAN_Configuration/NVMe-oF_Support_Matrix
Pure Storage provides best-effort integration support for all vendors/models. If a specific vendor or product model is not
listed, please contact your Pure Storage representative to determine if it is supported. Pure Storage certifies major
versions of Purity and will support appropriate minor versions.
Please refer to best practices documentation in the Solutions section for your environment when deploying FlashArray
with supported operating systems and hypervisors. Following best practices, documentation will help optimize
FlashArray performance and resiliency for the supported operating systems and hypervisors.
For any caveats related to switch and HBA connectivity, please see our field support bulletin. The bulletin will cover
caveats with 3rd party hardware products and list mitigation steps.
For related FlashArray product information, see Supported SFP Modules FA-400.
For related FlashArray hardware troubleshooting, see FlashArray Transceiver and Cable Support.
Operating Systems
Unless otherwise specified, Pure Storage supports all major operating system versions listed plus their minor and
maintenance releases.
AIX ActiveCluster
FlashArray//M, //X,
FA-300 FA-400
//C
AIX 6.1
AIX 7.1
ActiveCluster
FlashArray//M, //X,
IBMi FA-300 FA-400
//C
IBM VIOS
ActiveCluster
(Standard and FlashArray//M, //X,
FA-300 FA-400
Enterprise //C
Editions)
ActiveCluster
FlashArray//M, //X,
HP-UX FA-300 FA-400
//C
HP-UX 11i v2
-
(B.11.23)
HP-UX 11i v3
(B.11.31)
Linux ActiveCluster
FlashArray//M, //X,
FA-300 FA-400
//C
CentOS
(Equivalent to RHEL
-- see below) Refer to RHEL versions for supported platforms
Oracle Enterprise
Linux 5.6 and higher
Oracle Enterprise
Linux 6.5 and
Higher (See Note 1
& 2)
Oracle Enterprise
Linux 7.0 and -
Higher
Oracle Enterprise
Linux 8.0 and -
Higher
Debian 8.11 -
Ubuntu 16.04 -
Ubuntu
18.04.02 LTS (See -
Note 4)
Ubuntu
18.04.03 LTS (See -
Note 4)
Notes
1 iSCSI multipath boot from SAN is currently not supported at installation on some releases
2 Installation directly onto multipath SAN LUN on RHEL 6.9, 6.10 and OEL 6.7 not
supported due to RedHat bug. https://access.redhat.com/solutions/4466491 Install OS
on single path device and later add another path to devices .Refer OS vendor
documentation for "Moving root filesystem from single path device to multiple path device.
3 Qlogic FC driver 10.01.00.48.12.4 or higher recommended.
4 Contact [email protected] for Ubuntu settings, until Best Practices are finalized and
published.
5 Recommend update to kernel version 3.12.55-52.42
Microsoft ActiveCluster
FlashArray//M, //X,
FA-300 FA-400
//C
Windows Server
**AC
2008 R2 SP1
Windows Server
- **AC
2012
Windows Server
- **AC
2012 R2
Windows Server
- **AC
2016, x64
Windows Server
- **AC
2019, x64
Solaris 10 u8 or
***
greater / SPARC *
Solaris 10 u8 or
greater / x64 *
Solaris 11.2
SPARC* **
***
FlashArray//M, //X,
OpenVMS FA-300 FA-400 ActiveCluster
//C
UCS 2.2(2)
(FC, iSCSI, Direct Attach)
UCS 2.2(3)
(FC, iSCSI, Direct Attach)
UCS 2.2(6)
-
(FC, iSCSI, Direct Attach)
UCS 2.2(7)
-
(FC, iSCSI, Direct Attach)
UCS 3.1(1)
-
(FC, iSCSI, Direct Attach)
UCS 3.1(2)
-
(FC, iSCSI, Direct Attach)
UCS 3.1(3)
-
(FC, iSCSI, Direct Attach)
UCS 3.2(2)
-
(FC, iSCSI, Direct Attach)
UCS 3.2(3)
-
(FC, iSCSI, Direct Attach)
UCS 4.0(1)
-
(FC, iSCSI, Direct Attach)
UCS 4.0(2)
-
(FC, iSCSI, Direct Attach)
UCS 4.0(4)
-
(FC, iSCSI, Direct Attach)
UCS 4.1(1)
(FC, iSCSI, NVMe/RoCE, -
Direct Attach)
Note: the letters inside brackets are considered UCS maintenance releases and are supported, unless specifically called out here for example 3.1(2e) is
also supported.
Storage
DataCore FA-300 FA-400 FlashArray//M, //X, //C
SANsymphony-V -
VPLEX 5.3+
-
Please see guide for
details on support
-
Please see guide for
details on support
Symantec Storage
Foundation FA-300 FA-400 FlashArray//M, //X, //C
(rebranded Infoscale)
Solaris SPARC SF /
- -
SFHA 5.1
Windows
2008R2 / SFRAC 6.0,6.1, -
6.2, 7.1, 7.2,7.3, 7.4, 7.4.1
FlashArray//M,
Veritas Infoscale FA-400 ActiveCluster
FlashArray//X, //C
Solaris (SPARC) /
**
Infoscale 7.4
RHEL (x86_64) / **
** Requires Updated ALUA ASL from Verita that is not part of initial Infoscale install
Hypervisors
Citrix ActiveCluster
FlashArray//M, //X,
FA-300 FA-400
//C
XenServer 7.0,
7.1,7.2,7.3, 7.5, 7.6,
-
8.0, 8.1 (FC &
iSCSI)
XenDesktop 7.0 - -
XenDesktop 7.5,
-
7.6,7.7,7.8,7.9
ActiveCluster
FlashArray//M, //X,
Linux FA-300 FA-400
//C
RHEV/oVIRT 4.x
Microsoft ActiveCluster
FlashArray//M, //X,
FA-300 FA-400
//C
ActiveCluster
FlashArray//M, //X,
Oracle FA-300 FA-400
//C
Oracle VM 3.2
Oracle VM 3.4.3 FC
& iSCSI
Note: iSCSI Chap not
supported
Oracle VM 3.4.4 FC
ActiveCluster
VMware
FlashArray//M, //X,
FA-300 FA-400
//C
*AC
* VAAI must be enabled on the ESXi hosts that are connected to Pure Storage FlashArray devices. Contact
Pure Storage Support if VAAI is disabled.
* ** NVMe-oF Fibre Channel is only supported on FlashArray//X and C and only with 7.0 U1 and later.
*AC - VMware VAAI copy offload (XCOPY) works only between volumes in the same pod. Copy operations
across pod boundaries will be treated as normal copies.
**AC - Microsoft ODX (Offloaded Data Transfer) is not supported with ActiveCluster. Copy operations inside
pods or across pod boundaries will be treated as normal copies.
ActiveDR adds the ability to promote and demote pods to Purity//FA. While a pod is demoted (the default state of an
ActiveDR target pod) the volumes in that pod are read-only. To perform an ActiveDR test failover or real failover you
promote the pod causing the volumes in the pod to become writable.
Hosts may be connected to the volumes in the demoted pod* before a failover is performed however it is not required.
It is important to configure host personalities in Purity according to the type of host as described in the Host Personality
in Purity KB Article.
*Note that connecting NVME hosts to volumes in demoted pods is not allowed. NVME hosts must be connected after
the pod is promoted and disconnected before the pod is demoted.
FC Loop Support
A Host Operating System that requires the array to be in an FC-Loop mode is not supported at this time.
Emulex has identified a bug with certain versions of the Emulex HBA Driver where the FC drivers may acquire an
incorrect ring lock during abort processing. This opens a very small window where two consecutive I/Os could be
sent to the same WQ index, causing one of them to be dropped. These dropped I/Os can lead to data integrity
issues.