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 LUN In the graph of this measure however, states are represented using the numeric equivalents only.

Numeric Value	Measure Value
0	OK
1	In Service
2	Power Mode
3	Completed
4	Starting
5	Dormant
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 LUN. In the graph of this measure however, operational states are represented using the numeric equivalents only.

Typically, the detailed state will describe why the storage array is in a particular operational state. For instance, if the operationalStatus measure reports the value Stopping for a storage array, then this measure will explain why that storage array 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 LUN. In the graph of this measure however, detailed operational states are represented using the numeric equivalents only.

You may then want to take a look at the reads and writes measures to understand what to fine-tune – the load-balancing algorithm for read requests or that of the write requests.

Typically, from a striped LUN, OS disk formatting would create a partition, with a disk partition header. Then, an OS file system is created on that disk partition. As OS files are added to the the file system. the first file will have a piece sitting on the first stripe element of the LUN (for example, 64 KB). So, if we try to do an I/O of 64 KB on this OS file, part of the data will end up going to the first stripe element, which belongs to one physical drive, and the rest to the second drive that makes up the striped LUN. This type of drive crossing is called a stripe crossing. Striped crossing results in less efficient dispatches of I/O requests from the CLARiion storage processors to the back-end disk drives, thereby reducing request service efficiency. This is why, ideally, the value of this measure should be very low.