HP 3000 - 37XE System Reference page 33

6.0 Features supported by controller software version
6.1 Supported array features by controller software version
Array features depend on the controller software version. An HP P6000 Command View license is required to use these features.
Feature
Maximum number of arrays per HP P6000
1
Command View instance
Maximum number of virtual disks per array
(includes snapshots, snapclones,
mirrorclones, and DR group logs)
5
Maximum number of disk groups per array
Maximum number of hosts (clustered or
7
standalone) per array
8
Maximum virtual mapping capacity
Large LUN support
11
Thin provisioning
Vraid6 support
1
HP recommends a maximum of eight arrays per HP Command View EVA 9.2 or later instance. When running HP Command View EVA 9.1 or earlier, the recommended maximum is four. This recommendation applies to all
management server types.
2
On the EVAx400 and P6300/P6500 EVA, the maximum number of virtual disks per array also includes DR group logs. One LUN (LUN 0) is always reserved by the controller software. The number of DR group log virtual disks
will reduce the total number of virtual disks available to the user.
3
If the array configuration includes virtual disks that are greater than 2 TB, then the maximum number of virtual disks (including snapshots, snapclones, and mirrorclones) per array will be less than the maximum listed.
4
The P6300/P6500 EVA iSCSI controllers support a maximum of 256 initiators and 255 LUNs (plus LUN 0). The P6300/P6500 EVA iSCSI/FCoE controllers support a maximum of 1024 initiators, 1024 LUNs, and 256 LUNs
per virtual port group.
5
The maximum number of disk groups is also limited by the maximum number of disks. For Fibre Channel disk drives, each disk group requires a minimum of 8 disks. For solid state disk (SSD) drives, each disk group requires a
minimum of 6 and a maximum of 8 disks.
6
The EVA4400 supports a maximum of 96 disks, so a maximum of 12 disk groups (8 disks per group) is supported.
7
For additional maximums and rules on host presentations, See the "Configuration parameters" section of the "P6000/EVA storage system rules" chapter in the HP SAN Design Reference Guide .
8
The virtual mapping capacity is the sum of all virtual disks plus the mapped capacity of snapshots, snapclones, and mirrorclones. For HP P6000 Continuous Access configurations, the DR log file size is also included in this sum.
Note that demand-allocated and fully-allocated snapshots consume mapping capacity equal to the size of the source virtual disk. For information about enclosure capacity, see the QuickSpecs for the applicable array model.
9
Create virtual disks (LUNs) that are larger than 2 TB (32 TB maximum). The operations allowed on virtual disks that are 2TB or greater are create, present, and delete.
10
Create virtual disks (LUNs) that are larger than 2 TB (32 TB maximum). The operations allowed on virtual disks or snapshots that are 2TB or greater are create, present, delete, extend, and shrink virtual disks; create and delete
snapshots; and create, delete, and attach empty containers.
11
The operations allowed on thin provisioned virtual disks are create, present, delete, extend, and shrink.
VCS 3.1xx VCS 4.1xx
EVA3000/5000 EVA3000/5000 EVA4x00/6x00/8x00
16 16
512 1024
16 16
256 256
35 TB 35 TB 120/120/300 TB
Controller software version
XCS 6.2xx XCS 095xx000 XCS 095xx000
EVA4400 EVA6400/8400
16 16
2, 3
1024
1024 2048
16 6
12
256 256
120 TB 300/500 TB
9
•
•
XCS 10000000 XCS 10000000
EVA4400 EVA6400/8400
16 16 16
2, 3 2, 3 2, 3
1024 2048
16 5 16
12
256 256 256
120 TB 300/500 TB
9 10 10
• • •
• •
• • •
XCS 10000000
P6300/P6500 EVA
16
2, 3, 4
1024/2048
16
256
300/800 TB
10
•
•
•
33