How the condition of a resource is determined

Edit online

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.

To determine the condition of top-level resources (storage systems, servers, hypervisors, fabrics, and switches), IBM Spectrum Control uses the status of those resources and the status of their internal resources.

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

Table 1. Internal resources that are used to determine the condition of top-level resources
Top-level resource	Internal resources that are used to determine the condition of a top-level resource
Fabric	Ports Switches
Switch	Blades Inter-switch connections Logical switches Ports
	Switches Trunks Blades Ports
Hypervisor	Disks Virtual machines VMDKs
Server	Controllers Disks
Block storage system	Disks Drives External disks FC ports I/O groups IP ports Managed disks Modules , Nodes Pools RAID arrays Volumes
File storage system	Network shared disks Nodes
Object storage system	Network shared disks Nodes

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

Normal
Warning
Error

Exceptions:

Statuses that are acknowledged are treated as normal and contributes to determine the condition of related or higher-level resources.
Events received through Call Home with cloud services do not affect the condition of a top-level resource.

Internal resources for a top-level resource might have different statuses. IBM Spectrum ControlIBM 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, the overall condition of a storage system is Error, because it is the most critical status that was detected on internal resources.

The following table shows some of the possible combinations of statuses and the resulting, overall condition for a top-level resource.

Table 2. Propagation of the statuses for resources
Error	Unreachable ¹	Warning	Normal	Unknown ²	Resulting condition 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 condition of a top-level resource.