How the condition of a resource is determined

To determine the health (condition in classic UI) 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. You can also choose to include critical and warning alerts while determining the storage system health.

Note:

By default, storage system health is determined based on the status of its internal resources. You can also choose to include critical and warning severity alerts in the health determination. If you include alerts, then in IBM Storage Insights Pro, both Storage Insights and device alerts are considered. In the free version, only device alerts are considered. Device alerts are received directly from monitored block storage systems through Call Home with cloud services and are shown in the IBM Storage Insights GUI.
To include alerts in storage system health determination, go to Settings > Storage system health, select the alert types that you want to include, and then click Save. If you are in the classic UI, go to Configuration > Settings, select the alert types under Storage System Condition section, and save the changes. Only user with the Admin role can choose to include the alert to determine the storage system health.
In the modern UI of IBM Storage Insights, top-level resources, such as storage systems, display Health, while in the classic UI the same value is shown as Condition. Internal resources, such as disks, display Status in both UI.

The statuses of the following internal resources are used to calculate the overall health of a top-level resource.

Table 1. Internal resources that are used to determine the Health of top-level resources
Top-level resource	Internal resources that are used to determine the Health of a top-level resource
Fabric	Trunks Switches Ports Zone Sets
Switch	Trunks Ports
Chassis	Switches Trunks Blades Ports
Block storage system	Disks Drives Enclosures External disks FC ports I/O groups IP ports Managed disks Modules , Nodes Pools RAID arrays Device adapters Host adapters Volumes
File storage system	Network shared disks Nodes
Object storage system	Network shared disks Nodes

The following statuses of internal resources are used to calculate the Health of top-level resources:

Normal
Warning
Error

Exception: Statuses that are acknowledged are treated as normal and contributes to determine the Health of related or higher-level resources.

Internal resources for a top-level resource might have different statuses. IBM Storage Insights uses the most critical status of an internal resource to determine the overall Health 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, the overall Health of a storage system is Error, because it is the most critical status that was detected on internal resources.

The following table shows examples of internal resource statuses and the resulting overall health of a top-level resource.

Table 2. Propagation of the statuses for resources
Error	Unreachable ¹	Warning	Normal	Unknown ²	Resulting health for a top-level resource
				X	Unknown
			X		Normal
			X	X	Normal
		X			Warning
		X		X	Warning
		X	X	X	Warning
	X				Unreachable
	X			X	Unreachable
	X		X	X	Unreachable
	X	X	X	X	Unreachable
X					Error
X				X	Error
X			X	X	Error
X		X	X	X	Error
X	X	X	X	X	Error
Note: The condition alert for a storage system is suppressed when a component status alert is generated to avoid duplicate alerts for the same triggering condition. However, the overall health of the storage system is still determined based on the status of its internal components. The Unreachable status applies only to top-level resources. The Unknown status of an internal resource is not used to determine the health of a top-level resource.