Statistics collection

The system collects statistics over an interval and creates files that can be viewed.

Introduction

For each collection interval, the management GUI creates six statistics files: one for managed disks (MDisks), which is named Nm_stats; one for volumes and volume copies, which is named Nv_stats; one for volumes groups, which is named Ng_stats; one for nodes, which is named Nn_stats; one for drives, which is named Nd_stats; and one for hosts, which is named Nh_stats.

The files are written to the /dumps/iostats/ directory on the node. To retrieve the statistics files from the non-configuration nodes onto the configuration node, use the svctask cpdumps command.

A maximum of 16 files of each type can be created for the node. When the 17th file is created, the oldest file for the node is overwritten.

Tables

The lsportstats command displays statistics for each node and physical port. When the type field is Eth_iSCSI, Eth_NVMe_TCP and Eth_NVMe_RDMA, the statistics collection is displayed per physical port for iSCSI , NVMeTCP and NVMeRDMA.

Table 1 describe the information that is reported for Ethernet iSCSI individual nodes.

Table 1. Statistic collection per node per port of iSCSI, NVMeTCP and NVMeRDMA
Statistic name Description
hbt Indicates the bytes transmitted to hosts.
hbr Indicates the bytes received from hosts.
het Indicates the commands that are initiated to hosts.
her Indicates the commands that are received from hosts.
hsr Indicates the count of data transfers that were considered slow for host read operations.
hsw Indicates the count of data transfers that were considered slow for host write operations.
har Indicates the cumulative number of blocks of data written (since the node started).
haw Indicates the count aborted host write operations aborted while a data transfer was in progress. This count includes I/O operations aborted by hosts, and those operations aborted internally by the system.
Table 2 describes the statistics collection for hosts, for individual nodes.
Example XML showing the statistic collection for Host for Individual Nodes
<?xml version="1.0" encoding="utf-8" ?>
<diskStatsColl
xmlns="http://ibm.com/storage/management/performance/api/2024/10/hostIoStats"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://ibm.com/storage/management/performance/api/2024/10/hostIoStats schema/SVCPerfStatsH.xsd" scope="node" id="node1" cluster="KK" node_id="0x0000000000000001" cluster_id="0x000002042cc076a2" sizeUnits="512B" timeUnits="msec" contains="hostIoStats" timestamp="2026-02-03 05:31:04" timezone="GMT+0:00" timestamp_utc="2026-02-03 05:31:04">
<host idx="0"

id="KK"
ro="34754" wo="14395" wou="0" rb="318928" wb="115160"
rl="2643" wl="1987" rlw="0" wlw="0" xl="894"
wxl="436" rxl="458"
uo="0" ub="0" uou="0" ul="0" ulw="0" 
tiocnt="48760" tbw="52168" tqueuediocnt="0"
tfailediocnt="0" tmaxdelay="0" tcumdelay="0">

</host>
</diskStatsColl>
Table 2. Statistic collection for Host for Individual Nodes
Statistic name Description
idx Indicates the identifier of the Host for which the statistics apply.
id Indicates the name of the Host for which the statistics apply.
ro Indicates the cumulative number of Host read operations that were processed (since the node started).
wo Indicates the cumulative number of Host write operations that were processed (since the node started).
wou Indicates the cumulative number of Host write operations that are not aligned on a 4 K boundary.
rb Indicates the cumulative number of blocks of data that was read (since the node started).
wb Indicates the cumulative number of blocks of data written (since the node started).
rl Indicates the cumulative read response time in milliseconds for each Host. The cumulative response time for Host reads is calculated by starting a timer when a SCSI read command is received and stopped when the command completes successfully. The elapsed time is added to the cumulative counter.
wl Indicates the cumulative write response time in milliseconds for each Host. The cumulative response time for Host writes is calculated by starting a timer when a SCSI write command is received and stopped when the command completes successfully. The elapsed time is added to the cumulative counter.
rlw Indicates the worst read response time in microseconds for each Host since the last time statistics were collected. This value is reset to zero after each statistics collection sample.
wlw Indicates the worst write response time in microseconds for each Host since the last time statistics were collected. This value is reset to zero after each statistics collection sample.
xl Indicates the cumulative read and write data transfer response time in milliseconds for each Host since the last time the node was reset. When this statistic is viewed for multiple Host and with other statistics, it can indicate whether the latency is caused by the host, or fabric.
wxl Indicates the cumulative write data transfer response times in milliseconds for each Host since the last time the node was reset. A high value for this statistic indicates that latency is likely caused by the fabric and/or the host responding slowly when the node requests the data to write to the Host.
rxl Indicates the cumulative read data transfer response times in milliseconds for each Host since the last time the node was reset. A high value for this statistic indicates that latency is likely caused by the fabric or the host, which is submitting more read commands than it can process.
uo Indicates the cumulative number of Host unmap operations that were processed (since the node started).
ub Indicates the cumulative number of blocks of data unmapped (since the node started).
uou Indicates the cumulative number of Host unmap operations that are not aligned on an 8K boundary (according to the alignment/granularity setting in Block Limits VPD Page (0xb0).
ul Indicates the cumulative unmap response time in milliseconds for each Host. The cumulative response time for Host unmaps is calculated by starting a timer when a SCSI unmap command is received and stopped when the command completes successfully. The elapsed time is added to the cumulative counter.
ulw Indicates the worst unmap response time in microseconds for each Host. The worst response time for volume unmaps is calculated by starting a timer when a SCSI unmap command is received and stopped when the command completes successfully.
tiocnt Indicates the cumulative number of host I/O operations that were examined for I/O throttle (since the node started).
tbw Indicates the cumulative number of blocks of data transfer that was delayed due to I/O throttle (since the node started).
tqueuediocnt Indicates the cumulative number of host I/O operations that were delayed due I/O throttle (since the node started).
tfailediocnt Indicates the cumulative number of host I/O operations that were failed due to excessive delay introduced by I/O throttle (since the node started).
tmaxdelay Indicates the maximum delay introduced for any host I/O by throttle in microseconds (during stats collection interval).
tcumdelay Indicates the cumulative delay introduced for host I/O operations by throttle in milliseconds (since the node started).

Table 3 describes the statistics collection for MDisks, for individual nodes.

Table 3. Statistics collection for MDisks for individual nodes
Statistic name Description
id Indicates the name of the MDisk for which the statistics apply.
idx Indicates the identifier of the MDisk for which the statistics apply.
pre Indicates the peak of read external response time in milliseconds for each MDisk. The external response time for disk reads is calculated by starting a timer when a SCSI read command is issued and stopped when the command completes successfully.
pro Indicates the peak of read queued response time in milliseconds for each MDisk. The value means the peak elapsed time that is taken for read commands to complete from the time they join the queue.
pwe Indicates the peak of write external response time in milliseconds for each MDisk. The external response time for disk writes is calculated by starting a timer when a SCSI write command is issued and stopped when the command completes successfully.
pwo Indicates the peak of write queued response time in milliseconds for each MDisk. The value means the peak elapsed time that is taken for write commands to complete from the time they join the queue.
rb Indicates the cumulative number of blocks of data that was read (since the node started).
re Indicates the cumulative read external response time in milliseconds for each MDisk. The cumulative response time for disk reads is calculated by starting a timer when a SCSI read command is issued and stopped when the command completes successfully. The elapsed time is added to the cumulative counter.
ro Indicates the cumulative number of MDisk read operations that were processed (since the node started).
rq Indicates the cumulative read queued response time in milliseconds for each MDisk. This response is measured from above the queue of commands to be sent to an MDisk because the queue depth is already full. This calculation includes the elapsed time that is taken for read commands to complete from the time they join the queue.
ure Indicates the cumulative read external response time in microseconds for each MDisk. The cumulative response time for disk reads is calculated by starting a timer when a SCSI read command is issued and stopped when the command completes successfully. The elapsed time is added to the cumulative counter.
urq Indicates the cumulative read queued response time in microseconds for each MDisk. This response is measured from above the queue of commands to be sent to an MDisk because the queue depth is already full. This calculation includes the elapsed time that is taken for read commands to complete from the time they join the queue.
uwe Indicates the cumulative write external response time in microseconds for each MDisk. The cumulative response time for disk writes is calculated by starting a timer when a SCSI write command is issued and stopped when the command completes successfully. The elapsed time is added to the cumulative counter.
uwq Indicates the cumulative write queued response time in microseconds for each MDisk. This time is measured from above the queue of commands to be sent to an MDisk because the queue depth is already full. This calculation includes the elapsed time that is taken for write commands to complete from the time they join the queue.
wb Indicates the cumulative number of blocks of data written (since the node started).
we Indicates the cumulative write external response time in milliseconds for each MDisk. The cumulative response time for disk writes is calculated by starting a timer when a SCSI write command is issued and stopped when the command completes successfully. The elapsed time is added to the cumulative counter.
wo Indicates the cumulative number of MDisk write operations that were processed (since the node started).
wq Indicates the cumulative write queued response time in milliseconds for each MDisk. This time is measured from above the queue of commands to be sent to an MDisk because the queue depth is already full. This calculation includes the elapsed time that is taken for write commands to complete from the time they join the queue.
Note: MDisk statistics files for nodes are written to the /dumps/iostats directory on the individual node.
Table 4 describes the volume information that is reported for individual nodes.
Note: The system only collects a subset of statistics for volumes that are used for snapshot function and policy-based replication.
Example XML showing the statistic collection for vdisk for Individual Nodes
<vdsk idx="0"
...
id="CD"
ro="134" wo="2050268" wou="0" rb="862" wb="16407272"
rl="34" wl="850709" rlw="0" wlw="0" xl="62769"
wxl="62768" rxl="1" oro="0" owo="0"
orl="0" owl="0" oiowp="0"
uo="0" ub="0" uou="0" ul="0" ulw="0"
tiocnt="6123" tbw="6123" tqueuediocnt="5986"
tfailediocnt="0" tmaxdelay="0" tcumdelay="470283">
...
</vdsk>
Table 4. Statistic collection for volumes for individual nodes
Statistic name Description
id Indicates the volume name for which the statistics apply.
idx Indicates the volume for which the statistics apply.
rb Indicates the cumulative number of blocks of data read (since the node started).
rl Indicates the cumulative read response time in milliseconds for each volume. The cumulative response time for volume reads is calculated by starting a timer when a SCSI read command is received and stopped when the command completes successfully. The elapsed time is added to the cumulative counter.
rlw Indicates the worst read response time in microseconds for each volume since the last time statistics were collected. This value is reset to zero after each statistics collection sample.
ro Indicates the cumulative number of volume read operations that were processed (since the node started).
rxl Indicates the cumulative read data transfer response times in milliseconds for each volume since the last time the node was reset. A high value for this statistic indicates that latency is likely caused by the fabric or the host, which is submitting more read commands than it can process.
ub Indicates the cumulative number of blocks of data unmapped (since the node started).
ul Indicates the cumulative unmap response time in milliseconds for each volume. The cumulative response time for volume unmaps is calculated by starting a timer when a SCSI unmap command is received and stopped when the command completes successfully. The elapsed time is added to the cumulative counter.
ulw Indicates the worst unmap response time in microseconds for each volume. The worst response time for volume unmaps is calculated by starting a timer when a SCSI unmap command is received and stopped when the command completes successfully.
uo Indicates the cumulative number of volume unmap operations that were processed (since the node started).
uou Indicates the cumulative number of volume unmap operations that are not aligned on an 8 K boundary (according to the alignment/granularity setting in Block Limits VPD Page (0xb0).
wb Indicates the cumulative number of blocks of data written (since the node started).
wl Indicates the cumulative write response time in milliseconds for each volume. The cumulative response time for volume writes is calculated by starting a timer when a SCSI write command is received and stopped when the command completes successfully. The elapsed time is added to the cumulative counter.
wlw Indicates the worst write response time in microseconds for each volume since the last time statistics were collected. This value is reset to zero after each statistics collection sample.
wo Indicates the cumulative number of volumes write operations that were processed (since the node started).
wou Indicates the cumulative number of volumes write operations that are not aligned on a 4 K boundary.
wxl Indicates the cumulative write data transfer response times in milliseconds for each volume since the last time the node was reset. A high value for this statistic indicates that latency is likely caused by the fabric and/or the host responding slowly when the node requests the data to write to the volume.
xl Indicates the cumulative read and write data transfer response time in milliseconds for each volume since the last time the node was reset. When this statistic is viewed for multiple volumes and with other statistics, it can indicate whether the latency is caused by the host or fabric.
tiocnt Indicates the cumulative number of volume I/O operations that were examined for I/O throttle (since the node started).
tbw Indicates the cumulative number of blocks of data transfer that was delayed due to I/O throttle (since the node started).
tqueuediocnt Indicates the cumulative number of volume I/O operations were delayed due to I/O throttle (since the node started).
tfailediocnt Indicates the cumulative number of volume I/O operations that were failed due to excessive delay introduced by I/O throttle (since the node started).
tmaxdelay Indicates the maximum delay introduced for any volume I/O by throttle in microseconds (during stats collection interval).
tcumdelay Indicates the cumulative delay introduced for volume I/O operations by throttle in microseconds.
Note: For unmap statistics, it is where an unmap operation is a SCSI unmap or Write same with unmap command.

Table 5 describes the port information that is reported for individual nodes.

Table 5. Statistic collection for node ports
Statistic name Description
bbcz Indicates the total time in microseconds for which the buffer credit counter was at zero. This statistic is only reported by 8 Gbps Fibre Channel ports. For other port types, this statistic is 0.
cbr Indicates the bytes received from controllers.
cbt Indicates the bytes transmitted to disk controllers.
cer Indicates the commands that are received from disk controllers.
Note: The cer metric is always 0.
cet Indicates the commands that are initiated to disk controllers.
dtdc Indicates the number of transfers that experienced excessive data transmission delay.
dtdm Indicates the number of transfers that had their data transmission delay measured.
dtdt Indicates the total time in microseconds for which data transmission was excessively delayed.
har Indicates the count aborted host read operations aborted while a data transfer was in progress. This count includes I/O operations aborted by hosts, and those operations aborted internally by the system.
haw Indicates the count aborted host write operations aborted while a data transfer was in progress. This count includes I/O operations aborted by hosts, and those operations aborted internally by the system.
hbr Indicates the bytes received from hosts.
hbt Indicates the bytes transmitted to hosts.
her Indicates the commands that are received from hosts.
het Indicates the commands that are initiated to hosts.
Note: The het metric is always 0.
hsr Indicates the count of data transfers that were considered slow for host read operations.
hsw Indicates the count of data transfers that were considered slow for host write operations.
icrc Indicates the number of CRC that is not valid.
id Indicates the port identifier for the node.
itw Indicates the number of transmission word counts that are not valid.
lf Indicates a link failure count.
lnbr Indicates the bytes received to other nodes in the same cluster.
lnbt Indicates the bytes transmitted to other nodes in the same cluster.
lner Indicates the commands that are received from other nodes in the same cluster.
lnet Indicates the commands that are initiated to other nodes in the same cluster.
lsi Indicates the lost-of-signal count.
lsy Indicates the loss-of-synchronization count.
pspe Indicates the primitive sequence-protocol error count.
tmp Indicates the SFP temperature in degrees Celsius.
tmpht Indicates the SFP temperature high alarm threshold in degrees Celsius.
txpwr Indicates the TX power in microwatts (µW).
txpwrlt Indicates the TX power low alarm threshold in microwatts (µW).
rmbr Indicates the bytes received to other nodes in the other clusters.
rmbt Indicates the bytes transmitted to other nodes in the other clusters.
rmer Indicates the commands that are received from other nodes in the other clusters.
rmet Indicates the commands that are initiated to other nodes in the other clusters.
rxpwr Indicates the RX power in microwatts (µW).
rxpwrlt Indicates the RX power low alarm threshold in microwatts (µW).
wwpn Indicates the worldwide port name for the node.
Table 6 describes the node information that is reported for each node.
Table 6. Statistic collection for nodes
Statistic name Description
cluster_id Indicates the identifier of the cluster.
cluster Indicates the name of the cluster.
cpu busy - Indicates the total CPU average core busy milliseconds since the node was reset. This statistic reports the amount of the time that the processor spends polling, waiting for work versus doing work. This statistic accumulates from zero.
system - Indicates the total CPU average core busy milliseconds since the node was reset. This statistic reports the amount of the time the processor spends polling, waiting for work versus doing work. This statistic accumulates from zero. This statistic is the same information as the information provided with the cpu busy statistic and eventually replaces the cpu busy statistic.
cpu_core id - Indicates the CPU core ID.
system - Indicates the per-core CPU average core busy milliseconds for system process cores since node was reset.
env obj - Indicates whether enclosure (e) or node (n).
id - Indicates the enclosure or node ID.
p - Indicates the power consumption of the enclosure or node.
t - Indicates the temperature (Celsius) of the enclosure or node.
dimm id - Indicates the memory module ID.
loc - Indicates the location of the memory module.
manu - Indicates the manufacturer of the memory module.
sn - Indicates the serial number of the memory module.
ce - Indicates the number of corrected errors in the memory module.
id Indicates the name of the node.
lrb Indicates the number of logical bytes received from the other node.
lwb Indicates the number of logical bytes sent to the other node.
node_id Indicates the unique identifier for the node.
rb Indicates the number of physical bytes received from the other node.
re Indicates the accumulated receive latency, excluding inbound queue time. This statistic is the latency that is experienced by the node communication layer from the time that an I/O is queued to cache until the time that the cache gives completion for it.
ro Indicates the number of messages or bulk data received.
rq Indicates the accumulated receive latency, including inbound queue time. This statistic is the latency from the time that a command arrives at the node communication layer to the time that the cache completes the command.
wb Indicates the number of physical bytes sent to the other node.
we Indicates the accumulated send latency, excluding outbound queue time. This statistic is the time from when the node communication layer issues a message out onto the Fibre Channel until the node communication layer receives notification that the message arrived.
wo Indicates the number of messages or bulk data sent.
wq Indicates the accumulated send latency, including outbound queue time. This statistic includes the entire time that data is sent. This time includes the time from when the node communication layer receives a message and waits for resources, the time to send the message to the remote node, and the time that is taken for the remote node to respond.

Table 7 describes the statistics collection for volumes.

Table 7. Cache statistics collection for volumes and volume copies
Statistic Acronym Cache statistics for volumes Cache statistics for volume copies Cache partition statistics for volumes Cache partition statistics for volume copies Overall node cache statistics Cache statistics for mdisks Cache statistics for data reduction pools Space recommendation Units and state

read ios 

ri 

Yes 

Yes 

  

 

 

 

     ios, cumulative

write ios 

wi 

Yes 

Yes 

  

 

 

 

     ios, cumulative

read misses 

r 

Yes 

Yes 

  

 

 

 

     sectors, cumulative

read hits 

rh 

Yes 

Yes 

  

 

 

 

     sectors, cumulative

flush_through writes 

ft 

Yes 

Yes 

  

 

 

 

     sectors, cumulative

fast_write writes 

fw 

Yes 

Yes 

  

 

 

 

     sectors, cumulative

write_through writes 

wt 

Yes 

Yes 

  

 

 

 

     sectors, cumulative

write hits 

wh 

Yes 

Yes 

  

 

 

 

     sectors, cumulative

prefetches 

p 

 

Yes 

  

 

 

 

     sectors, cumulative

prefetch hits (prefetch data that is read)

ph 

 

Yes 

  

 

 

 

     sectors, cumulative

prefetch misses (prefetch pages that are discarded without any sectors read)

pm 

 

Yes 

  

 

 

 

     pages, cumulative

modified data

m

Yes

Yes

             sectors, snapshot, non-cumulative

read and write cache data

v

Yes

Yes

             sectors snapshot, non-cumulative

destages 

d 

Yes 

Yes 

  

 

 

 

  

 

 sectors, cumulative

fullness Average 

fav 

 

 

Yes 

Yes 

 

 

Yes

   %, non-cumulative

fullness Max 

fmx 

 

 

Yes 

Yes 

 

 

Yes 

   %, non-cumulative

fullness Min 

fmn 

 

 

Yes 

Yes 

 

 

Yes

   %, non-cumulative

Destage Target Average 

dtav 

 

 

  

Yes 

 

Yes 

Yes

   IOs capped 9999, non-cumulative

Destage Target Max 

dtmx

 

 

  

Yes 

 

 

Yes 

   IOs, non-cumulative

Destage Target Min 

dtmn

 

 

  

Yes 

 

 

Yes

   IOs, non-cumulative

Destage In Flight Average 

dfav 

 

 

  

Yes 

 

Yes 

Yes 

   IOs capped 9999, non-cumulative

Destage In Flight Max 

dfmx

 

 

  

Yes 

 

Yes 

   IOs, non-cumulative

Destage In Flight Min 

dfmn

 

 

  

Yes 

 

 

Yes 

   IOs, non-cumulative

destage latency average 

dav 

Yes 

Yes 

Yes 

Yes 

Yes 

Yes 

Yes 

   µs capped 9999999, non-cumulative

destage latency max 

dmx 

    

Yes 

Yes 

Yes 

  

Yes 

   µs capped 9999999, non-cumulative

destage latency min 

dmn 

    

Yes 

Yes 

Yes 

 

Yes 

   µs capped 9999999, non-cumulative

destage count 

dcn 

Yes 

Yes

Yes 

Yes 

Yes 

 

Yes

   ios, non-cumulative

stage latency average 

sav 

Yes 

Yes 

  

 

Yes 

 

     µs capped 9999999, non-cumulative

stage latency max 

smx 

 

 

  

 

Yes 

 

     µs capped 9999999, non-cumulative

stage latency min 

smn 

 

 

  

 

Yes 

 

     µs capped 9999999, non-cumulative

stage count 

scn 

Yes 

Yes

  

 

Yes 

 

     ios, non-cumulative

prestage latency average 

pav 

 

Yes 

  

 

Yes 

 

     µs capped 9999999, non-cumulative

prestage latency max 

pmx 

 

 

  

 

Yes 

 

     µs capped 9999999, non-cumulative

prestage latency min 

pmn 

 

 

  

 

Yes 

 

     µs capped 9999999, non-cumulative

prestage count 

pcn 

 

Yes 

  

 

Yes 

 

     ios, non-cumulative

Write Cache Fullness Average 

wfav 

 

 

  

 

Yes 

 

     %, non-cumulative

Write Cache Fullness Max 

wfmx 

 

 

  

 

Yes 

 

     %, non-cumulative

Write Cache Fullness Min 

wfmn 

 

 

  

 

Yes 

 

     %, non-cumulative

Read Cache Fullness Average 

rfav 

 

 

  

 

Yes 

 

     %, non-cumulative

Read Cache Fullness Max 

rfmx 

 

 

  

 

Yes 

 

     %, non-cumulative

Read Cache Fullness Min 

rfmn 

 

 

  

 

Yes 

 

     %, non-cumulative

Pinned Percent 

pp 

Yes 

Yes 

Yes 

Yes 

Yes 

 

Yes

   % of total cache snapshot, non-cumulative

data transfer latency average 

tav 

Yes 

Yes 

  

 

 

 

     µs capped 9999999, non-cumulative

Track Lock Latency (Exclusive) Average 

teav 

Yes 

Yes 

  

 

 

 

     µs capped 9999999, non-cumulative

Track Lock Latency (Shared) Average 

tsav 

Yes 

Yes 

  

 

 

 

     µs capped 9999999, non-cumulative

Cache I/O Control Block Queue Time 

hpt 

 

 

  

 

Yes 

 

     Average µs, non-cumulative

Cache Track Control Block Queue Time 

ppt 

 

 

  

 

Yes 

 

     Average µs, non-cumulative

Owner Remote Credit Queue Time 

opt 

 

 

  

 

Yes 

 

     Average µs, non-cumulative

Non-Owner Remote Credit Queue Time 

npt 

 

 

  

 

Yes 

 

     Average µs, non-cumulative

Admin Remote Credit Queue Time 

apt 

 

 

  

 

Yes 

 

     Average µs, non-cumulative

Cdcb Queue Time 

cpt 

 

 

  

 

Yes 

 

     Average µs, non-cumulative

Buffer Queue Time 

bpt 

 

 

  

 

Yes 

 

     Average µs, non-cumulative

Hardening Rights Queue Time 

hrpt 

 

 

  

 

Yes 

 

     Average µs, non-cumulative
vdisk size vdisksz               Yes Sectors, non-cumulative
compressed size cmpsz               Yes Sectors, non-cumulative
Note: Any statistic with a name av, mx, mn, and cn is not cumulative. These statistics reset every statistics interval. For example, if the statistic does not have a name with name av, mx, mn, and cn, and it is an Ios or count, it will be a field containing a total number.
  • The term pages means in units of 4096 bytes per page.
  • The term sectors means in units of 512 bytes per sector.
  • The term µs means microseconds.
  • Non-cumulative means totals since the previous statistics collection interval.
  • Snapshot means the value at the end of the statistics interval (rather than an average across the interval or a peak within the interval).
There are three types of data reduction properties per data reduction pool.
  • dca - these statistics are related to the data stored within the data reduction pool.
  • rca - these statistics are related to I/O to manage the background garbage collection processes of the data reduction pool.
  • jca - these statistics are related to journaling operations for the metadata that manages the data reduction pool.

Table 8 provides details about the statistic collection for volume performance.

Table 8. Performance statistics for volume. This table lists the performance statistics that is reported for individual volume.
Statistic name Description
entav Internal cyber resiliency statistic average
entcn Internal cyber resiliency statistic count
Table 9. Statistic collection for volume cache per individual nodes. This table describes the volume cache information that is reported for individual nodes.
Statistic name Description
cm Indicates the number of sectors of modified or dirty data that are held in the cache.
ctd Indicates the total number of cache destages that were initiated writes, submitted to other components as a result of a volume cache flush or destage operation.
ctds Indicates the total number of sectors that are written for cache-initiated track writes.
ctp Indicates the number of track stages that are initiated by the cache that are prestage reads.
ctps Indicates the total number of staged sectors that are initiated by the cache.
ctrh Indicates the number of total track read-cache hits on prestage or non-prestage data. For example, a single read that spans two tracks where only one of the tracks obtained a total cache hit, is counted as one track read-cache hit.
ctrhp Indicates the number of track reads received from other components, which are treated as cache hits on any prestaged data. For example, if a single read spans two tracks where only one of the tracks obtained a total cache hit on prestaged data, it is counted as one track that is read for the prestaged data. A cache hit that obtains a partial hit on prestage and non-prestage data still contributes to this value.
ctrhps Indicates the total number of sectors that are read for reads received from other components that obtained cache hits on any prestaged data.
ctrhs Indicates the total number of sectors that are read for reads received from other components that obtained total cache hits on prestage or non-prestage data.
ctr Indicates the total number of track reads received. For example, if a single read spans two tracks, it is counted as two total track reads.
ctrs Indicates the total number of sectors that are read for reads received.
ctwft Indicates the number of track writes received from other components and processed in flush through write mode.
ctwfts Indicates the total number of sectors that are written for writes that are received from other components and processed in flush through write mode.
ctwfw Indicates the number of track writes received from other components and processed in fast-write mode.
ctwfwsh Indicates the track writes in fast-write mode that were written in write-through mode because of the lack of memory.
ctwfwshs Indicates the track writes in fast-write mode that were written in write through due to the lack of memory.
ctwfws Indicates the total number of sectors that are written for writes that are received from other components and processed in fast-write mode.
ctwh Indicates the number of track writes received from other components where every sector in the track obtained a write hit on already dirty data in the cache. For a write to count as a total cache hit, the entire track write data must already be marked in the write cache as dirty.
ctwhs Indicates the total number of sectors that are received from other components where every sector in the track obtained a write hit on already dirty data in the cache.
ctw Indicates the total number of track writes received. For example, if a single write spans two tracks, it is counted as two total track writes.
ctws Indicates the total number of sectors that are written for writes that are received from components.
ctwwt Indicates the number of track writes received from other components and processed in write through write mode.
ctwwts Indicates the total number of sectors that are written for writes that are received from other components and processed in write through write mode.
cv Indicates the number of sectors of read and write cache data that is held in the cache.

Table 10 describes the XML statistics specific to an IP Partnership port.

Table 10. XML statistics for an IP partnership port
Statistic name Description
ipbz Indicates the average size (in bytes) of data that is being submitted to the IP partnership driver since the last statistics collection period.
iprc Indicates the total bytes that are received before any decompression takes place.
ipre Indicates the bytes retransmitted to other nodes in other clusters by the IP partnership driver.
iprt Indicates the average round-trip time in microseconds for the IP partnership link since the last statistics collection period.
iprx Indicates the bytes received from other nodes in other clusters by the IP partnership driver.
ipsz Indicates the average size (in bytes) of data that is being transmitted by the IP partnership driver since the last statistics collection period.
iptc Indicates the total bytes that are transmitted after any compression (if active) takes place.
iptx Indicates the bytes transmitted to other nodes in other clusters by the IP partnership driver.

Table 11 describes an IP partnership information that is reported for each partnership. It does not include the I/O statistics for high-speed Ethernet partnerships.

Table 11. Statistics collection for an individual IP partnership
Statistic name Description
index Indicates the index for which the IP partnership is configured.
Note: To view index parameter, use lspartnership -gui command.
cluster Indicates the name of the remote cluster.
remote_cluster_id Indicates the ID of the remote cluster.
port_id Indicates the selected port_id for IP partnership connection on local node.
Note: To view port_id parameter, use lsportethernet command.
ipbz Indicates the average size (in bytes) of data that is being submitted to the IP partnership driver since the last statistics collection period.
iprc Indicates the total bytes that are received before any decompression takes place.
ipre Indicates the bytes retransmitted to other nodes in other clusters by the IP partnership driver.
iprt Indicates the average round-trip time in microseconds for the IP partnership link since the last statistics collection period.
iprx Indicates the bytes received from other nodes in other clusters by the IP partnership driver.
ipsz Indicates the average size (in bytes) of data that is being transmitted by the IP partnership driver since the last statistics collection period.
iptc Indicates the total bytes that are transmitted after any compression (if active) takes place.
iptx Indicates the bytes transmitted to other nodes in other clusters by the IP partnership driver.
Table 12 describes the offload data transfer (ODX) Vdisk and node level I/O statistics.
Table 12. ODX VDisk and node level statistics
Statistic name Acronym Description
Read cumulative ODX I/O latency orl Cumulative total read latency of ODX I/O per VDisk. The unit type is micro-seconds (US).
Write cumulative ODX I/O latency owl Cumulative total write latency of ODX I/O per VDisk. The unit type is micro-seconds (US).
Total transferred ODX I/O read blocks oro Cumulative total number of blocks that are read and successfully reported to the host, by ODX WUT command per VDisk. It is represented in blocks unit type.
Total transferred ODX I/O write blocks owo Cumulative total number of blocks that are written and successfully reported to the host, by ODX WUT command per VDisk. It is represented in blocks unit type.
Wasted ODX I/Os oiowp Cumulative total number of wasted blocks that are written by ODX WUT command per node. It is represented in blocks unit type.
WUT failure count otrec Cumulative total number of failed ODX WUT commands per node. It includes WUT failures due to a token revocation and expiration.
Table 13 describes the statistics collection for cloud per cloud account ID.
Table 13. Statistics collection for cloud per cloud account ID
Statistic name Acronym Description
id id Cloud account ID
Total Successful Puts puts Total number of successful PUT operations
Total Successful Gets gets Total number of successful GET operations
Bytes Up bup Total number of bytes successfully transferred to the cloud
Bytes Down bdown Total number of bytes successfully downloaded/read from the cloud
Up Latency uplt Total time that is taken to transfer the data to the cloud
Down Latency dwlt Total time that is taken to download the data from the cloud
Down Error Latency dwerlt Time that is taken for the GET errors
Part Error Latency pterlt Total time that is taken for part errors
Persisted Bytes Down prbdw Total number of bytes successfully downloaded from the cloud and persisted on the local storage that were part of successful GET operation
Persisted Bytes Up prbup Total number of bytes successfully transferred to the cloud and persisted on the cloud that were part of successful PUT operation. The difference is that you might have a 100 bytes file, of which you successfully had 80 bytes sent to the cloud through a PUT operation, but the last data transfer cycle carrying 20 bytes errored out, and the entire request failed. In that case, the statistics indicates: BYTES_UP = 80 and PERSISTED_BYTES_UP = 0
Persisted Down Latency prdwlt Total time that is taken to download the data from the cloud that were part of successful GET operation
Persisted Up Latency pruplt Total time that is taken to transfer the data to the cloud that were part of successful PUT operation
Failed Gets flgt Total number of failed GET operations
Failed Puts flpt Total number of failed PUT operations
Get Errors gter Total number of times a read from the cloud failed (including the last retry that failed the GET request)
Get Retries gtrt Total number of GET retries
Part Errors pter Total number of part errors. It is the count if multi part upload occurs. The part refers to the multi-part upload scenario.
Parts Put ptpt Total number of parts that are successfully transferred to the cloud
Persisted parts prpt Total number parts successfully persisted on the cloud that were part of successful put operation
Put retries ptrt Total number of PUT retries
Throttle upload latency tuplt Average delay introduced due to setting upload bandwidth limit
Throttle download latency tdwlt Average delay introduced due to setting download bandwidth limit
Throttle upload bandwidth utilization percentage tupbwpc Bandwidth utilization in percentage of configured upload bandwidth limit
Throttle download bandwidth utilization percentage tdwbwpc Bandwidth utilization in percentage of configured download bandwidth limit
Table 14 describes the statistics collection for cloud per VDisk.
Table 14. Statistics collection for cloud per VDisk
SNo Statistic name Acronym Description
1 blocks up bup Number of blocks that are uploaded in the cloud.
2 blocks down bdn Number of blocks that are downloaded from cloud.
Note: A block is 512 bytes.

Retrieving statistics files

To view the statistics files, you need to retrieve them from the /dumps/iostats/ directory on the configuration node.

Use the Secure Copy (SCP) or SSH File Transfer Protocol (SFTP) to copy the statistics files from the configuration node to a local workstation. The system copies all the files from the /dumps/iostats/ directory on the configuration node to the /tmp/ directory on a local machine. To verify a particulate file in the individual partnership statistic details, check Nn_stats.

Fields

The following fields are available for user definition:
Interval
Specify the interval in minutes between the collection of statistics. You can specify 1 - 60 minutes in increments of 1 minute. Statistics must be set to 1 or 5 minute intervals when sending data to Storage Insights.
scp superuser@cluster_name:/dumps/iostats/* /tmp

XML formatting example for IP partnership statistics

The following example shows the summed up view for an IP partnership statistics:

<port id="21"
type="IPREP"
type_id="1"
wwpn="0x0000000000000000"
fc_wwpn=""
fcoe_wwpn=""
sas_wwn=""
iqn=""
hbt="266" hbr="0" het="0" her="4"
cbt="0" cbr="306" cet="6" cer="0"
lnbt="0" lnbr="0" lnet="0" lner="0"
rmbt="54792236296" rmbr="281758748" rmet="27812092" rmer="27530254"
iptx="47383884117" iprx="7213917137" ipre="30408" ipsz="611"
ipbz="254" iprt="265" iptc="40307617091" iprc="83362750" />

The following example shows an individual IP partnership view:

<partnership_ipperf index="1" cluster="fab3_recovery0" remote_cluster_id="0x000002043da02218" port_id="3"
iptx="16824170146" iprx="3571399065" ipre="0" ipsz="999"
ipbz="434" iprt="86" iptc="13298305502" iprc="23648286" />
<partnership_ipperf index="2" cluster="fab3_recovery1" remote_cluster_id="0x000002043c2061e0" port_id="4"
iptx="30559713971" iprx="3642518072" ipre="30408" ipsz="1990"
ipbz="916" iprt="77" iptc="27009311589" iprc="59714464" />