System Limits
This section summarizes the system limits for HPE Nimble Storage arrays. Alerts or log messages are generated when the system reaches the warning count, so this is a threshold. No more objects of the specified type can be created when the system reaches the maximum count, so this is a limit.
Volume scalability to 10,000 volumes per group is supported when the group leader is an array model that supports 10,000 volumes, and it belongs to a pool that can also support this limit. Pool limits are the same as the limits of the smallest capacity array in the pool.
See the notes at the end of the table for information about array models that support specific limits.
See Relationship of Groups, Pools, Arrays, Folders, and Volumes for information about the scope of objects in single-array and multi-array groups.
Object Type | Scope | iSCSI Maximum | FC Maximum | Warning | Notes |
---|---|---|---|---|---|
Array | Group | 4 | 4 | 4 | |
Pool | 4 | 4 | 4 | ||
Branch | Group | 10,000 | 10,000 | 9,500 | |
CHAP user | Group | 1024 | N/A | 960 | |
Data connection | Controller |
80000 15000 |
80000 15000 |
72000 13500 |
An iSCSI or a Fibre Channel path to a volume 1 (80000) 2 (15000) |
Session | Array | 12000 | 12000 | None | An iSCSI session or FC login |
FC initiator | FC port | N/A | 256 | None | Prior to NimbleOS 4.x, this value was 128. |
Folder | Pool | 128 | 128 | None | |
Group | 128 | 128 | None | ||
Initiator | Initiator group | 256 | 256 | 240 | |
Group | 10,000 | 10,000 | 9,500 | ||
Initiator group | Subnet | 60 | N/A | 54 | |
Group | 1,024 | 1,024 | 960 | ||
Network configuration | Array | 4 | 4 | 4 | |
Performance policy | Group | 100 | 100 | 90 | |
Pool | Group | 4 | 4 | 4 | |
Protection schedule | Group | 5,000 | 5,000 | 4,500 | |
Protection template | 10 | 10 | 8 | ||
Volume collection | 10 | 10 | 8 | ||
Protection template | Group | 50 | 50 | 45 | |
Replication bandwidth policy (throttle) | Group | 50 | 50 | 45 | |
Replication partner | 25 | 25 | 20 | ||
Replication partner | Group | 50 | 50 | 45 | |
Pool | 50 | 50 | 45 | ||
Route | Network configuration | 10 | 10 | 8 | |
SSH key | User | 10 | 10 | 8 | |
Snapshot | Group |
300,000 190,000 |
300,000 190,000 |
275,000 175,000 |
1 2 3 |
Pool |
300,000 190,000 |
300,000 190,000 |
275,000 175,000 |
1 2 3 |
|
Volume | 1,000 | 1,000 | 900 | ||
Writable Snapshot | Array |
40000 10000 |
40000 10000 |
None |
1 2 4 |
Snapshot Collection | Volume Collection | 1,000 | 1,000 | 900 | |
Subnet | Network configuration | 60 | 60 | 54 | |
User account | Group | 100 | 100 | 90 | |
Volume | Group |
10,000 1,024 |
10,000 1,024 |
9,200 960 |
1 2 |
Pool |
10,000 1,024 |
10,000 1,024 |
9,200 960 |
1 2 |
|
Performance policy |
10,000 1,024 |
10,000 1,024 |
9,200 960 |
1 2 |
|
Volume collection | 50 | 50 | 45 | Volumes in a collection can exist in different pools. | |
Synchronous replication | 128 | 128 | N/A | These values also apply to Peer Persistence. | |
Volume limit | 127 TiB | 127 TiB | N/A | ||
Volume access control list (ACL) | Group | 65,536 | 65,536 | 60,000 | |
Pool | 65,536 | 65,536 | 60,000 | ||
Volume | 64 | 64 | 60 | ||
Volume collection | Group |
2,000 512 |
2,000 512 |
1,800 480 |
1 2 |
NOTE:
1 Limits apply to AF5000, AF7000, AF9000, AF60, and AF80 model arrays 2 Limits apply to all model arrays not listed in Note 1. 3 A frequent schedule is a schedule in a volume collection that triggers snapshots more often than every five minutes. There is a limitation of five frequent schedules per array group. There is no restriction on schedules with a period of five minutes or more. 4 Writable snapshots also count against the total Snapshot limit. |