How the condition of a resource is determined
To determine the condition of top-level resources, such as storage systems, fabrics, and switches, IBM Storage Insights uses the status of their internal resources and data collection status.
Top-level resource | Internal resources that are used to determine the condition of a top-level resource |
---|---|
Fabric |
|
Switch |
|
Chassis |
|
Block storage system |
|
File storage system |
|
Object storage system |
|
- Normal
- Warning
- Error
- Statuses that are acknowledged are used to calculate the overall condition of a top-level resource.
- Events that are detected through Call Home affect the overall condition of a top-level resource. For example, a critical error event is detected by Call Home, but the status of the storage system and its internal resources are normal based on metadata collection. In this case, the condition of the top-level resource changes to error.
Internal resources for a top-level resource might have different statuses. IBM Storage Insights uses the most critical status of an internal resource to help determine the overall condition of a top-level resource. For example, in a storage system, a port might have an Error status, a pool might have a Warning status, and multiple controllers might have an Unknown status. In this case, if the storage system itself has a normal status, its overall condition is Error because it is the most critical status that was detected on internal resources.
Error![]() |
Unreachable 1![]() |
Warning ![]() |
Normal ![]() |
Unknown 2![]() |
Resulting condition for a top-level resource |
---|---|---|---|---|---|
X | ![]() |
||||
X | ![]() |
||||
X | X | ![]() |
|||
X | ![]() |
||||
X | X | ![]() |
|||
X | X | X | ![]() |
||
X | ![]() |
||||
X | X | ![]() |
|||
X | X | X | ![]() |
||
X | X | X | X | ![]() |
|
X | ![]() |
||||
X | X | ![]() |
|||
X | X | X | ![]() |
||
X | X | X | X | ![]() |
|
X | X | X | X | X | ![]() |
Note:
|