Preventive Service Planning
Abstract
This document lists the configuration limits and restrictions specific to SAN Volume Controller software version 7.6
Content
The use of WAN optimization devices such as Riverbed is not supported in native Ethernet IP partnership configurations containing SAN Volume Controller.
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.
Applying drive software update to all drives in a system with a distributed array containing more than 16 drives
Please do not update drive software on all drives together in a system that has a distributed array with more than 16 drives.
The following will perform a drive software upgrade on all drives together and are restricted in this case:
- Using command applydrivesoftware with "-all" parameter.
- Using the "Upgrade All" option in the GUI under "Pools > Internal Storage > Actions".
To workaround this restriction, please perform drive software update on one drive at a time.
You can do this using command applydrivesoftware with "-drive" parameter for each drive.
This restriction is now resolved with software version of 7.6.0.4
iSCSI Limitations
iSCSI host attachment is currently not supported with Software Version 7.6
This restriction is now resolved and iSCSI host attachment is supported with software version 7.6.0.2 and higher.
Due to the requirement for multiple access IO groups, iSCSI attached host types are not supported with HyperSwap volumes.
HyperSwap
HyperSwap is not supported with Software Version version 7.6.0
This restriction is now resolved and HyperSwap is supported with software version 7.6.0.1 and higher.
When using the HyperSwap function with software version 7.6.0.1 and higher, please configure your host multipath driver to use an ALUA-based path policy.
Due to the requirement for multiple access IO groups, iSCSI and SAS attached host types are not supported with HyperSwap volumes.
AIX Live Partition Mobility (LPM)
AIX LPM is now supported with the HyperSwap function and AIX 7.x
New CLI Commands
The following new CLI commands are not currently supported on Software Version 7.6
* addvolumecopy
* rmvolumecopy
Attempting to use a feature which is not supported will return the following error:
CMMVC7205E The command failed because it is not supported.
Support for these commands will be enabled in a future software release.
Clustered Systems
A SAN Volume Controller system at version 7.6 and higher requires native Fibre Channel SAN or alternatively 8Gbps/16Gbps Direct Attach Fibre Channel connectivity for communication between all nodes in the local cluster. Fibre Channel over Ethernet ( FCoE ) connectivity for communication between all nodes in the local cluster is also supported.
Partnerships between systems for Metro Mirror or Global Mirror replication can be used with both Fibre Channel, Native Ethernet connectivity and FCoE connectivity, however direct FCoE links are only supported to a maximum of 300 metres. Distances greater than 300 metres are only supported when using an FCIP link or Fibre Channel between source and target.
Direct Attachment
For information on support configurations using direct attachment please visit the following document
Direct Attachment of Storwize and SAN Volume Controller Systems
Cisco Nexus
The minimum level of Cisco Nexus firmware supported for FCoE with the IBM 2145-DH8 is 5.2(1)N1(2a).
16Gbps Fibre Channel Node Connection
Please see SSIC 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 the16Gbps Node hardware can be any supported fabric switch as currently listed in SSIC.
IP Partnership
Using an Ethernet Switch to convert a 10Gbps IP partnership link to 1Gbps link and vice versa is not supported. Therefore, the IP infrastructure on the two partnership sites should both be 1Gbps or 10Gbps. However, bandwidth limiting on 10Gbps and 1Gbps IP partnership between sites is supported.
Fabric Limitations
Only one FCF ( Fibre Channel Forwarder ) switch per fabric 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 VMware vSphere Virtual Volumes (VVols) on a system that is configured for HyperSwap is not currently supported with SVC/Storwize.
DS4000 Maintenance
Host Limitations
Microsoft Offload Data Transfer ( ODX ) and SDDDSM Requirements
SAN Volume Controller 7.5.0 introduced support for Microsft ODX. In order to utilise this function all windows hosts accessing SAN Volume Controller are required to be at a minimum SDDDSM version of 2.4.5.0. Earlier versions of SDDDSM are not supported when the ODX function is activated.
Non-Disruptive Volume Move (NDVM)
Windows 2008 with SDDDSM - Stale paths will be left after moving a volume to a new I/O group. A host reboot is required in order to remove the stale paths.
AIX 6.1 SDD PCM - Preferred paths are not detected after moving a volume to a new I/O group.
Windows NTP server
The Linux NTP client used by SAN Volume Controller may not always function correctly with Windows W32Time NTP Server
TPC Restrictions
TPC Supported Versions
The minimum supported TPC version for SVC/Storwize version 7.6 is TPC 5.2.6.
Vdisk Migration
When a vdisk is migrated between a child pool and its parent, or between child pools of the same parent, it is necessary to re-probe the cluster from TPC as no event is logged on the cluster for this type of migration
Migrations between non-child pools also currently require a re-probe
These issues will be addressed in future releases of TPC and SVC/Storwize Code.
Oracle
Restriction 1:
Oracle ASM disk groups may dismount with the following error
"Waited 15 secs for write IO to PST"
Priority Flow Control for iSCSI
Priority Flow Control for iSCSI is supported on Brocade VDX 10-gigabit Ethernet switches only.
Maximum Configurations
Configuration limits for SAN Volume Controller:
Maximum WWPNs per host Object and iSCSI Names
The maximum number of FC/SAS/FCoE hosts ports supported per host object is 32.
The maximum number of iSCSI names supported per host object is 8.
Please see the following document
http://www-01.ibm.com/support/docview.wss?uid=ssg1S1005261
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.
Applying drive software update to all drives in a system with a distributed array containing more than 16 drives
Please do not update drive software on all drives together in a system that has a distributed array with more than 16 drives.
The following will perform a drive software upgrade on all drives together and are restricted in this case:
- Using command applydrivesoftware with "-all" parameter.
- Using the "Upgrade All" option in the GUI under "Pools > Internal Storage > Actions".
To workaround this restriction, please perform drive software update on one drive at a time.
You can do this using command applydrivesoftware with "-drive" parameter for each drive.
This restriction is now resolved with software version of 7.6.0.4
iSCSI Limitations
iSCSI host attachment is currently not supported with Software Version 7.6
This restriction is now resolved and iSCSI host attachment is supported with software version 7.6.0.2 and higher.
Due to the requirement for multiple access IO groups, iSCSI attached host types are not supported with HyperSwap volumes.
HyperSwap
HyperSwap is not supported with Software Version version 7.6.0
This restriction is now resolved and HyperSwap is supported with software version 7.6.0.1 and higher.
When using the HyperSwap function with software version 7.6.0.1 and higher, please configure your host multipath driver to use an ALUA-based path policy.
Due to the requirement for multiple access IO groups, iSCSI and SAS attached host types are not supported with HyperSwap volumes.
AIX Live Partition Mobility (LPM)
AIX LPM is now supported with the HyperSwap function and AIX 7.x
New CLI Commands
The following new CLI commands are not currently supported on Software Version 7.6
* addvolumecopy
* rmvolumecopy
Attempting to use a feature which is not supported will return the following error:
CMMVC7205E The command failed because it is not supported.
Support for these commands will be enabled in a future software release.
Clustered Systems
A SAN Volume Controller system at version 7.6 and higher requires native Fibre Channel SAN or alternatively 8Gbps/16Gbps Direct Attach Fibre Channel connectivity for communication between all nodes in the local cluster. Fibre Channel over Ethernet ( FCoE ) connectivity for communication between all nodes in the local cluster is also supported.
Partnerships between systems for Metro Mirror or Global Mirror replication can be used with both Fibre Channel, Native Ethernet connectivity and FCoE connectivity, however direct FCoE links are only supported to a maximum of 300 metres. Distances greater than 300 metres are only supported when using an FCIP link or Fibre Channel between source and target.
Direct Attachment
For information on support configurations using direct attachment please visit the following document
Direct Attachment of Storwize and SAN Volume Controller Systems
Cisco Nexus
The minimum level of Cisco Nexus firmware supported for FCoE with the IBM 2145-DH8 is 5.2(1)N1(2a).
16Gbps Fibre Channel Node Connection
Please see SSIC 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 the16Gbps Node hardware can be any supported fabric switch as currently listed in SSIC.
IP Partnership
Using an Ethernet Switch to convert a 10Gbps IP partnership link to 1Gbps link and vice versa is not supported. Therefore, the IP infrastructure on the two partnership sites should both be 1Gbps or 10Gbps. However, bandwidth limiting on 10Gbps and 1Gbps IP partnership between sites is supported.
Fabric Limitations
Only one FCF ( Fibre Channel Forwarder ) switch per fabric 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 VMware vSphere Virtual Volumes (VVols) on a system that is configured for HyperSwap is not currently supported with SVC/Storwize.
DS4000 Maintenance
| SAN Volume Controller supports concurrent ESM firmware upgrades for those DS4000 models listed as such on the Supported Hardware List when they are running either 06.23.05.00 or later controller firmware. However, controllers running firmware levels earlier than 06.23.05.00 will not be supported for concurrent ESM upgrades. Customers in this situation, who wish to gain support for concurrent ESM upgrades, will need to first upgrade the DS4000 controller firmware level to 06.23.05.00. This action is a controller firmware upgrade, not an ESM upgrade and concurrent controller firmware upgrades are already supported in conjunction with SAN Volume Controller. Once the controller firmware is at 06.23.05.00 or later the ESM firmware can be upgraded concurrently. |
| Note: The DS4000 ESM firmware upgrade must be done on one disk expansion enclosure at a time. A 10 minute delay from when one enclosure is upgraded to the start of the upgrade of another enclosure is required. Confirm via the Storage Manager applications "Recovery Guru" that the DS4000 status is in an optimal state before upgrading the next enclosure. If it is not, then do not continue ESM firmware upgrades until the problem is resolved. |
Host Limitations
Microsoft Offload Data Transfer ( ODX ) and SDDDSM Requirements
SAN Volume Controller 7.5.0 introduced support for Microsft ODX. In order to utilise this function all windows hosts accessing SAN Volume Controller are required to be at a minimum SDDDSM version of 2.4.5.0. Earlier versions of SDDDSM are not supported when the ODX function is activated.
Non-Disruptive Volume Move (NDVM)
Windows 2008 with SDDDSM - Stale paths will be left after moving a volume to a new I/O group. A host reboot is required in order to remove the stale paths.
AIX 6.1 SDD PCM - Preferred paths are not detected after moving a volume to a new I/O group.
Windows NTP server
The Linux NTP client used by SAN Volume Controller may not always function correctly with Windows W32Time NTP Server
TPC Restrictions
TPC Supported Versions
The minimum supported TPC version for SVC/Storwize version 7.6 is TPC 5.2.6.
Vdisk Migration
When a vdisk is migrated between a child pool and its parent, or between child pools of the same parent, it is necessary to re-probe the cluster from TPC as no event is logged on the cluster for this type of migration
Migrations between non-child pools also currently require a re-probe
These issues will be addressed in future releases of TPC and SVC/Storwize Code.
Oracle
|
Oracle Version and OS
|
Restrictions that apply:
|
| Oracle Release 11.2 any platform |
1
|
| Oracle Release 12.1 any platform |
Oracle ASM disk groups may dismount with the following error
"Waited 15 secs for write IO to PST"
Recommendation
Increase the asm_hbeatiowait to 120 seconds to prevent this issue occurring.
Applies to Oracle Database - Enterprise Edition - Version 11.2.0.3 to 12.1.0.1 [Release 11.2 to 12.1] on any platform
Priority Flow Control for iSCSI
Priority Flow Control for iSCSI is supported on Brocade VDX 10-gigabit Ethernet switches only.
Maximum Configurations
Configuration limits for SAN Volume Controller:
Maximum WWPNs per host Object and iSCSI Names
The maximum number of FC/SAS/FCoE hosts ports supported per host object is 32.
The maximum number of iSCSI names supported per host object is 8.
Please see the following document
http://www-01.ibm.com/support/docview.wss?uid=ssg1S1005261
|
Property
|
Hardware Type
|
Maximum Number
|
Comments
|
|
System (Cluster) Properties
|
|||
| Nodes per system (cluster) |
All
|
8
|
Arranged as four I/O groups |
| Nodes per fabric |
All
|
64
|
Maximum number of 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 |
All
|
4
|
Each containing two nodes |
| Fabrics per system |
2145-CF8
|
6
|
The number of counterpart SANs which are supported - Up to 4 fabrics using native Fibre Channel ports - Up to 2 fabrics using FCoE ports |
| Fabrics per system |
2145-CG8
|
8
|
The number of counterpart SANs which are supported |
| Fabrics per system |
2145-DH8
|
12
|
The number of counterpart SANs which are supported |
| USB ports |
2145-CF8
2145-CG8 |
4
|
|
|
2145-DH8
|
6
|
||
| Inter-cluster partnerships per system |
All
|
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 |
All
|
5
|
|
| Data encryption keys per system |
2145-DH8
|
1024
|
|
|
Node Properties
|
|||
| Logins per node Fibre Channel port |
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
|
2048 in IP failover mode (when partner node is unavailable) | |
|
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
|
Internal distributed arrays consume 16 logical units. | |
| 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) |
1 PB
|
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. |
|
|
Volume (Virtual Disk) Properties
|
|||
| Basic volumes (VDisks) per system |
8192
|
Each basic volume uses 1 VDisk, each with one copy. Maximum requires an 8-node cluster; refer to the volumes per I/O group limit below |
|
| Stretched volumes per system |
4096
|
Each stretched volume uses 1 VDisk, each with two copies. | |
| HyperSwap volumes per system |
1024
|
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) |
2048
|
||
| Volumes accessible per I/O group |
8192
|
||
| Thin-provisioned (space-efficient) volume copies per system |
8192
|
No limit is imposed here beyond the volume copies per system limit. | |
| Compressed volume copies per system |
2145-CF8
2145-CG8 |
800
|
Maximum requires an 8-node cluster |
| Compressed volume copies per I/O group |
2145-CF8
2145-CG8 |
200
|
|
| Compressed volume copies per system |
2145-DH8
|
2048
|
Maximum requires an 8-node cluster |
| Compressed volume copies per I/O group |
2145-DH8
|
512
|
With 64GB Memory Option Only |
| 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) volume capacity |
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 |
96 TB
|
Maximum size for an individual compressed 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. |
|
| Host mappings per system |
20,000
|
See also - volume mappings per host object below | |
|
Mirrored Volume (Virtual Disk) Properties
|
|||
| Copies per volume |
2
|
||
| Volume copies per system |
8192
|
The maximum number of volumes cannot all have the maximum number of copies | |
| Total mirrored volume capacity per I/O group |
1024 TB
|
||
|
Generic Host Properties
|
|||
|
Host objects (IDs) per system
|
2145-CF8
2145-CG8 2145-DH8 |
2048
|
A host object may contain both Fibre Channel ports and iSCSI names
|
|
Host objects (IDs) per I/O group
|
2145-CF8
2145-CG8 2145-DH8 |
512
|
Refer to the additional Fibre Channel and iSCSI host limits below
|
| Volume mappings per host object |
2145-CF8
2145-CG8 2145-DH8 |
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). |
| Total Fibre Channel ports and iSCSI names per system |
8192
|
||
| Total Fibre Channel ports and iSCSI names per I/O group |
2048
|
||
| Total Fibre Channel ports and iSCSI names per host object |
32
|
||
| iSCSI names per host object (ID) |
8
|
||
|
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 hosts ports per host object (ID) |
32
|
||
| Port logins (4x 8Gb FC) |
1024
|
||
| Port logins (2x 16Gb FC) |
2048
|
||
| Simultaneous I/Os (4x 8Gb FC) |
2048
|
||
| Simultaneous I/Os (2x 16Gb FC) |
4096
|
||
|
iSCSI Host Properties
|
|||
| iSCSI hosts per system |
2048
|
||
| iSCSI hosts per I/O group |
512
|
||
| iSCSI names per host object |
8
|
||
| iSCSI names per I/O group |
512
|
||
| iSCSI (SCSI 3) registrations per VDisk |
512
|
||
|
Copy Services Properties
|
|||
| Remote Copy (Metro Mirror and Global Mirror) relationships per system |
8192
|
This can be any mix of Metro Mirror and Global Mirror relationships. Maximum requires an 8-node cluster (volumes per I/O group limit applies) |
|
| Active-Active Relationships |
1024
|
This is the limit for the number of HyperSwap volumes in a system | |
| Remote Copy relationships per consistency group |
-
|
No limit is imposed beyond the Remote Copy relationships per system limit | |
| 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 |
256
|
Change volumes used for active-active relationships do not count towards this limit. | |
| FlashCopy mappings per system |
4096
|
||
| FlashCopy targets per source |
256
|
||
| FlashCopy mappings per consistency group |
512
|
||
| FlashCopy consistency groups per system |
255
|
||
| Total FlashCopy volume capacity per I/O group |
4096 TB
|
||
|
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. | |
|
Internal Storage System Properties
|
|||
| Drives per node |
2145-CF8
2145-CG8 |
4
|
|
| Expansion enclosures per I/O group |
2145-DH8
|
2
|
|
| Max drives per enclosure |
2145-DH8
|
24
|
|
| Max drives per I/O group |
2145-DH8
|
48
|
|
| Max drives per system |
2145-DH8
|
192
|
|
| Simultaneous autosparing |
Drives per system
|
||
|
Non-Distributed RAID Array Properties
|
|||
| Min-Max member drives per RAID-0 array |
2145-CF8
2145-CG8 |
1-4
|
All drives in a RAID-0 array must be located in the same node |
|
2145-DH8
|
1-8
|
||
| Min-Max member drives per RAID-1 array |
2145-CF8
2145-CG8 |
2-2
|
The pair of drives must contain one drive from one node in the I/O group and one drive from the other node in the same I/O group |
|
2145-DH8
|
|||
| Min-Max member drives per RAID-5 array |
2145-DH8
|
3-16
|
|
| Min-Max member drives per RAID-6 array |
2145-DH8
|
5-16
|
|
| Min-Max member drives per RAID-10 array |
2145-CF8
2145-CG8 |
2-8
|
The drives are specified as a sequence of drive pairs. Each pair of drives must contain one drive from a node in the I/O group and a drive from the other node in the same I/O group |
|
2145-DH8
|
2-16
|
||
| Hot spare drives |
-
|
No limit is imposed | |
|
Distributed RAID Array Properties
|
|||
| Arrays per system |
2145-DH8
|
32
|
The presence of non-DRAID arrays will reduce this limit |
| Arrays per I/O group |
2145-DH8
|
10
|
The presence of non-DRAID arrays will reduce this limit |
| Drives per array |
2145-DH8
|
48
|
|
| Min-Max member drives per RAID-5 array |
2145-DH8
|
4-48
|
|
| Min-Max member drives per RAID-6 array |
2145-DH8
|
6-48
|
|
| Rebuild areas per array |
2145-DH8
|
1-4
|
|
| Min-Max stripe width for RAID-5 array |
2145-DH8
|
3-16
|
|
| Min-Max stripe width for RAID-6 array |
2145-DH8
|
5-16
|
|
|
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
|
||
|
2145-DH8 Options
|
|||
| 8Gbps Fibre channel cards per node |
4
|
||
| 16Gbps Fibre channel cards per node |
4
|
||
| Compression accelerator cards per node |
2
|
||
| 10GE Ethernet cards per node |
1
|
||
| 10Gbps Ethernet ports per node |
4
|
||
| 1Gbps Ethernet ports per node |
3
|
||
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
|
Maximum compressed volume size**
|
Maximum MDisk capacity in GB
|
Maximum DRAID Mdisk capacity in TB
|
Total storage capacity manageable per system*
|
|
16
|
2048 (2 TB)
|
2000
|
2048 (2 TB)
|
32
|
64 TB
|
|
|
32
|
4096 (4 TB)
|
4000
|
4096 (4 TB)
|
64
|
128 TB
|
|
|
64
|
8192 (8 TB)
|
8000
|
8192 (8 TB)
|
128
|
256 TB
|
|
|
128
|
16,384 (16 TB)
|
16,000
|
16,384 (16 TB)
|
256
|
512 TB
|
|
|
256
|
32,768 (32 TB)
|
32,000
|
32,768 (32 TB)
|
512
|
1 PB
|
|
|
512
|
65,536 (64 TB)
|
65,000
|
65,536 (64 TB)
|
1024 (1 PB)
|
2 PB
|
|
|
1024
|
131,072 (128 TB)
|
130,000
|
96TB **
|
131,072 (128 TB)
|
2048 (2 PB)
|
4 PB
|
|
2048
|
262,144 (256 TB)
|
260,000
|
96TB **
|
262,144 (256 TB)
|
4096 (4 PB)
|
8 PB
|
|
4096
|
262,144 (256 TB)
|
262,144
|
96TB **
|
524,288 (512 TB)
|
8192 (8 PB)
|
16 PB
|
|
8192
|
262,144 (256 TB)
|
262,144
|
96TB **
|
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
[{"Product":{"code":"STPVGU","label":"SAN Volume Controller"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"7.6","Platform":[{"code":"","label":"SAN Volume Controller"}],"Version":"7.6","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Was this topic helpful?
Document Information
Modified date:
20 March 2019
UID
ssg1S1005424