HP 3PAR Feature Availability (FA) Matrix

HP Restricted
Version 1.1 Internal and Channel Partner Use Only April 2014
 Host Connectivity Limits
3PAR StoreServ 3PAR StoreServ 3PAR StoreServ
HP 3PAR StoreServ Storage F Class T Class
10000 Storage 7000 Storage 7450 Storage

Host Connectivity Total (Fibre Channel, iSCSI, and/or mixed)

Fan-out (max initiators per HP 3PAR Storage System host facing port) 64 64 128 128 128
768 (for 2 nodes), 1,024 (for 4,096(for 4 nodes),8,192( for 1,024(for 2 nodes), 2,048( 1,024(for 2 nodes), 2,048(
Max initiators per HP 3PAR Storage System 1,024
4 nodes) 8 nodes) for 4 nodes) for 4 nodes)

Host Connectivity (Fibre Channel)

Fan-Out (max initiators (host HBA ports) per HP 3PAR Storage System port over SAN) NOTE: This
64 64 128 128 128
limit is an aggregate of the total iSCSI and/or FC initiators

Fan-In (number of HP 3PAR Storage System ports visible to a single initiator (host HBA port)) 8 8 8 8 8

Max initiators (host HBA ports) per HP 3PAR Storage System (direct-connect only)-max 1 host HBA 12(for 2 nodes), 24(for 4 32(for 2 nodes), 64(for 4 48(for 2 node), 96(for 4 12(for 2 nodes), 24(for 4 12(for 2 nodes), 24(for 4
per node(7xxx); max 6 host HBAs per node(10x00); max 4 host HBAs per node(T. F-Class) nodes) nodes), 128(for 8 nodes) nodes), 192(for 8 nodes) nodes) nodes)

Max initiators per HP 3PAR Storage System (SAN or SAN/direct-connect)1 - max 1 host HBA per 512(for 2 nodes), 1,024(for 2,048(for 2 nodes), 4,096(for 1,024(for 2 nodes), 2,048( 1,024(for 2 nodes), 2,048(
1,024
node(7xxx);max 6 host HBAs per node(10x00), max 3 host HBAs per node(T, F-Class) 4 nodes) 4 nodes), 8192(for 8 nodes) for 4 nodes) for 4 nodes)

Host Connectivity (iSCSI)

Fan-Out (max iSCSI initiators per HP 3PAR Storage System port over IP network; each Linux iSCSI
initiator counts as two iSCSI initiators on the HP 3PAR Storage System) Note: This limit is an 64 64 64 64 64
aggregate of the total iSCSI and/or FC initiators
Fan-In (number of HP 3PAR Storage System ports visible to a single initiator) 8 8 8 8 8
MTU Sizes NA NA 1,500 thru 9000 Bytes 1,500 thru 9,000 Bytes 1,500 thru 9,000 Bytes
512 (for 2 nodes), 1,024 (for 512 (for 2 nodes), 1,024 512 (for 2 nodes), 1,024 (for 256(for 2 nodes), 512(for 4 256(for 2 nodes), 512(for 4
Max iSCSI initiators per HP 3PAR Storage System
4 nodes) (for 4 nodes) 4 nodes) nodes) nodes)
Max dual-path iSCSI Linux hosts per HP 3PAR Storage System (each iSCSI Linux initiator visible to
a single HP 3PAR Storage System port = 1 initiators; Linux host with 1 iSCSI inititator that is visible 256 (for 2 nodes), 512 (for 4 256 (for 2 nodes), 512 (for 256 (for 2 nodes), 512 (for 4 128(for 2 nodes), 256(for 4 128(for 2 nodes), 256(for 4
to two HP 3PAR Storage System ports via IP network is equivalent to dual-path Linux host and nodes) 4 nodes) nodes) nodes) nodes)
counts as 2 initiators)
Max dual-path iSCSI Windows hosts per HP 3PAR Storage System (each iSCSI Windows initiator
visible to a single HP 3PAR Storage System port = 1 initiator; Windows host with 1 iSCSI initiator 256 (for 2 nodes), 512 (for 4 256 (for 2 nodes), 512 (for 256 (for 2 nodes), 512 (for 4 128(for 2 nodes), 256(for 4 128(for 2 nodes), 256(for 4
that is visible to two HP 3PAR Storage System ports via IP network is equivalent to a dual-path host nodes) 4 nodes) nodes) nodes) nodes)
and counts as 2 initiators)
1 mile (Data center/ small 1 mile (Data center/ small
Max distance from host to storage (tested and supported) campus) or 0.1 ms campus) or 0.1 ms 100 meters 100 Meters 100 Meters

Host Connectivity (FCoE) - Supported with 3PAR OS 3.1.3

12(for 2 node), 24(for 4 2(for 2 nodes), 4(for 4 2(for 2 nodes), 4(for 4
Max HP 3PAR Storage System host facing FCoE HBAs NA NA
node), 48(for 8 node) nodes) nodes)
24(for 2 node), 48(for 4 4(for 2 nodes), 8(for 4 4(for 2 nodes), 8(for 4
Max HP 3PAR Storage System host facing FCoE ports NA NA
node), 96(for 8 node) nodes) nodes)
Max FCOE initiators per port NA NA 64 64 64
256(for 2 nodes), 512(for 4 256(for 2 nodes), 512(for 4 256(for 2 nodes), 512(for 4
Max FCOE initiators per HP 3PAR Storage System NA NA
nodes or more) nodes) nodes)

Drive chassis & Disk Connectivity

6(for 2 nodes), 12(for 4
12(for 2 node), 24(for 4 4(for 2 node), 8(for 4 4(for 2 nodes), 8(for 4 4(for 2 nodes), 8(for 4
Max drive facing ports nodes), 24(for 8
node) node), 16(for 8 node) nodes) nodes)
nodes)[Facing 4 port HBA]
Min disk drives tested & supported per node pair 16 16 16 8 8
Min. disk drives of any supported drive type per drive chassis 8 8 8 2 2
Min. disk drives of a device type per node pair RAID 1 NA NA NA 6 6
Min. disk drives of a device type per node pair RAID 5 NA NA NA 8 8
Min. disk drives of a device type per node pair RAID 6 NA NA NA 12 12
Min. expansion drive chassis (24 Disk, 6Gb SAS) NA NA NA 0 0
Min. raw capacity per node pair (approx TBs) 1.2 1.2
12(for 2 nodes), 24(for 4 8(for 2 nodes), 16(for 4 12(for 2 nodes), 24(for 4 9(for 2 nodes), 18(for 4 9(for 2 nodes), 18(for 4
Max drive chassis
nodes) nodes), 32(for 8 nodes) nodes), 48(for 8 nodes) nodes) nodes)
240(for 2 nodes), 480(for 4 240(for 2 nodes), 480(for 4
480(for 2 nodes), 960(for 4
Maximum disk drives nodes)[assumes all SFF nodes)[assumes all SFF
nodes), 1,920(for 8 nodes)
drives] drives]
Spinning Media:
Spinning Media: 600TB(for
400TB(7200), 600TB(for 2
128(for 2 node F200), 2 node 7450), 1.2PB(for 4
200(for 2 nodes), 400(for 4 800(for 2 nodes), 1.6PB(for 4 node 7400), 1.2PB(for 4
Maximum raw capacity 192(for 2 node F400), node 7450); SSD Drives:
nodes), 800(for 8 nodes) nodes),3.2PB(for 8 nodes) node 7400); SSD Drives:
384(for 4 node F400) 110 TB(for 2 node), 220
110 TB(for 2 node), 220
TB(for 4 nodes)
TB(for 4 nodes)
8(Note: Requires 2.3.1
Minimum number of SSD drives behind a node pair 8 8 8 8
MU1)
32(for 2 nodes), 64(for 4 32(for 2 nodes), 64(for 4 120(for 2 nodes), 240(for 4 120(for 2 nodes), 240(for 4
Maximum number of SSD drives 128(per node pair)
nodes) nodes), 128(for 8 nodes nodes) nodes)
Notes
1: A single FC host initiator WWN would count as multiple initiators if it has logins to multiple host facing FC ports on a HP 3PAR Storage System

Version 1.1 HP Restricted - Internal and Channel Partner Use Only 01

 HP 3PAR Operating System Software
HP 3PAR OS software Release 3.1.2 MU2 Release 3.1.3

HP 3PAR OS support 64bit only 64bit only

F/T/StoreServ 10000, StoreServ 7000, F/T/StoreServ 10000, StoreServ 7000,

Supported HP 3PAR Storage Systems StoreServ 7450 StoreServ 7450

Console/User Interface
Max CLI Connections (For T and F Class) 64 64
Max CLI Connections (For HP 3PAR StoreServ 10400) 128 128
Max CLI Connections (For HP 3PAR StoreServ 10800) 192 192
Max CLI Connections (For HP 3PAR StoreServ 7xxx) 96 96
Max UI sessions (For T and F Class)
64 64
Includes ssh, IMC, CLI, System Reporter, RM
Max UI sessions( For HP 3PAR StoreServ 10400)
128 128
Includes ssh, IMC, CLI, System Reporter, RM.
Max UI sessions(For HP 3PAR StoreServ 10800)
192 192
Includes ssh, IMC, CLI, System Reporter, RM.
Max UI sessions(For HP 3PAR StoreServ 7xxx)
96 96
Includes ssh, IMC, CLI, System Reporter, RM.
Max SSH sessions (Local connections) (For T and F Class) 16 16
Max SSH sessions (Local connections) (For HP 3PAR StoreServ 10400) 32 32
Max SSH sessions (Local connections) (For HP 3PAR StoreServ 10800) 48 48
Max SSH sessions (Local connections) (For HP 3PAR StoreServ 7xxx) 24 24
Max number of HP 3PAR Storage Systems that can be simultaneously managed by HP
16 16
3PAR Management Console

Volume Management
Max VV per system (Base VVs + VCs + FCs) 3PAR StoreServ 10000 Storage systems 12,288 65,536
Max VV per system (Base VVs + VCs + FCs) T-Class / F-Class 8,192 8,192
16,384 (HP 3PAR StoreServ 74xx), 8,192
Max VV per system (Base VVs + VCs + FCs) StoreServ 7000 Storage Systems 8,192
(HP 3PAR StoreServ 7200)
32,768( HP 3PAR StoreServ 10x00), 8,192
Max Base VVs (Normal VV or TPVV) 4,096 (HP 3PAR StoreServ 74xx), 4,096(HP 3PAR
StoreServ T/F-Class,7200)
131,072 (10x00), 65,536 (74xx), 32,768(T/F-
Max VLUNs 32,000
Class,7200)
Minimum - Maximum Volume Size 256 MB - 16TB 256 MB - 16TB
Expand normal Volume Online - manually, and with Snapshots associated with base
Yes Yes
8,192 (T,F,StoreServ 7xxx) / 12,288 65,536(10x00), 16,384(74xx), 8,192(T/F-
Max VV per Common Provision Group (CPG)
(StoreServ 10000) Class, 7200)
32,766(10x00), 8,190(74xx), 4,094(T/F-
Max TPVVs per Common Provision Group (CPG) 4,095
Class, 7200)
Max VLUN ID 16,383 65,536

Logical Disk Management

MAX mirror depth (includes base) 4 4
Max RAID 5 Group 8+1 8+1
RAID 6 Groups (4+2) (6+2) (8+2) (10+2) (14+2) (4+2) (6+2) (8+2) (10+2) (14+2)

Common Provisioning Group (CPG) Management

Max CPGs per system 2,048 2,048

Version 1.1 HP Restricted - Internal and Channel Partner Use Only 02

 Software
Software Release 3.1.2 MU2 Release 3.1.3

Virtual Copy
Max Snapshots (SS) per VV: RO 500 recommended / 2,048 max 500 recommended / 2,048 max
Max Snapshots (SS) per VV: RW 256 256
Max RW Snapshots per RO Snapshot 256 256
Max VVs per Consistency Group for group snapshots (VC or FC) 100 100

Domains1
Max number of domains 1,024 1,024
Max number of domains a given user can belong to Up to 32 or all domains Up to 32 or all domains
Max number users per domain Unlimited Unlimited
Max User Accounts 500 500
T,F Class - 100 / T,F-Class - 100 / StoreServ 7xx00,
Max Scheduled tasks StoreServ 7xx0, 10400 - 256 / StoreServ 10400 - 256 / StoreServ
StoreServ 10800 - 384 10800 - 384

LDAP
Max concurrently logged in LDAP users 16 32
Max length of the LDAP string 1,211 None

Object Sets (Autonomic Groups)

Max volumes in a set 8,192 8,192
Max hosts in a set 8,000 8,000
Max domains in a set 1,024 1,024

Service Tools
Number of Managed Devices2 a Policy Manager (PM) can support 5 100
Security - Customer Controlled Access Yes Yes
Configuration Scripts Yes Yes
Data Collection Yes Yes
Data Transfer Yes Yes
Software Updates on SP Yes Yes
HP 3PAR StoreServ Storage Health Check - Short Yes Yes
HP 3PAR StoreServ Storage Health Check - Full Yes Yes
Notification (Customer) Yes Yes
Alert Filtering Yes Yes
Proxy Server Yes Yes
Permissive Firewall Yes Yes
User IDs & Activity Logging and Reporting (SPMAINT, SPOCC,
Yes Yes
REMOP)
Secure Site File Transfer Scrubbing Yes Yes
Full (F/T/10x00) Full (F/T/10x00)
Guided Maintenance
Lite(7xxx) Lite(7xxx)
GUI Interface to SP Yes Yes

SmartStart
Supported on HP 3PAR StoreServ Storage StoreServ 7xx0 StoreServ 7xx0
Supported on F Class/T Class/HP 3PAR StoreServ 10000 Storage No No
Win 2008 R2 Server, Win 2008 R2 Server, 2008 R2 SP1,
Host Platform Support 2008 R2 SP1, Windows 2012 Windows 2012 ( English and
(English & Japanese) Japanese)
l18n / L10N software (Internationalization/Localization) Partial (English and Japanese only) No (Only English)
Yes (but we recommend to setup 1 Yes (but we recommend to setup 1
Connection to multiple systems
system at a time) system at a time)
Notes:
1: There are no additional limits placed on the number of VVs, VLUNs, hosts, CPGs, CLI/GUI connections per domain beyond the system limits.
2: Managed Device is defined to be single SP/HP 3PAR StoreServ Storage

Version 1.1 HP Restricted - Internal and Channel Partner Use Only 03

 Adaptive Optimization
Adaptive Optimization (AO) Release 3.1.2 MU2 Release 3.1.3

Limits
Maximum number of AO configurations 1,024 1,024

Granularity of data moved 128MB (data) / 32MB (metadata) 128MB (data) / 32MB (metadata)

Minimum number of tiers in a AO configuration1 2 2

Maximum number of tiers in a AO configuration 3 3
Maximum capacity per AO configuration Max array capacity Max array capacity
Maximum data capacity movement per destination tier per execution greater of 1TiB or 5% of total AO config capacity greater of 1TiB or 5% of total AO config capacity
Maximum IO density measurement period 6 days 6 days
Max supported frequency of a AO policy execution per hour 1 hr 1 hr

General
Number of optimization modes supported 3 (Performance, Balanced, Cost) 3 (Performance, Balanced, Cost)
Requires separate System Reporter (SR) data server configuration No No
IMC / CLI support for AO configuration Yes Yes
Data movement across node pairs2 No (see footnote 2) No (see footnote 2)
Tier CPGs in different domains No No
Include FC class disks in a AO configuration3 Strongly recommended Strongly recommended
Same level of availability for all CPGs in a AO configuration4 Strongly recommended Strongly recommended
Track read and write IOs separately Yes (partial) Yes (partial)
Notes:
1: AO works by tiering multiple CPGs together, a single CPG is not tiered

2: In four or higher node configuration with AO it is important that all tiers are configured in the same proportion behind each controller node pair for AO to move data properly

3: Ensure that 1/3 of the capacity is FC class and if unsure can use % of AO configuration capacity per class- SSD (1%), FC (40%), NL (59%)

4: Using a CPG with “Magazine level” availability in an AO configuration with CPGs with “Cage level” availability will mean that all virtual volumes will have an effective availability equivalent to “Magazine level”

5: Although we sample AO performance data at a nominal rate of 2 per hour, (every 1/2 hour), on a very large and/or very busy array it can take longer to collect such sample data, delaying optimisation.. Additionally,
instead of a uniform gap of ½ hour between samples, we delete samples as they age so that the gap between older samples is longer.

Version 1.1 HP Restricted - Internal and Channel Partner Use Only 04

 Remote Copy
Remote Copy Release 3.1.2 MU2 Release 3.1.3
Features
Limits

Max Mirrored Volumes per HP 3PAR StoreServ Storage (Asynchronous 6,000 - 4 Node or more configuration
2,400
Periodic) 2,400 - 2 Node configuration

2,400 - 4 Node or more configuration

Max Mirrored Volumes per HP 3PAR StoreServ Storage (Synchronous) 800
800 - 2 Node configuration
Max Replicated Volumes per HP 3PAR StoreServ Storage (Synchronous
800 2,400
Long Distance)
Minimum number of nodes in a Synchronous Long Distance (SLD)
2 2
configuration (F, T, StoreServ 10000, StoreServ 7000)
Max Replicated Volumes per HP 3PAR StoreServ Storage (1-to-N;
Max N=2)
Asynchronous Periodic mode only 2,400 6,000
One link is Synchronous mode and the other Asynchronous Periodic
800 2,400
Mode
Max Replicated Volumes per HP 3PAR StoreServ Storage (N-to-1;
2,400 6,000
Max N=4)
Asynchronous Periodic mode only 2,400 6,000
Max Mirrored Volumes per Consistency Group 100 300
6,000 for Periodic or 2,400 for Sync ; 4 Node 10K/7K
Max Consistency Groups 2,400 (Periodic), 800(Sync) only) F&T and 2 node 10K/7K class remain as 2,400
Periodic and 800 Sync
Max Size of Mirrored Volume 16TB 16TB
Min. Interval for Asynchronous Periodic Resyncs 5 min 5 min.
MTU Sizes 1,500 thru 9,000 Bytes 1,500 thru 9,000 Bytes

Max Latency Allowed

Synchronous over IP 1.3 ms one way 1.3 ms one way
Synchronous over FC 1.3 ms one way 1.3 ms one way
Asynchronous Periodic over IP 150ms (round trip) 150 ms round trip
Asynchronous Periodic over FC 1.3 ms one way 1.3 ms one way
Asynchronous Periodic over FCIP 60 ms one way 60 ms one way
Notes:
1: Refer RC Configuration guide for details about different RC configurations and node requirements

Version 1.1 HP Restricted - Internal and Channel Partner Use Only 05

 Peer Persistence
Peer Persistence Release 3.1.2 MU2 Release 3.1.3

Limits Automated and manual failover Automated and manual failover

Max. No. of Volumes 250 250
Max. No. of Groups 20 20
Max. No. of Groups in a single failover relationship 5 5
Max. Vols/Group 50 50

Version 1.1 HP Restricted - Internal and Channel Partner Use Only 06

 Peer Motion
Peer Motion Release 3.1.2 MU2 Release 3.1.3

Max concurrent active moves 9 9

Partial host migration (online) No - MUST migrate all volumes on a host Yes
Partial host migration (offline) Yes Yes
Bi-directional Migration No No
2(3PAR to 3PAR), 2(3PAR to 3PAR),
Max HP 3PAR Storage System's in a PM relationship
1 (EVA to 3PAR) 1 (EVA to 3PAR)
Direct Connect Peer Link No No
Fabric Attached Peer Link Yes Yes
Max number of Peer ports per node 1 1
Max number of Peer ports per HP 3PAR StoreServ Storage 2 2
Import a volume into a CPG that is part of an Adaptive Optimization configuration on
No No
the destination
Can use System Tuner while using Peer Motion No No
Can use Dynamic Optimization while using Peer Motion No No
Support for migrating CPVVs Yes Yes
Support for migrating TPVVs Yes Yes
Automatically import a base volume and its snapshot tree No No
Import a base volume without needing to delete snapshot tree on source HP 3PAR
Yes Yes
StoreServ Storage (snapshot data is not migrated) (RW/RO/Both)
Migrate a snapshot from source HP 3PAR Storage System into a base volume on
Yes Yes
destination HP 3PAR StoreServ Storage
Migrating a snapshot from source HP 3PAR Storage System to a snapshot on
No No
destination HP 3PAR StoreServ Storage
1-1 Zoning required for Peer ports Yes Yes
Source HP 3PAR StoreServ Storage models E / F / T / StoreServ 10x00 / StoreServ 7xx0 E / F / T / StoreServ 10x00 / StoreServ 7xx0
Destination HP 3PAR StoreServ Storage models F / T / StoreServ 10x00 / StoreServ 7xx0 F / T / StoreServ 10x00 / StoreServ 7xx0

Version 1.1 HP Restricted - Internal and Channel Partner Use Only 07