Commands for QoS operations

Quality of Service User Guide for VSP One Block

Version
10.5.x
Audience
anonymous
Part Number
MK-23VSP1B013-03
ft:lastEdition
2026-02-03

Use the following CCI commands to specify the QoS settings and to obtain QoS monitor information. For details, see the Command Control Interface Command Reference.

Note: The QoS settings for a volume used as a CCI command device or a remote CCI command device are guarded and cannot be set.

Function

Command

Setting item

Command option

Configuring the settings on a volume

raidcom modify ldev

Upper limit

-upper_throughput_io

-upper_data_trans_mb

Lower limit

-lower_throughput_io

-lower_data_trans_mb

QoS priority

-response_priority

Threshold period for alert notification

-upper_alert_time

-lower_alert_time

-response_alert_time

Configuring the settings on a QoS group

raidcom add qos_grp

Creating a QoS group

-qos_grp_id

Adding a volume to a QoS group

-qos_grp_id

-ldev_id

raidcom delete qos_grp

Deleting a QoS group

-qos_grp_id

Deleting a volume from a QoS group

-qos_grp_id

-ldev_id

raidcom modify qos_grp

Upper limit

-upper_throughput_io

-upper_data_trans_mb

QoS priority

-response_priority

Threshold period for alert notification

-upper_alert_time

-response_alert_time

Viewing the settings for a volume

raidcom get ldev

Viewing the QoS settings configured on a volume

-key qos

Viewing the settings for a QoS group

raidcom get qos_grp

Viewing the QoS settings configured on a QoS group

-key monitor

Viewing the settings for a volume in a QoS group

raidcom get qos_grp

Viewing a volume included in a QoS group

-key resource

-qos_grp_id

QoS monitoring for a volume

raidcom get ldev

Viewing the performance information on a volume

-key qos_monitor

raidcom monitor resource*

-monitor_type qos_ldev

QoS monitoring for a QoS group

raidcom get qos_grp

Viewing the performance information on a QoS group

-key monitor

raidcom monitor resource*

-monitor_type qos_grp

* This command is used for periodically collecting the performance information. To run this command, log in to the storage system with a user account belonging to the user group for which all resource groups are set.

Verifying a volume or QoS group that has reached the alert conditions

You can use CCI to check the last time an alert was issued for a monitored volume or QoS group. If you receive an alert notification, check the last time the upper-limit value was exceeded for every monitored volume or QoS group.

Command example for a volume:

C:\HORCM\etc>raidcom get ldev -ldev_list defined -fx -key qos
LDEV# UPPER_THROUGHPUT(IOps) UPPER_DATA_TRANS(MBps) UPPER_ALERT(s) UPPER_ALERT_NOTICE
LOWER_THROUGHPUT(IOps) LOWER_DATA_TRANS(MBps) LOWER_ALERT(s) LOWER_ALERT_NOTICE PRIORITY RESPONSE_TARGET(ms) RESPONSE_ALERT(s) RESPONSE_ALERT_NOTICE
a000                          1000                        1                    1
2020 03-10T15:17:28                   100
1              1 2020 03-10T15:17:28        1
10                 1 -
Note:
  • UPPER_ALERT_NOTICE indicates the time the volume or QoS group reached the upper limit even if the time is before the alert notification.
  • UPPER_ALERT_NOTICE does not indicate the time if the volume or QoS group has never reached the upper limit.
  • LOWER_ALERT_NOTICE indicates the time the volume is determined not to reach the lower limit even if the time is before the alert notification.
  • LOWER_ALERT_NOTICE does not indicate the time if the I/O throughput of the volume is always equal to or more than the lower limit.
  • RESPONSE_ALERT_NOTICE indicates the time the volume or QoS group exceeds the target response time even if the time is before the alert notification.
  • RESPONSE_ALERT_NOTICE does not indicate the time if the volume or QoS group has never exceeded the target response time.
  • The time that reached an alert condition is recorded based on the system date and time (date, time, and time zone) of the storage system.

    Therefore, if you change the system date and time of the storage system, the time which previously reached the alert condition becomes incorrect after the change.