IBM Support

V8.3.1.x Configuration Limits and Restrictions for IBM Spectrum Virtualize for Public Cloud

Preventive Service Planning


Abstract

This document lists the configuration limits and restrictions specific to IBM Spectrum Virtualize for Public Cloud software version 8.3.1.x

Content

Features not supported

The following features are not supported by the v8.3.1 release:

  • Real Time Compression
  • Encryption
  • Stretched Cluster
  • HyperSwap
  • DRAID
  • NPIV
  • Software-based compression (on IBM Cloud)
  • Deduplication (on AWS c5.4xlarge only)
  • Hot Spare Node


IBM Cloud

Only the following CPU models in the dual-processor servers are supported on IBM Cloud:
CPU Model
Intel Xeon E5-2620
Intel Xeon E5-2650
Intel Xeon E5-5120

Multiple Availability Zones are not supported.


AWS

Only the following EC2 instances are supported on AWS:
Model
vCPU
Memory (GiB)
Instance Storage (GiB)
Network Bandwidth (Gbps)
Dedicated EBS Bandwidth (Mbps)
c5.4xlarge
16
32
EBS-only
Up to 10
4,750
c5.9xlarge
36
72
EBS-only
10
9,500
c5.18xlarge
72
144
EBS-only
25
19,000

Multiple Availability Zones are not supported.


Data Reduction Pools

The following restrictions apply for Data Reduction Pools (DRP):

  1. Child pools are not supported in a DRP;
  2. VVOL is not supported in a DRP (because child pool is not supported);
  3. A volume in a DRP cannot be shrunk;
  4. No volume move between I/O groups if volume in a DRP (use FlashCopy or Metro Mirror/Global Mirror instead);
  5. No split of a volume mirror to copy in a different I/O group;
  6. Real/used/free/free/tier capacity are not reported per volume - only per pool.

Note: These restrictions are applicable to all the versions of IBM Spectrum Virtualize v8.1.2 and later


REST API

Customers using the REST API to list more than 2000 objects may experience a loss of service, from the API, as it restarts due to memory constraints.


IPv6

IPv6 addresses are not supported. Only IPv4 addresses can be used.


Quorum

Only IP Quorum devices are supported.


VMware vSphere Virtual Volumes (VVols)

The maximum number of Virtual Machines on a single VMware ESXi host in an VVol storage configuration is limited to 680.


Oracle

Oracle Version and OS
Restrictions that apply:
Oracle Release 11.2 any platform
1
Oracle Release 12.1 any platform

Restriction 1:
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


Maximum Configurations

Configuration limits for Spectrum Virtualize for Public Cloud:

Property
Cloud Vendor
Maximum Limit
Comments
System (Cluster) Properties
Nodes per system (cluster)
IBM
8
Arranged as two I/O groups
AWS
4
I/O groups per system
IBM
4
Each containing two nodes
AWS
2
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
Node Properties
iSCSI sessions per node
1024
2048 in IP failover mode (when partner node is unavailable).
This limit includes both iSCSI Host Attach AND iSCSI Initiator sessions
Managed Disk Properties
Managed disks (MDisks) per system
IBM
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)
Elastic Block Stores (EBS) per IO group
AWS
20
Maximum of 320TB backend storage.
Managed disks per storage pool (managed disk group)
IBM
128
Internal distributed arrays consume 16 logical units.
Storage pools per system
IBM
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.
Total storage capacity manageable per system
IBM
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.
AWS
256TB
Volume (Virtual Disk) Properties
Basic volumes (VDisks) per system
10000
Each basic volume uses 1 VDisk, each with one copy.
Volumes per I/O group
(volumes per caching I/O group)
10000
Volumes accessible per I/O group
10000
Thin-provisioned (space-efficient) volume copies per system
-
No limit is imposed here beyond the volume copies per system limit.
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.
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
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 SV 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 SV.
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
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
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.
Maximum requires an 8-node cluster
Remote Copy relationships per consistency group
-
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 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
5000
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
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.
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.
External Storage System Properties
LUNs (managed disks) per storage system
-
No limit is imposed beyond the available max size of IBM Cloud Block Storage
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
Objects per response
2000


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 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
131,072 (128 TB)
2048 (2 PB)
4 PB
2048
262,144 (256 TB)
260,000
262,144 (256 TB)
4096 (4 PB)
8 PB
4096
262,144 (256 TB)
262,144
524,288 (512 TB)
8192 (8 PB)
16 PB
8192
262,144 (256 TB)
262,144
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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"STHLEK","label":"IBM Spectrum Virtualize for Public Cloud"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.3","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
24 May 2022

UID

ibm13369399