Ibm Controller Traffic Test
This test monitors the I/O and transaction traffic on each controller on a storage device, and reports irregularities in load balancing across controllers.
Target of the test : An IBM DS Raid Storage device
Agent deploying the test : A remote agent
Outputs of the test : One set of results for each controller on the storage device being monitored
Parameter | Description |
---|---|
Test Period |
How often should the test be executed . |
Host |
The IP address of the storage device |
Port |
The port number at which the specified Host listens. By default, this is NULL. |
SMCliLocation |
The test uses the command-line utility, SMcli.exe, to collect the required statistics from the IBM DS Raid Storage device. To enable the test to run the SMcli.exe, provide the full path to the exe in the SMCliLocation text box. Note: If the SMcli.exe resides in say, C:\Program Files\IBM_DS\client, your SMCliLocation should be : C:\Progra~1\IBM_DS\client. On the other hand, if the SMcli.exe resides in say, C:\Program Files (x86)\IBM_DS\client, your SMCliLocation should be: C:\Progra~2\IBM_DS\client. |
Alternate Controller IP |
By default, the Alternate Controller IP text box is set to none. This implies that by default, the storage device being monitored supports a single controller only, and the IP address of this controller is the same as the IP address of the target Host. Sometimes, a storage device could be configured with two/more controllers, so as to provide fail-over services - in other words, if the primary controller is down, then one of the alternate controllers will take over from the primary to provide the critical storage services. In this case, you can provide a comma-separated list of alternate controller IPs in the Alternate Controller IP text box. |
Timeout |
Indicate the duration (in seconds) for which this test should wait for a response from the storage device. By default, this is set to 30 seconds. |
Measurement |
Description |
Measurement Unit |
Interpretation |
---|---|---|---|
Current IO Operations |
Indicates the number of IO operations that occurred on this controller during the last measurement period. |
Number |
Comparing the value of this measure across controllers can reveal whether any controller is overloaded. If so, this revelation could turn the spotlight on imbalances in load distribution across the controllers. |
Percent read operations |
Indicates the percent of read operations that occurred on this controller. |
Percent |
|
Percent write operations |
Indicates the percentage of write operations that occurred on this controller. |
Percent |
|
Cache hit percent |
Indicates the percentage of requests to this controller that were served from the cache. |
Percent |
A high value is ideally desired for this measure. A low value could imply that most of the data requested is not in the cache, which in turn could result in a high degree of direct disk accesses. |
Transaction rate |
Indicates the rate of transactions to this controller. |
KB/Sec |
|
IO operations rate |
Indicates the rate of I/O operations to this controller. |
IO/Sec |
|