HP 3PAR InForm OS 3.1.1 CIM API (QL226-96591, July 2012)

3. Call the CreateOrModifyElementFromStoragePool method with the reference to the
TPD_StorageSetting from step 1 or 2 as the Goal parameter.
• To create a legacy volume with FC drives, use a reference to the FC StoragePool as
the InPool parameter.
• To create a legacy volume with SSDs, use reference to SSD StoragePool as the InPool
parameter.
• To create a legacy volume with NL drives, use a reference to the NL StoragePool as
the InPool parameter.
• To create a thinly provisioned volume or a fully provisioned volume that allocates from a
DynamicStoragepool, use reference to DynamicStoragePool as the InPool
parameter. For a TPVV, the ElementType parameter should also be set to
ThinlyProvisionedStorageVolume (5).
• For a fully provisioned volume, the ElementType parameter should be set to
StorageVolume(2).
• If the InPool parameter is NULL, by default, the FC drives are used to create the volume.
• The parameter TheElement has to be NULL.
4. You can optionally call DeleteInstance on the TPD_StorageSetting instance from
step 1 or 2 to delete it.
Table 35 Parameters for the CreateOrModifyElementFromStoragePool Method
Grow/Set VolumeCreate VolumeOperations/Parameters
New name of volume; NULL means
no change in volume name.
Name of VolumeElementName
2
5 (Thinly Provisioned Storage
Volume).
2 (Storage Volume)
5 (Thinly Provisioned Storage
Volume)
ElementType
Reference to a
TPD_StorageSetting instance
containing new parameter values;
NULL means no change in
StorageSetting parameters.
Reference to either fixed
TPD_StorageSetting or one
created through the
CreateSetting option; defaults
to fixed RAID-10 if NULL
Goal
Must be larger than the current
volume size; NULL means the volume
is not grown.
Minimum 268435456 (256 MB)Size (bytes)
NULL.Reference to all-FC, all-NL,
all-SSD pool or
DynamicStoragePool; defaults
to all-FC pool if NULL
InPool
Reference to an existing
TPD_StorageVolume.
NULLTheElement
Creating a Volume with Disk Pattern Filtering
Disk pattern filtering can be achieved using the 3PAR extension properties to the
TPD_StorageSetting class (refer to the following table). Each of these properties are defined
as an array, with each array set representing a set of patterns, so for example if a client wants to
provide for two sets of patterns, the array size of these properties must all be 2. Properties that are
not applicable must be set to either empty string for string type or –1 for integer type.
The format for the string is the same as that for the CLI as described in the Table 36 (page 35):
34 CIM API SMI-S Support