Preventive Service Planning
Abstract
This document lists the configuration limits and restrictions specific to SAN Volume Controller software version 8.4.1.x.
Content
V8.4.x does not support CG8 or earlier node types. Only DH8 or later nodes can be upgraded to v8.4.x.
Note: v8.4.1 is a Non-Long Term Support (Non-LTS) release. Non-LTS code levels are not intended to receive any PTFs. If issues are encountered the only resolution is likely to be an upgrade to a later LTS or Non-LTS release.
For details of the new Continuous Development release strategy refer to the Spectrum Virtualize Family of Products Upgrade Planning page.
The use of WAN optimisation devices such as Riverbed is not supported in native Ethernet IP partnership configurations containing SAN Volume Controller.
Data Reduction Pools
The following restrictions apply for Data Reduction Pools (DRP):
- VMware vSphere Virtual Volumes (vVols) are not supported in a DRP;
- A volume in a DRP cannot be shrunk;
- No volume move between I/O groups if volume in a DRP (use FlashCopy or Metro Mirror/Global Mirror instead);
- No split of a volume mirror to copy in a different I/O group;
- Real/used/free/free/tier capacity are not reported per volume - only per pool.
DRAID Strip Size
For candidate drives, with a capacity greater than 4TB, a strip size of 128 cannot be specified for either RAID-5 or RAID-6 DRAID arrays. For these drives a strip size of 256 should be used.
Non-Disruptive Volume Move (NDVM)
The following Fibre Channel attached host types are supported for non-disruptively moving a volume between I/O groups:
| Host Operating System | Host Multipathing | Host Clustering | Notes |
|---|---|---|---|
| AIX 7.2 | AIXPCM |
Non-disruptive volume move may result in the same volume being mapped to different hosts in the same host cluster using different SCSI IDs. If the host cluster cannot tolerate this configuration then non-disruptive volume move cannot be used.
|
SAN boot is supported
NPIV is supported
|
| Microsoft Windows 2019 | MSDSM |
Hyper-V Failover Cluster
|
SAN boot is supported
|
| Microsoft Windows 2016 | MSDSM |
Hyper-V Failover Cluster
|
SAN Boot is supported
|
| RedHat 8 | Native |
The original paths may need to be manually removed on the host after removing access to the old I/O group
|
|
| SLES 15 | Native | The original paths may need to be manually removed on the host after removing access to the old I/O group | |
| VMware 6.7 | Native | VAAI is supported | |
| VMware 6.5 | Native | VAAI is supported | |
| Solaris 11.3 SPARC | MPXIO | SAN boot is supported |
Note: For all other host types, I/O should be quiesced when moving a volume.
When moving a volume that is mapped to a host cluster then you must rescan disk paths on all host cluster nodes to ensure the new paths have been detected before removing access from the original I/O group.
Clustered Systems
A SAN Volume Controller system requires native Fibre Channel SAN or alternatively 8Gbps/16Gbps/32Gbps Direct Attach Fibre Channel connectivity for communication between all nodes in the local cluster. Clustering can also be accomplished with 25Gbps Ethernet, for standard topologies. For HyperSwap topologies a SCORE request will be required. Please contact your IBM representative to raise a SCORE request.
Partnerships between systems for Metro Mirror or Global Mirror replication can be used with both Fibre Channel and Native Ethernet connectivity. Distances greater than 300 metres are only supported when using an FCIP link or Fibre Channel between source and target.
| Clustering over Fibre Channel | Clustering over 25Gb Ethernet | HyperSwap over FIbre Channel | HyperSwap over Ethernet (25Gb only) | Metro/Global Mirror replication over Fibre Channel | Metro/Global Mirror replication over Ethernet (10Gb or 25Gb) |
|---|---|---|---|---|---|
| Yes up to 4 I/O groups | Yes up to 4 I/O groups | Yes up to 4 I/O groups | Yes up to 4 I/O groups | Yes | Yes (including 1Gb on older hardware) |
Hot Spare Node
In a situation where an adapter PCI slot location on the spare node does not match the active nodes, an active node cannot be replaced by a spare node using the swapnode command. The user will encounter error "CMMVC9261E The command failed because the specified node does not have a status of candidate". It is recommended to have adapters in the same slot for spare nodes and the active node for swapnode replace command to work.
When the online_spare node is put into the Service state, it is immediately removed back to spare and 5 minutes later it will rejoin as online_spare in the cluster. The user can, instead of putting the online_spare into service, wait for the original to come back or simply remove the online_spare and then perform their maintenance.
Transparent Cloud Tiering
Transparent cloud tiering on the system is defined by configuration limitations and rules. Please see the IBM Documentation maximum limits page for details.
The following restrictions apply for Transparent Cloud Tiering:
- When a cloud account is created, it must continue to use the same encryption type, throughout the life of the data in that cloud account - even if the cloud account object is removed and remade on the system, the encryption type for that cloud account may not be changed while back up data for that system exists in the cloud provider.
- When performing re-key operations on a system that has an encryption enabled cloud account, perform the commit operation immediately after the prepare operation. Remember to retain the previous system master key (on USB or in Keyserver) as this key may still be needed to retrieve your cloud backup data when performing a T4 recovery or an import.
- Restore_uid option should not be used when backup is imported to a new cluster.
- Import of TCT data is only supported from systems whose backup data was created at v7.8.0.1 or later.
- Transparent cloud tiering uses Sig V2, when connecting to Amazon regions, and does not currently support regions that require Sig V4.
Encryption and TCT
There is an extremely small possibility that, on a system using both Encryption and Transparent Cloud Tiering, the system can enter a state where an encryption re-key operation is stuck in 'prepared' or 'prepare_failed' state, and a cloud account is stuck in 'offline' state.
The user will be unable to cancel or commit the encryption rekey, because the cloud account is offline. The user will be unable to remove the cloud account because an encryption rekey is in progress.
The system can only be recovered from this state using a T4 Recovery procedure.
It is also possible that SAS-attached storage arrays go offline.
There are two possible scenarios where this can happen:
Scenario A
- Using USB encryption and Cloud;
- A new USB key is prepared using chencryption -usb newkey -key prepare;
- The new presumptive key is deleted from all USB sticks before the new key is committed;
- All nodes in the system are rebooted;
- The cloud account will now be offline as it can't get the presumptive key. The cloud account can not be removed, and the encryption rekey can not be completed or cancelled. The system will remain stuck in these cloud and encryption states;
- Any SAS-attached arrays will be offline and locked;
- The system can be restored by T4 to a previous config backup.
Scenario B
- Using key server encryption and Cloud;
- A new key server key is prepared using chencryption -keyserver newkey -key prepare;
- The new presumptive key is deleted from the key server before the new key is committed;
- All nodes in the system are rebooted;
- The cloud account will now be offline as it can't get the presumptive key. The cloud account can not be removed, and the encryption rekey can not be completed or cancelled. The system will remain stuck in these cloud and encryption states;
- SAS-attached arrays are not affected;
- The system can be restored by T4 to a previous config backup.
NPIV ( N_Port ID Virtualization )
The following recommendations and restrictions should be followed when implementing the NPIV feature.
FCoE is not supported with NPIV.
Operating systems not currently supported for use with NPIV:
- HPUX 11iV2
- Veritas DMP multipathing on Windows with RAID-5 volumes in VxVM
- IBMi in Direct attach
Other Operating Systems
Other operating Systems may also experience the same issue when changing the NPIV state from "Transitional" to "Disabled" in which case the operating system specific rescan command should be used.
Fabric Attachment
NPIV mode on SVC or Storwize is only supported when used with Brocade or Cisco fibre channel SAN switches which are NPIV capable.
Node Memory
Nodes in an I/O group cannot be replaced by nodes with less memory when compressed volumes are present.
If a customer must migrate from 64GB to 32GB memory node canisters in an I/O group, they will have to remove all compressed volume copies in that I/O group.
A customer must not:
- Create an I/O group with node canisters with 64GB of memory.
- Create compressed volumes in that I/O group.
- Delete both node canisters from the system with CLI or GUI.
- Install new node canisters with 32GB of memory and add them to the configuration in the original I/O group with CLI or GUI.
HyperSwap
When using the HyperSwap function, please configure your host multipath driver to use an ALUA-based path policy.
Due to the requirement for multiple access IO groups, SAS attached host types are not supported with HyperSwap volumes.
A volume configured with multiple access I/O groups, on a system in the storage layer, cannot be virtualized by a system in the replication layer. This restriction prevents a HyperSwap volume on one system being virtualized by another.
AIX Live Partition Mobility (LPM)
AIX LPM is supported with the HyperSwap function and AIX 7.x
Direct Attachment
SAN boot on Windows 2019 (Qlogic HBA) is not supported with 32GB direct-attached systems.
Cisco Nexus
The minimum level of Cisco Nexus firmware supported for FCoE with the IBM 2145-DH8 / 2145-SV1 /2145-SA2 / 2145-SV2 is 5.2(1)N1(2a).
16Gbps Fibre Channel Node Connection
Please see IBM System Storage Inter-operation Center (SSIC) - https://www.ibm.com/systems/support/storage/ssic/interoperability.wss ) for supported 16Gbps Fibre Channel configurations supported with 16Gbps node hardware.
Note 16Gbps Node hardware is supported when connected to Brocade and Cisco 8Gbps or 16Gbps fabrics only.
Direct connections to 2Gbps or 4Gbps SAN or direct host attachment to 2Gbps or 4Gbps ports is not supported.
Other configured switches which are not directly connected to the 16Gbps Node hardware can be any supported fabric switch as currently listed in SSIC.
25Gbps Ethernet Canister Connection
Three optional 2-port 25Gbps Ethernet adapters are supported in each SAN Volume Controller node for iSCSI communication with iSCSI capable Ethernet ports in hosts via Ethernet switches. These 2-port 25Gbps Ethernet adapters do not support FCoE.
There are two types of 25Gbps Ethernet adapter Feature supported:
- RDMA over Converged Ethernet (RoCE)
- Internet Wide-area RDMA Protocol (iWARP)
Either will work for standard iSCSI communications, i.e. not using Remote Direct Memory Access (RDMA). A future software release will add (RDMA) links using new protocols that support RDMA such as NVMe over Ethernet.
When use of RDMA with a 25Gbps Ethernet adapter becomes possible then RDMA links will only work between RoCE ports or between iWARP ports.
i.e. from a RoCE node canister port to a RoCE port on a host or from an iWARP node canister port to an iWARP port on a host.
The 25Gbps adapters come with SFP28 fitted, which can be used to connect to switches using OM3 optical cables.
For Ethernet switches and adapters supported in hosts see SSIC.
This is an example of a RoCE adapter for use in a host.
https://docs.nvidia.com/networking/display/cx4lxen
This is an example of a iWARP adapter for use in a host.
https://www.chelsio.com/nic/unified-wire-adapters/t6225-cr/
IP Partnership
IP partnerships are supported on any of the available ethernet ports. Using an Ethernet switch to convert a 25Gb to a 1Gb IP partnership, or a 10Gb to a 1Gb IP partnership is not supported. Therefore the IP infrastructure on both partnership sites must match. Bandwidth limiting on IP partnerships between both sites is supported.
VMware vSphere Virtual Volumes (vVols)
The maximum number of Virtual Machines on a single VMware ESXi host in an SVC / vVol storage configuration is limited to 680.
The use of vVols on a system that is configured for HyperSwap is not currently supported with SVC/Storwize.
REST API
It is not possible to access the REST API using a cluster's IPv6 address.
Host Limitations
SAN BOOT function on AIX 7.2 TL5
SAN BOOT is not supported for AIX 7.2 TL5 when connected using the NVME/FC protocol.
RDM Volumes attached to guests in VMware 7.0
Using RDM (raw device mapping) volumes attached to any guests, with the RoCE iSER protocol, results in pathing issues or inability to boot the guest.
N2225/N2226 SAS HBA
VMware 6.7 (Guest O/S SLES12SP4) connected via SAS N2225/N2226 host adapters are not supported.
Lenovo 430-16e/8e SAS HBA
VMware 6.7 and 6.5 (Guest O/S SLES12SP4) connected via SAS Lenovo 430-16e/8e host adapters are not supported.
Windows 2019 and 2016 connected via SAS Lenovo 430-16e/8e host adapters are not supported.
Windows 2016 HyperV
RHEL v7.1 guests on Windows 2016 HyperV, with Virtual Fibre Channel, are not supported.
iSER
Operating systems not currently supported for use with iSER:
- Windows 2012 R2 using Mellanox ConnectX-4 Lx EN
- Windows 2016 using Mellanox ConnectX-4 Lx EN
Windows NTP server
The Linux NTP client used by SAN Volume Controller may not always function correctly with Windows W32Time NTP Server
Fabric Limitations
Only one FCF ( Fibre Channel Forwarder ) switch per fabric is supported.
Storage connected directly to a Cisco Fabric Extender (FEX) is not supported.
Priority Flow Control for iSCSI/iSER
Priority Flow Control for iSCSI/iSER is supported on Emulex & Chelsio adapters (SVC supported) with all DCBX enabled switches.
Maximum Configurations
Configuration limits for SAN Volume Controller:
|
Property
|
Hardware Type
|
Maximum Number
|
Notes
|
|
System (Cluster) Properties
|
|||
| Nodes per system (cluster) |
8
|
Arranged as four I/O groups | |
| Nodes per fabric |
64
|
Maximum number of SVC or Storwize family system nodes that can be present on the same Fibre Channel fabric, with visibility of each other | |
| I/O groups per system |
4
|
Each containing two nodes | |
| Fabrics per system |
12
|
The number of counterpart SANs which are supported | |
| Inter-cluster partnerships per system |
3
(maximum 1 IP partnership is supported) |
A system may be partnered with up to three remote systems. No more than four systems may be in the same connected set | |
| IP Quorum devices per system |
5
|
||
| Data encryption keys per system |
1024
|
||
|
Node Properties
|
|||
| Logins per node Fibre Channel WWPN |
512
|
Includes logins from server HBAs, disk controller ports, node ports within the same system and node ports from remote systems | |
| Fibre Channel buffer credits per port |
8Gbps FC Adapter
|
255
|
The number of credits granted by the switch to the node |
|
16Gbps FC Adapter
|
4095
|
||
| iSCSI sessions per node |
1024
|
A maximum of 256 can be backend sessions. This limit includes both iSCSI Host Attach AND iSCSI Initiator sessions |
|
| iSER sessions per node |
256
|
Model SV1/SA2/SV2 only | |
|
Managed Disk Properties
|
|||
| Managed disks (MDisks) per system |
4096
|
The maximum number of logical units which can be managed by a cluster. Internal distributed arrays consume 16 logical units. This number includes external MDisks which have not been configured into storage pools (managed disk groups) |
|
| Managed disks per storage pool (managed disk group) |
128
|
||
| Storage pools per system |
1024
|
||
| Parent pools per system |
128
|
||
| Child pools per system |
1023
|
||
| Managed disk extent size |
8192 MB
|
||
| Capacity for an individual internal managed disk (array) |
-
|
No limit is imposed beyond the maximum number of drives per array limits. Maximum size is dependent on the extent size of the Storage Pool. Comparison Table: Maximum Volume, MDisk and System capacity for each extent size. |
|
| Capacity for an individual external managed disk |
1 PB
|
Note: External managed disks larger than 2 TB are only supported for certain types of storage systems. Refer to the supported hardware matrix for further details. Maximum size is dependent on the extent size of the Storage Pool. Comparison Table: Maximum Volume, MDisk and System capacity for each extent size. |
|
| Total storage capacity manageable per system |
32 PB
|
Maximum requires an extent size of 8192 MB to be used This limit represents the per system maximum of 2^22 extents. Maximum size is dependent on the extent size of the Storage Pool. Comparison Table: Maximum Volume, MDisk and System capacity for each extent size. |
|
|
Data Reduction Pool Properties
|
|||
| Data Reduction Pools per system |
4
|
||
| Mdisks per Data Reduction Pool |
128
|
||
| Volume copies per Data Reduction Pool |
10000 - (Number of Data Reduction Pools x 12)
|
||
| Extents per I/O group per Data Reduction Pool |
128000
|
||
|
Volume (Virtual Disk) Properties
|
|||
| Basic volumes (VDisks) per system |
10000
|
Each basic volume uses 1 VDisk, each with one copy. | |
| Stretched volumes per system |
5000
|
Each stretched volume uses 1 VDisk, each with two copies. | |
| HyperSwap volumes per system |
2000
|
Each HyperSwap volume uses 4 VDisks, each with one copy, 1 active-active remote copy relationship and 4 FlashCopy mappings. | |
| Volumes per I/O group (volumes per caching I/O group) |
10000
|
||
| Thin-provisioned (space-efficient) volume copies in regular pools per system |
-
|
No limit is imposed here beyond the volume copies per system limit. | |
| Compressed volume copies in regular pools per system |
2048
|
Maximum requires an 8-node cluster | |
| Compressed volume copies in regular pools per I/O group |
512
|
With 64GB Memory Option Only | |
| Compressed volume copies in data reduction pools per system |
-
|
No limit is imposed here beyond the volume copy limit per data reduction pool | |
| Compressed volume copies in data reduction pools per I/O group |
-
|
No limit is imposed here beyond the volume copy limit per data reduction pool | |
| Deduplicated volume copies in data reduction pools per system |
-
|
No limit is imposed here beyond the volume copy limit per data reduction pool | |
| Deduplicated volume copies in data reduction pools per I/O group |
-
|
No limit is imposed here beyond the volume copy limit per data reduction pool | |
| Volumes per storage pool |
-
|
No limit is imposed beyond the volumes per system limit | |
| Fully-allocated volume capacity |
256 TB
|
Maximum size for an individual fully-allocated volume. Maximum size is dependent on the extent size of the Storage Pool. Comparison Table: Maximum Volume, MDisk and System capacity for each extent size. |
|
| Thin-provisioned (space-efficient) per-volume capacity for volumes in regular and data reduction pools |
256 TB
|
Maximum size for an individual thin-provisioned volume Maximum size is dependent on the extent size of the Storage Pool. Comparison Table: Maximum Volume, MDisk and System capacity for each extent size. |
|
| Compressed volume capacity in regular pools | Pools containing non-Flash storage |
16 TB
|
Maximum size for an individual compressed volume. See this Flash for further information on this limit. Maximum size is dependent on the extent size of the Storage Pool. Comparison Table: Maximum Volume, MDisk and System capacity for each extent size. |
| Pools containing all-Flash storage |
32 TB
|
||
| Host mappings per system |
64,000
|
See also - volume mappings per host object below | |
|
Mirrored Volume (Virtual Disk) Properties
|
|||
| Copies per volume |
2
|
||
| Volume copies per system |
10000
|
The maximum number of volumes cannot all have the maximum number of copies | |
| Total mirrored volume capacity per I/O group |
1024 TB
|
||
|
Host Properties
|
|||
| Host objects (IDs) per system |
2048
|
||
| Host objects (IDs) per I/O group |
512
|
||
| Volume mappings per host object |
2048
|
Although SVC allows the mapping of up to 2048 volumes per host object, not all hosts are capable of accessing/managing this number of volumes. The practical mapping limit is restricted by the host OS, not SVC.
Note: this limit does not apply to hosts of type adminlun (used to support VMware vVols). |
|
|
Host Cluster Properties
|
|||
| Host clusters per system |
512
|
||
| Hosts in a host cluster |
128
|
||
|
Fibre Channel Host Properties (including hosts attached using FCoE)
|
|||
| Fibre Channel hosts per system |
2048
|
||
| Fibre Channel host ports per system |
8192
|
||
| Fibre Channel hosts per I/O group |
512
|
||
| Fibre Channel host ports per I/O group |
2048
|
||
| Fibre Channel host ports per host object (ID) |
32
|
||
| Simultaneous I/Os per node FC port |
8Gbps FC Adapter
|
2048
|
|
|
16Gbps FC Adapter
|
4096
|
||
|
iSCSI Host Properties
|
|||
| iSCSI hosts per system |
2048
|
||
| iSCSI hosts per I/O group |
512
|
||
| iSCSI names per host object |
4
|
||
| iSCSI names per I/O group |
512
|
||
|
iSER Host Properties
|
|||
| iSER hosts per system |
2048
|
Model SV1/SA2/SV2 only. | |
| iSER hosts per I/O group |
512
|
Model SV1/SA2/SV2 only. | |
| iSER names per host object |
4
|
Model SV1/SA2/SV2 only. | |
|
NVMe over Fibre Channel Host Properties
|
|||
| FC-NVMe hosts per system |
64
|
This limit is not policed by the Spectrum Virtualize software. Any configurations that exceed this limit may experience significant adverse performance impact. | |
| FC-NVMe hosts per I/O group |
16
|
This limit is not policed by the Spectrum Virtualize software. Any configurations that exceed this limit may experience significant adverse performance impact. | |
| Fibre Channel Logins per FC-NVMe WWPN | 16 | These are the number of FC2 logins supported. | |
| NVMe Qualified Names (NQNs) per host object (ID) |
2
|
||
|
Copy Services Properties
|
|||
| Remote Copy (Metro Mirror and Global Mirror) relationships per system |
10000
|
This can be any mix of Metro Mirror and Global Mirror relationships. | |
| Active-Active Relationships (HyperSwap) |
2000
|
||
| Remote Copy relationships per consistency group (<=256 GMCV relationships configured) |
-
|
No limit is imposed beyond the Remote Copy relationships per system limit. Refer to the Changes to support for Global Mirror with Change Volumes page for information relating to GMCV performance considerations and best practice. |
|
| Remote Copy relationships per consistency group (>256 GMCV relationships configured) |
200
|
||
| Remote Copy consistency groups per system |
256
|
||
| Total Metro Mirror and Global Mirror volume capacity per I/O group |
1024 TB
|
This limit is the total capacity for all master and auxiliary volumes in the I/O group. | |
| Total number of Global Mirror with Change Volumes relationships per system |
2145-DH8
|
256
|
60s cycle time (Change volumes used for active-active relationships do not count towards this limit). |
|
1500
|
300s cycle time (Change volumes used for active-active relationships do not count towards this limit). | ||
|
2145-SV1
2145-SA2
2145-SV2
|
256
|
60s cycle time (Change volumes used for active-active relationships do not count towards this limit). | |
|
2500
|
300s cycle time (Change volumes used for active-active relationships do not count towards this limit). | ||
| FlashCopy mappings per system |
10000
|
||
| FlashCopy targets per source |
256
|
||
| FlashCopy mappings per consistency group |
512
|
||
| FlashCopy consistency groups per system |
500
|
||
| Total FlashCopy volume capacity per I/O group |
4096 TB
|
||
| 3-site Remote Copy (Metro Mirror) relationships per consistency group |
256
|
||
| 3-site Remote Copy (Metro Mirror) consistency groups per system |
16
|
||
| 3-site Remote Copy (Metro Mirror) relationships per system |
1250
|
||
|
IP Partnership Properties
|
|||
| Inter-cluster IP partnerships per system |
1
|
A system may be partnered with up to three remote systems. A maximum of one of those can be IP and the other two FC. | |
| I/O groups per system |
2
|
The nodes from a maximum of two I/O groups per system can be used for IP partnership. | |
| Inter site links per IP partnership |
2
|
A maximum of two inter site links can be used between two IP partnership sites. | |
| Ports per node |
1
|
A maximum of one port per node can be used for IP partnership. | |
| IP Partnership Software Compression Limit |
2145-DH8
2145-SV1 2145-SA2
2145-SV2
|
140 MB/s
|
|
|
Internal Storage System Properties
|
|||
| Expansion enclosures per I/O group |
20
|
The limiting factor is the combined chain weight of the various components. The maximum SAS chain weight that can be attached to a node SAS port is 10: 2145-92F enclosures have a chain weight of 2.5; 2145-24F and 2145-12F enclosures have a chain weight of 1. |
|
| Drives per enclosure |
92
|
||
| Drives per I/O group |
736
|
||
| Drives per system |
2944
|
||
| SCM drives per I/O group | 12 | ||
|
Non-Distributed RAID Array Properties
|
|||
| Min-Max member drives per RAID-0 array |
1-8
|
||
| Min-Max member drives per RAID-1 array |
2-2
|
||
| Min-Max member drives per RAID-5 array |
3-16
|
||
| Min-Max member drives per RAID-6 array |
5-16
|
||
| Min-Max member drives per RAID-10 array |
2-16
|
||
|
Distributed RAID Array Properties
|
|||
| Arrays per system |
32
|
The presence of non-DRAID arrays will reduce this limit | |
| Encrypted arrays per system |
32
|
The presence of non-DRAID arrays will reduce this limit | |
| Arrays per I/O group |
10
|
The presence of non-DRAID arrays will reduce this limit | |
| Drives per array |
128
|
||
| Min-Max member drives per RAID-5 array |
4-128
|
||
| Min-Max member drives per RAID-6 array |
6-128
|
||
| Rebuild areas per array |
1-4
|
||
| Min-Max stripe width for RAID-5 array |
3-16
|
||
| Min-Max stripe width for RAID-6 array |
5-16
|
||
| Drives added to an array in a single DRAID expansion |
12
|
||
| Concurrent DRAID expansions per system |
4
|
||
| Concurrent DRAID expansions per parent storage pool |
1
|
||
|
External Storage System Properties
|
|||
| Storage system WWNNs per system (cluster) |
1024
|
||
| Storage system WWPNs per system (cluster) |
1024
|
||
| WWNNs per storage system |
16
|
||
| WWPNs per WWNN |
16
|
||
| LUNs (managed disks) per storage system |
-
|
No limit is imposed beyond the managed disks per system (cluster) limit | |
|
System and User Management Properties
|
|||
| User accounts per system |
400
|
Includes the default user accounts | |
| User groups per system |
256
|
Includes the default user groups | |
| Authentication servers per system |
1
|
||
| NTP servers per system |
1
|
||
| iSNS servers per system |
1
|
||
| Concurrent open SSH sessions per system |
32
|
||
|
Event Notification Properties
|
|||
| SNMP servers per system |
6
|
||
| Syslog servers per system |
6
|
||
| Email (SMTP) servers per system |
6
|
Email servers are used in turn until the email is successfully sent | |
| Email users (recipients) per system |
12
|
||
| LDAP servers per system |
6
|
||
|
REST API Properties
|
|||
| Threads per session |
64
|
||
| HTTP header size |
16 KB
|
||
|
2145-DH8 Hardware Properties
|
|||
| 8Gbps Fibre channel cards per node |
4
|
||
| 16Gbps Fibre channel cards per node |
4
|
||
| Compression accelerator cards per node |
2
|
||
| 10Gbps Ethernet adapters per node |
2
|
||
| 10Gbps Ethernet ports per node |
8
|
FCoE is supported on the first four 10GbE ports in the system | |
| 1Gbps Ethernet ports per node |
3
|
||
|
2145-SV1 Hardware Properties
|
|||
| 16Gbps Fibre channel cards per node |
4
|
||
| Compression accelerator cards per node |
2
|
||
| 10Gbps Ethernet cards per node |
1
|
||
| 10Gbps Ethernet optical ports per node |
4
|
||
| 10Gbps Ethernet copper ports per node |
3
|
||
| 25Gbps Ethernet adapters per node |
3
|
||
| Ethernet adapters that can be used per node |
11
|
Not counting the dedicated Technician port which cannot be used for iSCSI | |
|
2145-SV1 iSER Hardware Properties
|
|||
| 25Gbps iWARP adapters per node |
4
|
||
| 25Gbps ROCE adapters per node |
4
|
||
| 25Gbps iWARP ports per node |
8
|
||
| 25Gbps ROCE ports per node |
8
|
||
Extents
The following table compares the maximum volume, MDisk and system capacity for each extent size.
|
Extent size (MB)
|
Maximum non thin-provisioned volume capacity in GB
|
Maximum thin-provisioned volume capacity in GB (for regular pools)
|
Maximum compressed volume size (for regular pools) **
|
Maximum thin-provisioned and compressed volume size in data reduction pools in GB
|
Maximum total thin-provisioned and compressed capacity for all volumes in a single data reduction pool per IOgroup in GB
|
Maximum MDisk capacity in GB
|
Maximum DRAID Mdisk capacity in TB
|
Total storage capacity manageable per system*
|
|
16
|
2048 (2 TB)
|
2000
|
2TB
|
2048 (2 TB)
|
2048 (2 TB)
|
2048 (2 TB)
|
32
|
64 TB
|
|
32
|
4096 (4 TB)
|
4000
|
4TB
|
4096 (4 TB)
|
4096 (4 TB)
|
4096 (4 TB)
|
64
|
128 TB
|
|
64
|
8192 (8 TB)
|
8000
|
8TB
|
8192 (8 TB)
|
8192 (8 TB)
|
8192 (8 TB)
|
128
|
256 TB
|
|
128
|
16,384 (16 TB)
|
16,000
|
16TB
|
16,384 (16 TB)
|
16,384 (16 TB)
|
16,384 (16 TB)
|
256
|
512 TB
|
|
256
|
32,768 (32 TB)
|
32,000
|
32TB
|
32,768 (32 TB)
|
32,768 (32 TB)
|
32,768 (32 TB)
|
512
|
1 PB
|
|
512
|
65,536 (64 TB)
|
65,000
|
64TB
|
65,536 (64 TB)
|
65,536 (64 TB)
|
65,536 (64 TB)
|
1024 (1 PB)
|
2 PB
|
|
1024
|
131,072 (128 TB)
|
130,000
|
96TB **
|
131,072 (128 TB)
|
131,072 (128 TB)
|
131,072 (128 TB)
|
2048 (2 PB)
|
4 PB
|
|
2048
|
262,144 (256 TB)
|
260,000
|
96TB **
|
262,144 (256 TB)
|
262,144 (256 TB)
|
262,144 (256 TB)
|
4096 (4 PB)
|
8 PB
|
|
4096
|
262,144 (256 TB)
|
262,144
|
96TB **
|
262,144 (256 TB)
|
524,288 (512 TB)
|
524,288 (512 TB)
|
8192 (8 PB)
|
16 PB
|
|
8192
|
262,144 (256 TB)
|
262,144
|
96TB **
|
262,144 (256 TB)
|
1,048,576 (1024 TB)
|
1,048,576 (1024 TB)
|
16384 (16 PB)
|
32 PB
|
* The total capacity values assumes that all of the storage pools in the system use the same extent size.
** Please see the following Flash
Was this topic helpful?
Document Information
Modified date:
08 May 2024
UID
ibm16441373