XIO Initiators Test
The XtremIO Storage Array uses the term “Initiators” to refer to ports which can access a volume. Initiators can be managed by assigning them to an Initiator Group. The Initiators within an Initiator Group share access to one or more of the cluster's volumes. This test auto discovers the initiators of the target storage array and reports the current connection state. In addition, this test helps administrators to figure out the initiator that is busy processing I/O requests along initiators, detect irregularities in the distribution of I/O load across the initiators and thus enables administrators to initiate pre-emptive measures.
Target of the test : An EMC XtremIO Storage array
Agent deploying the test : A remote agent
Outputs of the test : One set of results for each initiator of the target EMC XtremIO being monitored.
| Parameter | Description |
|---|---|
|
Test Period |
How often should the test be executed. |
|
Host |
The IP address of the storage device for which this test is to be configured. |
|
Port |
The port number at which the storage array listens. The default is NULL. |
|
XtremIO User and XtremIO Password |
Provide the credentials of a user who has read only privileges to access the XtremIO storage array in the XtremIO User and XtremIO Password text boxes. |
|
Confirm Password |
Confirm the password by retyping it here. |
|
XMS IP |
This parameter is applicable only for EMC XtremIO 4.x. By default, None will be chosen from this list. If the target EMC XtremIO storage array is within a XMS Management Server that is auto-discovered, then the IP or host name of that XMS Management Server will be displayed in this list. Select that particular XMS IP to configure this test. If you wish to monitor an EMC XtremIO Storage Array that is either not an integral part of the auto-discovered XMS Management Server or a brand new EMC XtremIO Storage Array, choose the Other option. This will enable you to add a new XMS Managament Server. To know how to add a new XMS Management Server, refer to Adding a new XMS. |
|
SSL |
The eG agent collects performance metrics by invoking Restful APIs on the target Storage array. Typically, the Restful APIs can be invoked through the HTTP or the HTTPS mode. By default, the eG agent invokes the Restful APIs using the HTTPS mode. This is why, the SSL flag is set to Yes by default. If the target storage array is not SSL-enabled, then the Restful APIs can be accessed through the HTTP mode only. In this case, set the SSL flag to No. |
| Measurement | Description | Measurement Unit | Interpretation | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
Initiator connection state |
Indicates the connection state of this initiator to the XtremIO storage array via at least one target port. |
|
The values reported by this measure and their numeric equivalents are available in the table below:
Note: This measure reports the Measure Values listed in the table above to indicate the connection state of this initiator. However, in the graph, this measure is indicated using the Numeric Values listed in the above table. |
||||||||
|
Bandwidth |
Indicates the amount of data utilized for performing I/O operations per second through this initiator. |
MB/Sec |
|
||||||||
|
Read bandwidth |
Indicates the amount of data utilized for performing read I/O operations per second through this initiator. |
MB/Sec |
|
||||||||
|
Write bandwidth |
Indicates the amount of data utilized for performing write I/O operations per second through this initiator. |
MB/Sec |
|
||||||||
|
IOPS |
Indicates the rate at which I/O operations were performed through this initiator during the last measurement period. |
IOPS |
Compare the value of this measure across the initiators to know which initiator handled the maximum number of I/O operations and which handled the least. If the gap between the two is very high, then it indicates serious irregularities in I/O operations across the initiators. |
||||||||
|
Read IOPS |
Indicates the number of read operations performed through this initiator per second. |
IOPS |
|
||||||||
|
Write IOPS |
Indicates the number of the write operations performed through this initiator per second. |
IOPS |
|
||||||||
|
Read latency |
Indicates the time taken to perform read operations through this initiator. |
msec |
A low value is desired for this measure. A high value indicates that the read and write operations take too long to execute which directly affects the performance of the XtremIO Storage Array. |
||||||||
|
Write latency |
Indicates the time taken to perform write operations through this initiator. |
msec |
|||||||||
|
Average latency |
Indicates the average time taken to perform I/O operations through this initiator. |
msec |
|
||||||||
|
Reads |
Indicates the rate at which the read operations were performed through this initiator during the last measurement period. |
Reads/sec |
Compare the value of this measure across initiators to know which initiator handled the maximum number of read requests and which handled the least. |
||||||||
|
Writes |
Indicates the rate at which the write operations were performed through this initiator during the last measurement period. |
Writes/sec |
Ideally, the value of this measure should be high. A steady dip in this measure value could indicate a potential writing bottleneck. By comparing the value of this measure across the initiators, you can quickly identify the initiator which is the slowest in processing write requests. |
||||||||
|
Data reads |
Indicates the rate at which data was read through this initiator during the last measurement period. |
MB/Sec |
Compare the values of these measures across the initiators to identify the slowest initiator in terms of servicing read and write requests (respectively). |
||||||||
|
Data written |
Indicates the rate at which data was written through this initiator during the last measurement period. |
MB/Sec |
|||||||||
|
Average read size |
Indicates the amount of data read through this initiator per I/O operation during the last measurement period. |
MB/Op |
Compare the values of these measures across the initiators to identify the slowest initiator in terms of servicing read and write requests (respectively). |
||||||||
|
Average write size |
Indicates the amount of data written through this initiator per I/O operation during the last measurement period. |
MB/Op |
