|
Measures reported by SANRAIDPortTest
Storage ports help the storage processors receive and process I/O requests. By periodically checking port status and measuring the I/O load on the ports, you can identify overloaded ports and thus proactively detect potential/existing load-balancing irregularities and/or processing bottlenecks with the ports. The SANRAIDPortTest test facilitates this port check. For every port configured for the storage processors supported by the storage system, this test reports the port state, the I/O load on the ports, and the processing ability of the ports. In the process, the test not only points administrators to overloaded ports, but also puts a finger on ports that are slow when processing I/O requests.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| healthState |
Indicates how healthy this port currently is. |
|
The values that this measure can report and their corresponding numeric values are discussed in the table below:
| Numeric Value |
Measure Value |
| 0 |
OK |
| 1 |
Unknown |
| 2 |
Degraded/Warning |
| 3 |
Minor failure |
| 4 |
Major failure |
| 5 |
Critical failure |
| 6 |
Non-recoverable error |
Note:
By default, this measure reports the Measure Values discussed above to indicate the state of a port. In the graph of this measure however, states are represented using the numeric equivalents only. |
| operationalStatus |
Indicates the current operational state of this port. |
|
The values that this measure can report and their corresponding numeric values are discussed in the table below:
| Numeric Value |
Measure Value |
| 0 |
OK |
| 1 |
In Service |
| 2 |
Power Mode |
| 3 |
Completed |
| 4 |
Starting |
| 5 |
Dormat |
| 6 |
Other |
| 7 |
Unknown |
| 8 |
Stopping |
| 9 |
Stressed |
| 10 |
Stopped |
| 11 |
Supporting Entity in Error |
| 12 |
Degraded or Predicted Failure |
| 13 |
Predictive Failure |
| 14 |
Lost Communication |
| 15 |
No Contact |
| 16 |
Aborted |
| 17 |
Error |
| 18 |
Non-Recoverable Error |
Note:
By default, this measure reports the Measure Values discussed above to indicate the operational state of a port. In the graph of this measure however, operational states are represented using the numeric equivalents only. |
| detailedStatus |
Describes the current operational state of this port. |
|
This measure will be reported only if the API provides a detailed operational state.
Typically, the detailed state will describe why the port is in a particular operational state. For instance, if the Operational status measure reports the value Stopping for a port, then this measure will explain why that port is being stopped.
The values that this measure can report and their corresponding numeric values are discussed in the table below:
| Numeric Value |
Measure Value |
| 0 |
Online |
| 1 |
Success |
| 2 |
Power Saving Mode |
| 3 |
Write Protected |
| 4 |
Write Disabled |
| 5 |
Not Ready |
| 6 |
Removed |
| 7 |
Rebooting |
| 8 |
Offline |
| 9 |
Failure |
Note:
By default, this measure reports the Measure Values discussed above to indicate the detailed operational state of a port. In the graph of this measure however, detailed operational states are represented using the numeric equivalents only. |
| dataTransmitted |
Indicates the rate at which data was transmitted by this port. |
MB/Sec |
|
| iops |
Indicates the rate at which I/O operations were performed on this port. |
IOPS |
Compare the value of this measure across ports to know which port handled the maximum number of I/O requests and which handled the least. If the gap between the two is very high, then it indicates serious irregularities in load-balancing across ports. |
|