HP WBEM TC Document Number: P00122 Date: 10/27/2010 Version: 1.1.0 HP SAS HBA Profile © Copyright 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.
Contents Foreword................................................................................................................................................. 5 Introduction ............................................................................................................................................. 6 1 Scope .............................................................................................................................................. 7 2 Normative References ..............
Figures Figure 1 – HP SAS HBA profile: HHRC Class Diagram .......................................................................... 10 Figure 2 - HP SAS HBA profile: Block Services Class Diagram .............................................................. 12 Figure 3 - HP SAS HBA profile: Disk Drive Lite class diagram................................................................ 14 Figure 4 - HP SAS HBA profile: Extent Mapping Class Diagram.............................................................
Tables Table 1 – Related Profiles........................................................................................................................ 9 Table 2 – Consolidated Status Algorithm ............................................................................................... 18 Table 3 - HP SAS HBA profile: HPSAS_DiskDrive.DriveInterface........................................................... 19 Table 4 - HP SAS HBA profile: HPSAS_DiskDrive.DriveConfiguration .............................
Foreword The HP SAS HBA Profile (P00122) was prepared by the HP WBEM TC. Version 1.1.
Introduction The information in this specification should be sufficient for a provider or consumer of this data to identify unambiguously the classes, properties, methods, and values that shall be instantiated and manipulated to represent HP SAS controller HBAs. The target audience for this specification is implementers who are writing CIM based providers or consumers of management interfaces representing the component described in this document. 6 Version 1.1.
1 Scope The HP SAS HBA profile is an autonomous profile to describe management aspects of HP SAS HBA controllers and their attached storage devices. This profile extends certain profiles and sub-profiles defined in SNIA SMI-S version 1.2. 2 Normative References The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies.
3.2 cannot used for statements of possibility and capability, whether material, physical or causal 3.3 conditional used to indicate requirements strictly to be followed in order to conform to the document when the specified conditions are met 3.4 mandatory used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted 3.5 may used to indicate a course of action permissible within the limits of the document 3.
4 Symbols and Abbreviated Terms None. 5 Synopsis Profile Name: HP SAS HBA Profile Version: 1.1.0 Organization: HP WBEM TC CIM Schema Version: 2.18.1 Extends: SNIA Host Hardware RAID Controller profile. The HP SAS HBA Profile extends the SNIA HHRC profile to add the ability to model and represent HP SAS controllers. Central Class: HPSAS_PortController Table 1 – Related Profiles Profile Name Organization Version Relationship P00100 HP Profile Registration Profile HP WBEM TC 1.0.
6.
HPSAS_ArraySystem represents the top level system for the host based SAS HBA. Most SAS HBA managed objects will be scoped (or associated) to this top level system instance. This instance of HPSAS_ArraySystem will be associated to the central class (HPSAS_PortController) via CIM_LogicalIdentity. The use of PhysicalPackage will serve to model the physical aspects of the HBA and also the use of HPSAS_Product to hold Marketing names for supported HBAs.
6.
In this implementation, there will be two Primordial Pools to represent all the raw storage managed by the Array system. One Primordial Pool models all the drives that are currently configured in RAID sets. The other Primordial Pool models any drives that are not configured as part of a RAID set, in which case the controller will map these drives to the OS as SCSI devices. The Primordial Pool instances shall be associated to the Top Level System via CIM_HostedStoragePool.
6.
Figure 3 shows how the disk drives may be contained within a storage enclosure. (See HP Storage Enclosure Profile, P00120). 6.4 Extent Mapping Figure 4 - HP SAS HBA profile: Extent Mapping Class Diagram The Extent Mapping profile (Defined in SNIA SMI-S version 1.0.2) is used to model the relationship between Storage Volumes and the actual disk drives (storage extents) that are used in the make up of the volume. The implementation is restricted to primordial storage extents.
6.5 Disk Sparing StorageExtent StoragePool StorageRedundancySet HPSAS_StorageExtent MemberOfCollection ConcreteComponent HPSAS_StoragePool HPSAS_StorageRedundancySet Concrete Pool ConcreteComponent MemberOfCollection HPSAS_StorageExtent HPSAS_StorageExtent IsSpare Spare Figure 5 - HP SAS HBA profile: Disk Sparing Class Diagram The Disk Sparing profile is used to model spare drives for raid sets.
Figure 6 - HP SAS HBA profile: Profile Registration The CIM_Registered profile instances will be populated in the root\Interop namespace and will use the CIM_ElementConformsToProfile association to locate the central class for each profile. Supported profile shall be SNIA:HHRC. An instance of HP_RegisteredProfile shall be instantiated in the Interop namespace to indicate that the SNIA HHRC profile has been extended. Version 1.1.
6.
6.8 Location information An instance of HP_Location sub class will be associated to applicable physical packages by CIM_PhysicalElementLocation. 6.9 Software Inventory Firmware version is supported for SAS HBAs. Firmware version will be reported in an instance of CIM_SoftwareIdentity as defined in DMTF Software Inventory profile DSP1023. Figure 8 - HP SAS HBA profile: Software Inventory Disk Drive firmware will be reported as part of the SNIA Disk Drive Lite implementation (See section 6.3).
7.1.2 HPSAS_DiskDrive.DriveConfiguration Indicates the how the drive has been configured by the controller. Supported values are: Table 4 - HP SAS HBA profile: HPSAS_DiskDrive.DriveConfiguration Value 0 1 2 3 4 7.1.3 ValueMap Unknown Unconfigured Data Spare Non RAID HPSAS_DiskDrive.DriveRotationalSpeed Value indicates the rotational speed of the drive in Revolutions per minute. 7.1.4 HPSAS_DiskDrive.
Value 4 5 6 7 7.2.3 ValueMap RAID 4 RAID 5 RAID 51 RAID 6 HPSAS_StorageVolume.OSName This should display the volume name as it is known to the operating system if known otherwise it shall either show “Unknown” or not be assigned a value. 7.3 HPSAS_StorageExtent The HPSAS_StorageExtent class has been extended from CIM_StorageExtent class as defined in SNIA Block Services profile. 7.3.1 HPSAS_StorageExtent.
9.
Figure 9 - HP SAS HBA profile: Host Hardware RAID Controller The example in Figure 9 shows a PCI based SAS HBA in slot 3. The HPSAS_PortController central class instance can be identified by following the CIM_ElementConformsToProfile association from CIM_RegisteredProfile instance in root\Interop namespace. This instance of RegisteredProfile is identified as SNIA HHRC.
9.1.1 Host Hardware RAID Controller Physical model Figure 10 - HP SAS HBA profile: Host Hardware RAID Controller Physical 24 Version 1.1.
Figure 10 shows the physical instances for the same embedded SAS HBA. Instances of HP_Location classes are used to define location strings for each physical package. Version 1.1.
9.
Figure 11 shows a typical SAS HBA configuration that has one storage pool configured with two disk drives. This pool has one Storage Volume configured. 9.
The Non RAID pool shows one Storage Extent that is not part of any RAID configuration. 9.
9.5 Disk Sparing - Drive failure example The following sections describe the implementation of Disk Sparing for SAS HBA controllers. 9.5.1 Before drive failure Figure 14 - HP SAS HBA profile: Disk sparing – Pre failure Figure shows a three drive raid set with one spare drive. OperationalStatus for all the drives and the storage volume are “OK”. The data drives can be identified by their MemberOfCollection association to the StorageRedundancySet instance.
9.5.2 Drive Failed – data rebuilding Figure 15 - HP SAS HBA profile: Disk sparing – Drive failed - rebuilding Figure shows the instance diagram after one of the data drives has failed. OperationalStatus will show “ERROR” for the failed drive. The OperationalStatus for the StorageVolume will show “Degraded, Recovering”. The OperationalStatus for the Spare drive will show “OK” and the ExtentStatus will show “Rebuild”. The data is being rebuilt to the spare drive.
9.5.3 Drive Failed – Rebuild complete Figure 16 - HP SAS HBA profile: Drive Failed – Rebuild complete Figure shows that the rebuild operation has completed. The OperationalStatus values are now “OK” for the StorageVolume and the Spare Drive since rebuild is complete and redundancy has been restored. Now the spare drive has become the data drive for the Storage Pool and the failed drive is now a spare with “Error” status value. Version 1.1.
9.5.4 Drive replaced Figure 17 - HP SAS HBA profile: Drive Replaced Figure shows the instance diagram for the case where the failed drive has been replaced with a functional drive. The replaced drive will now act as a spare for the collection. 9.6 Host based HBA controller model Figure 18 - HP SAS HBA profile: Host HBA Controller Figure shows the instance diagram for a SAS HBA controller.
we see that the “degraded” status of a logical drive has been consolidated into HPSAS_ArraySystem.OperationalStatus[0]. 9.
10 CIM Elements The implementation requirements for the classes and properties described in this section are defined in the “Implementation Requirements” section (see Section 7). Table 7 – CIM Elements – HP SAS HBA Profile Element Name Requirement Description Classes HPSAS_DiskDrive Mandatory See Section 7.1 HPSAS_StorageVolume Mandatory See Section 7.2 HPSAS_StorageExtent Mandatory See Section 7.3 Indications None defined. 10.
Table 10 – Class: HPSAS_StorageExtent Properties Requirement OSName 10.4 O Notes See Section 7.3.1 HP_RegisteredProfile Implementation shall implement an instance of HP_RegisteredProfile in the Interop namespace with the values specified. Table 11 – Class: HP_RegisteredProfile Properties Requirement Notes RegisteredOrganization Mandatory Other (1) OtherRegisteredOrganization Mandatory “HP WBEM TC” RegisteredName Mandatory “HP SAS HBA RegisteredVersion Mandatory “1.1.
ANNEX A (normative) Change Log 36 Version Date .001 09/08/06 Initial Draft Description .002 10/08/06 Updated per WBEM TC review 10/06/06 1.0.1 03/01/10 Verified the profile against SMI-S 1.3.0 spec for compliance and updated the Synopsis section with corresponding version number for individual profiles 1.0.1.001 03/04/10 1.1.
ANNEX B (Informative) Acknowledgments Version 1.1.
ANNEX C (Informative) Included WBEM TC CR Numbers CR Number 38 Date Title CR00112 9/08/06 Create HP Profile for HP SAS HBA CR00165 10/27/10 Clarification of SAS Profile Version 1.1.
Bibliography This section contains a list of the external references and dependencies for this specification. Version 1.1.
