Managing volumes
You can get information about volumes, get detailed information about specific volumes, or change volume settings.
- raidcom add ldev
- raidcom modify ldev
- raidcom delete ldev
- raidcom extend ldev
- raidcom get ldev
To manage external storage resources, use Ops Center Administrator.
Modifying a volume name
You can modify the volume name.
In the dashboard or in the navigation bar, click Volumes.
Click (Edit Volumes) of the volume you want to modify.
Modify the name and click Submit.
Modifying the capacity saving setting for volumes
You can modify the capacity saving setting (deduplication and compression) for volumes.
Capacity saving is significantly effective in reducing the amount of data stored if high data reduction ratio is already observed for other volumes used for similar operations. Enable capacity saving to reduce the amount of data stored on volumes for which the feature is expected to be as effective as it is for other volumes. Disable the feature for volumes where the function is not effectively reducing the amount of data being stored. If you change the capacity saving settings while it is enabled, rehydrating data might take some time.
The capacity saving function for VSP E1090 and VSP E1090H storage systems includes a compression accelerator. For details about the capacity saving function that uses compression acceleration, see the Provisioning Guide. We recommend using compression acceleration because it allows you to reduce the load that data compression places on the storage system. Note that changing the capacity savings compression method when using compression acceleration means that the new method is applied to all volume data and the processing takes some time.
Before you begin
- Identify the server name.
- Identify the volume name.
- If the planned changes can impact the free space on the pool, check the current amount of free space.
Procedure
In the dashboard or in the navigation bar, click Servers. If you are not using Storage Advisor Embedded to manage servers, click Volumes in the dashboard or in the navigation bar, and then skip to step 3.
Click the server name to open the server details page.
Select one or more volumes and click (Edit Volumes).
Modify the capacity saving setting.
Click the volume name to open the details page, and then confirm that the settings are specified correctly.
Checking the operating status of volumes
You can check whether any irregularities occur during your daily operations. For example, you can check for any volumes for which no I/O is issued or for volumes for which more I/O than usual is issued. You can also check the operating status of volumes when you receive an inquiry from a server administrator.
If QoS settings are enabled for volumes, you can check QoS-related status as well as configure and clear QoS settings.
Checking the operating status of volumes in the performance graphs
You can display and check the operating status of each volume with respect to IOPS, response time (time required to respond to a server request), and transfer rate. You can also download the content of each performance graph as a CSV file.
In Windows Server, to export the content of performance graphs to a CSV file by using Internet Explorer, first disable Internet Explorer Enhanced Security Configuration.
Procedure
In the dashboard or in the navigation bar, click Servers. If you are not using Storage Advisor Embedded to manage servers, click Volumes in the dashboard or in the navigation bar, and then skip to step 3.
Click the server name to open the server details page.
Click the volume name to open the volume details page.
If the QoS settings are enabled for volumes, the items displayed in the volume details window and the Performance Monitor tab differ from those in normal times.
On the Performance Monitor, check the operating status based on the graphs of IOPS, response time, and transfer rate.
The volume details window includes the following information.
-
Volume overview
-
QoS settings information
QoS information appears only when QoS settings are enabled.
The occurrence time displayed in the QOS ALERT TIME tab is the time that the last alert was issued.
NoteIf you use the web-based user interface, the date and time when an alert was issued is displayed based on the time zone set for the management client system. If you use the REST API, the data and time are based on Coordinated Universal Time (UTC).
If you change the time zone of the storage system, the times displayed for alerts that were issued before the change are invalid.
-
Activity status performance graph
When QoS settings for volumes enabled, the items displayed in the performance status graph are different from those normally displayed.
The information displayed when QoS settings are enabled are as follows.
Performance Monitor tab (IOPS)
Displayed item
Description
Received
Number of commands requested from the server
Completed
Number of commands processed by the storage system
Upper Limit
Value specified for IOPS UPPER LIMIT
Lower Limit
Value specified for IOPS LOWER LIMIT
Performance Monitor tab (Response Time)
Displayed item
Description
Actual Time
Time required to respond to a request from the server
Target Time
Value specified for TARGET RESPONSE TIME
Performance Monitor tab (Transfer Rate)
Displayed item
Description
Received
Data transfer speed for commands requested from the server
Completed
Actual data transfer speed with which the storage system processed the commands
Upper Limit
Value specified for TRANSFER RATE UPPER LIMIT
Lower Limit
Value specified for TRANSFER RATE LOWER LIMIT
Caution-
I/O information between the server and the storage system is monitored, but I/O information between storage systems is not monitored.
-
The times displayed in performance graphs are the times when data was measured by the storage system, instead of the standard displayed times (times when data was acquired by the client).
-
NotePerformance reports might not show the current information if performance data is not obtained from the storage system. This issue should resolve itself after some time when the storage system is less busy.
-
Editing QoS settings of volumes
You can edit QoS settings for a volume.
Before you begin
Check the following information:
- Server name
- Volume name
Procedure
In the navigation bar or on the dashboard, click Servers.
Click the server name to open the server details page.
Click the volume name to open the volume details page.
Click of the volume for which you want to edit the QoS setting and update the settings as needed.
For the amount of allowable time before alert, specify the amount of time to wait for the following:
- IOPS OR TRANSFER RATE EXCEEDING UPPER LIMIT
- IOPS OR TRANSFER RATE NOT REACHING LOWER LIMIT
- RESPONSE TIME NOT ACHIEVING TARGET SETTING
Click the volume name to display the details window, and verify that the settings are correct.
Clearing the QoS settings of volumes
You can clear the QoS settings of volumes.
Before you begin
Check the following information:
- Server name
- Volume name
Procedure
In the navigation bar or on the dashboard, click Servers.
Click the server name to open the server details page.
Click the volume name to open the volume details page.
Click of the volume for which you want to clear the QoS settings.
Disable all QoS settings.
When you Disable the QoS settings the QoS settings for the applicable volume are cleared and any previously set values are deleted.
Deleting volumes
You can delete volumes that are no longer needed. Data in the volumes is also deleted. You cannot delete volumes that are attached to servers.
Before you begin
- Ensure that there is no snapshot created for the volume.
- Ensure that neither Snapshot nor Attached Unmanaged is displayed for the volume type.
Volumes for which Attached Unmanaged is displayed for the volume type are volumes that were attached by using management software other than Storage Advisor Embedded.
Procedure
In the dashboard or in the navigation bar, click Volumes.
Select one or more volumes and click (Delete Volumes) .
Volume management
You can use the REST API to obtain volume information, create new volumes, and increase the capacity of volumes that have high usage rates.
Getting volume information
The following request obtains volume information. You can also specify filter conditions.
Storage Administrator (View Only)
GET base-URL/simple/v1/objects/volumes
Object ID
None.
Query parameters
With each request, you can obtain information about a maximum of 500 volumes. To obtain information about additional volumes, execute the API request multiple times by using a combination of the count and startVolumeId parameters. By specifying the count parameter, you can also filter the volume information you require.
Parameter
Type
Filter Condition
poolId
int
(Optional) ID of the pool to which the volumes belong
If poolName is specified, do not specify this parameter.
poolName
string
(Optional) Name of the pool to which the volumes belong
Volume information will also be obtained if part of the specified value matches the pool name.
If poolId is specified, do not specify this parameter. If both poolId and this parameter are specified, this parameter is ignored.
serverId
int
Only applicable if the server provisioning option is enabled.
(Optional) ID of the server to which the volumes have been attached
If serverNickName is specified, do not specify this parameter.
serverNickName
string
Only applicable if the server provisioning option is enabled.
(Optional) Nickname of the server to which the volumes have been attached
Volume information will also be obtained if part of the specified value matches the nickname of a server.
If serverId is specified, do not specify this parameter. If both serverId and this parameter are specified, this parameter is ignored.
nickname
string
(Optional) Nickname of the volumes
Volume information will also be obtained if part of the specified value matches the nickname of the volume.
minTotalCapacity
long
(Optional) Minimum capacity of the volumes (MiB)
Specify the minimum capacity of the volumes for which you want to obtain information as an integer in the range from 47 through 268435456.
maxTotalCapacity
long
(Optional) Maximum capacity of the volumes (MiB)
Specify the maximum capacity of the volumes for which you want to obtain information as an integer in the range from 47 through 268435456.
minUsedCapacity
long
(Optional) Minimum usage capacity of the volumes (MiB)
Specify the minimum usage capacity of the volumes for which you want to obtain information as an integer in the range from 0 through 268435456.
maxUsedCapacity
long
(Optional) Maximum usage capacity of the volumes (MiB)
Specify the maximum usage capacity of the volumes for which you want to obtain information an integer in the range from 0 through 268435456.
startVolumeId
int
(Optional) Specify the ID of the volume for which you want to start acquiring information, by using a value in the range from 0 through 65279.
count
int
(Optional) Specify the number of volumes for which information is to be obtained, by using a value in the range from 1 through 500.
If this parameter is omitted, 500 is considered.
Body
None.
Body
The following is an example of output of obtained information for a volume that belongs to the pool with ID 63 (63 is specified in the poolId query parameter):
{ "data": [ { "id": 100, "nickname": "JH-26216_DP", "poolId": 63, "poolName": "NASOS", "totalCapacity": 1024, "usedCapacity": 42, "numberOfConnectingServers": 2, "numberOfSnapshots": 2, "volumeTypes": [] }, { "id": 101, "nickname": "JH-26216_DP", "poolId": 63, "poolName": "NASOS", "totalCapacity": 1024, "usedCapacity": 0, "numberOfConnectingServers": 2, "numberOfSnapshots": 2, "volumeTypes": [ "Snapshot" ] } ], "count": 2, "totalCount": 2, "hasNext": false }
Attribute
Type
Description
id
int
Volume ID
nickname
string
Nickname
poolId
int
ID of the pool to which the volume belongs
poolName
string
Name of the pool to which the volume belongs
This attribute do not appear when the volume is being created or deleted.
totalCapacity
long
Total capacity of the volume (MiB)
usedCapacity
long
Used capacity of the volume (MiB)
0 appears when the volume is being created or deleted.
numberOfConnectingServers
int
numberOfSnapshots
int
Number of snapshots
volumeTypes
object[]
Volume Types
- Snapshot: Volumes that are created from snapshots and for which volume IDs are defined.
- System: Volumes used for deduplication system data volumes or journal volumes.
- Command Device: Volumes used as command devices.
- SLU: Volumes with the SLU (Subsidiary Logical Unit) attribute.
- AttachedUnmanaged: Volumes are attached using other management tools.
See HTTP status codes.
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/volumes?poolId=63
Getting information about a specific volume
The following request gets information about the volume for the specified volume ID.
Storage Administrator (View Only)
GET base-URL/simple/v1/objects/volumes/object-ID
Object ID
Specify the id value obtained by getting information about volumes.
Attribute
Type
Description
id
int
(Required) Volume ID
Query parameters
None.
Body
None.
Body
The following is an example of getting information about a volume with ID 100:
{ "id": 100, "nickname": "JH-26216_DP", "poolId": 63, "poolName": "pool-1", "totalCapacity": 1024, "usedCapacity": 42, "freeCapacity": 982, "reservedCapacity": 0, "savingSetting": "COMPRESSION", "compressionAcceleration": true, "compressionAccelerationStatus": "ENABLED", "capacitySavingStatus": "Enabled", "numberOfConnectingServers": 2, "numberOfSnapshots": 0, "luns": [ { "lun": 1, "serverId": 10, "portId": "CL1-A" }, { "lun": 1, "serverId": 11, "portId": "CL2-A" } ], "volumeTypes": [] }
The obtained attributes include the following attributes, in addition to the attributes obtained when volume information is obtained:
Attribute
Type
Description
freeCapacity
long
Free space in the volume (MiB)
The total capacity of the volume appears when the volume is being created or deleted.
reservedCapacity
long
Capacity of the reserved pages in the volume (MiB)
savingSetting
string
Whether capacity saving (deduplication and compression) is enabled:
- DEDUPLICATION_AND_COMPRESSION: Deduplication and compression is enabled.
- COMPRESSION: Compression is enabled.
- DISABLE: No settings are specified.
compressionAcceleration
boolean
Whether using compression acceleration with the capacity saving function is enabled
- true: Enabled
- false: Disabled
This attribute appears if the storage system is a VSP E series storage system and capacity saving is enabled for the volume.
compressionAccelerationStatus
string
Whether using compression acceleration with the capacity saving function is enabled for data in the volume
- DISABLED: Capacity saving with compression acceleration is disabled.
- ENABLED: Capacity saving with compression acceleration is enabled.
- HYBRID: Volume contains both data for which capacity saving with compression acceleration is enabled and data for which capacity saving with compression acceleration is disabled.
This attribute appears if the storage system is a VSP E series storage system and the volume is a volume for which capacity saving is enabled or a deduplication system data volume (datastore).
capacitySavingStatus
string
Setting of the capacity saving (deduplication and compression)
- Disabled: Capacity saving is disabled.
- Enabled: Capacity saving is enabled.
- Rehydrating: Capacity saving is being disabled.
- Enabling: Capacity saving is being enabled.
- Deleting: Volumes for which the capacity saving is enabled are being deleted.
- Converting: Method of compression for capacity saving is being changed.
- Failed: Data on the deduplication system data volumes is invalid.
capacitySavingProgress
int
Progress rate of the capacity saving (deduplication and compression) (%)
luns
object[]
Array of LUN configuration information:
- lun (int):
LU number
- serverId
(int):
Server ID
- portId
(string):
ID of the port to which the LUN is assigned
When volumeTypes is Namespace, this attribute does not appear.
See HTTP status codes.
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/volumes/100
Changing the volume settings
The following request changes the nickname and capacity saving setting for the specified volume.
Storage Administrator (Provisioning)
PATCH base-URL/simple/v1/objects/volumes/object-ID
Object ID
Specify the id value obtained by getting information about volumes.
Attribute
Type
Description
id
int
(Required) Volume ID
Query parameters
None.
Body
Only the specified attributes are changed.
The following is an example of changing the nickname of a volume:
{ "nickname": "REST_API_10GVolume" }
The following is an example of disabling the value set for the capacity saving (deduplication and compression) of a volume:
{ "savingSetting": "DISABLE" }
Attribute
Type
Description
nickname
string
(Optional) Specify a new nickname 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:
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.
You cannot use a hyphen (-) at the beginning of the name.
If you specify this attribute, do not specify savingSetting.
savingSetting
string
(Optional) Settings for the capacity saving (deduplication and compression)
- DEDUPLICATION_AND_COMPRESSION:
Deduplication and
compression is enabled.
Compression is enabled when you enable deduplication.
- COMPRESSION: The capacity saving (compression) is enabled.
- DISABLE: No settings are specified.
If you specify this attribute, it might take time to complete.
If you specify this attribute, do not specify nickname.
compressionAcceleration
boolean
(Optional) Settings for the capacity saving function with compression acceleration
- true: Enabled
- false: Disabled
You can specify this attribute for VSP E1090 and VSP E1090H storage systems only.
If this attribute is omitted, when the value of the savingSetting attribute is changed from DISABLE to a different value, the storage system automatically sets a value for this attribute.
- If the capacity saving function with compression acceleration can be used: true
- If the capacity saving function with compression acceleration cannot be used: false
If DISABLE is specified for the savingSetting attribute, the value of this parameter is ignored.
If you specify this attribute, do not specify nickname.
- DEDUPLICATION_AND_COMPRESSION:
Deduplication and
compression is enabled.
Body
- If you changed the volume nickname:
Attribute
Type
Description
affectedResources
string[]
List of URLs for referencing information about the changed volume
operationDetails
object[]
Details about the changed volume
For details, see the description of the operationDetails attribute of the commandStatus object.
- If you changed the settings for the
capacity saving (deduplication and compression):
Attribute
Type
Description
statusResource
string
URL for referencing information about the changed volume
NoteExecute the API function for obtaining information about the status of the API function that performs asynchronous processing. For details, see Getting status information about an API function that performs asynchronous processing.
- If you changed the volume nickname:
See HTTP status codes.
curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X PATCH --data-binary @./InputParameters.json https://192.0.2.100/ConfigurationManager/simple/v1/objects/volumes/100
Getting information about the QoS settings of a specific volume
The following request gets information about the QoS settings of the volume for which the volume ID is specified.
Storage Administrator (View Only)
GET base-URL/simple/v1/objects/volumes/object-ID/qos-setting
Object ID
Specify the id value obtained by getting information about volumes.
Attribute
Type
Description
id
int
(Required) Volume ID
Query parameters
None.
Body
None.
Body
The following is an example of getting information about the QoS settings of a volume with a volume ID of 100:
{ "volumeId": 100, "threshold": { "isUpperIopsEnabled": true, "upperIops": 2000, "isUpperTransferRateEnabled": true, "upperTransferRate": 20000, "isLowerIopsEnabled": true, "lowerIops": 1000, "isLowerTransferRateEnabled": true, "lowerTransferRate": 10000, "isResponsePriorityEnabled": false }, "alertSetting": { "isUpperAlertEnabled": true, "upperAlertAllowableTime": 10, "isLowerAlertEnabled": true, "lowerAlertAllowableTime": 20, "isResponseAlertEnabled": false }, "alertTime": {} }
Attribute
Type
Description
volumeId
int
Volume ID
threshold
object
Information about the QoS settings of the volume:
- isUpperIopsEnabled (boolean)
Whether the upper limit on the IOPS is enabled
- true: Enabled
- false: Disabled
- upperIops (int)
Upper limit on the IOPS
This attribute appears if true is set for isUpperIopsEnabled.
- isUpperTransferRateEnabled
(boolean)
Whether the upper limit on the amount of data that can be transferred is enabled
- true: Enabled
- false: Disabled
- upperTransferRate (int)
Upper limit on the amount of data that can be transferred (MiBps)
This attribute appears if true is set for isUpperTransferRateEnabled.
- isLowerIopsEnabled (boolean)
Whether the lower limit on the IOPS is enabled
- true: Enabled
- false: Disabled
- lowerIops (int)
Lower limit on the IOPS
This attribute appears if true is set for isLowerIopsEnabled.
- isLowerTransferRateEnabled
(boolean)
Whether the lower limit on the amount of data that can be transferred is enabled
- true: Enabled
- false: Disabled
- lowerTransferRate (int)
Lower limit on the amount of data that can be transferred (MiBps)
This attribute appears if true is set for isLowerTransferRateEnabled.
- isResponsePriorityEnabled (boolean)
Whether the priority level of the I/O processing is enabled
- true: Enabled
- false: Disabled
- responsePriority (string)
Priority level of the I/O processing
A larger value indicates a higher level of priority, and a smaller value indicates a lower level of priority.
This attribute appears if true is set for isResponsePriorityEnabled.
- targetResponseTime (int)
Target response time (msec)
This attribute appears if true is set for isResponsePriorityEnabled.
alertSetting
object
Information about the alert settings of the volume:
- isUpperAlertEnabled (boolean)
Whether alerts are output if the IOPS or the amount of data transferred not achieve the upper limit for a continuous period of time
- true: Output
- false: Not output
- upperAlertAllowableTime (int)
Amount of time to wait before issuing an alert when an upper limit is exceeded for a continuous period of time (in seconds)
This attribute appears if true is set for isUpperAlertEnabled.
- isLowerAlertEnabled (boolean)
Whether alerts are output if the IOPS or the amount of data transferred falls below the lower limit for a continuous period of time
- true: Output
- false: Not output
- lowerAlertAllowableTime (int)
Amount of time to wait before issuing an alert when a lower limit is not met for a continuous period of time (in seconds)
This attribute appears if true is set for isLowerAlertEnabled.
- isResponseAlertEnabled (boolean)
Whether alerts are output if the average response time not achieve the target response time for a continuous period of time
- true: Output
- false: Not output
- responseAlertAllowableTime (int)
Amount of time to wait before issuing an alert when the average response time not achieve the target response time (in seconds)
This attribute appears if true is set for isResponseAlertEnabled.
alertTime
object
Information about the times# when alerts were issued for the volume appears.
- upperAlertTime (ISO8601string)
Time when the last alert was issued because the IOPS or the amount of data transferred per second had exceeded the upper limit for a continuous period of time (UTC)
This attribute does not appear if the setting to issue alerts is not configured or if no alerts have been issued.
- lowerAlertTime (ISO8601string)
Time when the last alert was issued because the IOPS or the amount of data transferred per second had fallen below the lower limit for a continuous period of time (UTC)
This attribute does not appear if the setting to issue alerts is not configured or if no alerts have been issued.
- responseAlertTime (ISO8601string)
Time when the last alert was issued because the average response time had exceeded the target response time for a continuous period of time (UTC)
This attribute does not appear if the setting to issue alerts is not configured or if no alerts have been issued.
#
If you change the time zone of the storage system, the times displayed for alerts that were issued before the change will be invalid.
- isUpperIopsEnabled (boolean)
See HTTP status codes.
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/volumes/100/qos-setting
Changing the QoS settings of a volume
The following request changes the QoS settings of the volume for which the volume ID is specified.
Storage Administrator (System Resource Management)
PATCH base-URL/simple/v1/objects/volumes/object-ID/qos-setting
Object ID
Specify the id value obtained by getting information about volumes.
Attribute
Type
Description
id
int
(Required) Volume ID
Query parameters
None.
Body
You cannot specify both the threshold attribute and the alertSetting attribute at the same time.
Only the specified attributes are changed.
The following is an example of an API request to change the QoS settings (the threshold attribute):
- isUpperIopsEnabled: true
- upperIops (upper limit on the IOPS): 2000
- isLowerIopsEnabled: true
- lowerIops (lower limit on the IOPS): 1000
- isResponsePriorityEnabled: true
- responsePriority (priority level of the I/O processing): 3 (High)
{ "threshold": { "isUpperIopsEnabled": true, "upperIops": 2000, "isLowerIopsEnabled": true, "lowerIops": 1000, "isResponsePriorityEnabled": true, "responsePriority": 3 } }
The following is an example of an API request to change the alert settings (the alertSetting attribute):
- isUpperAlertEnabled: true
- upperAlertAllowableTime (Amount of time to wait before issuing an alert): 10
- isLowerAlertEnabled: true
- lowerAlertAllowableTime (Amount of time to wait before issuing an alert): 20
- isResponseAlertEnabled: true
- responseAlertAllowableTime (Amount of time to wait before issuing an alert): 30
{ "alertSetting": { "isUpperAlertEnabled": true, "upperAlertAllowableTime": 10, "isLowerAlertEnabled": true, "lowerAlertAllowableTime": 20, "isResponseAlertEnabled": true, "responseAlertAllowableTime": 30 } }
Attribute
Type
Description
threshold
object
Information about the QoS settings of the volume
- isUpperIopsEnabled (boolean)
(Optional) Specify whether to enable the upper limit on the IOPS.
- true: Enabled
- false: Disabled
If you specify true for this attribute, you must also specify the upperIops attribute.
- upperIops (int)
(Optional) Specify the upper limit on the IOPS.
Specify an integer in the range from 100 to 2147483647.
If you specify this attribute, you must specify true for the isUpperIopsEnabled attribute.
- isUpperTransferRateEnabled
(boolean)
(Optional) Specify whether to enable the upper limit on the amount of data that can be transferred.
- true: Enabled
- false: Disabled
If you specify true for this attribute, you must also specify the upperTransferRate attribute.
- upperTransferRate (int)
(Optional) Specify the upper limit on the amount of data that can be transferred (in MiBps).
Specify an integer in the range from 1 to 2097151.
If you specify this attribute, you must specify true for the isUpperTransferRateEnabled attribute.
- isLowerIopsEnabled (boolean)
(Optional) Specify whether to enable the lower limit on the IOPS.
- true: Enabled
- false: Disabled
If you specify true for this attribute, you must also specify the lowerIops attribute.
- lowerIops (int)
(Optional) Specify the lower limit on the IOPS.
Specify an integer in the range from 10 to 2147483647.
If you specify this attribute, you must specify true for the isLowerIopsEnabled attribute.
-
isLowerTransferRateEnabled (boolean)
(Optional) Specify whether to enable the lower limit on the amount of data that can be transferred.
- true: Enabled
- false: Disabled
If you specify this attribute, you must specify true for the lowerTransferRate attribute.
- lowerTransferRate (int)
(Optional) Specify the lower limit on the amount of data that can be transferred (in MiBps).
Specify an integer in the range from 1 to 2097151.
If you specify this attribute, you must specify true for the isLowerTransferRateEnabled attribute.
- isResponsePriorityEnabled (boolean)
(Optional) Specify whether to enable the priority level of the I/O processing.
- true: Enabled
- false: Disabled
If you specify this attribute, you must specify true for the responsePriority attribute.
- responsePriority (int)
(Optional) Specify the priority level of the I/O processing.
Specify an integer in the range from 1 to 3.
A larger value indicates a higher level of priority.
If you specify this attribute, the target response time will be automatically set.
If you specify this attribute, you must specify true for the isResponsePriorityEnabled attribute.
alertSetting
object
Information about the alert settings of the volume
- isUpperAlertEnabled (boolean)
(Optional) Specify whether to issue an alert when the IOPS or the amount of data transferred not achieve the upper limit for a continuous period of time.
- true: Enabled
- false: Disabled
You can specify this attribute only if an upper limit on the IOPS or on the amount of data that can be transferred is set.
If you specify this attribute, you must specify true for the upperAlertAllowableTime attribute.
- upperAlertAllowableTime (int)
(Optional) Specify the amount of time to wait before issuing an alert when the IOPS or the amount of data transferred per second not achieve the upper limit for a continuous period of time (in seconds).
Specify an integer in the range from 1 to 600.
If you specify this attribute, you must specify true for the isUpperAlertEnabled attribute.
- isLowerAlertEnabled (boolean)
(Optional) Specify whether to issue an alert when the IOPS or the amount of data transferred falls below the lower limit for a continuous period of time.
- true: Enabled
- false: Disabled
You can specify this attribute only if a lower limit on the IOPS or on the amount of data that can be transferred is set.
If you specify this attribute, you must specify true for the lowerAlertAllowableTime attribute.
- lowerAlertAllowableTime (int)
(Optional) Specify the amount of time to wait before issuing an alert when the IOPS or the amount of data transferred per second falls below the lower limit for a continuous period of time (in seconds).
Specify an integer in the range from 1 to 600.
If you specify this attribute, you must specify true for the isLowerAlertEnabled attribute.
- isResponseAlertEnabled (boolean)
(Optional) Specify whether to issue an alert when the average response time not achieve the target response time for a continuous period of time.
- true: Enabled
- false: Disabled
You can specify this attribute only if a target average response time is set.
If you specify this attribute, you must specify true for the responseAlertAllowableTime attribute.
- responseAlertAllowableTime (int)
(Optional) Specify the amount of time to wait before issuing an alert when the response time not achieve the target response time (in seconds).
Specify an integer in the range from 1 to 600.
If you specify this attribute, you must specify true for the isResponseAlertEnabled attribute.
Body
Attribute
Type
Description
statusResource
string
URL for referencing information about the volume for which QoS settings were changed
NoteExecute the API function for obtaining information about the status of the API function that performs asynchronous processing. For details, see Getting status information about an API function that performs asynchronous processing.
curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X PATCH --data-binary @./InputParameters.json https://192.0.2.100/ConfigurationManager/simple/v1/objects/volumes/100
Deleting a volume
The following request deletes the volume corresponding to the specified volume ID.
The request to delete a volume for which the capacity saving (deduplication and compression) is enabled might take some time to complete. For this reason, we recommend that you plan when to delete such volumes.
Storage Administrator (Provisioning)
DELETE base-URL/simple/v1/objects/volumes/object-ID
Object ID
Specify the id value obtained by getting information about volumes.
Attribute
Type
Description
id
int
(Required) Volume ID
Query parameters
None.
Body
None.
Body
Attribute
Type
Description
statusResource
string
URL for referencing information about a volume that was deleted
NoteExecute the API function for obtaining information about the status of the API function that performs asynchronous processing. For details, see Getting status information about an API function that performs asynchronous processing.
See HTTP status codes.
curl -v -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization:Session b74777a3f9f04ea8bd8f09847fac48d3" -X DELETE https://192.0.2.100/ConfigurationManager/simple/v1/objects/volumes/100
raidcom get ldev
Displays the information of the specified LDEV or the device file. A device group can also be specified instead of an LDEV.
raidcom get ldev {-ldev_id <ldev#> … [-cnt <count>] | -grp_opt <group option> -device_grp_name <device group name> [<device name>] | -ldev_list <ldev list option>} [-key <keyword>][{-check_status | -check_status_not} <string>... [-time <time>]] [-time_zone <time zone>]
-ldev_id <ldev#> …
Specifies the LDEV number (0-65279). For example:
- -ldev_id 200
- -ldev_id 100-110
- -ldev_id 100 -cnt 10
[-cnt <count> ]
Specifies the count (2-65280).
If this option is omitted, the count is set to one.
-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.
-ldev_list <ldev list option>
Specifies the type of LDEVs to display. Specify one of the following LDEV list options. If the LDEV that meets the specified condition does not exist,
[EX_ENODEV] No such device
is displayed.- defined: Displays all implemented LDEVs.
- dp_volume: Displays LDEVs that have
Dynamic Provisioning attributes.
Combining this with -pool_id <pool id> specification displays LDEVs that have Dynamic Provisioning attributes related to the specified POOL.
- external_volume: Displays external volumes.
- undefined: Displays all LDEV numbers that are not implemented.
- mapped: Displays all LDEVs to which
LU paths are defined.
Combining this with -pool_id <pool id> specification displays LDEVs (defined the LU path) relate to the specified POOL.
- mapped_nvme: Displays all LDEVs that are assigned to namespaces.
- unmapped: Displays all LDEVs to
which LU paths are defined. However, LDEVs, mainframe volumes, and
namespaces that are not implemented are not displayed because they
cannot specify the LU path.
Combining this with -pool_id <pool id> specification displays LDEVs (not defined the LU path) relate to the specified POOL.
- journal -journal_id <journal id>: Displays LDEVs that belong to the specified journal.
- pool -pool_id <pool id>: Displays LDEVs that belong to the specified pool.
If a -pool_id option is non-numeric, the specified value is recognized as a pool name to identify the pool ID.
- parity_grp -parity_grp_id <parity group id>: Displays LDEVs that belong to the specified parity group.
- mp_blade -mp_blade_id <mp#>: Displays LDEVs that are set to the specified MP blades.
- quorum: Displays LDEVs set for the quorum disks.
- clpr -clpr_id <clpr#> : Displays LDEVs belonging to the specified CLPR.
Supported storage systems:
- VSP 5000 series
- VSP G1x00 and VSP F1500
- VSP G/F350, G/F370, G/F700, G/F900
[-key <keyword> ]
Specifies a display keyword.
If this option is omitted, basic LDEV information is displayed. If this option is specified, the following information is displayed. The following display keywords can be specified:
- front_end: Front-end information
- front_end_nvme: Front-end NVMe (NVMe-oF) information
- parity_grp: Parity group information
- external: External volume information
- tier: Tier information for the Dynamic Tiering or active flash V-VOL.
- powersave: Information on the capacity saved by the capacity saving feature for volumes with the capacity saving feature enabled.
- naa: The NAA identifier of the LU (LUN WWN)
- nguid: Namespace identifier (NGUID: Namespace Global Unique Identifier)
- qos: Specifies the qos when displaying the QoS setting information. This display keyword can be specified only for VSP 5000 series, VSP G130, G/F350, G/F370, G/F700, G/F900.
- qos_monitor: Specifies the qos_monitor when displaying the performance monitor information related to the QoS of the target LDEV. This display keyword can be specified only for VSP 5000 series, VSP G130, G/F350, G/F370, G/F700, G/F900.
[-check_status <string>... [-time <time>]]
Check if the LDEV is in the same state as the specified in <string>. If the option contains multiple states, the OR condition check is performed and verifies that the LDEV is in one of the states contained in the option.
The following strings are specified in the <string>.
- STS
- NML: Normal
- BLK: Blocked
- BSY: Status is changing
- OPE_TYPE
- FMT: Formatting
- QFMT: Quick formatting
- CCOPY: Data copying (Correction copy / Copy back / Drive copy / Dynamic sparing)
- CACCS: Accessing to collections
- NONE: Not in operation
- SHRD: Shredding
- ZPD: Page discarding
- SHRPL: Deleting from the pool
- RLC: Pool relocating
- RBL: Pool rebalancing
- VOL_TYPE
- NOT DEFINED: An LDEV is not installed
- DEFINING: An LDEV is being created
- REMOVING: An LDEV is being deleted
If "-time" is specified, the status of the LDEV is checked every three seconds until the end of the specified <time> (seconds).
When this option is specified, the returned values are as follows.
- The LDEV is in one of the specified states: 0
- The LDEV is in none of the specified states (without -time option): 1
- The LDEV is in none of the specified states (when the specified <time> passed): EX_EWSTOT
- STS
[-check_status_not <string>... [-time <time>]]
Check that the LDEV is not in the same state as the specified in <string>. If the option contains multiple states, the NOR condition check is performed and verifies that the LDEV is not in any of the states contained in the option.
The following strings are specified in the <string>.
- STS
- NML: Normal
- BLK: Blocked
- BSY: Status is changing
- OPE_TYPE
- FMT: Formatting
- QFMT: Quick formatting
- CCOPY: Data copying (Correction copy / Copy back / Drive copy / Dynamic sparing)
- CACCS: Accessing to collections
- NONE: Not in operation
- SHRD: Shredding
- ZPD: Page discarding
- SHRPL: Deleting from the pool
- RLC: Pool relocating
- RBL: Pool rebalancing
- VOL_TYPE
- NOT DEFINED: An LDEV is not installed
- DEFINING: An LDEV is being created
- REMOVING: An LDEV is being deleted
If "-time" is specified, the status of the LDEV is checked every three seconds until the end of the specified <time> (seconds).
When this option is specified, the returned values are as follows.
- The LDEV is not in any of the specified states: 0
- The LDEV is in one of the specified states (without -time option): 1
- The LDEV is in one of the specified states (when the specified <time> passed): EX_EWSTOT
- STS
[-time_zone <time zone>]
Supported storage systems:
- VSP 5000 series
- VSP G130, G/F350, G/F370, G/F700, G/F900
Specifies the time zone displayed in storage systems. If this option is omitted, the time in the time zone set for the storage system is displayed. This option is valid only when it is specified with the -key qos option or -key qos_monitor option.
- utc: Displays the time in Coordinated Universal Time (UTC).
A hyphen (-) is displayed if the DKCMAIN microcode version is not supported.
Some keywords might not be displayed depending on the LDEV attribute as shown below.
LDEV attribute |
Front end |
Parity group |
External |
Tier | |
Normal volume |
Internal volume |
Y |
Y |
N |
Y |
External volume |
Y |
N |
Y |
Y | |
POOL Volume for Thin Image, Copy-on-Write Snapshot, Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, active flash, Dynamic Tiering for Mainframe, or active flash for mainframe |
Internal volume |
N |
Y |
N |
N |
External volume |
N |
N |
Y |
N | |
Journal volume |
Internal volume |
N |
Y |
N |
N |
External volume |
N |
N |
Y |
N | |
Legend Y: Displayed, N: Not displayed |
- Internal volume examples
- External volume examples
- Dynamic Provisioning V-VOL examples
- Deduplication system data volume example
- Volume deletion examples
- Dynamic Tiering V-VOL examples
- Thin Image primary volume example
- Pool volume example
- rmawk command examples
- Capacity saving example
raidcom modify ldev
Changes the following LDEV attributes:
- Blocking LDEV and restoring LDEV.
- Setting LDEV nickname.
- Setting MP blade ID of LDEV.
- Setting the Tiering policy, the new page assignment tier, or enabling or disabling of the tier relocation for the Dynamic Tiering, active flash, Dynamic Tiering for Mainframe, or active flash for mainframe V-VOL.
- Instructing the page discarding of V-VOL for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, active flash, Dynamic Tiering for Mainframe, or active flash for mainframe.
- Setting the SSID.
- Setting the command device attribute.
- Setting the quorum disk and releasing setting of the quorum disk.
- Setting capacity saving.
- Setting the capacity saving processing mode (post process or inline).
- Setting compression accelerator (enable or disable) (only for VSP 5000 series).
When blocking LDEV, restoring LDEV, setting the quorum disk, releasing setting of the quorum disk, setting capacity saving, setting compression accelerator, or setting QoS, this command is executed asynchronously with the command input. Check the completion of this process using the raidcom get command_status command.
raidcom modify ldev -ldev_id <ldev#> {-status <status> [<level>] [-forcible -password <One Time Password>] | -ldev_name <ldev naming> | -mp_blade_id <mp#> | -ssid <value> | -command_device {y | n} [Security value] | -quorum_enable <serial#> <id> -quorum_id <quorum id> | -quorum_disable | -alua {enable|disable} | -capacity_saving <capacity saving> | -capacity_saving_mode <saving mode>| -compression_acceleration {enable | disable} -request_id auto | -upper_throughput_io<upper throughput io> -request_id auto | -upper_data_trans_mb <upperdata trans mb> -request_id auto | -upper_alert_time <upper alert time> -request_id auto | -lower_throughput_io <lower throughput io> -request_id auto | -lower_data_trans_mb <lower data trans mb> -request_id auto | - lower_alert_time <lower alert time> -request_id auto | - response_priority <priority> -request_id auto | -response_alert_time <response alert time> -request_id auto | -ese {enable | disable} -request_id auto}
raidcom modify ldev -pool {<pool ID#> | <pool naming>} -compression_acceleration {enable | disable} -request_id auto
-ldev_id <ldev#>
Specifies the LDEV number (0-65279). For example:
- -ldev_id 200
-status <status> [<level>]
Specifies the LDEV status. The following LDEV statuses can be specified.
- nml: Changes the LDEV status to Normal
- blk: Changes the LDEV status to Blockade
- {enable_reallocation [<level>]|enable_relocation [<level>]}: Relocation of LDEV (V-VOL for
Dynamic Tiering,
active flash,
Dynamic Tiering for Mainframe, or
active flash for mainframe) enabled. Defines the tier that is used for reallocation depending on the value of the level.
- all: Uses all tiers in the pool.
- 1-5: Specifies the level of the tier for use. For details, see the Provisioning Guide for your storage system.
- disable_reallocation | disable_relocation: Relocation of LDEV (V-VOL for Dynamic Tiering, active flash, Dynamic Tiering for Mainframe, or active flash for mainframe) disabled
- discard_zero_page: Discarding 0 page of LDEV(V-VOL) for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, active flash, Dynamic Tiering for Mainframe, or active flash for mainframe.
- stop_discard_zero_page (only for VSP 5000 series, VSP G130, G/F350, G/F370, G/F700, G/F900): Stops the discard of LDEV (virtual volume) pages for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, active flash, Dynamic Tiering for Mainframe, or active flash for mainframe.
- enable_relocation_policy <policy_id>: Enables the LDEV relocation for
Dynamic Tiering or
active flash, and sets the level or customized policy of the Tier to be used for the relocation by Policy ID.
<policy_id>:
- all: Uses all tiers in the pool.
- 1-5: Specifies the level of the tier for use.
- 6-31: Specifies the customized policy of the tier for use.
- new_page_allocation: Sets the Tier when new page is allocated to the LDEV for Dynamic Tiering or active flash (V-VOL). The value is one of high/middle/low.
- 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.
For example:
- -status nml
[-forcible -password <One Time Password>]
Supported storage systems:
- VSP 5000 series
- VSP G130, G/F350, G/F370, G/F700, G/F900
-ldev_name <ldev naming>
Specifies the LDEV nickname (maximum 32 characters).
-mp_blade_id <mp#>
Specifies the MP blade ID (0-15).
Do not change the MP blade ID during initial copying or I/O processing of TrueCopy, ShadowImage, Universal Replicator, or global-active device.
To change the MP blade ID again for the same LDEV, wait for more than 30 minutes after changing the MP blade ID. For example:
-mp_blade_id 2
When you change the MP blade ID where the LDEV is allocated, both before and after the changing should be executed during as off-peak hours for the rate of write pending data of the MP blade as possible. It is recommended to execute when the rate of write pending data of all CLPRs is less than 50%.
Do not change the MP blade ID in regard to a lot of LDEVs at the same time. The number of LDEVs and I/O workload for which you can change the MP blade ID at the same time is lower than 10% of the total number of LDEVs where the same MP blade ID is allocated as a guideline.
-ssid <value>
Specifies SSID (hexadecimal number).
When specifying SSID, specify not only unallocated SSID but also LDEV ID. In this case, LDEV ID must be ID for the undefined LDEV in the area where SSID is not allocated. For example:
-ssid 0x1234 -ldev_id 200
NoteThis option is for enterprise storage systems. You do not need to specify SSID for VSP Gx00 models, and VSP Fx00 models, HUS VM, but this option is enabled.-command_device {y | n} [Security value]
Configures command device attribute.
y: Command device attribute enabled.
n: Command device attribute disabled.
Specifies the value of command device security (0-7).
You can specify 0-7 to Security value as the command device security setting:
- 0: Security: OFF, User authentication: OFF, Group information acquisition: OFF
- 1: Security: OFF, User authentication: OFF, Group information acquisition: ON
- 2: Security: OFF, User authentication: ON, Group information acquisition: OFF
- 3: Security: OFF, User authentication: ON, Group information acquisition: ON
- 4: Security: ON, User authentication: OFF, Group information acquisition: OFF
- 5: Security: ON, User authentication: OFF, Group information acquisition: ON
- 6: Security: ON, User authentication: ON, Group information acquisition: OFF
- 7: Security: ON, User authentication: ON, Group information acquisition: ON
-quorum_enable <serial#> <id>
Sets quorum disk for global-active device configuration. You must also set the -quorum_id parameter.
serial#: Serial number (of the migration source storage system)
- When specifying the serial number for VSP 5000 series, add a “5” at the beginning of the serial number. For example, for serial number 12345, enter 512345.
- When specifying the serial number for VSP G1x00 and VSP F1500, add a “3” at the beginning of the serial number. For example, for serial number 12345, enter 312345.
id: The identifier of the source storage system
- R900: VSP 5000 series
- R800: VSP G1x00, VSP F1500
- R700: VSP
- M700: HUS VM
-quorum_id <quorum id>
Specifies the quorum ID for setting the quorum disk.
-quorum_disable
Releases setting of the quorum disk.
-alua {enable|disable}
Specifies the ALUA mode. You must enable ALUA mode only when you use ALUA by global-active device.
- enable: The ALUA mode is enabled.
- disable: The ALUA mode is disabled.
[-capacity_saving <capacity saving>]
Specifies the capacity saving setting:
- disable: Capacity saving is disabled.
- compression: Compression is enabled.
- deduplication_compression: Deduplication and compression are enabled.
(VSP 5000 series) When there are no pool-associated LDEVs for which the capacity saving setting is deduplication_compression, the deduplication system data volumes are automatically deleted asynchronously with the deletion of the LDEVs. To verify that a deduplication system data volume is deleted, use the raidcom get pool -key saving command to check the LDEV number, and use the raidcom get ldev command to verify that VOL_TYPE of the LDEV is changed from REMOVING to NOT DEFINED.
NoteDisabling the capacity saving setting for a deduplication volume might take a while to complete due to its data extension operation. Also, more pool/physical capacity might be used. You cannot stop the operation of disabling the capacity saving setting while it is in process.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>]
Specifies 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 5000 series, and VSP G/F350, G/F370, G/F700, G/F900, inline is the default.
-lower_throughput_io <lowerthroughput io> -request_id auto
(For VSP 5000 series, VSP G130, G/F350, G/F370, G/F700, G/F900) Specifies the lower limit of the throughput per second. To disable it, specify 0. For more information on the lower limit of the throughput per second, see the Performance Guide.
The request ID is output in the following format when the raidcom modify ldev command ends.
- REQID : <request#>
For details, see Request ID function.
- lower_data_trans_mb <lower data trans mb> -request_id auto
(For VSP 5000 series, VSP G130, G/F350, G/F370, G/F700, G/F900) Specifies the lower limit of the data transfer volume (MB) per second. To disable it, specify 0. For more information on the lower limit of the data transfer volume (MB) per second, see the Performance Guide.
The request ID is output in the following format when the raidcom modify ldev command ends.
- REQID : <request#>
For details, see Request ID function.
- lower_alert_time <lower alert time> -request_id auto
(For VSP 5000 series, VSP G130, G/F350, G/F370, G/F700, G/F900) Specifies the following alert notification time (second). To disable it, specify 0.
- The alert notification time (second) when the number of received commands has not continuously reached the lower limit of the throughput per second.
- The alert notification time (second) when the transfer volume of received commands has not continuously reached the lower limit of the data transfer volume per second.
For more information on the lower limit of the alert notification time per second, see the Performance Guide.
The request ID is output in the following format when the execution of the raidcom modify ldev command ends.
- REQID : <request#>
For details, see Request ID function.
-response_priority <priority> -request_id auto
(For VSP 5000 series, VSP G130, G/F350, G/F370, G/F700, G/F900) Specifies the I/O processing priority. The valid ranges are 1-3. To disable it, specify 0. For more information on the I/O processing priority, see the Performance Guide.
The request ID is output in the following format when the execution of the raidcom modify ldev command ends.
- REQID : <request#>
For details, see Request ID function.
-response_alert_time <responsealert time> -request_id auto
(For VSP 5000 series, VSP G130, G/F350, G/F370, G/F700, G/F900) Specifies the alert notification time (second) when the target response time is not reached . To disable it, specify 0. If the target response time has not been continuously reached for more than the alert notification time, an alert is issued. For more information on the alert notification time (second) when the target response time is not reached , see the Performance Guide.
The request ID is output in the following format when the execution of the raidcom modify ldev command ends.
- REQID : <request#>
For details, see Request ID function.
-compression_acceleration {enable | disable} -request_id auto
Supported storage systems:
- VSP 5000 series
Specifies whether compression accelerator is enabled or disabled.
If you change -capacity_saving from disable to compression or deduplication_compression, and omit this 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.
-ese {enable | disable} -request_id auto
Supported storage systems:
- VSP 5000 series
Specifies whether to set or cancel the ESE attribute for the LDEV.
- enable: Set the ESE attribute
- disable: Cancel the ESE attribute
<request#> is the request ID assigned each time the command is run. For details, see Request ID function
Restoring the LDEV: 200.
# raidcom modify ldev -status nml -ldev_id 200
Blocking the LDEV: 200.
# raidcom modify ldev -status blk -ldev_id 200
Assigning an LDEV nickname: my_volume to LDEV: 200
# raidcom modify ldev -ldev_id 200 -ldev_name my_volume
Setting the LDEV owner MP blade ID of LDEV: 200 to 2
# raidcom modify ldev -ldev_id 200 -mp_blade_id 2
Enabling relocation of LDEV (Dynamic Tiering, active flash, Dynamic Tiering for Mainframe, or active flash for mainframe V-VOL): 200
# raidcom modify ldev -ldev_id 200 -status enable_reallocation
Disabling relocation of LDEV (Dynamic Tiering, active flash, Dynamic Tiering for Mainframe, or active flash for mainframe V-VOL): 200
# raidcom modify ldev -ldev_id 200 -status disable_reallocation
Discarding the zero page of LDEV (Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, active flash, Dynamic Tiering for Mainframe, or active flash for mainframe V-VOL): 200
# raidcom modify ldev -ldev_id 200 -status discard_zero_page
Specifying 0x1234 to LDEV SSID of LDEV: 200.
Specify undefined LDEV number: 200 in the area that is not allocated SSID, and assign new SSID: 0x1234. If you specify an LDEV number that is already defined or an SSID that is already registered, an error occurs.
# raidcom modify ldev -ssid 0x1234 -ldev_id 200
Enabling LDEV command device attribute of LDEV: 200. Specifies 2 to the value of command device security.
# raidcom modify ldev -command_device y 2 -ldev_id 200
Disabling LDEV command device attribute of LDEV: 200.
# raidcom modify ldev -command_device n -ldev_id 200
Setting the relocation of LDEV for LDEV:200 by the customized policy 6.
# raidcom modify ldev -ldev_id 200 -status enable_relocation_policy 6
Setting the tier from which the new mapped page of LDEV: 200 is allocated to High.
# raidcom modify ldev -ldev_id 200 -status new_page_allocation high
Setting LDEV: 200 as the quorum disk whose quorum ID is 10.
# raidcom modify ldev -ldev_id 200 -quorum_enable 65384 R700 -quorum_id 10
Enabling the ALUA mode for LDEV: 200.
# raidcom modify ldev -ldev_id 200 -alua enable
Setting the capacity saving setting to compression for LDEV: 200.
# raidcom modify ldev -ldev_id 200 -capacity_saving compression
Enabling the compression accelerator setting for LDEV: 200.
# raidcom modify ldev -ldev_id 200 -compression_acceleration enable -request_id auto
Enabling all compression accelerator settings associated with pool ID: 1.
# raidcom modify ldev -pool 1 -compression_acceleration enable -request_id auto
Enabling the compression accelerator settings for all LDEVs associated with from pool ID: 0 to maximum 128 pools.
# raidcom get dp_pool | rmawk @L-gt:1 exe="raidcom modify ldev -pool @1 -compression_acceleration enable -request_id auto"
Changing the capacity saving processing mode for LDEV: 0 to the inline mode.
# raidcom modify ldev -ldev_id 0 -capacity_saving_mode inline
Changing the capacity saving processing mode for LDEV: 0 to the post-process mode.
# raidcom modify ldev -ldev_id 0 -capacity_saving_mode post_process
(For VSP 5000 series, VSP G130, G/F350, G/F370, G/F700, G/F900) Setting the lower limit of the throughput per second to 1500 IOPS for LDEV ID: 200.
# raidcom modify ldev -ldev_id 200 -lower_throughput_io 1500 -request_id auto
(For VSP 5000 series, VSP G130, G/F350, G/F370, G/F700, G/F900) Setting the I/O processing priority to 1 for LDEV ID: 200.
# raidcom modify ldev -ldev_id 200 -response_priority 1 -request_id auto
(For VSP 5000 series, VSP G130, G/F350, G/F370, G/F700, G/F900) Setting the alert notification time when the lower limit is not reached to 10 seconds for LDEV ID: 200.
# raidcom modify ldev -ldev_id 200 -lower_alert_time 10 -request_id auto
(For VSP 5000 series) Enabling ESE for LDEV: 200.
# raidcom modify ldev -ldev_id 200 -ese enable -request_id auto
raidcom delete ldev
Deletes the specified LDEVs or V-VOLs. A device group can also be specified instead of an LDEV.
This command is executed asynchronously with the command input. Check the completion of this process on the raidcom get command_status command.
raidcom delete ldev {-ldev_id <ldev#> | -grp_opt <group option> -device_grp_name <device group name> [<device name>] } [-operation initialize_capacity_saving]
-ldev_id <ldev#> (0-65279)
Specifies the LDEV number (0-65279). For example:
- -ldev_id 200
-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.
[-operation initialize_capacity_saving]
Deletes an LDEV for which the capacity saving setting is enabled. When you specify this option, use the raidcom get command_status command to check if the LDEV deletion started, and then use the raidcom get ldev command to check if VOL_TYPE of the LDEV is changed from REMOVING to NOT DEFINED. If you perform another operation during or immediately after deletion of the LDEV, the operation might fail. In this case, wait a while and then retry the operation.
(VSP 5000 series) When there are no pool-associated LDEVs for which the capacity saving setting is deduplication_compression, the deduplication system data volumes are automatically deleted asynchronously with the deletion of the LDEVs. To verify that a deduplication system data volume is deleted, use the raidcom get pool -key saving command to check the LDEV number, and use the raidcom get ldev command to verify that VOL_TYPE of the LDEV is changed from REMOVING to NOT DEFINED.
Note- Deleting a deduplication volume using this command might take a while. Also, more pool/physical capacity might be used. You cannot stop the deletion operation while it is in process.
- If you want to delete all of the pool-associated volumes for which capacity saving is enabled, first execute the raidcom modify ldev command to block both the pool-associated volumes and the deduplication system data volumes, and then execute the raidcom initialize pool command. By executing the raidcom initialize pool command before deleting the volumes, you can shorten the time for the volume deletion process and prevent the increase of pool capacity to be used.
Deleting an LDEV: 200.
raidcom delete ldev -ldev_id 200
Deleting an LDEV belonging to the device group: grp1.
raidcom delete ldev -grp_opt ldev -device_grp_name grp1
Deleting an LDEV: 200, for which capacity saving setting is enabled.
# raidcom delete ldev -ldev_id 200 -operation initialize_capacity_saving
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.
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] | -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>
-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.
CautionYou 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 5000 series
- VSP G1x00 and VSP F1500
- VSP G130, 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.
[-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.
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: 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
raidcom : Please check if LDEV over 4 TB will be used for replication products, and then check the supported capacity.
raidcom extend ldev
Extends the capacity of a V-VOL for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, Dynamic Tiering for Mainframe, active flash, or active flash for mainframe.
If the specified LDEV is not a V-VOL of Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, Dynamic Tiering for Mainframe, active flash, or active flash for mainframe, the command is rejected with EX_ENOOBJ.
A device group can also be specified instead of an LDEV.
raidcom extend ldev {-ldev_id <ldev#> | -grp_opt <group option> -device_grp_name <device group name> [<device name>]} -capacity <size> | -offset_capacity <size> | -cylinder <size> [-request_id auto]
-ldev_id <ldev#> (0-65279)
Specifies the LDEV number (0-65279). Specify LDEVs for Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic Tiering, Dynamic Tiering for Mainframe, active flash, or active flash for mainframe. For example:
- -ldev_id 200
-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.
-capacity <size>
The increment size of capacity 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.
Example of specification:
1GB (gigabyte) is:
-capacity 1G, -capacity 1g, -capacity 1024M, -capacity 1024m, -capacity 1048576K, -capacity 1048576k, -capacity 2097152
-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.
-cylinder <size>
Specifies the size in cylinder unit. When specifying, the unit is g/G (gigabyte), m/M (megabyte), or k/K (kilobyte). Cylinder is applied if you do not specify the unit.
When the emulation type for the Open System is specified, this option cannot be specified.
-request_id auto
(VSP 5000 series, VSP G1x00, VSP F1500and VSP G130, G/F350, G/F370, G/F700, G/F900 only) Specifying this option is recommended when running the command. <request#> is a Request ID assigned each time the command is run. For more information, see Request ID function.
Extending the capacity of a Dynamic Provisioning or Dynamic Provisioning for Mainframe V-VOL: 200 by 10 GB.
# raidcom extend ldev -ldev_id 200 -capacity 10G
Extending the capacity of a Dynamic Provisioning or Dynamic Provisioning for Mainframe V-VOL: 201 by 200 MB.
# raidcom extend ldev -ldev_id 201 -capacity 200M
Extending the capacity of Dynamic Provisioning or Dynamic Provisioning for Mainframe V-VOL belonging to the device group: grp1 by 200 MB.
# raidcom extend ldev -grp_opt ldev -device_grp_name grp1 -capacity 200M
Shredding volumes
By using the CCI, you can completely erase all data from volumes. After the erase, the volumes can be reused securely.
Data cannot be restored after the shredding. Therefore, before executing the command, make sure that the specified volumes are correct.
You can prevent data leakage by shredding volumes in the following cases:
- When you want to reuse a volume.
- When you want to dispose of a drive.
Shredding erases the volume data by overwriting it repeatedly with dummy data.
Block the target volume, and then delete the data.
- Block the volume.
To stop access to the target volume, block the volume. To prevent operation mistakes, data can be erased only when the volume is blocked.
- Erase the data from the volume.
Delete data from the volume by repeatedly overwriting the unnecessary dummy data. You can specify any data pattern for the second time. By default, the dummy data is overwritten in the following order:
-
First time: 0x00000000
-
Second time: 0xFFFFFFFF
-
Third time: 0x00000000
-
The following figure shows an example system environment.
-
-
Server
CCI is installed on the server.
-
Storage volumes for shredding
Volume ID: 100
Volume ID: 200
-
User name and password of storage system
User name: user00
Password: password00
-
Volume shredding command example
Delete data from all of the volumes in a pool.
Before you begin
- I/O operations of the volume have stopped.
- The volume is not paired with another volume.
Procedure
Log in to a storage system by using the CCI.
# raidcom -login user00 password00
Block volumes for shredding.
# raidcom modify ldev -ldev_id 100 200 -status blk
Delete the data from the blocked volumes.
# raidcom initialize ldev -operation shrd 0x55aa55aa -ldev_id 100 200
Make sure that the data has been deleted.
# raidcom get command_status # echo $? 0
If the return value is 0, the shredding command completed normally. If the return value is 1, the command returned errors.
Log out from the storage system.
# raidcom -logout