Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Configuring storage resources

Use the web-based user interface and the REST API to set up spare drives, configure drives, and create pools and volumes.

Workflow for configuring storage resources

Prepare the storage capacity of a storage system to be used as volumes. To attach the volumes, register servers to be managed by Storage Advisor Embedded and configure connection information for the port on the storage system, as shown in the following figure.

GUID-E36676A9-BE15-4ED0-B44F-429CDBD5BEB3-low.gif
Note
  • "Registering a server" and "Setting port connections for server" are enabled if the servers are managed by Storage Advisor Embedded.
  • You can also add and delete WWNs or iSCSI initiator names after registering servers.

Configuring drives

You can configure the storage system to recognize drives that are inserted into slots and configured for use.

Drives are hardware composed of storage media and devices for reading and writing to the storage media. According to the specified settings, you can use drives as data drives for reading and writing data, or as spare drives if an error occurs in a data drive.

Procedure

  1. In the navigation bar, click Others Drive Settings.

    GUID-6B7693F5-F8E0-44EA-9F7C-DD954C4E3AF8-low.png

  2. In the maintenance utility, click Install to detect the added drives.

  3. Click Install again for the storage system to recognize the drives.

  4. Confirm that the new drives are added to the list of available drives.

  5. In the maintenance utility, click Log Out.

Setting up spare drives

You can set up spare drives to prepare for the possibility of a drive failure. If a drive failure occurs, a spare drive allows you to continue the work by using data that was copied to another drive.

Free drives that are not specified as data drives (drives that are not used for the reading and writing of data) can be selected and set up as spare drives.

Before you begin

Drives that are identified as spare are displayed in the list of available drives.

Procedure

  1. In the navigation bar, click Others Configure Spare Drives.

    GUID-21C6A2A9-8818-44AC-9646-A0E1EA668A05-low.gif

  2. Specify the number of spare drives that you want to set up as Spare Drives, and then click Submit.

Creating a pool

You can create a pool by specifying drives.

Pools for thin provisioning are virtual areas in a storage system that are associated with multiple drives. Thin provisioning provides virtual volumes to a server and uses the actual capacity from a pool when a server makes a write request.

If you create a pool in Storage Advisor Embedded, a recommended configuration is displayed from among the various different configurations supported by the storage system. This configuration consists of the combination of drives that allows drive space to be used most effectively.

Using the Dynamic Tiering license, you can create tiered pools by specifying drives that have different drive types, drive interface, or drive speeds. The tiers are arranged by performance, and data is automatically stored in optimum tiers.

Before you begin

  • Make sure that a drive that is configured in the storage system is available.
  • Identify the pool name.

    To specify the configuration of the pool being created, also obtain the following information:

    • Drive information (drive type, drive interface, drive speed, and capacity)
    • RAID level
    • Number of drives to be used

Procedure

  1. In the navigation bar, click Pools.

  2. Click the plus sign (+).

  3. Enter the Pool Name. To accept the recommended configuration, click Submit to create a pool.

    To specify the pool configuration, change the number of drives. To specify a different RAID configuration, select the RAID level and specify the number of usable drives. Next, click Check to check the available combinations, and then click Submit.

    GUID-3D3E6A50-FB55-489B-A932-BDF5FC8CB52D-low.png

Creating volumes

You can create volumes from a pool. By enabling the capacity saving (deduplication and compression), you can reduce the amount of data to be stored, depending on the characteristics of the data.

Before you begin

  • Ensure that a pool is available.

    If you want to enable the capacity saving for the volumes to be created, you cannot use a tiered pool.

  • Obtain the following items:
    • Pool name
    • Capacity
    • Number of volumes
    • Volume name

Procedure

  1. In the dashboard or in the navigation bar, click Volumes.

  2. Click the plus sign (+).

  3. Specify the required information and create the volumes.

    GUID-C96EA6E5-C38B-43A0-9818-1E4F43DDCEC1-low.gif

    For the name of a volume, specify a name that is a combination of Volume Name and a number beginning with Suffix Start Number (optional).

    For example, if you specify "volume" for Volume Name, "7" for Suffix Start Number, and "2" for Number of Digits, the volume name will be "volume07".

Getting drive information

The following request gets information about drives. You can specify filter conditions.

Execution permission

Storage Administrator (View Only)

Request line

GET base-URL/simple/v1/objects/drives
Request message
  • Object ID

    None.

  • Query parameters

    Parameter

    Type

    Filter Condition

    poolId

    int

    (Optional) ID of the pool to which the drives belong

    If poolName is specified, do not specify this parameter.

    poolName

    string

    (Optional) Name of the pool to which the drives belong

    Drive information will also be obtained if part of the specified value matches a pool name.

    If poolId is specified, do not specify this parameter. If both poolId and this parameter are specified, this parameter is ignored.

    status

    string

    (Optional) Specify any of the following values as the status of the drives to be obtained:

    • Normal: The drive with a status of normal.
    • Warning: An error has occurred in a part of the drive.
    • Copying: Copying is in progress.
    • CopyIncomplete: Copying is incomplete.
    • Reserved: The spare drive cannot be used.
    • Failed: The drive is in the error status because of a failure.
    • Blocked: The drive is in the error status because it is under maintenance.

    useOfTheDrive

    string

    (Optional) Specify any of the following values as the purpose of the drives to be obtained:

    • data: Data drive
    • spare: Spare drive
    • free: Unused drive
  • Body

    None.

Response message
  • Body

    The following is an example of output when drive information is obtained for drives that are not in use (drives for which free is specified for the useOfTheDrive query parameter):

    {
        "data": [
            {
                "location": "0-0",
                "status": "Normal",
                "driveType": "HDD",
                "driveInterface": "SAS",
                "driveRpm": "NUMBER_10000",
                "driveCapacity": 300,
                "displayDriveCapacity": "300 GB",
                "typeCode": "DKR5C-J300SS",
                "poolIds": [],
                "useOfTheDrive": "free"
            },
            {
                "location": "0-1",
                "status": "Normal",
                "driveType": "HDD",
                "driveInterface": "SAS",
                "driveRpm": "NUMBER_10000",
                "driveCapacity": 300,
                "displayDriveCapacity": "300 GB",
                "typeCode": "DKR5C-J300SS",
                "poolIds": [],
                "useOfTheDrive": "free"
            },
            {
                "location": "0-2",
                "status": "Normal",
                "driveType": "HDD",
                "driveInterface": "SAS",
                "driveRpm": "NUMBER_10000",
                "driveCapacity": 300,
                "displayDriveCapacity": "300 GB",
                "typeCode": "DKR5C-J300SS",
                "poolIds": [],
                "useOfTheDrive": "free"
            },
            {
                "location": "0-3",
                "status": "Normal",
                "driveType": "HDD",
                "driveInterface": "SAS",
                "driveRpm": "NUMBER_10000",
                "driveCapacity": 300,
                "displayDriveCapacity": "300 GB",
                "typeCode": "DKR5C-J300SS",
                "poolIds": [],
                "useOfTheDrive": "free"
            }
      ],
      "count": 4
    }

    Attribute

    Type

    Description

    location

    string

    Mounted location of the drive. Also commonly referred to as "name" or "ID".

    status

    string

    Status of the drive:

    • Normal: The drive with a status of normal.
    • Warning: An error has occurred in a part of the drive.
    • Copying: Copying is in progress.
    • CopyIncomplete: Copying is incomplete.
    • Reserved: The spare drive cannot be used.
    • Failed: The drive is experiencing an error because of a failure.
    • Blocked: The drive is experiencing an error because it is under maintenance.
    • Unknown: The status is unknown.

    driveType

    string

    Drive type:

    • HDD
    • SSD(RI)
    • SSD
    • FMD DC2: A Hitachi flash-based SSD with compression capability.

    driveInterface

    string

    Drive interface:

    • SAS
    • NVMe

    driveRpm

    string

    Drive rotation speed (rpm):

    • NUMBER_0
    • NUMBER_7200
    • NUMBER_10000
    • NUMBER_15000
    • High
    • Middle
    • Low
    • Unknown

    driveCapacity

    int

    Drive capacity (GB)

    displayDriveCapacity

    string

    Capacity of the drive and unit of measurement (GB or TB)

    typeCode

    string

    Drive type code

    poolIds

    int[]

    List of pool IDs to which the drives belong

    useOfTheDrive

    string

    Purpose of the drive:

    • data: Data drive
    • spare: Spare drive
    • free: Unused drive
Status codes

See HTTP status codes.

Coding example

curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X GET https://192.0.2.100/ConfigurationManager/simple/v1/objects/drives?useOfTheDrive=free

Getting information about a specific drive

The following request gets information about a specific drive by using the specified drive location.

Execution permission

Storage Administrator (View Only)

Request line

GET base-URL/simple/v1/objects/drives/object-ID
Request message
  • Object ID

    Specify a value for the location that was obtained by getting information about drives.

    Attribute

    Type

    Description

    location

    string

    (Required) Mounted location of the drive. Also commonly referred to as "name" or "ID".

  • Query parameters

    None.

  • Body

    None.

Response message
  • Body

    The following is an example of the output when getting information about a specific drive (location:0-0):

    {
      "location": "0-0",
      "status": "Normal",
      "driveType": "HDD",
      "driveInterface": "SAS",
      "driveRpm": "NUMBER_10000",
      "driveCapacity": 300,
      "displayDriveCapacity": "300 GB",
      "typeCode": "DKR5C-J300SS",
      "poolIds": [],
      "useOfTheDrive": "free"
    }

    For details on attributes to be obtained, see the description of the API function for getting drive information.

Status codes

See HTTP status codes.

Coding example

curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X GET https://192.0.2.100/ConfigurationManager/simple/v1/objects/drives/0-0

Setting up spare drives

The following request sets up a spare drive with the specified number of drives.

Execution permission

Storage Administrator (Provisioning)

Request line

POST base-URL/simple/v1/objects/drives/actions/set-spare/invoke
Request message
  • Object ID

    None.

  • Query parameters

    None.

  • Body

    The following is an example of setting up four data drives that have the drive type code DKR5D-J600SS as spare drives:

    {
      "additionalSpareDrives": [
        {
          "driveTypeCode": "DKR5D-J600SS",
          "driveCount": 4
        }
      ]
    }

    Attribute

    Type

    Description

    additionalSpareDrives

    object[]

    Drive information to be set for the spare drive:

    • (Required) driveTypeCode (string)

      Specify a drive type code consisting of 12 characters.*

      Example: DKR5D-J900SS

    • (Required) driveCount (int)

      Specify the number of data drives as an integer from 1 through 1440.

    * The spare drive setting can be specified for drives with a different drive type code, even if the drive conditions (drive type, drive interface, drive rotation speed, and drive capacity) are the same. The system specifies the spare drive setting for drives that match the drive conditions, regardless of the drive type code you specify. You can check information about the drives specified as spare drives by running the API request for getting drive information.

Response message
Status codes

See HTTP status codes.

Coding example

curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X POST --data-binary @./InputParameters.json https://192.0.2.100/ConfigurationManager/simple/v1/objects/drives/actions/set-spare/invoke

Creating a pool

The following request creates a pool by using the specified pool name and drive information.

For storage systems with a Dynamic Tiering license, if you specify drives that have different drive information (drive type, drive interface, drive rotation speed) at the same time, tiered pools, where the tiers are arranged by performance, are created. In a tiered pool, data is automatically stored in optimum tiers.

Note

If the differential data of a snapshot is stored in a pool and the usage rate of the pool exceeds the depletion threshold value, the created snapshot might become unusable. To change the depletion threshold value, change the pool settings after you create the pool.

Execution permission

Storage Administrator (Provisioning)

Request line

POST base-URL/simple/v1/objects/pools
Request message
  • Object ID

    None.

  • Query parameters

    None.

  • Body

    The following is an example of creating a pool, with the pool name and drive information specified as follows:

    • Pool name: NASOS
    • Drive type code: DKR5D-J600SS
    • Number of data drives: 4
    • RAID level: RAID5
    {
      "name": "NASOS",
      "drives": [
        {
          "driveTypeCode": "DKR5D-J600SS",
          "dataDriveCount": 4,
          "raidLevel": "RAID5"
        }
      ]
    }

    Attribute

    Type

    Description

    name

    string

    (Required) Specify a pool name consisting of up to 32 characters.

    You can use alphanumeric characters (0 through 9, A through Z, a through z), space characters, and the following symbols:

    Comma (,), hyphen (-), period (.), forward slash (/), colon (:), at sign (@), back slash (\), underscore (_)

    This attribute is case-sensitive.

    You can use a space character between characters, but cannot use it at the beginning or end of the pool name.

    You cannot use a hyphen (-) at the beginning of the pool name.

    drives

    object[]

    Specify the drive information to be used for the pool:

    • (Required) driveTypeCode (string)

      Specify a drive type code consisting of 12 characters.*

      Example: DKR5D-J900SS

    • (Required) dataDriveCount (int)

      Specify the number of data drives as an integer from 1 through 1440.

      If RAID1 or RAID5 is specified as the RAID level, specify 4 or a greater value for the number of data drives.

      If RAID6 is specified as the RAID level, specify 8 or a greater value for the number of data drives.

    • (Required) raidLevel (string)

      RAID level

      Specify one of the following RAID levels:

      • RAID1
      • RAID5
      • RAID6

    * The storage system can contain drives that have the same drive conditions (drive type, drive interface, drive rotation speed, and drive capacity), but different drive type codes. In this case, regardless of the drive type code you specified, drives that match the drive conditions are used to create a pool.

    You can check information about the drives belonging to the newly created pool by specifying the corresponding pool ID as a query parameter for the API request to getting drive information and then executing the request.

Response message
Status codes

See HTTP status codes.

Coding example

curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X POST --data-binary @./InputParameters.json https://192.0.2.100/ConfigurationManager/simple/v1/objects/pools

Creating a volume

The following request creates a volume with the specified capacity and nickname.

Execution permission

Storage Administrator (Provisioning)

Request line

POST base-URL/simple/v1/objects/volumes
Request message
  • Object ID

    None.

  • Query parameters

    None.

  • Body

    The following is an example of creating a volume, in the pool with ID 63, with a capacity of 100 MiB, and the nickname REST_API_100MVolume, for which deduplication and compression are enabled:

    {
      "capacity": 100,
      "number": 1,
      "nicknameParam": {
        "baseName": "REST_API_100MVolume"
      },
      "savingSetting": "DEDUPLICATION_AND_COMPRESSION",
      "poolId": 63
    }

    Attribute

    Type

    Description

    capacity

    long

    (Required) Capacity of the volume to be created (MiB)

    Specify a value in the range from 47 through 268435456.

    number

    int

    (Optional) Number of volumes to be created

    Specify a value in the range from 1 through 1000.

    If this attribute is omitted, a single volume is created.

    nicknameParam

    object

    Information about the nickname to be assigned to the new volume:

    • (Required) baseName (string)

      The nickname can contain up to 32 characters.

      You can use alphanumeric characters (0 through 9, A through Z, a through z), space characters, and the following symbols:

      Exclamation mark (!), hash mark (#), dollar sign ($), percent sign (%), ampersand (&), single quotation mark ('), left parenthesis ((), right parenthesis ()), plus sign (+), comma (,), hyphen (-), period (.), forward slash (/), colon (:), equal sign (=), at sign (@), left square bracket ([), back slash (\), right square bracket (]), caret (^), underscore (_), grave accent mark (`), left curly bracket ({), right curly bracket (}), tilde (~)

      This attribute is case-sensitive.

      You can use a space character between characters, but you cannot use it at the beginning or end of the nickname.

    • (Optional) startNumber (int)

      Specify the lowest serial number to be added after the nickname as an integer in the range from 0 to 65279.

    • (Optional) numberOfDigits (int)

      Specify the number of digits in the serial number to be added after the nickname as an integer in the range from 1 to 5.

      If you specify this attribute, you must also specify startNumber. If you specify startNumber but omit this attribute, 1 is assumed.

    Example: If you specify AAA for baseName, 1 for startNumber, and 3 for numberOfDigits, and specify 100 for number, indicating the number of volumes to be created, nicknames from AAA001 through AAA100 are assigned to the volumes.

    Specify the values so that the sum of the number of characters specified for baseName, and the number of digits in the number generated from the values specified for startNumber and numberOfDigits, is not more than 32.

    savingSetting

    string

    (Optional) Settings for the capacity saving (deduplication and compression)

    Specify the following values:

    • DEDUPLICATION_AND_COMPRESSION: The capacity saving (deduplication and compression) is enabled.

      The capacity saving (compression) is enabled when you enable the capacity saving (deduplication).

    • COMPRESSION: The capacity saving (compression) is enabled.
    • DISABLE: No settings are specified.

    If this attribute is omitted, DISABLE is considered.

    poolId

    int

    (Required) Specify the ID of the pool in which the volumes are to be created as a value in the range from 0 through 127.

Response message
Status codes

See HTTP status codes.

Coding example

curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X POST --data-binary @./InputParameters.json https://192.0.2.100/ConfigurationManager/simple/v1/objects/volumes

Releasing the spare drive setting

The following request releases the spare drive setting with the specified number of drives. The drive can then be used as a normal drive.

Execution permission

Storage Administrator (Provisioning)

Request line

POST base-URL/simple/v1/objects/drives/actions/release-spare/invoke
Request message
  • Object ID

    None.

  • Query parameters

    None.

  • Body

    The following is an example of releasing four spare drives that have the drive type code DKR5D-J600SS:

    {
      "releasedSpareDrives": [
        {
          "driveTypeCode": "DKR5D-J600SS",
          "driveCount": 4
        }
      ]
    }

    Attribute

    Type

    Description

    releasedSpareDrives

    object[]

    Drive information for which the spare drive setting is to be released:

    • (Required) driveTypeCode (string)

      Specify a drive type code consisting of 12 characters.*

      Example: DKR5D-J900SS

    • (Required) driveCount (int)

      Specify the number of data drives as an integer from 1 through 1440.

    * The spare drive setting can be released for drives with a different drive type code, even if the drive conditions (drive type, drive interface, drive rotation speed, and drive capacity) are the same. The system releases the spare drive setting for drives that match the drive conditions, regardless of the drive type code you specify. You can check information about the drives for which the spare drive setting is released by running the API request for getting drive information.

Response message
Status codes

See HTTP status codes.

Coding example

curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X POST --data-binary @./InputParameters.json https://192.0.2.100/ConfigurationManager/simple/v1/objects/drives/actions/release-spare/invoke

raidcom get drive

Supported storage systems:

  • VSP 5000 series
  • VSP G130, G/F350, G/F370, G/F700, G/F900

Displays drive information.

Syntax
raidcom get drive [-parity_grp_id <gno-sgno> | -usage <usage>]
Options and parameters
  • -parity_grp_id <gno-sgno>

    Specifies the parity group number (gno: 1 to 52, sgno: 1 to 32)

    Example:

    3-1

  • -usage <usage>

    Specifies the drive usage.

    Specify the following character strings for <usage>:

    • data: Data drive
    • spare: Spare drive
    • free: Unused drive
Example

Displaying drive information.

#raidcom get drive
LOCATION	TYPE	RPM	TOTAL_CAP(GB)	CODE		USAGE	STS	GROUP
1-1		SAS	15000		300	DKS5C-K300SS	DATA	NML	1-1
Description of the raidcom get drive output:
  • LOCATION

    Displays the location of the drive in the xx-yy format. In Device Manager - Storage Navigator, the drive location is displayed in the HDDxx-yy format.

  • TYPE

    Displays the drive type.

  • RPM

    Displays the number of revolutions of a drive in rpm. For SSD, a hyphen (-) is displayed.

  • TOTAL_CAP(GB)

    Displays the capacity of a drive in gigabytes.

  • CODE

    Displays the drive type code.

  • USAGE

    Displays the drive usage.

    • DATA: Data drive
    • SPARE: Spare drive
    • FREE: Unused drive
  • STS

    Displays the drive status.

    • NML: Normal.
    • WAR: A blocked part exists.
    • CPY: Drive copy is in process.
    • CPI: Copy is incomplete.
    • RSV: Spare disk is unusable.
    • FAI: Blocked due to a failure.
    • BLK: Blocked due to maintenance.
    • UNK: The status is unknown.
  • GROUP

    Displays the parity group number of the drive if it is contained in a parity group. If the drive is not contained in a parity group, a hyphen (-) is displayed.

raidcom modify drive

Supported storage systems:

  • VSP G130, G/F350, G/F370, G/F700, G/F900

Configures spare drives or cancels the settings.

This command is executed asynchronously with the command input. Use the raidcom get command_status command to check if the command is completed.

Syntax
raidcom modify drive -drive_location <drive location> -spare {enable|disable}
Options and parameters
  • -drive_location <drive location>

    Specifies the drive location.

    Example:

    When the drive location is HDD00-01:

    0-1

  • -spare {enable|disable}

    Sets a spare drive or cancels the setting.

    • enable: Sets a drive as a spare drive.
    • disable: Cancels the spare drive setting.
Example

Setting a drive whose drive location is HDD00-01 as a spare drive.

# raidcom modify drive -drive_location 0-1 -spare enable

raidcom add dp_pool

Create a pool for Dynamic Provisioning or Dynamic Provisioning for Mainframe by the specified resource. Or, add pool volumes to the pools for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, Dynamic Tiering for Mainframe, active flash, or active flash for mainframe. A parity group, an LDEV, and a device group can be specified as a resource.

TipFor VSP G130, G/F350, G/F370, G/F700, G/F900, specifying a parity group is recommended. When a parity group is specified, an LDEV is created and a pool volume is added. It is not necessary to create an LDEV in advance. In addition, you cannot add an existing LDEV as a pool volume.

When specifying a pool that is already created for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, Dynamic Tiering for Mainframe, active flash, or active flash for mainframe, the specified LDEV is added as a pool volume.

Specify either one of Pool ID or Pool Name certainly. If both the Pool ID and Pool Name options are omitted, this command is rejected with EX_REQARG.

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

Syntax
raidcom add dp_pool {-pool_id <pool ID#> | -pool_name <pool 
    naming> | -pool_id <pool ID#> 
    -pool_name <pool naming>} 
   {-parity_grp_id <gnosgno> [-resource_id <resource group id >]
   | -ldev_id <ldev#> …[-cnt <count>] | -grp_opt <group option> 
   -device_grp_name <device group name> [<device name>]}
   [ -user_threshold <threshold_1>[<threshold_2>] ]
   [-suspend_tipair {yes | no}] 
   [-auto_add_poolvol {enable|disable}]
Options and parameters
  • -pool_id <pool ID#>

    Specifies the Pool ID (0-127) for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, Dynamic Tiering for Mainframe, active flash, or active flash for mainframe. When the specification of Pool ID is omitted, a Pool Name must be specified.

    If a -pool_id option is non-numeric, the specified value is recognized as a pool name to identify the pool ID.

    When you omit specifying -pool_id option, you need to specify -pool_name option.

    When specifying the -pool_name option without a -pool_id option, the specified pool is searched first. If the pool exists, the pool volume is added to the corresponding pool. If the pool does not exist, a new pool is created and is assigned a pool ID. However, if the pool does not exist and multiple commands without the -pool_id option are executed simultaneously, the same pool ID might be assigned to multiple newly created pools.

    To avoid this behavior, use the raidcom lock resource command in advance to lock all resource groups. If all the resource groups are locked, commands executed by other users cannot take out unused pool IDs from all the resource groups. If you create multiple pools, execute the next raidcom add snap_pool command after the execution of the current raidcom add snap_pool command is complete.

    After the execution of all the raidcom add snap_pool commands are complete, use the raidcom unlock resource command to unlock all the resource groups.

  • -pool_name <pool naming>

    Specifies a pool name of a pool for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, Dynamic Tiering for Mainframe, active flash, or active flash for mainframe. Up to 32 characters can be specified.

    When specifying a pool ID or a pool name, if the pool name exists in the specified pool ID, the pool name is overwritten. If the pool volume is added by specifying only a pool ID for already existing pool, the pool name is not changed. When the specification of Pool Name is omitted, a Pool ID must be specified. When the Pool ID is specified and the Pool Name and -device_grp_name option are omitted, a pool name is allocated automatically in the form of "New Pool<number>".

    The -pool_name option cannot be specified by configuring only in numeric because numeric values are preferentially identified as a pool ID. Specifies a pool ID with the '-pool_id<pool ID#>' option.

  • -parity_grp_id <gno-sgno> [-resource_id <resource group id >]

    Supported storage systems:

    • VSP G130, G/F350, G/F370, G/F700, G/F900

    Specifies the parity group number (gno: 1 to 52, sgno: 1 to 32).

    For example: 3-1

    When -resource_id <resource grp id> is specified, select the LDEV which is not installed in the specified resource group and has the largest LDEV number to create a pool volume. This option is valid only when a pool is created. If you omit this option, the smallest ID of a resource group for which the user has operation permissions is set.

  • -ldev_id <ldev#> …

    Specifies the LDEV number (0 to 65279). Up to 64 of LDEVs can be specified at a time. For example:

    • -ldev_id 100
    • -ldev_id 100 - 110
    • -ldev_id 100 -cnt 10
  • [-cnt <count> ]

    Specifies the count (2 to 64).

    If this specificaion is omitted, "1" is used.

    Up to 64 of LDEVs can be specified at a time.

  • -grp_opt <group option>

    Specifies the device information extracted from the LDEV belonging to the device group. Specify "ldev" (fixed). The information of LDEV belonging to the device group is used.

  • -device_grp_name <device group name> [<device name>]

    Specifies the name of device group (maximum 32 characters) to be operated.

    To operate an LDEV in the device group, specify the device name of LDEV (maximum 32 characters) within the device group.

    If the device name is omitted, all the LDEVs belonging in the device group are operated.

    When the -pool_name option is omitted, the device group name changes into the pool name.

  • [-user_threshold <threshold_1> [<threshold_2>] ]

    You may specify two user-defined thresholds, and their valid ranges are 1-100%, respectively. If you specify <threshold_1> and <threshold_2>:

    the value of <threshold_1> is set as the threshold for WARNING specified to a pool.

    the value of <threshold_2> is set as the threshold for High water mark specified to a pool.

    If you specify only <threshold_1>, your specified value and the system default value (80%) are applied. If you omit to specify the value, 70% and 80% are applied, automatically.

    When you add a pool volume, this option is ignored even if it is specified. If you want to change the user defined threshold value of the additional pool volume, execute the raidcom modify pool command.

  • [-suspend_tipair {yes | no}]

    Specifies whether to suspend Thin Image pairs when the threshold for high water mark is exceeded. This option is valid only for creating pairs.

    • yes: Thin Image pairs are suspended.
    • no: Thin Image pairs are not suspended.

    If this option is omitted , "yes" is set.

  • [-auto_add_poolvol {enable|disable}]

    Specifies whether to automatically add pool volumes for which accelerated compression is enabled. This option is valid only for creating pools. This option can be specified for VSP G1x00 or VSP F1500.

    • enable: Automatically adds pool volumes for which accelerated compression is enabled according to the compression ratio of a parity group for which accelerated compression is enabled.
    • disable: The pool volumes for which accelerated compression is enabled are not added automatically.

    When these options are not specified, the default values will be applied as follows:

    • enable: When the storage system is VSP G/F350, G/F370, G/F700, G/F900.
    • disable: When the storage system is VSP G1x00 or VSP F1500.
Examples

By using LDEVs:400, 401, and 402, creating a pool of Pool ID:1, Pool Name: my_pool for Dynamic Provisioning/Dynamic Provisioning for Mainframe.

# raidcom add dp_pool -pool_id 1 -pool_name my_pool -ldev_id 400 401 402

By using LDEVs:500, 501, and 502, creating a pool of Pool ID: Allocated automatically, Pool Name: my_pool for Dynamic Provisioning/Dynamic Provisioning for Mainframe.

# raidcom add dp_pool -pool_name my_pool -ldev_id 500 501 502

By using LDEVs:600, 601, and 602, creating a pool of Pool ID: 2, Pool Name: Allocated automatically for Dynamic Provisioning/Dynamic Provisioning for Mainframe.

# raidcom add dp_pool -pool_id 2 -ldev_id 600 601 602

By using LDEVs: 700, 701, and 702, creating a pool of Pool ID: 3, Pool Name: my_pool for Dynamic Provisioning, Dynamic Provisioning for Mainframe, with the user-defined thresholds WARNING specified to 70% and High water mark to 80%.

# raidcom add dp_pool -pool_id 3 -pool_name my_pool 
-ldev_id 700 701 702 -user_threshold 70 80

Add LDEV: 368 to the pool ID: 10 for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, Dynamic Tiering for Mainframe, active flash, or active flash for mainframe.

# raidcom add dp_pool -pool_id 10 -ldev_id 368

By using LDEV belonging to the device group: grp1, creating a pool of Pool ID:1, pool name: Allocated automatically for Dynamic Provisioning/Dynamic Provisioning for Mainframe.

# raidcom add dp_pool -pool_id 1 -grp_opt ldev -device_grp_name grp1

By using LDEVs: 800, 801, and 802, creating a pool of Pool ID: 4, Pool Name: my_pool for Dynamic Provisioning, with the user-defined thresholds WARNING specified to 70% and High water mark to 80%, and Thin Image pairs are suspended when the high water mark threshold is exceeded.

# raidcom add dp_pool -pool_id 4 -pool_name my_pool -ldev_id 800 801 802 -user_threshold 70 80 -suspend_tipair yes

Using an LDEV ID of resource group ID: 0, creating an LDEV for parity group: 1-1, and then creating a pool of Pool ID: 1, Pool Name: Allocated automatically for Dynamic Provisioning or Dynamic Provisioning for Mainframe.

# raidcom add dp_pool -pool_id 1 -parity_grp_id 1-1 -resource_id 0

Using LDEVs: 500, 501, and 502, creating a pool of Pool ID: Allocated automatically and Pool Name: my_pool for Dynamic Provisioning for which automatic addition settings of pool volumes whose accelerated compression is enabled: enabled.

# raidcom add dp_pool -pool_name my_pool -ldev_id 500 501 502 -auto_add_poolvol enable

raidcom add snap_pool

Creates pools and adds pool VOLs for Thin Image and Copy-on-Write Snapshot by the specified resource.

When specifying a pool that is already created for Thin Image or Copy-on-Write Snapshot, the specified resource is added as a pool volume. A parity group, an LDEV, and a device group can be specified as a resource.

TipFor VSP 5000 series, VSP G/F350, G/F370, G/F700, G/F900, specifying a parity group is recommended. When a parity group is specified, an LDEV is created and a pool volume is added. It is not necessary to create an LDEV in advance. In addition, you cannot add an existing LDEV as a pool volume.

Specify either one of Pool ID or Pool Name certainly. If both the Pool ID and Pool Name options are omitted, this command is rejected with EX_REQARG.

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

Syntax
raidcom add snap_pool {-pool_id <pool ID#> | -pool_name <pool 
    naming> | -pool_id <pool ID#> 
    -pool_name <pool naming>} 
     {-parity_grp_id <gno-sgno> [-resource_id <resource group_id >] |
    -ldev_id <ldev#> …[-cnt<count>] | -grp_opt <group option> 
     -device_grp_name <device group name> [<device name>]}
     [-user_threshold <%> ][-thinsnap][-auto_add_poolvol {enable|disable}]
Options and parameters
  • -pool_id <pool ID#>

    Specifies the Pool ID (0-127) of a Thin Image or Copy-on-Write Snapshot pool.

    If a -pool_id option is non-numeric, the specified value is recognized as a pool name to identify the pool ID.

    When you omit specifying the -pool_id option, you need to specify -pool_name option.

    When specifying the -pool_name option without a -pool_id option, the specified pool is searched first. If the pool exists, the pool volume is added to the corresponding pool. If the pool does not exist, a new pool is created and is assigned a pool ID. However, if the pool does not exist and multiple commands without the -pool_id option are executed simultaneously, the same pool ID might be assigned to multiple newly created pools.

    To avoid this behavior, use the raidcom lock resource command in advance to lock all resource groups. If all the resource groups are locked, commands executed by other users cannot take out unused pool IDs from all the resource groups. If you create multiple pools, execute the next raidcom add snap_pool command after the execution of the current raidcom add snap_pool command is complete.

    After the execution of all the raidcom add snap_pool commands are complete, use the raidcom unlock resource command to unlock all the resource groups.

  • -pool_name <pool naming>

    Specifies the pool name of a pool for Thin Image or Copy-on-Write Snapshot. Up to 32 characters can be specified.

    When specifying a pool ID or a pool name, if a pool name exists in the specified pool ID, the pool name is overwritten. If the pool volume is added by specifying only a pool ID, the pool name is not changed. When the specification of Pool Name is omitted, a Pool ID must be specified. When the Pool ID is specified and the Pool Name is omitted, a pool name is allocated automatically in the form of "New Pool<number>".

    The -pool_name option cannot be specified by configuring only in numeric because numeric values are preferentially identified as a pool ID. Specifies a pool ID with the -pool_id<pool ID#> option.

  • -parity_grp_id <gno-sgno> [-resource_id <resource group_id >]

    Supported storage systems:

    • VSP G130, G/F350, G/F370, G/F700, G/F900

    Specifies the parity group number (gno: 1 to 52, sgno: 1 to 32).

    For example: 3-1

    When -resource_id <resource grp id> is specified, select the LDEV that is not installed in the specified resource group and has the largest LDEV number to create a pool volume. This option is valid only when a pool is created. If you omit this option, the smallest ID of a resource group for which the user has operation permissions is set.

  • -ldev_id <ldev#>

    Specifies the LDEV number (0 to 65279). Up to 64 of LDEVs can be specified at a time. For example:

    • -ldev_id 100
    • -ldev_id 100-110
    • -ldev_id 100 -cnt 10
  • [-cnt <count> ]

    Specifies the count (2 to 64).

    The count becomes singular if not specified.

    Up to 64 of LDEVs can be specified at a time.

  • -grp_opt <group option>

    Specifies the device information extracted from the LDEV belonging to the device group. Specify "ldev" (fixed). The information of LDEV belonging to the device group is used.

  • -device_grp_name <device group name> [<device name>]

    Specifies the name of device group (maximum 32 characters) to be operated.

    To operate an LDEV in the device group, specify the device name of LDEV (maximum 32 characters) within the device group.

    If the device name is omitted, all the LDEVs belonging to the device group are operated.

    When the -pool_name option is omitted, the device group name changes into the pool name.

  • [-user_threshold <%> ]

    Specifies the user defined threshold value (20 to 95) (%).

    If this option is omitted, "80" is used.

    When you add a pool volume, this option is ignored even if it is specified. If you want to change the user defined threshold value of the additional pool volume, execute the raidcom modify pool command.

  • [-thinsnap]

    When this option is specified, a pool for Thin Image is created.

  • [-auto_add_poolvol {enable|disable}]

    Specifies whether to automatically add pool volumes for which accelerated compression is enabled. This option is valid only for creating pools. This option can be specified for VSP G1x00 or VSP F1500.

    • enable: Automatically adds pool volumes for which accelerated compression is enabled according to the compression ratio of a parity group for which accelerated compression is enabled.
    • disable: The pool volumes for which accelerated compression is enabled are not added automatically.

    When these options are not specified, the default values will be applied as follows:

    • enable: When the storage system is VSP G/F350, G/F370, G/F700, G/F900.
    • disable: When the storage system is VSP G1x00 or VSP F1500.
Examples

Using LDEVs:400, 401, and 402, creating a pool of Pool ID:1, Pool Name: my_ss_pool for Copy-on-Write Snapshot.

# raidcom add snap_pool -pool_id 1 -pool_name my_ss_pool -ldev_id 400 401 402

Using LDEVs:410, 411, and 412, creating a pool of Pool ID:3, Pool Name: my_ss_pool for Thin Image.

# raidcom add snap_pool -pool_id 3 -pool_name my_ss_pool -ldev_id 410 411 412 -thinsnap

Using LDEVs:500, 501, and 502, creating a pool of Pool ID: Allocated automatically, Pool Name: my_ss_pool for Copy-on-Write Snapshot.

# raidcom add snap_pool -pool_name my_ss_pool -ldev_id 500 501 502

Using LDEVs:600, 601, and 602, creating a pool of Pool ID: 2, Pool Name: Allocated automatically for Copy-on-Write Snapshot.

# raidcom add snap_pool -pool_id 2 -ldev_id 600 601 602

Using LDEV belonging to the device group: grp1, creating a pool of Pool ID: 1, Pool Name: Allocated automatically for Copy-on-Write Snapshot.

# raidcom add snap_pool -pool_id 1 -grp_opt ldev -device_grp_name grp1

Using an LDEV ID of resource group ID: 0, creating an LDEV for parity group: 1-1, and then creating a pool of Pool ID: 1, Pool Name: Allocated automatically for Thin Image.

# raidcom add snap_pool -pool_id 1 -parity_grp_id 1-1 -resource_id 0 -thinsnap

Using LDEVs: 410, 411, and 412, creating a pool of Pool ID: 3 and Pool Name: my_ss_pool for Thin Image for which automatic addition settings of pool volumes whose accelerated compression is enabled: enable.

# raidcom add snap_pool -pool_id 3 -pool_name my_ss_pool -ldev_id 410 411
412 -thinsnap -auto_add_poolvol enable

raidcom add ldev

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.

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#> | -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#>]
   [-status {enable_fullallocation | disable_fullallocation}] 
   [-t10pi_enable]
   [-capacity_saving {compression | deduplication_compression} 
   [-capacity_saving_mode <saving_mode>] | 
   -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#>

    Specifies the LDEV number (0-65279).

    If you specify the -tse_ldev_id option, the volume is the same as the volume used by FlashCopy SE. When using -tse_ldev_id option, you must create the virtual volumes in Dynamic Provisioning for Mainframe. For example:

    • -ldev_id 200
    • -tse_ldev_id 400
  • -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:

    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>

    Supported storage systems:

    • VSP G1x00 and VSP F1500
    • VSP G/F350, G/F370, G/F700, G/F900

    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.

  • [-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.
  • [-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.

Examples

Creating an LDEV: 100 of size 10 GB 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, 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: 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
CautionIf an LDEV larger than 4 TB is specified, the following message is shown:

raidcom : Please check if LDEV over 4 TB will be used for replication products, and then check the supported capacity.