eG Monitoring
 

Measures reported by NAUSDBlkPrtclIOTest

Volumes are data containers. Clients can access the data in volumes through the access protocols supported by Data ONTAP. These protocols include Network File System (NFS), Common Internet File System (CIFS), HyperText Transfer Protocol (HTTP), Web-based Distributed Authoring and Versioning (WebDAV), Fibre Channel Protocol (FCP), and Internet SCSI (iSCSI).

Obviously, if one/more of these protocols are suddenly rendered unavailable, then clients will not be able to access critical data through these protocols. Moreover, whenever request processing delays are noticed, it becomes necessary for administrators to determine which protocol took the longest to perform read/write operations, so that slow protocol services can be identified.

The NetApp Block I/O Protocol test provides these protocol-centric insights. For every protocol used for accessing data volumes, this test reports the availability of the protocol service, the rate of I/O operations performed through each protocol, and the time taken by each protocol to process read-write requests, so that problem-prone protocols can be accurately identified.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
is_Available Indicates whether this protocol service is currently available.   This measure reports a value Yes if this protocol service is currently available and a value No if this protocol service is not available.

The values reported by this measure and their numeric equivalents are available in the table below:

Measure Value Numeric Value
Yes 1
No 0

Note:

This measure reports the Measure Values listed in the table above while indicating whether this protocol service is currently available. However, in the graph of this measure, the state is indicated using only the Numeric Values listed in the above table.

Total_ops Indicates the rate at which operations were performed by users through this block protocol. Ops/sec  
Latency Indicates the average time taken for performing the operations through this protocol. Milliseconds A low value is desired for this measure.

When users complaint of slowdowns when accessing data volumes, you can compare the value of this measure across protocols to know which protocol took the longest to perform the read-write operations.

Read_ops Indicates the rate at which the read operations are performed across all LUNs of this storage system through this protocol. Ops/sec Very high values for these measures are indicative of the existence of road-blocks to rapid reading/writing by the storage device.

By observing the variations in these measures over time, you can understand whether the latencies are sporadic or consistent. Consistent delays in reading/writing could indicate that there are persistent bottlenecks (if any) in the storage device to speedy I/O processing.

Read_latency Indicates the average time taken to perform read operations across all LUNs through this protocol. Milliseconds
Read_data Indicates the rate at which data is read from this storage system through this protocol. Bytes/sec
Write_ops Indicates the rate at which the write operations were performed on the LUNs of this storage system through this protocol. Ops/sec
Write_latency Indicates the average time taken to perform write operations on the LUNs of this storage system through this protocol. Milliseconds
Write_data Indicates the rate at which data is written to the LUNs of this storage system through this protocol. Bytes/sec
Partner_read_latency Indicates the average time taken to perform read operations across all the LUNs of the partner system (i.e., either the master/slave in a cluster setup of this storage system) through this protocol. Milliseconds
Partner_write_latency Indicates the average time taken to perform write operations on the LUNs of the partner system (i.e., either the master/slave in a cluster setup of this storage system) through this protocol. Milliseconds