Support Matrix

HPE Peer Persistence/

Active Peer Persistence
Host OS Support Matrix
HPE Primera

20th December 2021, version 1.8

Support Matrix

Document Revision History

Document Version Date Section and Text Revised

1.0 20th September 2019 Initial Release

1.1 18th October 2019 Corrected link

1.2 10th January 2020 Add AIX/IBM VIOS and HP-UX

support

1.3 21st January 2020 Add Primera OS 4.1 and RCFC for
Primera to Primera support

1.4 23th June 2020 Add Primera OS 4.2 support

Remove Windows Sever 2012R2
support per Windows 2012/2012R2
EOL. Remove ESXi 6.0 support per
6.0 EOL. Remove support for SLES
11 per EOL. Add ESXi 7.0.
1.5 1st December 2020 Correct dates in doc. Updated 3PAR
ODM for AIX MPIO requirement.
Updated iSCSI support to date

1.6 24th May 2021 Add Active Peer Persistence support.

Update to remove inactive Primera
OS and 3PAR OS versions.

1.7 4th October 2021 Add Primera OS 4.4 support.

Updated iSCSI support to date.
Updated per Remote Copy interop to
date.
1.8 20th December 2021 Add Windows Server 2022 support
Support Matrix

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

Introduction
Active Peer Persistence versus Peer Persistence - Active Peer Persistence is a Remote Copy feature enhancement of classic Peer
Persistence and defined by RC groups in the replication relationship having the active_active RC group policy enabled. RC groups with
the active_active policy enabled are in an Active Peer Persistence relationship. Active Peer Persistence can only be supported if both
storage arrays in the array pair support the active_active RC group policy.
Further information and deployment recommendations regarding Active Peer Persistence may be found in the publication:
HPE ACTIVE PEER PERSISTENCE

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

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

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

Support Notes
• Support includes array combinations of both Primera to Primera and Primera to 3PAR array pairs. Host OS
configuration support for both Primera to Primera and Primera to 3PAR array pairs are restricted to the host OS
configurations depicted in this matrix. There is no support for Active Peer Persistence between Primera and 3PAR
pairs.
• Any combination of host configurations represented in this matrix can be supported concurrently on a single HPE
Primera-Primera or Primera-3PAR storage array pair.
• Active Peer Persistence RC groups, where supported, can coexist with Peer Persistence RC groups in the same array
pair and for the same host configuration.
• 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.
• Non-uniform host connectivity configurations, i.e., host configurations without cross-connected host I/O path
connectivity between array pairs, are not supported with Peer Persistence/Active Peer Persistence.
• Host boot from SAN (BFS) is supported in accordance with the HPE Primera 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/Active Peer Persistence volumes are accessed by applications as regular multi-pathed volumes,
Peer Persistence/Active 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/Active Peer
Persistence volumes as long as the host OS vendor supports the application and Peer Persistence/Active Peer
Persistence supports the host OS version.
• Refer to the HPE Primera Support Matrix in SPOCK [Other Hardware > HPE Primera Support Matrices] for storage
array combinations in support of HPE Three Data Center (3DC) configurations for Peer Persistence.
– HPE Three Data Center (3DC) configurations are not currently supported with Active Peer Persistence.
• 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 Active Peer Persistence for AIX and IBM VIO Server
Table 1: HPE Primera Active Peer Persistence support matrix for IBM AIX and VIOS
HPE Primera OS Version Host OS and Version Host Access Protocol Replication Connectivity

4.3 AIX 7.1 TL05 or later FC RCIP, RCFC

4.4 AIX 7.2 TL04 or later
VIOS 2.2.5.x or later
VIOS 3.1.x.x or later

HPE Peer Persistence for AIX and IBM VIO Server

Table 1: HPE Primera Peer Persistence support matrix for IBM AIX and VIOS
HPE Primera OS Version Host OS and Version Host Access Protocol Replication Connectivity

4.2 AIX 7.1 TL05 or later FC RCIP, RCFC

4.3 AIX 7.2 TL04 or later
4.4 VIOS 2.2.5.x or later
VIOS 3.1.x.x or later

Table 2: Compatible 3PAR OS for Primera to 3PAR Peer Persistence array pairs

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

3.3.1 MU5 AIX 7.1 TL05 or later FC RCIP

AIX 7.2 TL04 or later
VIOS 2.2.5.x or later
VIOS 3.1.x.x or later

3.3.2 AIX 7.1 TL05 or later FC RCIP, RCFC

AIX 7.2 TL04 or later
VIOS 2.2.5.x or later
VIOS 3.1.x.x or later

• 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.4.0.0 or later, is required.
• Veritas Dynamic Multipathing (VxDMP) is not supported.
• Supported with PowerHA 7.2.2 or later (including PowerHA SystemMirror)
• PowerHA SystemMirror linked cluster is not supported.
• PowerHA disk fencing (use of SCSI-3 Persistence Reservations) is supported as of Primera OS 4.3.
– Use of SCSI-3 Persistence Reservations is not supported in conjunction with 3PAR OS.
Support Matrix Page 5

HPE Active Peer Persistence for HP-UX

Table 1: HPE Primera Active Peer Persistence support matrix for HP-UX
HPE Primera OS Version Host OS and Version Host Access Protocol Replication Connectivity

4.3 HP-UX 11.31 FC RCIP, RCFC

4.4

HPE Peer Persistence for HP-UX

Table 1: HPE Primera Peer Persistence support matrix for HP-UX
HPE Primera OS Version Host OS and Version Host Access Protocol Replication Connectivity

4.2 HP-UX 11.31 FC RCIP, RCFC

4.3
4.4

Table 2: Compatible 3PAR OS for Primera to 3PAR Peer Persistence array pairs

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

3.3.1 MU5 HP-UX 11.31 FC RCIP

3.3.2 HP-UX 11.31 FC RCIP, RCFC

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

• Veritas Dynamic Multipathing (VxDMP) is not supported.
Support Matrix Page 6

HPE Active Peer Persistence for Red Hat Enterprise Linux (RHEL)
Table 1: HPE Primera Active Peer Persistence support matrix for RHEL
HPE Primera OS Version Host OS and Version Host Access Protocol Replication Connectivity

4.3 RHEL 7.x, 8.x FC RCIP, RCFC

4.4 RHEL 7.x, 8.x FC, iSCSI RCIP, RCFC

HPE Peer Persistence for Red Hat Enterprise Linux (RHEL)

Table 1: HPE Primera Peer Persistence support matrix for RHEL
HPE Primera OS Version Host OS and Version Host Access Protocol Replication Connectivity

4.2 RHEL 6.x, 7.x, 8.x FC, iSCSI RCIP, RCFC

4.3 RHEL 7.x, 8.x FC, iSCSI RCIP, RCFC

4.4

Table 2: Compatible 3PAR OS for Primera to 3PAR Peer Persistence array pairs

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

3.3.1 MU5 RHEL 6.x, 7.x FC RCIP

3.3.2 RHEL 7.x, 8.x FC RCIP, RCFC

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

• Support includes RedHat Virtualization (KVM).
• iSCSI support is software iSCSI only.
• GPFS cluster management and high availability solution is not supported with RHEL.
• Veritas Dynamic Multipathing (VxDMP) is not supported.
• Reference the HPE Primera Red Hat Enterprise Linux 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:
fast_io_fail_tmo 10
dev_loss_tmo “infinity”
Support Matrix Page 7

HPE Active Peer Persistence for SuSE Linux Enterprise Server (SLES)
Table 1: HPE Primera Active Peer Persistence support matrix for SLES
HPE Primera OS Version Host OS and Version Host Access Protocol Replication Connectivity

4.3 SLES 12 SP5 FC RCIP, RCFC

4.4 SLES 15 SP2

HPE Peer Persistence for SuSE Linux Enterprise Server (SLES)

Table 1: HPE Primera Peer Persistence support matrix for SLES
HPE Primera OS Version Host OS and Version Host Access Protocol Replication Connectivity

4.2 SLES 12 SP5 FC RCIP, RCFC

4.3 SLES 15 SP2
4.4

Table 2: Compatible 3PAR OS for Primera to 3PAR Peer Persistence array pairs

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

3.3.1 MU5 SLES 12 SP5

SLES 15 SP2 FC RCIP

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

• Support includes SLES Virtualization (KVM).
• GPFS cluster management and high availability solution is not supported with SLES.
• Veritas Dynamic Multipathing (VxDMP) is not supported.
• Reference the HPE Primera 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:
fast_io_fail_tmo 10
dev_loss_tmo “infinity”
Support Matrix Page 8

HPE Active Peer Persistence for VMware vSphere and ESXi

Table 1: HPE Primera Active Peer Persistence support matrix for VMware

HPE Primera OS Version Host OS and Version Host Access Protocol Replication Connectivity

4.3 ESXi 6.7, 7.0 FC RCIP, RCFC

4.4 ESXi 6.7, 7.0 FC, iSCSI RCIP, RCFC

HPE Peer Persistence for VMware vSphere and ESXi

Table 1: HPE Primera Peer Persistence support matrix for VMware

HPE Primera OS Version Host OS and Version Host Access Protocol Replication Connectivity

4.2 ESXi 6.7, 7.0 FC, iSCSI RCIP, RCFC

4.3
4.4

Table 2: Compatible 3PAR OS for Primera to 3PAR Peer Persistence array pairs

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

3.3.1 MU5 ESXi 6.7 FC RCIP

3.3.1 MU5 ESXi 7.0 FC, iSCSI RCIP

3.3.2 ESXi 6.7, 7.0 FC RCIP, RCFC

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

• Use VMFS locking mode ATS-only for all VMFS datastores with Active Peer Persistence.
– The VMFS locking mode ATS+SCSI is not compatible and not supported with Active Peer Persistence. The ATS-only
VMFS locking mode is the default for VMFS-5 and VMFS-6 datastore creation, but datastores upgraded from VMFS-3
may have the ATS+SCSI VMFS locking mode. VMFS locking mode can be checked using the command #esxcli
storage vmfs lockmode list on the ESXi host(s). Refer to VMware vSphere documentation for changing
VMFS lockmodes.
• VMware Metro Cluster (vMSC) certified.
• Includes support of all VMware ESXi Updates (for example, ESXi 6.7 u1).
• iSCSI support is software iSCSI only.
• Microsoft Cluster Service 2016 (MSCS or Windows Failover Cluster) in VMware guest VMs (guest clustering) is
supported (FC only).
• Microsoft Cluster Service 2019 (MSCS or Windows Failover Cluster) in VMware guest VMs (guest clustering) is
supported (FC only).
• The ESXi 7.0 “VMDK clustering” feature, as might be used instead of RDMs for data disks with VMware guest VMs
(guest clustering) is supported as of Primera OS 4.3.
• VMware RDM support is limited to guest OS’s (VM OS’s) that are supported by VMware and are also listed as OS’s
supported for Peer Persistence/Active Peer Persistence in this matrix.
Support Matrix Page 9

– Configuration of VMware physical compatibility mode (pass-thru / pMode) RDMs with Linux 7.x or 8.x VMs requires
setting of the “perennially reserved” flag for the storage devices used as physical mode RDMs, and enabling “ignore
Device Inquiry Cache” for the scsi controller for each RDM for each VM in the VM’s vmx file.

NOTE: The RDMs with Linux 7.x or 8.x VMs may become unavailable to the VM at the hypervisor level upon VM
reset/reboot after failover or switchover without this configuration.

• Procedures for setting the perennially reserved flag can be found in VMware KB 1016106
• Procedures for setting “ignore Device Inquiry Cache” can be found in the VMware vSphere documentation for a
given vSphere version under “Virtual Machines with RDMs Need to Ignore SCSI INQUIRY Cache”

• 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 10

HPE Active Peer Persistence for Microsoft Windows Server

Table 1: HPE Primera Active Peer Persistence support matrix for Microsoft Windows Server

HPE Primera OS Host OS and Version Host Access Replication Connectivity

Version Protocol

4.3 Windows Server 2016 (Standalone, Cluster1, Hyper-V1), FC RCIP, RCFC

Windows Server 2019 (Standalone, Cluster1, Hyper-V1),
Windows Server 2022 (Standalone, Cluster1, Hyper-V1)

4.4 Windows Server 2016 (Standalone, Cluster1, Hyper-V1), FC, iSCSI RCIP, RCFC
Windows Server 2019 (Standalone, Cluster1, Hyper-V1)

4.4 Windows Server 2022 (Standalone, Cluster1, Hyper-V1) FC RCIP, RCFC

HPE Peer Persistence for Microsoft Windows Server

Table 1: HPE Primera Peer Persistence support matrix for Microsoft Windows Server

HPE Primera OS Host OS and Version Host Access Replication Connectivity

Version Protocol

4.2 Windows Server 2016 (Standalone, Cluster, Hyper-V), FC RCIP, RCFC

Windows Server 2019 (Standalone, Cluster, Hyper-V)

4.3 Windows Server 2016 (Standalone, Cluster1, Hyper-V1), FC RCIP, RCFC

Windows Server 2019 (Standalone, Cluster1, Hyper-V1),
Windows Server 2022 (Standalone, Cluster1, Hyper-V1)

4.4 Windows Server 2016 (Standalone, Cluster1, Hyper-V1), FC, iSCSI RCIP, RCFC
Windows Server 2019 (Standalone, Cluster1, Hyper-V1)

4.4 Windows Server 2022 (Standalone, Cluster1, Hyper-V1) FC RCIP, RCFC

Table 2: Compatible 3PAR OS for Primera to 3PAR Peer Persistence array pairs

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

Version Protocol

3.3.1 MU5 Windows Server 2016 (Standalone, Cluster, Hyper-V), FC RCIP

Windows Server 2019 (Standalone, Cluster, Hyper-V)
3.3.2 Windows Server 2016 (Standalone, Cluster, Hyper-V), FC RCIP, RCFC
Windows Server 2019 (Standalone, Cluster, Hyper-V)

1. Customers are advised to deploy or migrate to quorum witness solutions other than disk witness when configuring a
stretched Windows Server Failover Cluster (WSFC) with Peer Persistence/Active Peer Persistence with Primera OS
version 4.3 or later 4.x. Microsoft alternatives include file share witness and cloud witness.
a. An instance of data site failure with a Windows Server Failover Cluster (WSFC) stretched configuration,
using disk witness for quorum within a Peer Persistence or Active Peer Persistence configuration, may
experience a temporary offline of cluster resources on the surviving site. The issue is specific to a failover
with the combination of a data site failure and the use of disk quorum with Primera OS 4.3 or later 4.x.
• Host persona WindowsServer (host mode/persona 15) is required.
• Includes support of all Windows Server minor updates.
• Windows Nano Server is not supported.
Support Matrix Page 11

• Windows Server Failover Cluster (WSFC) is supported in physical hosts and well as in Windows guest VMs.
• Veritas Storage Foundation, including Veritas Cluster Server (VCS), VxVM/VxDMP, is not supported.
• Path Verify Enabled needs to be set in the MPIO settings on Windows Server hosts (PathVerificationState
parameter Get-MPIOSetting).
• Because of Windows multipath behavior, in the configuration of a Windows Server with Peer Persistence/Active Peer
Persistence set up for unidirectional replication and all volumes presented to the server in Remote Copy groups, i.e., all
volumes replicated and with 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 Windows Server host.
– For the configuration with Windows noted above, and without the “dummy” LUN configuration, 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

Learn more at HPE Primera

https://www.hpe.com/us/en/storage/hpe-primera.html

© 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