raidcom add ldev

Storage Advisor Embedded User Guide

Version
93-07-2x
88-08-12
Audience
anonymous
Part Number
MK-97HM85022-25

Adds an LDEV to the specified parity group or the external volume group. Or this adds V-VOL for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, active flash, Dynamic Tiering for Mainframe, active flash for mainframe, Thin Image, or Copy-on-Write Snapshot to the specified pool.

Alternatively, this command creates V-VOL for Dynamic Provisioning associated with a pool volume having the data direct mapping attribute.

This command is executed asynchronously with the command input. Check the completion of this process on the raidcom get command_status command.

There is a limit to the number of asynchronous commands that can be accepted simultaneously. For details, see Maximum number of acceptable asynchronous commands
Note:

For VSP 5000 series, if the total cache initialization capacity for open system DP-VOLs created at once is large, the processing might time out.

If the number of DP-VOLs to be created by using this command exceeds 256, 256 DP-VOLs are created per creation on the storage system.

To prevent this processing from timing out, the total cache initialization capacity for up to 256 DP-VOLs to be created should be at most 8 PB. If 8 PB is exceeded, limit the total cache initialization capacity for DP-VOLs to be created at once to less than 8 PB, verify that the processing is complete by using the raidcom get command_status command, and then run the command to create the next DP-VOLs.

For more information about how to calculate the initialization capacity of the cache, see the Provisioning Guide for your storage system.

Note: If a failure occurs in a processor on an MP blade or a controller, this command cannot be run even on an MP blade or a controller on which no failure occurs.

If cache memory is blocked, a DP-VOL cannot be created. If CHB, DKB, or cache memory is blocked, a V-VOL in Thin Image cannot be created.

Syntax

When creating an LDEV or V-VOL in the specified parity group, external volume group, or pool.

raidcom add ldev {-parity_grp_id <gno-sgno>| 
   -external_grp_id <gno-sgno> | -pool {<pool ID#> |
    <pool naming> | snap}} {-ldev_id <ldev#> | 
   -tse_ldev_id <ldev#> | -ese_ldev_id <ldev#> | -ldev_id auto -request_id auto 
   [-resource_id <resource group id>] [-ldev_range <range>]} 
   {-capacity <size> | -offset_capacity <size> | -cylinder <size>} 
   [-emulation <emulation type>][-location <lba>]
   [-mp_blade_id <mp#>][-clpr <clpr#>]
   [-t10pi_enable]
   [-status {enable_fullallocation | disable_fullallocation} | -capacity_saving {compression | deduplication_compression} 
   [-capacity_saving_mode <saving_mode>] [-compression_acceleration {enable | disable} -request_id auto] | [-drs -request_id auto]
   -capacity_saving disable]

When creating a V-VOL for Dynamic Provisioning associated with a pool volume having the data direct mapping attribute.

raidcom add ldev -ldev_id <ldev#> -mapping_ldev_id <ldev id>

Options and parameters

-parity_grp_id <gno-sgno>

Specifies the parity group number (gno:1-52, sgno:1-32) (for example, 3-1).

-external_grp_id <gno-sgno>

Specifies the external volume group number (gno:1-16384, sgno:1-4096) (for example, 52-11 ("E" is not required)).

-pool {<pool ID#> | <pool naming> | snap}

Specifies a Pool ID or Pool name for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, active flash, Dynamic Tiering for Mainframe, or active flash for mainframe when V-VOL is created to Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, active flash, Dynamic Tiering for Mainframe, or active flash for mainframe pool.

When only a number is specified, it is recognized as a pool ID. Therefore, when you specify a pool that the pool name is only a number, specify the pool ID instead of the pool name.

When creating V-VOL for a Thin Image or Copy-on-Write Snapshot pool, specify "snap".

-ldev_id <ldev#> | -tse_ldev_id <ldev#> | -ese_ldev_id <ldev#>

Specifies the LDEV number (0-65279).

If you specify the -tse_ldev_id option, the TSE-VOL that is used by FlashCopy SE is created. For example:

  • -ldev_id 200
  • -tse_ldev_id 400

If you use the -tse_ldev_id or -ese_ldev_id option in a command other than the raidcom add ldev command, that option functions as the -ldev_id option.

-ldev_id auto -request_id auto [-resource_id <resource group id>] [-ldev_range <range>]

This option can be specified only when a V-VOL of which emulation type is OPEN-V is created in a Dynamic Provisioning or Dynamic Tiering pool.

Specify this option to automatically assign an LDEV number to the LDEV you created. From the unused numbers of the LDEVs for which the user has operation permission, the smallest LDEV number is assigned. To limit the range of the LDEV numbers to be assigned, use any of the following options:
  • -request_id auto: Effective only when "auto" is specified as the -request_id option. If other option than "auto" is specified, EX_INVARG or EX_REQARG is replied.
  • -resource_id <resource grp id>: Assigns the smallest LDEV number from the numbers of the unused LDEVs with the specified resource group ID.
  • -ldev_range <range>: Assigns the smallest LDEV number from the numbers of the unused LDEVs with the LDEV number specified by <range>. If the -resource_id <resource grp id> is specified with this option, the smallest LDEV number from the numbers of the unused LDEVs that have the LDEV number in <range> and the specified resource group number is assigned.

Specify <range> in the format of <starting-LDEV-number-ending-LDEV-number>. LDEV numbers must be specified in decimal or hexadecimal. To specify in hexadecimal, add 0x at the beginning of the LDEV number.

For example, to specify LDEV numbers from 300 to 305:
  • -ldev_range 300-305
  • -ldev_range 0x12c-0x131
  • -ldev_range 0x12c-305

    (You can combine decimal and hexadecimal numbers.)

You can check the selected LDEV numbers using the raidcom get command_status command.

The request ID is output in the following format after completion of the raidcom add ldev command:
  • REQID : <request#>

    Where <request#> is a request ID assigned each time the command is executed. For details, see Request ID function.

Unused LDEV numbers in the resource group where you create an LDEV and in the LDEV number range must satisfy the following requirements:
  • The unused LDEV numbers are not in the same range (grouped by every 32 LDEV numbers) as the installed LDEV in an emulation group other than OPEN-V. If this requirement is not satisfied, the command might fail with EX_CMDRJE (SSB1=2E30, SSB2=0026).
  • The unused LDEV numbers are not used as an alias of PAV. If this requirement is not satisfied, the command might fail with EX_CMDRJE (SSB1=2E30, SSB2=0025).
  • The unused LDEV numbers can be used in the shared memory installed in the storage system. If this requirement is not satisfied, the command might fail with EX_CMDRJE (SSB1=2E23, SSB2=0001).
  • When using a mainframe volume in the same storage system, SSID that is not used by the mainframe volume is assigned to the unused LDEV numbers.

The storage system might execute multiple raidcom add ldev commands at the same time. In such a batch operation, if one command fails, the others also fail. You can display command error information by executing raidcom get command_status -request_id <request#>, where you must specify the Request ID output when the command is executed. For errors caused due to batch operation, 'O' is displayed in column R, while for errors caused for other reason, 'T' is displayed in the same column. For example, if a user issues two raidcom add ldev -ldev_id auto commands at the same time to a storage system having only one free LDEV number, the system attempts to execute the commands in a batch, causing both of them to fail. Check command status by executing raidcom get command_status -request_id <request#> with the Request ID. If 'O' is displayed under column R, retry the command.

-capacity <size>

Specifies the capacity. The size can be specified in bytes or blocks. When specifying in bytes, the unit is t/T (terabyte), g/G (gigabyte), m/M (megabyte), or k/K (kilobyte). If this unit is omitted, block (512 bytes) is used.

When specifying in bytes, note the following:

  • There is no size correction.
  • If the capacity of LDEVs that are created by GUI and by CLI are the same, a copy pair might not be created. To create a pair with an LDEV that was created by GUI, create the LDEV by specifying blocks.

Example of specification:

1GB (gigabyte) is:

-capacity 1G, -capacity 1g, -capacity 1024M, -capacity 1024m, -capacity 1048576K, -capacity 1048576k, -capacity 2097152

In the case of volumes other than OPEN-V, more free space than the capacity that was actually specified is required. For details, see the Provisioning Guide for the storage system.

When you specify "all" instead of digits to create an OPEN-V LDEV and no LDEV has been created in the specified parity group* or the external volume group, the system allocates all empty space for the LDEV. If the empty space is larger than the maximum capacity of an LDEV, the system creates the LDEV with the maximum capacity and leaves the rest of the space as an empty space.

*: "all" cannot be specified depending on the combination of the drive type and drive level because of the LDEV control area allocation, and so on. In this case specify bytes or blocks.

-offset_capacity <size>

Specifies capacity. Corrects the size as well as GUI for the specified capacity. The capacity can be specified in bytes or blocks. When specifying byte, the unit is t/T (terabyte), g/G (gigabyte), m/M (megabyte), or k/K (kilobyte).

-cylinder <size>

Specifies the size in cylinder unit. When specifying, the unit is t/T (teracylinder), g/G (gigacylinder), m/M (megacylinder), or k/K (kilocylinder). Cylinder is applied if you do not specify the unit.

When an open-systems emulation type is specified, this option cannot be specified.

[-location <lba>]

Specifies the Location (the starting point of the LDEV to be created in the parity group/external volume group). If this specification is omitted, create a LDEV and close up in the free space.

[-emulation <emulation type> ]

Specifies the emulation type (for example, OPEN-V).

If this specification is omitted, OPEN-V is specified.

If this specification is omitted when the virtual volume is crated, the following emulation type is specified.

  • OPEN-V: Dynamic Provisioning, Dynamic Tiering, or active flash
  • 3390-A: Dynamic Provisioning for Mainframe, Dynamic Tiering for Mainframe, or active flash for mainframe

The values that can be specified for <emulation type> are:

  • OPEN-3, OPEN-8, OPEN-9, OPEN-E, OPEN-L, OPEN-V
  • 3390-1, 3390-2, 3390-3, 3390-A, 3390-3A, 3390-3B, 3390-3C, 3390-3R, 3390-9, 3390-9A, 3390-9B, 3390-9C, 3390-L, 3390-LA, 3390-LB, 3390-LC, 3390-M, 3390-MA, 3390-MB, 3390-MC, 3390-V
  • 3380-3, 3380-3A, 3380-3B, 3380-3C

Some emulation types cannot be specified depending on the emulation type.

CAUTION:

You can specify 3390-3 or 3390-3R as the emulation type, but these are unable to be mixed. You can specify the 3380 series or the 3390 series as the emulation type for each parity group, but they are unable to be mixed for each 32 address boundary because of the OS restriction.

[-mp_blade_id <mp#> ]

Specifies the MP blade ID (0-15). If this specification is omitted, it is allocated automatically.

[-clpr <clpr#> ]

When you create virtual volumes by specifying the -pool <pool#> option, specify the CLPR ID. If you omit this option, the ID number of CLPR to which the pool is allocated is used.

[-status {enable_fullallocation | disable_fullallocation}]

Specifies an availability of Full Allocation when the virtual volume is used for Dynamic Provisioning, Dynamic Tiering, or active flash. If this specification is omitted, Full Allocation is disabled.

  • enable_fullallocation: Enables Full Allocation. If all areas equivalent to the sum of the pool capacities the specified volume requires can be reserved, it is guaranteed that all areas of DP-VOL are writable.
  • disable_fullallocation: Disables Full Allocation.
[-t10pi_enable]

Enables the T10 PI attribute.

-mapping_ldev_id <ldev id>

Creates the V-VOL for Dynamic Provisioning associated with the pool volume having the data direct mapping attribute. When you specify this option, the data direct mapping attribute is automatically set to the V-VOL to be created.

[-compression_acceleration {enable | disable} -request_id auto]
Supported storage systems:
  • VSP 5000 series
Specifies whether compression accelerator is enabled or disabled. If you omit this option, it will be enabled when COMPRESSION_ACCELERATION of raidcom get system -key dedupe_compression is AVAILABLE. It will be disabled when COMPRESSION_ACCELERATION of raidcom get system -key dedupe_compression is UNAVAILABLE.
  • enable: Compression accelerator is enabled.
  • disable: Compression accelerator is disabled.

<request #> is the Request ID assigned for each command execution. For details, see Request ID function.

[-capacity_saving <capacity saving>]

Specifies the capacity saving setting. If you omit this option, a volume is created with the capacity saving function disabled.

  • compression: Enables compression.
  • deduplication_compression: Enables deduplication and compression.
  • disable: Disables capacity saving.

For VSP 5000 series, compressed volumes for accelerated compression, or volumes for deduplication and compression can be created only for pools whose subscription limit is set to 65535 (unlimited). An error occurs if compression or deduplication_compression is specified for a pool whose subscription limit is other than 65535 (unlimited).

[-capacity_saving_mode <saving mode>]

When you enable capacity saving, specifies the post-process mode or inline mode as the capacity saving processing mode for DP-VOLs. For details about the capacity saving processing modes, see the Provisioning Guide for the storage system.

  • post_process: Sets the post-process mode for capacity saving processing.
  • inline: Sets the inline mode for capacity saving processing.

For VSP G1x00, VSP F1500, VSP G200, G400, G600, G800, and VSP F400, F600, F800, post_process is the default. For VSP G/F350, G/F370, G/F700, G/F900, inline is the default.

[-drs -request_id auto]
Supported storage systems:
  • VSP 5000 series

Specify this option to create a data reduction shared volume (DRS-VOL).

<request #> is the Request ID assigned for each command execution. For details, see Request ID function.

Examples

Creating an LDEV: 100 of size 10 GB (gigabytes) in a parity group: 5-2.

Location in the parity group: automatic allocation, LDEV Emulation type: OPEN-V

# raidcom add ldev -parity_grp_id 5-2 -ldev_id 100 -capacity 10G

Creating an LDEV with the following conditions: Parity group: 5-3, location of the parity group: automatic allocation, Emulation type: 3390-3, Size: 10 M cylinder (Cylinder specification), LDEV: 120.

# raidcom add ldev -parity_grp_id 5-3 -ldev_id 120 -cylinder 10m -emulation 3390-3

Creating an LDEV of position in the external volume: allocated automatically, emulation type: OPEN-V, External volume: 01-02, Capacity: 200 MB (megabytes), and LDEV number: 200.

# raidcom add ldev -external_grp_id 01-02 -ldev_id 200 -capacity 200m

Creating an LDEV of external volume group: 01-03, position in the external volume: allocated automatically, emulation type: OPEN-V, External volume size: takeover, and LDEV number: 220.

# raidcom add ldev -external_grp_id 01-03 -ldev_id 220 -capacity all

Creating a V-VOL of Capacity: 300 MB and number: 300, to a pool for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, active flash, Dynamic Tiering for Mainframe, or active flash for mainframe.

# raidcom add ldev -pool 4 -ldev_id 300 -capacity 300m

Creating a V-VOL of Capacity: 300 MB and LDEV number: 400, to a pool for Thin Image or Copy-on-Write Snapshot.

# raidcom add ldev -pool snap -ldev_id 400 -capacity 300m

Creating a V-VOL of Capacity: 300 MB, LDEV number: 300, and Full Allocation: enable, to the pool ID: 4 for Dynamic Provisioning.

# raidcom add ldev -pool 4 -ldev_id 300 -capacity 300m -status enable_fullallocation

Creating a V-VOL (LDEV ID: 44:44) for Dynamic Provisioning associated with the pool volume (LDEV ID: 22:22) that has the data direct mapping attribute in the Dynamic Provisioning pool.

#raidcom add ldev -ldev_id 44:44 -mapping_ldev_id 22:22

Creating a V-VOL of Capacity: 300 MB, LDEV number: 300, and the T10 PI attribute: valid, in a pool (pool ID: 4) for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, active flash, Dynamic Tiering for Mainframe, or active flash for mainframe.

# raidcom add ldev -pool 4 -ldev_id 300 -capacity 300m -t10pi_enable

Creating a V-VOL of Capacity: 300 MB, LDEV number: 300, and capacity saving setting: compression, in the pool (ID: 4) for Dynamic Provisioning.

# raidcom add ldev -pool 4 -ldev_id 300 -capacity 300m -capacity_saving compression

Creating a V-VOL of Capacity: 300 MB, LDEV number: 300, capacity saving setting: compression, and compression accelerator: enable, in the pool (ID: 4) for Dynamic Provisioning.

# raidcom add ldev -pool 4 -ldev_id 300 -capacity 300m -capacity_saving compression -compression_acceleration enable -request_id auto

Creating a V-VOL of Capacity: 300 MB, LDEV number: 300, capacity saving setting: deduplication and compression, and capacity saving mode: inline, in the pool (ID: 4) for Dynamic Provisioning.

#raidcom add ldev -pool 4 -ldev_id 300 -capacity 300m -capacity_saving deduplication_compression -capacity_saving_mode inline

Creating a V-VOL of capacity: 10 GB for a Dynamic Provisioning or Dynamic Tiering pool (pool ID: 4), and assigning an unused LDEV number automatically.

# raidcom add ldev -pool 4 -ldev_id auto -request_id auto -capacity 10G
REQID : 1

Creating a DRS-VOL with capacity: 300 MB, LDEV number: 300, and capacity saving setting: deduplication and compression in a Dynamic Provisioning pool (pool ID: 4).

#raidcom add ldev -pool 4 -ldev_id 300 -capacity 300m -capacity_saving
deduplication_compression -drs -request_id auto
CAUTION:
The following message is shown whenever an LDEV larger than 4 TB is specified. It does not necessarily indicate that there is a problem:
raidcom : Please check if LDEV over 4 TB will be used for replication products, and then check the supported capacity.