Support Matrix

HPE Peer Persistence

Host OS Support Matrix
HPE 3PAR StoreServ

20th September 2019, version 1.0

Support Matrix

Document Revision History

Document Version Date Section and Text Revised

1.0 20th September 2019 Initial Release

Support Matrix

Contents
Document Revision History ..................................................................................................................................................... 1
Introduction.............................................................................................................................................................................. 3
Support Notes ...................................................................................................................................................................... 3
HPE Peer Persistence for AIX and IBM VIO Server ............................................................................................................... 4
HPE Peer Persistence for Citrix XenServer ............................................................................................................................ 5
HPE Peer Persistence for HP-UX ........................................................................................................................................... 6
HPE Peer Persistence for Oracle VM Server for x86 (Oracle VM) ......................................................................................... 7
HPE Peer Persistence for Red Hat Enterprise Linux (RHEL) ................................................................................................. 8
HPE Peer Persistence for Solaris ........................................................................................................................................... 9
HPE Peer Persistence for SuSE Linux Enterprise Server (SLES) ....................................................................................... 10
HPE Peer Persistence for VMware vSphere and ESXi ........................................................................................................ 11
HPE Peer Persistence for Microsoft Windows Server .......................................................................................................... 12
Support Matrix Page 3

Introduction
Host ecosystem interoperability support with HPE Peer Persistence is a subset of the HPE 3PAR Interoperability listings of HPE
Storage SPOCK (see “Explore HPE 3PAR Storage interoperability”) https://www.hpe.com/Storage/Spock/ .The subset of supported
host ecosystems (host OS’s) for HPE Peer Persistence for 3PAR StoreServ are enumerated in this matrix.

Hosts in a Peer Persistence configuration must be set up in accordance with the recommendations found in the associated HPE 3PAR
Host OS Implementation Guides and conform to supported configurations per the HPE 3PAR Interoperability listings in HPE Storage
SPOCK https://www.hpe.com/Storage/Spock/

Supplemental host support information for Peer Persistence, and exceptions to the support listed in the HPE 3PAR Interoperability
listings in HPE Storage SPOCK, are also enumerated in this matrix.

For host OS configuration support information for 3PAR to Primera and Primera to Primera Peer Persistence array configurations, refer
to the HPE Primera Peer Persistence Host OS Support Matrix in SPOCK [https://www.hpe.com/Storage/Spock/]>Software>Array SW:
Primera

Support Notes
• All host configurations represented in this matrix can be supported concurrently on a single HPE 3PAR StoreServ
storage array pair.
• All volumes within an RC group must be exported to the same OS type.
• All host configurations must use an ALUA capable host persona/host mode.
• Host boot from SAN (BFS) is supported in accordance with the HPE 3PAR Interoperability listings in HPE Storage
SPOCK unless otherwise noted as an exception in this support matrix.
• Support of cluster management and high availability solutions includes support of “stretched cluster” (aka, “metro
cluster”) configurations as supported by the cluster solution vendor.
• As Peer Persistence volumes are accessed by applications as regular multi-pathed volumes, Peer Persistence
operations are transparent to application software. Any application software, including application level clustered
databases (e.g. Oracle RAC), can be deployed to use Peer Persistence volumes as long as the host OS vendor
supports the application and Peer Persistence supports the host OS version.
• HPE 3PAR Three Data Center (3DC) for Peer Persistence is supported with all host OS configurations supported in this
matrix.
• It is recommended for Linux LVM users to modify the host lvm.conf file to filter out scans of ghost/standby device
paths. Such scanning results in innocuous read error process sequences that slow response to LVM commands. The
following filter limits scans to only device mapper paths along with cciss paths being used with LVM commands.
filter = [ "a/dev/mapper/.*/", "a/dev/cciss/.*/", "r/.*/" ]
Support Matrix Page 4

HPE Peer Persistence for AIX and IBM VIO Server

Table 1: HPE 3PAR Peer Persistence support matrix for IBM AIX and VIOS
HPE 3PAR OS Version Host OS and Version Host Access Protocol Replication Transpor
Protocol

3.3.1 MU2+ AIX 7.1 TL04 or later, FC RCIP, RCFC

AIX 7.2 TL01 or later

3.3.1 MU2+ VIOS 2.2.5.x or later FC RCIP, RCFC

• 3PAR host persona AIX-ALUA (host mode/persona 16) is required.

– NOTE: AIX-ALUA (host mode/persona 16) is not supported for HPE 3PAR 8Gb FC target adapters.
• 3PAR ODM for AIX MPIO 3.3.0.0 or later, is required.
• Veritas Dynamic Multipathing (VxDMP) is not supported in a Peer Persistence configuration.
• Supported with PowerHA 7.1.3 or later (including PowerHA SystemMirror)
• PowerHA SystemMirror linked cluster is not supported.
• PowerHA disk fencing (use of SCSI-3 Persistence Reservations) is not supported.
Support Matrix Page 5

HPE Peer Persistence for Citrix XenServer

Table 2: HPE 3PAR Peer Persistence support matrix for Citrix XenServer
HPE 3PAR OS Version Host OS and Version Host Access Protocol Replication Transpor
Protocol

3.2.2.MU4+, FC RCIP, RCFC

XenServer 7.0, 7.1
3.3.1 MU2+

• 3PAR host persona Generic-ALUA (host mode/persona 2) is required.

• Brocade HBA’s are not supported with Citrix XenServer in a Peer Persistence configuration.
Support Matrix Page 6

HPE Peer Persistence for HP-UX

Table 3: HPE 3PAR Peer Persistence support matrix for HP-UX
HPE 3PAR OS Version Host OS and Version Host Access Protocol Replication Transpor
Protocol

3.2.2.MU4+, FC RCIP, RCFC

HP-UX 11.31
3.3.1 MU2+

• 3PAR host persona HPUX (host mode/persona 13) is required.

• Veritas Dynamic Multipathing (VxDMP) is not supported in a Peer Persistence configuration.
Support Matrix Page 7

HPE Peer Persistence for Oracle VM Server for x86 (Oracle VM)
Table 4: HPE 3PAR Peer Persistence support matrix for Oracle VM
HPE 3PAR OS Version Host OS and Version Host Access Protocol Replication Connectivity

3.2.2.MU4+, OVM 3.4 FC RCIP, RCFC

3.3.1 MU2+

• Host persona Generic-ALUA (host mode/persona 2) is required.

• Microsoft Cluster Service (MSCS or Windows Failover Cluster) in Oracle VM guest VMs (guest clustering) is not
supported with Peer Persistence.
• Raw device mappings (RDM) support is limited to guest OS’s (VM OS’s) that are also listed as OS’s supported for Peer
Persistence in this matrix.
• For Oracle VM multipath configuration with Peer Persistence, reference the HPE 3PAR Red Hat Enterprise Linux,
CentOS Linux, Oracle Linux, and Oracle VM Server Implementation Guide multipath configuration information specified
for RHEL with ALUA. Note that the Device Mapper (DM) multipath values for “fast_io_fail_tmo” and “dev_loss_tmo”
need to be the following for a Peer Persistence configuration:
fast_io_fail_tmo 20
dev_loss_tmo "infinity"
Support Matrix Page 8

HPE Peer Persistence for Red Hat Enterprise Linux (RHEL)

Red Hat support includes Oracle Linux (Oracle Enterprise Linux (OEL) with RH compatible Kernel)

Table 5: HPE 3PAR Peer Persistence support matrix for RHEL

HPE 3PAR OS Version Host OS and Version Host Access Protocol Replication Connectivity

3.2.2.MU4+, RHEL 6.x FC, iSCSI RCIP, RCFC

3.3.1 MU2+

3.2.2.MU4+, RHEL 7.x FC, iSCSI, FCoE RCIP, RCFC

3.3.1 MU2+

3.3.1 MU2+ RHEL 8.x FC RCIP, RCFC

• Host persona Generic-ALUA (host mode/persona 2) is required.

• Support includes RedHat Virtualization (KVM).
• RHEL iSCSI support is software iSCSI only.
• GPFS cluster management and high availability solution is not supported with RHEL in a Peer Persistence
configuration.
• Veritas Dynamic Multipathing (VxDMP) is not supported in a Peer Persistence configuration.
• Reference the HPE 3PAR Red Hat Enterprise Linux, CentOS Linux, Oracle Linux, and Oracle VM Server
Implementation Guide multipath configuration information specified for RHEL with ALUA. Note that the Device Mapper
(DM) multipath values for “fast_io_fail_tmo” and “dev_loss_tmo” need to be the following for a Peer Persistence
configuration:
fast_io_fail_tmo 10
dev_loss_tmo "infinity"
Support Matrix Page 9

HPE Peer Persistence for Solaris

Table 6: HPE 3PAR Peer Persistence support matrix for Solaris
HPE 3PAR OS Version Host OS and Version Host Access Protocol Replication Transpor
Protocol

3.2.2.MU4+, Solaris 11 x86, FC RCIP, RCFC

3.3.1 MU2+ Solaris 11 SPARC

• Host persona Generic-ALUA (host mode/persona 2) is required.

• Veritas Dynamic Multipathing (VxDMP) is not supported in a Peer Persistence configuration.
Support Matrix Page 10

HPE Peer Persistence for SuSE Linux Enterprise Server (SLES)

Table 7: HPE 3PAR Peer Persistence support matrix for SLES
HPE 3PAR OS Version Host OS and Version Host Access Protocol Replication Transpor
Protocol

3.2.2.MU4+, SLES11 SP3 or newer SP, FC, iSCSI RCIP, RCFC

3.3.1 MU2+ SLES12 SP2 or newer SP,
SLES 15

• Host persona Generic-ALUA (host mode/persona 2) is required.

• Support includes SLES Virtualization (KVM).
• SLES iSCSI support is software iSCSI only.
• GPFS cluster management and high availability solution is not supported with SLES in a Peer Persistence
configuration.
• Veritas Dynamic Multipathing (VxDMP) is not supported in a Peer Persistence configuration.
• Reference the HPE 3PAR SUSE Linux Enterprise Server Implementation Guide multipath configuration information
specified for SLES with ALUA. Note that the Device Mapper (DM) multipath values for “fast_io_fail_tmo” and
“dev_loss_tmo” need to be the following for a Peer Persistence configuration:
fast_io_fail_tmo 10
dev_loss_tmo "infinity"
Support Matrix Page 11

HPE Peer Persistence for VMware vSphere and ESXi

Table 8: HPE 3PAR Peer Persistence support matrix for VMware
HPE 3PAR OS Version Host OS and Version Host Access Protocol Replication Transpor
Protocol

3.2.2.MU4+, FC, iSCSI, FCoE RCIP

ESXi 6.0, 6.5, 6.7
3.3.1 MU2+

• Host persona VMware (host mode/persona 11) is required.

• VMware Metro Cluster (vMSC) certified.
• Includes support of all VMware ESXi Updates (for example, ESXi 6.0 u1).
• Microsoft Cluster Service 2008 R2, 2012, 2012 R2 (MSCS or Windows Failover Cluster) in VMware guest VMs (guest
clustering) is supported with Peer Persistence.
• Microsoft Cluster Service 2016 (MSCS or Windows Failover Cluster) in VMware guest VMs (guest clustering) is
supported with host access protocol FC only.
• Microsoft Cluster Service 2019 (MSCS or Windows Failover Cluster) in VMware guest VMs (guest clustering) is
supported with Peer Persistence as of ESXi 6.5 and for host access protocol FC only.
• VMware RDM support is limited to guest OS’s (VM OS’s) supported by VMware and that are also listed as OS’s
supported for Peer Persistence in this matrix.
– VMware RDMs are not supported with RHEL 7.x or 8.x VMs in a Peer Persisitence configuration.
• VMware 6.x added the VMware vVol feature. VMware vVols cannot be configured in Remote Copy groups for Peer
Persistence and therefore are not supported with Peer Persistence.
– VMware vVols can coexist in an array with non-VMware vVol volumes that are in RC groups configured for Peer
Persistence.
Support Matrix Page 12

HPE Peer Persistence for Microsoft Windows Server

Table 9: HPE 3PAR Peer Persistence support matrix for Microsoft Windows Server
HPE 3PAR OS Host OS and Version Host Access Replication Transpor
Version Protocol Protocol

3.2.2.MU4+, FC, FCoE, iSCSI RCIP

Windows Server 2012 R2 (Standalone, Cluster, Hyper-V),
3.3.1 MU2+
Windows Server 2016 (Standalone, Cluster, Hyper-V),
Windows Server 2019 (Standalone, Cluster, Hyper-V)

• Host persona WindowsServer (host mode/persona 15) is required.

• Includes support of all Windows Server minor updates.
• Windows 2016 and Windows Server 2019 Nano Server are not supported in a Peer Persistence configuration.
• Microsoft Cluster Service (MCS or Windows Failover Cluster) is supported in Windows guest VMs with Peer
Persistence, however, live migration of clustered VMs is not supported using Virtual FC
• Veritas Storage Foundation, including Veritas Cluster Server (VCS), VxVM/VxDMP, is not supported in a Peer
Persistence configuration.
• Path Verify Enabled needs to be set in the MPIO settings on Windows Server hosts configured for a 3PAR Peer
Persistence implementation (PathVerificationState parameter Get-MPIOSetting).
• Because of Windows multipath behavior, the particular configuration of Windows servers with Peer Persistence, all
volumes in Remote Copy groups, and set up for unidirectional replication, i.e., all primary groups on one array in the
pair, it is advisable to present at least one non-replicated LUN to each host, from each array. This helps facilitate
automatic recovery of all Windows host IO paths to an array that is recovering from powerfail. The non-replicated LUN
can be a small (8Gb-16Gb) “dummy” LUN configured as read only, and shared by each attached host.
– Given the particular Peer Persistence configuration with Windows noted and without the LUN configuration noted, a
manual rescan will likely be necessary to reacquire all host IO paths to an array recovered from powerfail [Disk
Management > Actions > Rescan].
Support Matrix

© Copyright 2018 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change
without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an
additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions
contained herein.

This document contains confidential and/or legally privileged information. It is intended for Hewlett Packard Enterprise
and Channel Partner Internal Use only. If you are not an intended recipient as identified on the front cover of this
document, you are strictly prohibited from reviewing, redistributing, disseminating, or in any other way using or relying
on the contents of this document.

September 2019