Installation manual

Adding a Managed Volume
Selecting a VPU (optional)
9-48 CLI Storage-Management Guide
For example:
bstnA6k(gbl)# namespace medarcv
bstnA6k(gbl-ns[medarcv])# volume /test_results
bstnA6k(gbl-ns-vol[medarcv~/test_results])# no vpu
bstnA6k(gbl-ns-vol[medarcv~/test_results])# ...
VPU Limits for Managed Volumes and Shares
Managed volumes have stricter limits on shares than direct volumes. (For the
maximum shares in a direct volume, see “VPU Limits for Direct Volumes and
Shares” on page 8-24.) Table 9-1 specifies managed-volume and share limits on each
platform.
These limits are evaluated on a credit system; to create a new managed volume or
share, its VPU must have sufficient credits. Volume limits are enforced whenever a
volume is enabled, and share limits are enforced when both the share and its volume
are enabled. The enable operation is denied if the VPU lacks sufficient credits.
Table 9-1. VPU Configuration Limits
Platform Maximum
Volumes (all
types)
Maximum
Shares per
Managed
Volume
Maximum
Managed
Shares (total)
ARX®500 (1 VPU) 64 64 128
ARX®1000 (1 VPU) 64 64 128
ARX®6000 (per VPU) 64 64 256
• ARX®6000 with 1
ASM (2 VPUs)
12864512
• ARX®6000 with 2
ASMs (4 VPUs)
256 64 1,024