PI_LDS

Ops Center Analyzer REST API Reference Guide

Version
11.0.x
Audience
anonymous
Part Number
MK-99ANA003-18

The PI_LDS record stores the performance data indicating the execution status of read and write operations on the logical device. This is a multi-instance record.

Note that if you are monitoring a VSP 5000 series storage system and the Access Type is 3 or 4, you cannot collect performance information about mainframe systems.

Collection Interval

300

Key Field

LDEV_NUMBER

Lifetime

From when the logical device is set up to when it is removed

Fields

Field Name Description Access Type Format
INPUT_RECORD_TYPE Record type identifier.9 1, 2, 3, 4 string(8)
INTERVAL Interval (in seconds) at which information is collected. 1, 2, 3, 4 ulong
LDEV_NUMBER Logical device number.1 1, 2, 3, 4 string(16)
RANDOM_TOTAL_IO_RATE Frequency of random operations (sum of processing times for random read and write operations per second). 1, 2, 3, 4 float
RANDOM_TOTAL_XFER_RATE2 Transfer rate of random operations (total megabytes for random read and write operations per second). 1, 2, 3, 4 float
READ_HIT_IO_COUNT Number of times the cache is hit for read operations. 1, 2, 3, 4 ulong
READ_HIT_RATE Cache hit rate of read operations.

The value is calculated based on the following formula:

(READ_HIT_IO_COUNT / READ_IO_COUNT) * 100

1, 2, 3, 4 float
READ_IO_COUNT Number of read operations. 1, 2, 3, 4 ulong
READ_IO_RATE Frequency of read operations (number of times per second).

The value is calculated based on the following formula:

READ_IO_COUNT / INTERVAL

1, 2, 3, 4 float
READ_MBYTES3 Read data transfer size (MB). 1, 2, 3, 4 ulong
READ_RESPONSE_RATE3 Average processing time for each read operation request (in microseconds). 1, 2, 3, 4 float
READ_TOTAL_RESPONSE3 Sum of processing times for read-operation requests processed during the collection period (in microseconds). 1, 2, 3, 4 double
READ_XFER_RATE3 Read data transfer rate (MB per second).

The value is calculated based on the following formula:

READ_MBYTES / INTERVAL

1, 2, 3, 4 float
RECORD_TIME Time (in GMT) at which data was collected from the storage system and the record was created. 1, 2, 3, 4 time_t
SEQUENTIAL_TOTAL_IO_RATE Frequency of sequential operations (sum of processing times for sequential read and write operations per second). 1, 2, 3, 4 float
SEQUENTIAL_TOTAL_XFER_RATE2 Transfer rate of sequential operations (total megabytes for sequential read and write operations per second). 1, 2, 3, 4 float
TOTAL_RESPONSE_RATE3 Average processing time for each read and write operation request (in microseconds). 1, 2, 3, 4 float
VIRTUAL_DKC_DETAIL_NAME

This field cannot be used because it is reserved.

-- --
VIRTUAL_DKC_NAME4, 5, 6, 8 Product name of the virtual storage machine to which the logical device belongs. 1, 2 string(32)
VIRTUAL_LDEV_NUMBER4, 7 Virtualized logical device number associated with the logical device. 1, 2 string(16)
VIRTUAL_SERIAL_NUMBER4, 5 Serial number of the virtual storage machine to which the logical device belongs. 1, 2 string(32)
WRITE_HIT_IO_COUNT This field cannot be used because it is reserved. -- --

WRITE_HIT_RATE

This field cannot be used because it is reserved.

--

--

WRITE_IO_COUNT Number of write operations. 1, 2, 3, 4 ulong
WRITE_IO_RATE Frequency of write operations (number of times per second).

The value is calculated based on the following formula:

WRITE_IO_COUNT / INTERVAL

1, 2, 3, 4 float
WRITE_MBYTES3 Write data transfer size (MB). 1, 2, 3, 4 ulong
WRITE_RESPONSE_RATE3 Average processing time for each write operation request (in microseconds). 1, 2, 3, 4 float
WRITE_TOTAL_RESPONSE3 Sum of processing times for write-operation requests processed during the collection period (in microseconds). 1, 2, 3, 4 double
WRITE_XFER_RATE3 Write transfer speed (MB per second).

The value is calculated based on the following formula:

WRITE_MBYTES / INTERVAL

1, 2, 3, 4 float

Notes:

  1. If the logical device is a component of a LUSE, the value of LDEV_NUMBER indicates the logical device number of the first logical device of the LUSE.

    Each performance information field contains statistics on the read or write operations performed on the entire logical device group that makes up the LUSE. No record is created for individual logical devices that are included in the LUSE. If the LUSE consists of external volume, or logical devices of V-VOLs for Copy-on-Write Snapshot/Thin Image or Dynamic Provisioning, and no LU path is set for the LUSE, the LUSE is not recognized and records are created for individual logical devices.

  2. This field is not supported for logical devices for which the mainframe emulation type is set.
  3. For logical devices for which the mainframe emulation type is set, this value can be collected only for VSP 5000 series, VSP G1000 (80-03 or later), G1500, or VSP F1500 storage systems.
  4. If the logical device does not belong to a virtual storage machine, the field value is NULL.
  5. If the logical devices that compose a global-active device copy pair are not virtualized, the field value will be NULL.
  6. If the virtual storage machine is VSP F400 or VSP F600, the value is VSP G400 G600. If the virtual storage machine is VSP F800, the value is VSP G800.
  7. If either of the following applies to the logical device, the field value will be NULL:
    • The logical device is part of a global-active device copy pair, and is not virtualized.
    • No virtualized logical device number is set for the logical device.
  8. If the virtual storage machine is VSP G1000, the value stored in the VIRTUAL_DKC_NAME field is VSP G1000 G1500 F1500.
  9. Depending on the logical device number, one of the following values is used: LDS, LDS1, LDS2, or LDS3.