HP Insight Management WBEM Providers for HP integrated VMware ESXi 5.0 U1 June 2012 Profiles

16 Version 2.1.0
6.5 Disk Sparing
HPSAS_StorageExtent
HPSAS_StorageExtent
HPSAS_StoragePool
Concrete Pool
ConcreteComponent
ConcreteComponent
HPSAS_StorageRedundancySet
MemberOfCollection
MemberOfCollection
HPSAS_StorageExtent
Spare
IsSpare
StorageExtent
StorageRedundancySet
StoragePool
Figure 5 - HP SAS HBA profile: Disk Sparing Class Diagram
The Disk Sparing profile is used to model spare drives for raid sets. All the drives (HPSAS_StorageExtent
instances) in a raid shall be associated to an instance of HPSAS_StorageRedundancySet via
CIM_MemberOfCollection. Any spare drives (HPSAS_StorageExtent) shall be associated to the same
Storage Redundancy Set via the CIM_IsSpare association.
For SAS HBA, only one spare drive can be configured but this can act as a spare for any RAID sets
configured on the controller.
When a spare drive is “in use”, the HPSAS_StorageExtent will be associated to the failed drive(s) via
CIM_Spared association.
To determine if a concrete pool had spare drives configured, you would need to identify at least one
StoragExtent that was associated to the pool using CIM_ConcreteComponent association. If this instance
of a StorageExtent had a CIM_MemberOfCollection association to a CIM_StorageRedudancySet
instance, this would imply that at least one spare drive was configured for the Pool. Use CIM_IsSpare
association to find all the spare drives for the StorageRedundancySet.
See Section 9.5 for specific use cases.
6.6 Profile Registration