hp insight management wbem providers for hp integrated ...h20628.hp insight management wbem...

HP Insight Management WBEM Providers for HP integrated VMware ESXi 5.0 U2 December 2012 Profiles

HP WBEM TC

Document Number: P00100

Date: 06/02/2010

Version: 2.0.0

HP Profile Registration Profile

© Copyright 2008 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. HP shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.

2 Version 2.0.0

Contents

Foreword ....................................................................................................................................................... 5 Introduction.................................................................................................................................................... 6 1 Scope .................................................................................................................................................... 7 2 Normative References........................................................................................................................... 7

2.1 Approved References ................................................................................................................. 7 2.2 References Under Development ................................................................................................ 7 2.3 Other References........................................................................................................................ 7

3 Terms and Definitions ........................................................................................................................... 7 4 Symbols and Abbreviated Terms .......................................................................................................... 8 5 Synopsis ................................................................................................................................................ 8 6 Description ............................................................................................................................................ 9 7 Implementation Requirements ............................................................................................................ 10

7.1 HP_RegisteredProfile ............................................................................................................... 10 7.2 HP_ExtendsProfile .................................................................................................................... 11 7.3 HP_ReferencedProfile .............................................................................................................. 11 7.4 HP_ElementConformsToProfile................................................................................................ 11

8 Methods............................................................................................................................................... 11 8.1 Profile Conventions for Operations ........................................................................................... 11 8.2 HP_RegisteredProfile ............................................................................................................... 12 8.3 HP_ExtendsProfile .................................................................................................................... 13 8.4 HP_ReferencedProfile .............................................................................................................. 13 8.5 HP_ElementConformsToProfile................................................................................................ 13

9 Use Cases ........................................................................................................................................... 13 9.1 Object Diagrams ....................................................................................................................... 13 9.2 Find all HP profiles registered in the interop namespace ......................................................... 21 9.3 Determining if a standard profile implementation has HP specific extensions ......................... 22

10 CIM Elements ...................................................................................................................................... 22 10.1 HP_RegisteredProfile ............................................................................................................... 23 10.2 HP_ReferencedProfile .............................................................................................................. 23 10.3 HP_ExtendsProfile .................................................................................................................... 23 10.4 HP_ElementConformsToProfile................................................................................................ 24

11 Durable Names and Correlatable IDs ................................................................................................. 24 ANNEX A (normative) Change Log ........................................................................................................... 25 ANNEX B (informative) Acknowledgments ................................................................................................ 26 ANNEX C (informative) Included WBEM TC CR Numbers ....................................................................... 27 Bibliography ................................................................................................................................................ 28

Version 2.0.0 3

Figures

Figure 1 – HP Profile Registration Profile: Class Diagram ........................................................................... 9 Figure 2 – HP Profile Registration Profile: Inheritance Hierarchy Diagram ................................................ 10 Figure 3 – HP PRP: Fan and Processor Object Diagram (Scoping Class Methodology)........................... 14 Figure 4 – HP PRP: Fan and Processor Object Diagram (product specific extension) .............................. 15 Figure 5 – HP PRP: Fan and Processor Object Diagram (Central Class Methodology) ............................ 16 Figure 6 – HP PRP: Fan and Processor w/ Physical Asset ........................................................................ 17 Figure 7 – HP PRP: HP Processor and Consolidated Status ..................................................................... 20

4 Version 2.0.0

Tables

Table 1 – Related Profiles ............................................................................................................................. 9 Table 2 – Operations: HP_ExtendsProfile ................................................................................................. 13 Table 3 – Operations: HP_ReferencedProfile............................................................................................ 13 Table 4 – Operations: HP_ElementConformsToProfile ............................................................................. 13 Table 5 – CIM Elements – HP Profile Registration Profile.......................................................................... 23 Table 6 – Class: HP_RegisteredProfile ...................................................................................................... 23 Table 7 – Class: HP_ReferencedProfile ..................................................................................................... 23 Table 8 – Class: HP_ExtendsProfile ........................................................................................................... 23 Table 9 – Class: HP_ElementConformsToProfile ....................................................................................... 24 Table 10 – Durable Names generated by this Profile ................................................................................. 24 Table11 – Correlatable IDs generated by this Profile ................................................................................. 24

Version 2.0.0 5

Foreword

The HP Profile Registration Profile (P00100) was prepared by the HP WBEM TC.

6 Version 2.0.0

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 registration of HP profiles. 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.

Version 2.0.0 7

1 Scope

The HP Profile Registration profile extends the management capability of referencing profiles by adding the capability to HP Specific Profiles.

2 Normative References

The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

2.1 Approved References

DMTF DSP0200, CIM Operations over HTTP 1.2.0

DMTF DSP0004, CIM Infrastructure Specification 2.3.0

DMTF DSP1000, Management Profile Specification Template

DMTF DSP1001, Management Profile Specification Usage Guide

DMTF DSP1033, Profile Registration Profile

2.2 References Under Development

2.3 Other References

ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards – Downloadable from http://isotc.iso.org/livelink/livelink.exe?func=ll&objId=4230456&objAction=browse&sort=subtype

UML Specifications – Downloadable from http://www.omg.org/technology/documents/modeling_spec_catalog.htm#UML

3 Terms and Definitions

For the purposes of this document, the following terms and definitions apply.

3.1 can used for statements of possibility and capability, whether material, physical or causal

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

http://isotc.iso.org/livelink/livelink.exe?func=ll&objId=4230456&objAction=browse&sort=subtype

http://www.omg.org/technology/documents/modeling_spec_catalog.htm#UML

8 Version 2.0.0

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.6 need not used to indicate a course of action permissible within the limits of the document

3.7 optional used to indicate a course of action permissible within the limits of the document

3.8 referencing profile Indicates a profile which owns the definition of this class and can include a reference to this profile in its “Related Profiles” section.

3.9 shall used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted

3.10 shall not used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted

3.11 should used to indicate that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others, or that a certain course of action is preferred but not necessarily required

3.12 should not used to indicate that a certain possibility or course of action is deprecated but not prohibited

4 Symbols and Abbreviated Terms

None.

5 Synopsis

Profile Name: HP Profile Registration

Version: 2.0.0

Organization: HP WBEM TC

CIM Schema Version: 2.12

Version 2.0.0 9

Extends: DMTF DSP1033, Profile Registration Profile 1.0.0

The HP Profile Registration Profile extends DMTF DSP1033 to add the capability of registering HP specific profiles.

Table 1 – Related Profiles

Profile Name Organization Version Relationship Behavior DSP1033 – Profile Registration Profile

DMTF 1.0.0 Extends

6 Description

CIM_RegisteredProfile

1 (see DMTF Profile Registration Profile)

HP_ExtendsProfile

*

HP_ReferencedProfile

HP_RegisteredProfile

*

*

*

HP_ElementConformsToProfile CIM_ManagedElement

(see Referencing HP

* Profile)

Figure 1 – HP Profile Registration Profile: Class Diagram

The HP Profile Registration profile extends profile registration defined in DSP1033 to add the capability to register profiles that are developed by HP and administered by the HP WBEM TC. This profile handles the cases for registering all types of HP developed profiles: Autonomous, Component, Specializes and Extension.

HP_RegisteredProfile is the main class clients use to determine if an HP specific profile has been implemented in an implementation namespace.

HP_ExtendsProfile associates an HP Extension profile with its parent profile.

HP_ReferencedProfile is used to represent references between an HP profile and either a standard profile or another HP profile that are referenced from within the profile listed as the dependent in the association.

HP_ElementConformsToProfile is used to associate an HP profile with the central class in the implementation namespace that implements the profile.

10 Version 2.0.0

HP_ElementConformsToProfile

HP_ExtendsProfile

CIM_ReferencedProfile CIM_Dependency CIM_ElementConformsToProfile

see Profile Registration Profile

see Profile Registration Profile


Figure 2 – HP Profile Registration Profile: Inheritance Hierarchy Diagram 7 Implementation Requirements

This section details the requirements related to the arrangement of instances and properties of instances for implementations of this profile.

7.1 HP_RegisteredProfile

All HP specific profiles implemented in the implementation namespace that have a corresponding profile definition shall be registered in the interop namespace with in instance of HP_RegisteredProfile.

7.1.1 HP_RegisteredProfile.RegisteredOrganization

This property Identifies the organization that is responsible for administering this profile. For WBEM TC profiles, this property shall be set to Other(1).

7.1.2 HP_RegisteredProfile.OtherRegisteredOrganization

This property along with RegisteredOrganization is used to fully identify WBEM TC Profiles. This property shall be set to “HP WBEM TC” for profiles submitted, approved, and administered by the HP WBEM TC.

7.1.3 HP_RegisteredProfile.RegisteredName

This property is implemented as defined in the parent profile (DMTF Profile Registration Profile). Each referencing HP defined profile shall include a definition for HP_Registered profile in the CIM Elements section of the profile which includes the value this property shall contain.

7.1.4 HP_RegisteredProfile.RegisteredVersion

This property is implemented as defined in the parent profile (DMTF Profile Registration Profile). Each referencing HP defined profile, shall include a definition for HP_Registered profile in the CIM Elements section of the profile which includes the value this property shall contain.

7.1.5 HP_RegisteredProfile.ImplementationCentralClassNames

This property is an indexed array that lists the class names of the central classes for compliant provider implementations. This is the actual class name implemented by the providers, not the parent class name, such as CIM_xxx. This property shall be set to the central class names of the providers that directly implement the profile.

Version 2.0.0 11

7.1.6 HP_RegisteredProfile.ImplementationNameSpaces

This property is an indexed array that lists the namespaces for the compliant provider implementations for the associated class name listed in ImplementationCentralClassNames. This property shall be set to the namespaces of the providers that directly implement the profile.

7.2 HP_ExtendsProfile

This association shall be made between each extension profile registration and the parent profile it extends. This association is conditional on whether any of the profiles implemented in the implementation namespace have been extended by HP extension profile.

7.2.1 HP_ExtendsProfile.Antecedent

Set to the reference of the profile that is extended by another HP profile.

7.2.2 HP_ExtendsProfile.Dependent

Set to the reference to the HP profile that extends a profile.

7.3 HP_ReferencedProfile

This association shall be used to associate an HP profile that references another profile when both are registered in the interop namespace. Note that only extension profiles that extend an autonomous profile need to associate with referenced profiles and not peer or second level extension profile.

7.3.1 HP_ReferencedProfile.antecedent

Set to the reference of the HP profile the references another profile.

7.3.2 HP_ReferencedProfile.dependent

Set to the reference of the HP profile that is referenced by the antecedent profile.

7.4 HP_ElementConformsToProfile

HP_ElementConformsToProfile is used to associate an HP registered profile with the HP specific central class that defined the implementation of the profile. Implementation shall only use this associate when using the central class methodology for profile registration. The single CIM_ElementConformsToProfile association between the top-level autonomous profile and the its central class should be all that is needed for implementation using the scoping class methodology (see DSP1033)

8 Methods

None.

8.1 Profile Conventions for Operations

Support for operations for each profile class (including associations) is specified in the following sub- clauses. Each sub-clause includes either a statement “All operations are supported as described by DSP200 v1.2” or a table listing all the operations that are Unspecified by this profile or where the profile requires behavior other that described by DSP200.

The default list of operations is as follows:

• GetInstance

12 Version 2.0.0

• Associators

• AssociatorNames

• References

• ReferenceNames

• EnumerateInstances

• EnumerateInstanceNames

A compliant implementation shall support all the operations in the default list for each class, unless the Requirements column states something other than Mandatory.


All operations are supported as described by DSP200 v1.2.

Version 2.0.0 13


Table 2 lists operations that either have special requirements beyond those from DSP0200 or shall not be supported. All other operations may be supported as defined in DSP0200.

Table 2 – Operations: HP_ExtendsProfile

Operation Requirement Messages Associators Unspecified None AssociatorNames Unspecified None References Unspecified None ReferenceNames Unspecified None



Table 3 – Operations: HP_ReferencedProfile




Table 4 – Operations: HP_ElementConformsToProfile


9 Use Cases

9.1 Object Diagrams

NOTE: The object diagrams shown below represent illustration of profile relationships and implementations that may or may not valid. The intention is to show the relationship of the implementation of profiles with their registration in the interop namespace and not to be normative with respect to the specific profiles being illustrated. For example, HP or the DMTF may or may not extend or implement the DMTF Fan profile in the manner shown in these diagrams.

Figure 3 shows a simple implementation of a system containing one processor and one fan that have been extended via HP extension profiles. The DMTF base server profile has also been extended via the

14 Version 2.0.0

HP Base Server profile. The example uses the scoping class methodology for registering compliance to profiles. Using the methodology only one CIM_ElementConformsToProfile is required to associate the single autonomous profile (DMTF Base Server in this case) with the central class instance (HP_ComputerSystem in this case) in the implementation namespace. Note that even though the scoping class is of type HP_ComputerSystem, generic SMASH based clients would see an instance of CIM_ComputerSystem because HP_ComputerSystem sub-classed off of CIM_ComputerSystem.

The interop namespace contains the same referenced profiles as you would expect given the description contained in the Profile Registration Profile (DSP1033). The registered DMTF Base Server profile references both the DMTF Fan and CPU registered profiles because the implementation namespace contains implementations (or central classes) for each. In addition, the interop namespace contains the registrations for extensions to the base model because the DMTF Base Server, CPU, and Fan profiles have been extended with HP specific profiles (HP Base Server, HP CPU, and HP Fan). From the interop namespace clients can tell which autonomous and component profiles are implemented and which of those profiles have been extended via HP extension profiles.

system1: HP_ComputerSystem

HP_SystemFan

fan1: HP_Fan

HP_SystemProcessor

cpu1: HP_Processor:

CIM_ElementConformsToProfile

prof3: CIM_RegisteredProfile

RegisteredOrg: DMTF (2) RegisteredName: Base Server

CIM_ReferencedProfile



RegisteredOrg: DMTF (2) RegisteredName: CPU

prof1: CIM_RegisteredProfile RegisteredOrg: DMTF RegisteredName: Fan

HP_ExtendsProfile HP_ExtendsProfile

HP_ExtendsProfile

prof4: HP_RegisteredProfile

RegisteredOrg: Other (1) OtherRegOrg: HP WBEM TC RegisteredName: HP Base Server

prof5: HP_RegisteredProfile RegisteredOrg: Other (1) OtherRegOrg: HP WBEM TC RegisteredName: HP CPU

prof6: HP_RegisteredProfile RegisteredOrg: Other (1) OtherRegOrg: HP WBEM TC RegisteredName: HP Fan

Interop Namespace

Figure 3 – HP PRP: Fan and Processor Object Diagram (Scoping Class Methodology)

Version 2.0.0 15

Figure 4 shows adds an extended profile from the HP Fan profile to show that profile can be extended to differing levels of specificity. In this example, the namespace implements an instance of HP_x86Fan which conforms to the DMTF Fan profile and the HP Fan profile. It additionally conforms to a very specific profile defining fans specific to x86 platforms. Clients can determine this by discovering the additional HP_ExtendsProfile association instance which association the profile registration for the HP Fan profile and the HP x86 Fan profile. Note that this example is for illustration purpose only and may or may not reflect any actual profile implementations or relationships.


HP_SystemFan

fan2: HP_x86Fan

HP_SystemProcessor

cpu1: HP_Processor:









HP_ExtendsProfile

HP_ExtendsProfile

HP_ExtendsProfile





HP_ExtendsProfile


Interop Namespace

RegisteredOrg: Other (1) OtherRegOrg: HP WBEM TC RegisteredName: HP x86 Fan

Figure 4 – HP PRP: Fan and Processor Object Diagram (product specific extension)

16 Version 2.0.0

Figure 5 shows the same implementation using the central class methodology for registering profiles. Each profile is associated to its central class via a CIM_ElementConformsToProfile (for DMTF profiles) or an HP_ElementConformsToProfile (for HP Profiles) association. Notice that a single central class instance can be associated to multiple profiles if the central class has been extended via an HP extension profile. For example, the instance of the DMTF FAN profile central class HP_Fan is associated to both the DMTF Fan profile registration and the HP Fan extension profiles. In this case, a client can tell directly that the instance of HP_Fan conforms to both the DMTF Fan profile and the HP FAN extension profiles.


HP_SystemFan

fan1: HP_Fan HP_ElementConformsToProfile

HP_SystemProcessor CIM_ElementConformsToProfile

cpu1: HP_Processor: HP_ElementConformsToProfile

CIM_ElementConformsToProfile CIM_ElementConformsToProfile









RegisteredOrg: DMTF RegisteredName: Fan

HP_ExtendsProfile

HP_ExtendsProfile

HP_ExtendsProfile

prof4: HP_RegisteredProfile prof5: HP_RegisteredProfile prof6: HP_RegisteredProfile


RegisteredOrg: Other (1) OtherRegOrg: HP WBEM TC RegisteredName: HP CPU

RegisteredOrg: Other (1) OtherRegOrg: HP WBEM TC RegisteredName: HP Fan

Interop Namespace

Figure 5 – HP PRP: Fan and Processor Object Diagram (Central Class Methodology)

Figure 6 extends figure 3 by adding HP physical extensions for fans and processors. In this example, the DMTF Physical asset has 2 extension profiles associated with it that represent the HP physical asset extensions for both processors and fans. The implementation namespace show the central classes for these profiles being instantiated. For the HP CPU Physical Asset extension profile, an instance of HP_ProcessorChip is associated with both the chassis that containes it (HP_ComputerSystemChassis) and its logical representation (HP_Processor). Likewise, the HP Fan Physical Asset extension profile central class (HP_FanModule) is associated with HP_ComputerSystemChassis and its logical representation (HP_Fan).

Version 2.0.0 17

HP_ComputerSystem: system1

HP_ComputerSystemPackage

HP_ComputerSystemChassis: chassis1

HP_SystemPhysicalFan

HP_SystemFan mod1: HP_FanModule

fan1: HP_Fan

HP_RealizesFan

HP_SystemPhysicalProcessor

HP_SystemProcessor

CPU2: HP_Processor

HP_RealizesProcessor proc1:

HP_ProcessorChip


HP_ExtendsProfile

prof3: CIM_RegisteredProfile RegisteredOrg: DMTF (2) RegisteredName: Base Server





RegisteredOrg: DMTF (2) RegisteredName: Physical Asset


prof7: CIM_RegisteredProfile RegisteredOrg: DMTF RegisteredName: CPU

HP_ExtendsProfile

HP_ExtendsProfile HP_ExtendsProfile


RegisteredOrg: Other (1) OtherRegOrg:HP WBEM TC RegisteredName: HP Base Server

prof5: HP_RegisteredProfile RegisteredOrg: Other (1) OtherRegOrg: HP WBEM TC RegisteredName: HP Fan Physical Asset




RegisteredOrg: Other (1) OtherRegOrg: HP WBEM TC RegisteredName: HP CPU Physical Asset

Interop Namespace

Figure 6 – HP PRP: Fan and Processor w/ Physical Asset

Figure 7 shows an example of a system with 2 processor that implement consolidated status. The example also includes HP extended physical characteristics for each processor. This example uses the scoping class methodology to register the implemented profiles.

As shown in the previous figures, the DMTF Base Server profile references both the Physical Asset and CPU profiles. The DMTF Base Server profile is extended by the HP Base Server extension profile.

18 Version 2.0.0

Likewise for the DMTF CPU profile. The DMTF Physical Asset profile is extended to include HP CPU physical assets.

The HP CPU Consolidated Status profile is an HP specific component profile that is referenced by the HP Base Server extension profile. Notice that neither of the profile reference the CPU Consolidated Status profile. Autonomous profiles or profiles that extend autonomous profiles associate to referenced profiles and not second tier component profiles or the profiles that extend them. This is consistent with the DMTF Profile Registration profile.


HP_ComputerSystemChassis: chassis1

HP_ComputerSystem: system1

HP_ProcessorGroupHostedCollection

HP_SystemProcessor HP_ProcessorCollection: collection1


HP_PhysicalMemberOfProcessorCollection

HP_LogicalMemberOfProcessorCollection

HP_Processor: proc1

HP_RealizesProcessor

HP_ProcessorChip: procchip1

HP_Processor: proc2

HP_ProcessorChip: procchip2


CIM_ElementConformsToProfile prof3: CIM_RegisteredProfile





RegisteredOrg: DMTF (2) RegisteredName: Physical Asset

prof1: CIM_RegisteredProfile RegisteredOrg: DMTF RegisteredName: CPU

HP_ExtendsProfile

HP_ExtendsProfile

HP_ExtendsProfile



prof5: HP_RegisteredProfile RegisteredOrg: Other (1) OtherRegOrg: HP WBEM TC RegisteredName: HP CPU Physical Asset




RegisteredOrg: Other (1) OtherRegOrg: HP WBEM TC RegisteredName: HP CPU Consolidated Status

Version 1.0.0

Interop Namespace 19

20 Version 2.0.0

Figure 7 – HP PRP: HP Processor and Consolidated Status

Figure 8 shows is an example of an implementation of the HP Fan and HP Base Server profiles and a direct implementation of the DMTF OS Status profile. Prof4 is the instance of the HP Base Server profile and prof6 is the instance of the HP Fan profile. Both of these profiles are directly implemented, thus their instances set values for the ImplementationCentralClassNames and the ImplementationNameSpaces properties. Note that their parent profile instances, prof3 and prof1 respectively, do not set values for these properties as they are not directly implemented.

Prof2 is the instance of the DMTF OS Status profile. This profile is directly implemented and thus sets values for the ImplementationCentralClassNames and the ImplementationNameSpaces properties.

Note that this example is for illustration purpose only and may or may not reflect any actual profile implementations or relationships.

Version 2.0.0 21

System1:HP_ComputerSystem: SMX_ComputerSystem

HP_SystemFan

Fan1:HP_Fan:SMX_Fan

CIM_RunningOS

Os1:CIM_OperatingSystem: SMX_OperatingSystem



HP_ExtendsProfile


CIM_ReferencedProfile CIM_ReferencedProfile


RegisteredOrg: DMTF (2) RegisteredName: OS Status ImplementationCentralClassNames[0]:”SMX _OperatingSystem” ImplementationNameSpaces[0]: “root/hpq”


HP_ExtendsProfile


RegisteredOrg: Other (1) OtherRegOrg: HP WBEM TC RegisteredName: HP Base Server ImplementationCentralClassNames[0]: “SMX_ComputerSystem” ImplementationNameSpaces[0]: “root/hpq”

prof6: HP_RegisteredProfile RegisteredOrg: Other (1) OtherRegOrg: HP WBEM TC RegisteredName: HP Fan ImplementationCentralClassNames[0]: “SMX_Fan” ImplementationNameSpaces[0]: “root/hpq”

Interop Namespace

Figure 8 – HP PRP: Standard OS and extended Fan with Implementation array properties

9.2 Find all HP profiles registered in the interop namespace

The following algorithm can be followed to find HP profiles registered in the interop namespace:

• Query for all instances of HP_RegisteredProfile in the interop namespace

• For each instance of HP_RegisteredProfile found in the previous step

• Find the references of HP_RegisteredProfile (returns list of association).

22 Version 2.0.0

• For each association instance found in previous step

• If the association instance is a HP_ExtendsProfile

• If HP_ExtendsProfile.dependent property equals the REF of this instance of HP_RegisteredProfile, then this profile is an extension profile. The client can determine the profile being extended by following the antecedent property of the found HP_ExtendsProfile association instance. NOTE:It is invalid for an extension profile to extend 2 different profiles, thus it is an error if another HP_ExtendsProfile association is found where the dependent property equals this HP_RegisteredProfile instances REF.

• Else if HP_ExtensProfile.antecedent property equals this HP_RegisteredProfile instance REF then this profile has been extended and the client can follow the HP_ExtendsProfile.dependent to determine the profile that extends this profile instance. NOTE: It is valid for a profile to be extended by multiple extension profiles. Therefore, it is not an error for this case to be hit for multiple given HP_RegisteredProfile instances.

• If the association instance is a HP_ReferencedProfile

• If HP_ReferencedProfile.antecedent equals this instance of HP_RegisteredProfile, then this profile references another profile. The client can determine which HP profile this registered profile references by following the dependent REF.

• If HP_ReferencedProfile.dependent equals this instance of HP_RegisteredProfile then

the profile is referenced by another profile. The client can determine which profile references this profile by following the dependent REF.

9.3 Determining if a standard profile implementation has HP specific

extensions

The following algorithm can be followed to determine if a standard profile implementation has been extended by a profile defined by HP:

• For any given standard profile, find its central class using the algorithms defined in DMTF Profile Registration Profile (DSP1033).

• From the central class, find its corresponding profile registration using the algorithm defined in DSP 1033.

• Query all instances of HP_ExtendsProfile where the Antecedent property equals the instance of

profile registration found in the previous step.

• Follow the association (via the Dependent REF) to the corresponding extension profile.

• This profile will define the extension to the profile referenced in the Antecedent REF. This includes:

• All classes that have been extended via inheritance (sub-classes)

• All additional classes and association added to extended classes. 10 CIM Elements

The implementation requirements for the classes and properties described in this section are defined in the “Implementation Requirements” section (see Section 10).

Version 2.0.0 23

Table 5 – CIM Elements – HP Profile Registration Profile

Element Name Requirement Description Classes

HP_RegisteredProfile Mandatory see Section 7.1 HP_ReferencedProfile Conditional see Section 7.3 HP_ExtendsProfile Conditional see Section 7.2 HP_ElementConformsToProfile Conditional see Section 7.4

Indications None defined.


HP_RegisteredProfile represents an HP defined profile registered in the interop namespace.

Table 6 – Class: HP_RegisteredProfile

Properties Requirement Notes RegisteredOrganization M (see section 7.1.1) OtherRegisteredOrganization M (see section 7.1.2) RegisteredName M (see section 7.1.3) RegisteredVersion M (see section 7.1.4) ImplementationCentralClassNames M (see section 7.1.5) ImplementationNameSpaces M (see section 7.1.6)


This association is used to associate an HP referenced profile to its referencing profile.

Table 7 – Class: HP_ReferencedProfile

Properties Requirement Notes Antecedent M REF: HP_RegisteredProfile (see section 7.3.1) Dependent M REF: HP_RegisteredProfile (see section 7.3.2)


This association is used to associate an HP extension profile to the parent profile it extends.

Table 8 – Class: HP_ExtendsProfile

Properties Requirement Notes Antecedent Mandatory REF:CIM_RegisteredProfile (see section 7.2.1) Dependent Mandatory REF:HP_RegisteredProfile (see section 7.2.2)

24 Version 2.0.0


This association is used associate a profile registered in the interop namespace with its central class that implements the profile in the implementation namespace.

Table 9 – Class: HP_ElementConformsToProfile

Properties Requirement Notes ConformantStandard M REF:HP_RegisteredProfile – reference to the HP profile

registered in the interop namespace. ManagedElement M REF:CIM_MangedElement – pointer to the central class in

the implementation namespace that implements this profile.

11 Durable Names and Correlatable IDs

None.

Table 10 – Durable Names generated by this Profile

Class

Durable Name(s)

Source ID

Information

Circumstances for

Change None Defined

Table11 – Correlatable IDs generated by this Profile

Class

Correlatable ID(s)

Source ID Information

Circumstances for

Change None Defined

Version 2.0.0 25

ANNEX A (normative)

Change Log

Version Date Description 0.1 3/15/06 Initial Draft

26 Version 2.0.0

ANNEX B (informative)

Acknowledgments

Version 2.0.0 27

ANNEX C (informative)

Included WBEM TC CR Numbers

CR Number

Date

Title

CR00100 5/3/06 Create HP Profile Registration profile

28 Version 2.0.0

Bibliography

This section contains a list of the external references and dependencies for this specification.

HP WBEM TC Document Number: P00101

Date: 04/22/2011

Version: 2.1.1

HP Management Processor (MP) Lite Profile




2 Version 2.1.1

Contents Forward ......................................................................................................................................................... 5 Introduction.................................................................................................................................................... 6 1 Scope .................................................................................................................................................... 7 2 Normative References ........................................................................................................................... 7

2.1 Approved References ................................................................................................................. 7 2.2 References Under Development ................................................................................................ 7 2.3 Other References ........................................................................................................................ 7 2.4 HP Internal References............................................................................................................... 7


7.1 HP_ManagementProcessor ...................................................................................................... 12 7.2 HP_MPCollection ...................................................................................................................... 14 7.3 HP_MPHostedCollection .......................................................................................................... 14 7.4 HP_MPMemberOfCollection ..................................................................................................... 14 7.5 HP_MPComponentCS .............................................................................................................. 14 7.6 CIM_ManagementController (Optional) .................................................................................... 14 7.7 CIM_ConcreteIdentity (Optional) .............................................................................................. 15

8 Methods ............................................................................................................................................... 15 8.1 Method: HP_ManagementProcessor.RequestStateChange() Optional ................................... 15 8.2 Profile Conventions for Operations ........................................................................................... 15 8.3 HP_ManagementProcessor ...................................................................................................... 15 8.4 HP_MPCollection ...................................................................................................................... 16

9 Use Cases ........................................................................................................................................... 16 9.1 Object Diagrams ....................................................................................................................... 16 9.2 Identify the Management Processor ......................................................................................... 19 9.3 Discover the Management Processor Configuration Interface ................................................. 19 9.4 Discover the Management Processor Status ........................................................................... 19 9.5 Discover the Management Processor PCI Device IDs ............................................................. 19

10 CIM Elements ...................................................................................................................................... 20 10.1 HP_ManagementProcessor ...................................................................................................... 20 10.2 HP_MPCollection ...................................................................................................................... 24 10.3 HP_MPHostedCollection .......................................................................................................... 25 10.4 HP_MPMemberOfCollection ..................................................................................................... 25 10.5 HP_MPComponentCS .............................................................................................................. 26 10.6 HP_RegisteredProfile ............................................................................................................... 26 10.7 HP_MPFirmware ....................................................................................................................... 26 10.8 HP_MPElementFirmwareIdentity .............................................................................................. 27 10.9 HP_MPInstalledFirmwareIdentity ............................................................................................. 27


Version 2.1.1 3

Figures

Figure 1 – Management Processor System: Class Diagram ...................................................................... 10 Figure 2 – Management Processor Association Hierarchy: Class Diagram ............................................... 11 Figure 3 – Management Processor Lite Profile: Example Object Diagram ................................................ 16 Figure 4 – Management Processor Lite Profile: Example Object Diagram ................................................ 17 Figure 5 – Management Processor Lite Profile: Example Object Diagram ................................................ 18 Figure 6 – Management Processor Lite Profile: Example Object Diagram ................................................ 19

4 Version 2.1.1

Tables

Table 1 – Related Profiles ............................................................................................................................. 9 Table 2 – OperationalStatus mapping ........................................................................................................ 13 Table 3 – Operations: HP_ManagementProcessor ................................................................................... 15 Table 4 – Operations: HP_MPCollection .................................................................................................... 16 Table 5 – CIM Elements – HP Management Processor Profile .................................................................. 20 Table 6 – Class properties: HP_ManagementProcessor ............................................................................ 21 Table 7 – Class properties: HP_MPCollection ............................................................................................ 25 Table 8 – Class properties: HP_MPHostedCollection ................................................................................ 25 Table 9 – Class properties: HP_MPMemberOfCollection ........................................................................... 26 Table 10 – Class properties: HP_MPComponentCS .................................................................................. 26 Table 11 – Class properties: HP_RegisteredProfile ................................................................................... 26 Table 12 – Class properties: CIM_SoftwareIdentity ................................................................................... 27 Table 13 – Durable Names generated by this Profile ................................................................................. 27 Table 14 – Correlatable IDs generated by this Profile ................................................................................ 27

Version 2.1.1 5

Forward

The HP Management Processor Lite Profile (P00101) was prepared by the HP WBEM TC.

6 Version 2.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 Management Processor subsystems in HP systems. 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.

Version 2.1.1 7

1 Scope

The HP Management Processor profile extends the management capability of referencing profiles by adding the capability to represent HP Management Processor systems.



2.1 Approved References DMTF DSP0200, CIM Operations over HTTP 1.2.0




DMTF DSP1023, Software Inventory Profile

DMTF DSP1004, Base Server Profile

DMTF DSP1075, PCI Device Profile

HP WBEM TC P00100, HP Profile Registration Profile

HP WBEM TC P00105, HP Base Server Profile

HP WBEM TC P00113, HP Consolidated Status Profile


2.3 Other References ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards Downloadable from: http://isotc.iso.org/livelink/livelink.exe?func=ll&objId=4230456&objAction=browse&sort=subtype

UML Specifications- Downloadable from: http://www.omg.org/technology/documents/modeling_spec_catalog.htm#UML

2.4 HP Internal References





8 Version 2.1.1













Version 2.1.1 9


MP Management Processor

5 Synopsis Profile Name: HP Management Processor Lite Profile

Version: 2.1.1



Central Class: HP_ManagementProcessor

Scoping Class: HP_ComputerSystem

Extends: does not extend any current DMTF profile

Specializes: HP WBEM TC P00113, HP Consolidated Status Profile

The HP Management Processor Lite profile does not extend any current DMTF profile. The profile specializes HP WBEM TC P00113 to add management processor consolidated status characteristics that are specific to HP systems.


Profile Name Organization Version Relationship Behavior

P00100 – HP Profile Registration Profile HP WBEM TC 1.0 Mandatory

P00105 – HP Base Server Profile HP WBEM TC 1.0 Mandatory

DSP1023 – Software Inventory Profile DMTF 1.0 Mandatory

DSP1075 – PCI Device Profile DMTF 1.0.0 Optional

6 Description

The HP Management Processor (MP) Lite profile is a component profile that does not extend any current DMTF profile.

The profile attempts to target only MP elements which are hardware platform and OS agnostic in nature.

The profile describes the classes and properties required for basic instrumentation of an HP MP system. The data described would be populated in a host OS CIMOM by providers executing in the same host OS. The data content is not all-encompassing; only a basic MP system is described. The profile attempts to define only enough information to meet the following client objectives:

1. Provide comprehension that an MP exists in the system.

2. Basically identify the type of MP controller.

3. Provide the MP operational status with the ability to disable state propagation.

4. Provide the IP address and/or URL of the MP-resident network configuration interface. Any additional MP configuration data can be obtained from the MP (and the MP can be configured) by pointing a browser to this address and/or URL.

A “Computer System” in this profile represents an individual system or a single hardware partition executing some host OS for which a management processor system is associated.

10 Version 2.1.1

For systems comprised of multiple hardware partitions sharing common MP hardware, the profile provides only a description of the MP and it’s relationship in a single hardware partition, i.e. the information presented in this profile is relevant only within a single partition running some host OS and represented in that host OS CIMOM. The profile does not present a view of the MP as encompassing all of the partitions in a system or managing multiple partitions running multiple OSes and having multiple CIMOMs.

HP_GroupSystemSpecificCollection-(see P00107-HP Cosolidated Status Profile)

CIM_SystemSpecificCollection

HP_RegisteredProfile-(see P00100-HP Profile Registration profile)

HP_MPCollection

HP_ComputerSystem-(see P00105-HP Base Server profile)

CIM_ComputerSystem

HP_MPHostedCollection

1

1

HP_MPComponentCS

1

*

HP_MPMemberOfCollection

1

*

1

1


1

*

HP_MPElementFirmwareIdentity

HP_ManagementProcessor-

1

*

HP_MPInstalledFirmwareIdentity

HP_MPFirmware

CIM_ManagementController

+(see DSP1075 PCI Device Profile)CIM_PCIDevice

CIM_SystemDevice

CIM_ConcreteIdentity

Figure 1 – Management Processor System: Class Diagram

Version 2.1.1 11

CIM_SystemComponent

CIM_Component

CIM_ComponentCS

HP_MPComponentCS

CIM_MemberOfPolicyCollection

CIM_MemberOfCollection

CIM_HostedDependency

CIM_HostedCollection

HP_GroupHostedCollection


CIM_Dependency

HP_MPMemberOfCollection

HP_MPFirmware

CIM_SoftwareIdentity

Figure 2 – Management Processor Association Hierarchy: Class Diagram

12 Version 2.1.1

7 Implementation Requirements

7.1 HP_ManagementProcessor

There shall be at least one instance of HP_ManagementProcessor instantiated for the active or enabled MP controller. If a system contains additional controllers which are disabled or inactive, instance(s) may be instantiated with the appropriate state indicated.

7.1.1 HP_ManagementProcessor.ControllerType

HP_ManagementProcessor.ControllerType is a property which describes the identity or type of MP controller in the system using an appropriate enumeration value.

The property is conditional based on the enabled state of the MP (see section 7.1.7). If the MP is disabled, the property will not be populated; if the MP is enabled, the property is Mandatory.

7.1.2 HP_ManagementProcessor.UniqueIdentifier

HP_ManagementProcessor.UniqueIdentifier is a property which contains an identifier to uniquely distinguish an MP controller from any other MP hardware. This may be the serial number, MAC address, UUID or other identifier which uniquely identifies an individual MP. This value is opaque and not intended to be parsed; it is intended to be used as a correlatable identifier to match an instance of a MP in the host OS CIMOM namespace with the data provided at the MP network interface.


7.1.3 HP_ManagementProcessor.IPAddress

HP_ManagementProcessor.IPAddress is a property which contains the IP address of the MP network interface controller where MP configuration can be obtained.


7.1.4 HP_ManagementProcessor.URL

HP_ManagementProcessor.URL is a property which contains the Uniform Resource Locator (URL) of the MP provided web interface.


7.1.5 HP_ManagementProcessor.SupportedProtocols

HP_ManagementProcessor.SupportedProtocols is a property which contains a list of the protocols which are supported and enabled/active on the MP. Each protocol is represented using an appropriate enumeration value.


7.1.6 HP_ManagementProcessor.NICCondition

HP_ManagementProcessor.NICCondition is a property which indicates the operating state of the MP network interface controller using an appropriate enumeration value.

Version 2.1.1 13


7.1.7 HP_ManagementProcessor.EnabledState

HP_ManagementProcessor.EnabledState is a mandatory property which indicates the operating state of the MP using an appropriate enumeration value.

7.1.8 HP_ManagementProcessor.OperationalStatus

HP_ManagementProcessor.OperationalStatus is a mandatory property which indicates the status of the MP using appropriate enumeration values.

The overall MP status is provided in OperationalStatus[0]. Overall MP status is determined by the status of the MP software application interface and optionally, the status of the MP-resident network interface connection.

MP status participation in overall system status is optional. Overall MP status will contribute to overall system status if the provider chooses to instantiate the optional class HP_MPCollection and related association classes (see section 7.2).

Management Processors which are in a disabled state should not participate in overall system status. The OperationalStatus[0] property shall be loaded with a value of (2) OK for a disabled MP.

If the provider is unable to communicate via the MP software application interface, OperationalStatus[0] shall contain a value of (6) Error.

Providers who are able to communicate successfully with the MP via the software application interface can optionally include the status of the on-board, MP-resident network interface connection in OperationalStatus[1]. Providers who populate this element should comprehend that by doing so, the MP NIC status will participate in overall MP status and ultimately overall system status if the HP_MPCollection class is instantiated (see section 7.2). Providers who do not desire for NIC status participation in overall MP status should not populate the OperationalStatus[1] element.

The mapping of OperationalStatus is described in Table 2.

Table 2 – OperationalStatus mapping

EnabledState SW Interface OK?

NICCondition OperationalStatus [1]

OperationalStatus [0]

Disabled YES N/A N/A (not populated) (2) OK

Enabled NO N/A (0) Unknown (6) Error

Enabled YES Provider does not desire for NIC status to participate in overall system status; NIC Status not being presented in OperationalStatus[1]

N/A (not populated) (2) OK

Enabled YES (0) Unknown (0) Unknown (0) Unknown

Enabled YES (2) OK (2) OK (2) OK

Enabled YES (3) NIC disabled (10) Stopped (2) OK

Enabled YES (4) NIC not in operation-alternate host NIC in use, e.g. ProLiant iLO sideband operation

(15) Dormant (2) OK

Enabled YES (5) NIC in operation but disconnected (3) Degraded (3) Degraded

Enabled YES (6) Failed (6) Error (6) Error

14 Version 2.1.1

7.2 HP_MPCollection

The implementation of the HP_MPCollection class is optional. Providers who desire for overall MP status to contribute to overall system status shall instantiate one instance of HP_MPCollection which aggregates the collection of all MP controllers in a system. Instances of HP_ManagementProcessor are associated to HP_MPCollection through the HP_MPMemberOfCollection aggregate association. The instance of HP_MPCollection is associated to the scoping computer system through the HP_MPHostedCollection association.

7.2.1 HP_MPCollection.GroupOperationalStatus[0]

HP_MPCollection.GroupOperationalStatus[0] shall comprehend the status of all instances of HP_ManagementProcessor included in the collection. The status shall represent the ‘worst-of’ algorithm for all individual statuses in HP_ManagementProcessor.OperationalStatus[0].

7.3 HP_MPHostedCollection

The implementation of the HP_MPHostedCollection class is conditional based on its dependence on the implementation of the HP_MPCollection class (see section 7.2). If implemented, there shall be one instance of HP_MPHostedCollection to associate the HP_MPCollection to the scoping HP_ComputerSystem.

7.4 HP_MPMemberOfCollection

The implementation of the HP_MPMemberOfCollection class (subclassed from CIM_MemberOfPolicyCollection) is conditional based on its dependence on the implementation of the HP_MPCollection class (see section 7.2). If implemented, there shall be one instance of HP_MPMemberOfCollection for each instance of HP_ManagementProcessor instantiated. The HP_MPMemberOfCollection provides the association between the collection of MPs in a system and the scoping computer system. The HP_MPMemberOfCollection association aggregates all MPs in a collection.

7.5 HP_MPComponentCS

There shall be one instance of HP_MPComponentCS for each instance of HP_ManagementProcessor instantiated. The HP_ComponentCS provides the association between an individual MP (HP_ManagementProcessor) and the computer system (HP_ComputerSystem) for which it provides management capabilities.

7.6 CIM_ManagementController (Optional)

CIM_ManagementController is an optional class. It is only instantiated if the provider implements the CIM_ConcreteIdentity association to the CIM_PCIDevice instance.

7.6.1 CIM_ManagementController.EnabledState

CIM_ManagementController.EnabledState is a mandatory property which indicates the operating state of the MP using an appropriate enumeration value.

7.6.2 CIM_ManagementController.OperationalStatus

CIM_ManagementController.OperationalStatus is a mandatory property which indicates the status of the MP using appropriate enumeration values. OperationalStatus[0] shall match the value in HP_ManagementProcessor.OperationalStatus[0].

Version 2.1.1 15

7.7 CIM_ConcreteIdentity (Optional)

CIM_ConcreteIdentity is an optional class. It is only instantiated if the provider supports the association from CIM_ManagementController and CIM_PCIDevice instance.

8 Methods

8.1 Method: HP_ManagementProcessor.RequestStateChange() Optional

Implementations may support the RequestStateChange method to change the state of the management processor. If implemented, the provider should support the “RequestedState” property with a value of 11 (Reset). Support of the “Job” and “TimeoutPeriiod” parameters are optional.


Support for operations for each profile class (including associations) is specified in the following sub-clauses. Each sub-clause includes either a statement “All operations are supported as described by DSP200 v1.2” or a table listing all the operations that are Unspecified by this profile or where the profile requires behavior other that described by DSP200.


• GetInstance

• Associators

• AssociatorNames

• References

• ReferenceNames




8.3 HP_ManagementProcessor


Table 3 – Operations: HP_ManagementProcessor

Operation Requirement Messages

GetInstance Mandatory None

Associators Unspecified None

AssociatorNames Unspecified None

References Unspecified None

ReferenceNames Unspecified None

EnumerateInstances Unspecified None

EnumerateInstanceNames Unspecified None

16 Version 2.1.1

8.4 HP_MPCollection


Table 4 – Operations: HP_MPCollection









9 Use Cases

9.1 Object Diagrams

Figure 3 represents a possible implementation of the HP Management Processor Lite profile. In this example, the system has 1 Management Processor – MP1. MP1 belongs to the collection MPCollection1. Because MPCollection1 is instantiated and HP_MemberOfCollection.Included property has a value of TRUE, the GroupOperationalStatus is participating in overall system status. The on-board network interface is in use in this example and is reporting that it currently disconnected from the network resulting in a status of Degraded for both MP1 and the overall MPCollection1.

For simplicity, not all properties are shown.

Profile2:HP_RegisteredProfile

RegisteredOrg: OtherOtherRegOrg: HP WBEM TCRegisteredName: HP Base Server

Profile3:CIM_RegisteredProfile

RegisteredOrg: DMTFRegisteredName: Base Server


RegisteredOrg: OtherOtherRegOrg: HP WBEM TCRegisteredName: HP MP Lite

FW1:HP_MPFirmware

MPCollection1:HP_MPCollection

GroupOperationalStatus[0]: Degraded

MP1:HP_ManagementProcessor

ControllerType: Embedded iLOEnabledState: EnabledNICCondition: (5) DisconnectedOperationalStatus[0]: DegradedOperationalStatus[1]: Degraded

System1:HP_ComputerSystem

HP_MPComponentCS

HP_MPMemberOfCollectionIncluded: TRUE




HP_ExtendsProfile



Figure 3 – Management Processor Lite Profile: Example Object Diagram

Version 2.1.1 17

Figure 4 represents a possible implementation of the HP Management Processor Lite profile. In this example, the system has 2 Management Processors – MP1 is enabled (active) and MP2 is disabled (inactive). MP1 and MP2 belong to the collection MPCollection1 and because both MP1 and MP2 are reporting statuses of ‘OK’ and their respective HP_MemberOfCollection.Included properties have values of TRUE, the overall group operational status is also OK. Because MPCollection1 is instantiated, the GroupOperationalStatus is participating in overall system status. FW1 and FW2 are the HP_MPFirmware instantiations representing the MP1 and MP2 firmware respectively.








FW1:HP_MPFirmware


GroupOperationalStatus[0]: OK


ControllerType: Embedded iLOEnabledState: DisabledOperationalStatus[0]: OK


ControllerType: PCI Board, RILOE IIEnabledState: EnabledNICCondition: OKOperationalStatus[0]: OKOperationalStatus[1]: OK


HP_MPComponentCS

HP_MPComponentCS




FW2:HP_MPFirmware




HP_ExtendsProfile





Figure 5 represents a possible implementation of the HP Management Processor Lite profile. In this example, the system has 1 Management Processor – MP1. MP1 belongs to the collection MPCollection1. Because MPCollection1 is instantiated and HP_MemberOfCollection.Included property has a value of TRUE, the GroupOperationalStatus is participating in overall system status. The on-board network interface is in use in this example and is reporting that it is currently disconnected from the network. However, in this example the provider does not wish for the NIC status to participate in overall MP status (and as a result, overall system status) and therefore has not populated the HP_ManagementProcessor.OperationalStatus[1] property. The overall resulting MP status reported in HP_ManagementProcessor.OperationalStatus[0] is therefore OK and this status is forwarded to participate in overall system status via the HP_MPCollection.GroupOperationalStatus[0] property.

18 Version 2.1.1








FW1:HP_MPFirmware




ControllerType: Embedded iLOEnabledState: EnabledNICCondition: (5) DisconnectedOperationalStatus[0]: OK


HP_MPComponentCS





HP_ExtendsProfile




Figure 6 represents a possible implementation of the HP Management Processor Lite profile. In this example, the system has 1 Management Processor – MP1. The provider does NOT wish for MP status to participate in overall system status and therefore has instantiated the HP_MPMemberOfCollection class instantiated with the “Included” property having a value of FALSE. The on-board network interface is in use in this example and is reporting a failed condition. In this example the provider wishes for the NIC status to participate in overall MP status and therefore has populated the HP_ManagementProcessor.OperationalStatus[1] property with an Error Status. The overall resulting MP status reported in HP_ManagementProcessor.OperationalStatus[0] is therefore also a status of Error.


Version 2.1.1 19







FW1:HP_MPFirmware




ControllerType: Embedded iLOEnabledState: EnabledNICCondition: (5) DisconnectedOperationalStatus[0]: ErrorOperationalStatus[1]: Error


HP_MPComponentCS

HP_MPMemberOfCollectionIncluded: FALSE




HP_ExtendsProfile




9.2 Identify the Management Processor

The HP_ManagementProcessor instance is a CIM_ComputerSystem whose Dedicated property is set to a value of (14), ”Management”. For a given instance of HP_ManagementProcessor, the model or type of the MP can be determined by retrieving the value of the HP_ManagementProcessor.ControllerType property.

9.3 Discover the Management Processor Configuration Interface

For a given instance of HP_ManagementProcessor, retrieve the value of the HP_ManagementProcessor.URL property. The MP configuration interface can be obtained by specifying the supplied URL address to any browser.

9.4 Discover the Management Processor Status

For a given instance of HP_ManagementProcessor, overall MP status is given by the property HP_ManagementProcessor.OperationalStatus[0] (see section 7.1.8). Optionally, the overall MP status may participate and contribute to overall system status if the provider implements the HP_MPCollection class; in this case the overall MP collection status is given by the property HP_MPCollection.GroupOperationalStatus[0] (see section 7.2.1).

9.5 Discover the Management Processor PCI Device IDs

For a given instance of HP_ManagementProcessor, follow the CIM_SystemDevice association to the CIM_ManagementController instance. From that instance, follow the CIM_ConcreteIdentity to one or more CIM_PCIDevice instances.

20 Version 2.1.1

10 CIM Elements

The implementation requirements for the classes and properties in this section are defined in section 7, “Implementation Requirements”.

Table 5 – CIM Elements – HP Management Processor Profile


HP_ManagementProcessor Mandatory See sections 7.1 and 10.1 HP_MPCollection Optional See sections 7.2 and 10.2 HP_MPHostedCollection Conditional See sections 7.3 and 10.3 HP_MPMemberOfCollection Conditional See sections 7.4 and 10.4 HP_MPComponentCS Mandatory See sections 7.5 and 10.5 HP_MPFirmware Mandatory See section 10.7 HP_MPElementFirmwareIdentity Mandatory See section 10.8 HP MPInstalledFirmwareIdentity Mandatory See section 10.9 HP_RegisteredProfile Mandatory See section 10.6 CIM_ManagementController Optional See section 7.6 CIM_ConcreteIdentity Optional See section 7.7

Indications (None defined in this profile)

10.1 HP_ManagementProcessor HP_ManagementProcessor extends the class CIM_ComputerSystem in ways that are specific to HP systems.

Version 2.1.1 21

Table 6 – Class properties: HP_ManagementProcessor

Properties Requirement Notes Properties of class HP_ManagementProcessor ControllerType Conditional

(See Note 1) uint16 The Management Processor model/type: 0=Unknown 1=Other 2=PCI Board-Remote Insight Lights Out Edition II (RILOE II) 3=Embedded Integrated Lights Out Controller (iLO) 4=Embedded Integrated Lights Out Controller 2 (iLO 2) 5=Embedded Integrity Management Processor 6=Embedded Integrity Integrated Lights Out Controller (iLO) 7=Embedded Integrity Integrated Lights Out Controller 2 (iLO 2) 8=Embedded Lights Out 100 Series (LO 100) 9=Embedded Integrated Lights Out Controller 3 (iLO 3)

10=Embedded Integrity Integrated Lights Out Controller 3 (iLO 3)

11=Embedded Integrated Lights Out Controller 4 (iLO 4)See section 7.1.1

OtherControllerType Optional string Describing text when ControllerType property is set to 1=Other

HardwareVersion Optional (See Note 1)

uint32 The hardware version of the management processor controller if applicable. Most Integrity server MP hardware does not surface HWVersion info.

UniqueIdentifier Conditional (See Note 1)

string An identifier which uniquely distinguishes the management processor controller from any other MP hardware. See section 7.1.2

22 Version 2.1.1

Properties Requirement Notes IPAddress Deprecated

Deprecated string The IP Address of the management processor controller’s network interface controller (NIC). Will contain either the active IPv4Address or IPv6Address of the Management Processor. If both IPv4 and IPv6 properties are configured, this property shall contain only the IPv4Address. See section 7.1.3

HostName Optional string Should contain the network hostname in use by this client.

PermanentAddress Mandatory string The logical MAC address of a the management controller’s network interface card (NIC). in the format “FFFFFFFFFFFF” where each F is a text representation of a hexidecimal digit 0x0 - 0xF.

IPv4Address Conditional string Shall be implemented if IPv4 Address is configured. The IPv4 Address of the management processor controller’s network interface controller (NIC).

IPv4SubNetMask Conditional string Shall be implemented if IPv4 Address is configured

IPv6Address Conditional string Shall be implemented if IPv6 Address is configured. The IPv6 Address of the management processor controller’s network interface controller (NIC).

IPv6SubnetPrefixLength Conditional uint16 Shall be implemented if IPv6 Address is configured. The IPv6 prefix length of the management processor controller’s network interface controller (NIC).

GatewayIPAddresses[]

Conditional Shall contain either IPv4 or IPv6 default gateway IPs. Can contain multiple IPs if both IPv6 and IPv4 gateways are configured.

URL Conditional (See Note 1)

string The Uniform Resource Locator(s) of the management processor controller’s user interface. See section 7.1.4

Version 2.1.1 23

Properties Requirement Notes SupportedProtocols[] Conditional

(See Note 1) uint16 An array of values indicating the protocol(s) supported by the management processor controller. It is assumed that any protocol listed is active and can be utilized. Values: see MOF file See section 7.1.5

NICCondition Conditional (See Note 1)

uint16 The condition of the local, MP-resident network interface connection: 0=Unknown 2=OK 3=NIC disabled 4=NIC not in operation-alternate host NIC in use, e.g. ProLiant iLO sideband operation 5=NIC in operation but disconnected 6=Failed See section 7.1.6

Properties of class CIM_ComputerSystem Dedicated Mandatory uint16

Value = 14, ‘Management’

Properties of class CIM_System CreationClassName Mandatory Key Name Mandatory Key

Properties of class CIM_EnabledLogicalElement EnabledState Mandatory uint16

The operating state of the MP: 2=Enabled 3=Disabled See section 7.1.7

Properties of class CIM_ManagedSystemElement

24 Version 2.1.1

Properties Requirement Notes OperationalStatus[] Mandatory uint16

[0] = Overall MP status: 0=Unknown 2=OK 3=Degraded 6=Error [1] = MP NIC status (optional): 0=Unknown 2=OK 3=Degraded 6=Error See section 7.1.8

Note 1: The property is conditional based on the enabled state of the MP (see EnabledState). If the MP is disabled, the property will not be populated; if the MP is enabled, the property is Mandatory.

10.2 HP_MPCollection

HP_MPCollection extends the class HP_GroupSystemSpecificCollection in ways that are specific to HP management processor systems. Implementations shall adhere to the requirements defined in HP WBEM TC P00113, HP Consolidated Status Profile for the class HP_GroupSystemSpecificCollection as well as additional requirements defined in this section.

The implementation of the class is optional (see section 7.2).

Version 2.1.1 25

Table 7 – Class properties: HP_MPCollection

Properties Requirement Notes

Properties of class HP_MPCollection

<none>

Properties of class HP_GroupSystemSpecificCollection

GroupOperationalStatus[] Mandatory uint16 [0] = overall MP status: 0 =Unknown 2=OK 3=Degraded 6=Error See section 7.2.1

Properties of class CIM_SystemSpecificCollection

InstanceID Mandatory Key

10.3 HP_MPHostedCollection HP_MPHostedCollection extends the class HP_GroupHostedCollection in ways that are specific to HP management processor systems. It defines the relationship between the management processor system collection and the computer system of which it is a part. Implementations shall adhere to the requirements defined in HP WBEM TC P00113, HP Consolidated Status Profile for the class HP_GroupHostedCollection as well as additional requirements defined in this section.

The implementation of the class is conditional (see section 7.3).

Table 8 – Class properties: HP_MPHostedCollection

Properties Requirement Notes Antecedent Mandatory REF:HP_ComputerSystem

Dependent Mandatory REF:HP_MPCollection

10.4 HP_MPMemberOfCollection HP_MPMemberOfCollection extends the class CIM_MemberOfPolicyCollection in ways that are specific to HP management processor systems. It defines the aggregate relationship between the management processor system collection and the individual management processor system(s) which comprise it. Implementations shall adhere to the requirements defined in DSP1006, System Collections Profile and HP WBEM TC P00113, HP Consolidated Status Profile for the class CIM_MemberOfPolicyCollection as well as additional requirements defined in this section.

The implementation of the class is conditional (see section 7.4).

26 Version 2.1.1

Table 9 – Class properties: HP_MPMemberOfCollection

Properties Requirement Notes Member Mandatory REF:HP_ManagementProcessor

Collection Mandatory REF:HP_MPCollection

Included Mandatory Writeable property to indicate if the member will participate in status roll-up as described in the HP WBEM TC P00113, HP Consolidated Status Profile

10.5 HP_MPComponentCS HP_MPComponentCS extends the class CIM_ComponentCS (which extends CIM_SystemComponent) in ways that are specific to HP systems. It defines the relationship between the management processor system and the computer system of which it is a part or subcomponent. Implementations shall adhere to the requirements defined in DSP1004, Base Server Profile for the class CIM_SystemComponent as well as additional requirements defined in this section.

Table 10 – Class properties: HP_MPComponentCS

Properties Requirement Notes GroupComponent Mandatory REF:HP_ComputerSystem

PartComponent Mandatory REF:HP_ManagmentProcessor

10.6 HP_RegisteredProfile The HP_RegisteredProfile class is defined by document HP WBEM TC P00100, HP Profile Registration Profile.

Table 11 – Class properties: HP_RegisteredProfile

Properties Requirement Notes RegisteredName Mandatory “HP Management Processor Lite”

RegisteredVersion Mandatory This property shall have a value corresponding to the version of this profile (2.1.1).

RegisteredOrganization Mandatory “Other”

OtherRegisteredOrganization Mandatory “HP WBEM TC”

10.7 HP_MPFirmware

HP_MPFirmware extends the class CIM_SoftwareIdentity in ways that are specific to HP management processor systems and is used to describe MP Firmware. Implementation shall adhere to the requirements defined in DMTF DSP1023, Software Inventory Profile.

Version 2.1.1 27

Table 12 – Class properties: HP_MPFirmware

Properties Requirement Notes Classifications[] Mandatory This property shall have the value of

10=’Firmware’ in the [0] element.

Manufacturer Mandatory Indicates the manufacturer of the firmware, e.g. “HP”.

Classifications[] Mandatory [0]=Software classification: 10=Firmware

Major Version Mandatory The major version value of the MP firmware. If version string begins with non-numeric characters, Major Version will represent the most significant numeric version within the string,

Minor Version Mandatory The minor version value of the MP firmware, If version string begins with non-numeric characters, Minor Version will represent the most significant numeric version beyond Major Version.

VersionString Mandatory A string representing the complete firmware version information.

10.8 HP_MPElementFirmwareIdentity

HP_MPFirmware extends the class CIM_ElementSoftwareIdentity that associates a management processor to its corresponding firmware.

10.9 HP_MPInstalledFirmwareIdentity

HP_MPFirmware extends the class CIM_InstalledSoftwareIdentity that associates a management processor to its corresponding installed firmware.



Class Durable Name(s)


Circumstances for Change

Table 14 – Correlatable IDs generated by this Profile

Class Correlatable ID(s)



HP_ManagementProcessor UniqueIdentifier

28 Version 2.1.1

Version 2.1.1 29

ANNEX A (normative)

Change Log

Version Date Description

1.0 6/9/2006 Initial Draft & submission to HP WBEM TC review 1.0 6/13/2006 Changes per HP WBEM TC review of 6/12/2006 (see CR00101.002)

1.0 6/16/2006 Changes per HP WBEM TC review of 6/14/2006 (see CR00101.003). The document was approved pending changes.

1.0.1 3/13/2008 Added state propagation filtering support 1.1.0 12/15/2008 Added RequestStateChange method support 1.3.0 02/15/2009 Added iLO 3 enum values

2.0.0 08/17/2009

Changed MP.HardwareVersion to optional for Integrity MP/iLO support, SWIdentity,.Major &MinorVersion are better defined for Integrity iLO/MP. Added HP_ManagementProciessor properties to expose both ipv4 and ipv6 addresses for Diagonal+.

2.0.1 09/17/2009 Correction of HP_ManagementProcessor.GatewayIPAddresses[] property name to match MOF. Better define behavior of IPAddress property if both IPv4 and IPv6 addrs are configured.

2.1.0 03/04/2011 Added iLO4 ControllerType enum values Updated to include HP_MPFirmware

2.1.1 4/22/2011 v 2.1.1 Add PCIDevice association. Add missing classes from Table 5 in section 10

30 Version 2.1.1


Acknowledgments

Version 2.1.1 31



CR Number Date Title

CR00101.001 6/9/2006 Initial draft & submission to HP WBEM TC review. CR00101.002 6/13/2006 Documents comments and changes from HP WBEM TC review of 6/12/2006. CR00101.003 6/16/2006 Documents comments and changes from HP WBEM TC review of 6/14/2006 CR00134.001 3/13/2008 Initial draft of CR00134

CR00146.001 06/03/2009 Added LO100 & iLO 3 ControllerTypes from last CR, and changed MP.HardwareVersion to conditional

CR00146.002 08/17/2009 Added changes related to TC comments from first review. Major/Minor f/w versions to be exposed for Integrity instead of optional. Also added Diagonal+ requirements to report IPv4 and IPv6 properties for the ManagementProcessor’s NIC.

32 Version 2.1.1

Bibliography



Date: 09/11/08

Version: 1.3.0

HP Fan Profile




2 Version 1.3.0

Contents

Foreword ...................................................................................................................................................... 5 Introduction .................................................................................................................................................. 6 1 Scope ......................................................................................................................................................... 7 2 Normative References ............................................................................................................................... 7 3 Terms and Definitions ................................................................................................................................ 7 4 Symbols and Abbreviated Terms ............................................................................................................... 9 5 Synopsis ..................................................................................................................................................... 9 6 Description ................................................................................................................................................ 9 7 Implementation Requirements ................................................................................................................. 11 8 Methods.................................................................................................................................................... 13 9 Use Cases ................................................................................................................................................ 13 10 CIM Elements ......................................................................................................................................... 17 11 Durable Names and Correlatable IDs ................................................................................................... 20 Bibliography .............................................................................................................................................. 25

Figures

Figure 1 – HP Fan Profile: Class Diagram ................................................................................................. 10 Figure 2 – HP Fan Profile: Inheritance Hierarchy Diagram ........................................................................ 10 Figure 3 – HP Fan Profile: Object Diagram ............................................................................................... 14 Figure 4 – HP Fan Profile: Fan Redundancy Object Diagram ................................................................... 15 Figure 5 – HP Fan Profile: Associated Cooling Object Diagram ................................................................ 16

Tables

Table 1 – Related Profiles ........................................................................................................................... 9 Table 1 – Related Profiles ........................................................................................................................... 9 Table 2 – CIM Elements – HP Fan Profile .................................................................................................. 17 Table 2 – CIM Elements – HP Fan Profile .................................................................................................. 17 Table 3 – Class: HP_Fan ............................................................................................................................ 18 Table 3 – Class: HP_Fan ............................................................................................................................ 18 Table 4 – Class: HP_RegisteredProfile ..................................................................................................... 18 Table 4 – Class: HP_RegisteredProfile ..................................................................................................... 18 Table 5 – Class: HP_CoolingCollection ...................................................................................................... 18 Table 5 – Class: HP_CoolingCollection ...................................................................................................... 18 Table 6 – Class: HP_CoolingReduncancySet ............................................................................................ 19 Table 6 – Class: HP_CoolingReduncancySet ............................................................................................ 19 Table 7 – Class: HP_MemberOfCoolingRedundancy ................................................................................ 19 Table 7 – Class: HP_MemberOfCoolingRedundancy ................................................................................ 19 Table 8 – Class: HP_HostedCoolingRedundancySet ................................................................................. 19 Table 8 – Class: HP_HostedCoolingRedundancySet ................................................................................. 19 Table 9 – Class: HP_MemberOfCoolingCollection ..................................................................................... 19 Table 9 – Class: HP_MemberOfCoolingCollection ..................................................................................... 19 Table 10 – Class: HP_HostedCoolingCollection......................................................................................... 20 Table 10 – Class: HP_HostedCoolingCollection......................................................................................... 20

Version 1.3.0 3

Table 11 – Class: HP_SystemFan .............................................................................................................. 20 Table 11 – Class: HP_SystemFan .............................................................................................................. 20 Table 12 – Class: HP_AssociatedCooling .................................................................................................. 20 Table 13 – Durable Names generated by this Profile ................................................................................. 20 Table 13 – Durable Names generated by this Profile ................................................................................. 20 Table 14 – Correlatable IDs generated by this Profile ................................................................................ 21 Table 14 – Correlatable IDs generated by this Profile ................................................................................ 21

4 Version 1.3.0

Foreword

The HP Fan Profile P00102 was prepared by the HP WBEM TC.

Version 1.3.0 5

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 logical Fans in HP systems. 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.3.0

1 Scope The HP Fan profile extends the management capability of referencing profiles by adding the capability to represent the logical fans, fan redundancy and fan consolidated status in HP specific ways.

2 Normative References The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.





DMTF DSP1013, Fan Profile



HP WBEM TC P00115, HP Fan Physical Asset Profile

HP WBEM TC P00104, HP Sensors Profile


2.3 Other References ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards – Downloadable from http://isotc.iso.org/livelink/livelink.exe?func=ll&objId=4230456&objAction=browse&sort=subtype


3 Terms and Definitions For the purposes of this document, the following terms and definitions apply.

can used for statements of possibility and capability, whether material, physical or causal

cannot used for statements of possibility and capability, whether material, physical or causal



Version 1.3.0 7

conditional used to indicate requirements strictly to be followed in order to conform to the document when the specified conditions are met

mandatory used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted

may used to indicate a course of action permissible within the limits of the document

need not used to indicate a course of action permissible within the limits of the document

optional used to indicate a course of action permissible within the limits of the document

referencing profile Indicates a profile which owns the definition of this class and can include a reference to this profile in its “Related Profiles” section.

shall used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted

shall not used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted

should used to indicate that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others, or that a certain course of action is preferred but not necessarily required

should not used to indicate that a certain possibility or course of action is deprecated but not prohibited


None.

8 Version 1.3.0

5 Synopsis Profile Name: HP Fan Profile

Version: 1.3.0



Central Class: HP_Fan

Scoping Class: Same as DSP1013 – Fan Profile

Extends: DMTF DSP1013, Fan Profile 1.0.0


The HP Fan profile extends DMTF DSP1013 and specializes HP WBEM TC P00113 to add fan, fan redundancy, and fan consolidated status characteristics that are specific to HP systems.


Profile Name Organization Version Relationship Behavior DSP1013 – Fan Profile DMTF 1.0.0 Mandatory

P00100 – HP Profile Registration Profile

HP WBEM TC 1.0.0 Mandatory

P00113 – HP Consolidated Status Profile

HP WBEM TC 1.0.0 Specializes

P00115 – HP Fan Physical Asset Profile

HP WBEM TC 1.0.0 Optional

P00104 – HP Sensors Profile HP WBEM TC 1.0.0 Optional

6 Description The HP Fan Profile describes the properties and methods of HP fans, fan collections and redundant fans in a managed system. Also included are definitions of associations that describe the relationship of the HP fan with fan collections, redundancy sets, profile version information and the computer system.

Figure 1 represents the class schema for the HP Fan Profile. Figure 2 represents additional inheritance hierarchies for classes described in this profile.

In the HP Fan Profile, the collection of fans is represented by an instance of HP_CoolingCollection, containing a consolidated status. The redundancy of fans is represented by instances of HP_CoolingRedundancySet that contains respective HP_Fan instances.

Version 1.3.0 9

CIM_Fan

see DMTF Fan Profile

HP_HostedCoolingCollection

HP_CoolingCollection

HP_Fan

CIM_ComputerSystem

see referencing profile

HP_CoolingRedundancySet


see HP profile registration profile

HP_SystemFan

HP_GroupSystemSpecificCollection

see HP Consolidated Status profile

1

1..*1..*

0..* 0..1

1..*

1

*

1

0..*

HP_MemberOfCoolingCollection

HP_MemberOfCoolingRedundancy

HP_HostedCoolingRedundancySet

HP_NumericSensor

see HP sensors profile

CIM_AssociatedSensor(see HP Sensors profile) 1..**

CIM_ManagedSystemElement


HP_AssociatedCooling

1..*

*

HP_ElementConformsToProfile(see HP Profile Registration

profile) Figure 1 – HP Fan Profile: Class Diagram



HP_MemberOfCoolingRedundancy HP_MemberOfCoolingCollection HP_CoolingRedundancySet

CIM_RedundancySet


HP_SystemFan

CIM_SystemDevice



CIM_OwningCollectionElement





Figure 2 – HP Fan Profile: Inheritance Hierarchy Diagram

10 Version 1.3.0

7 Implementation Requirements This section details the requirements related to the arrangement of instances and properties of instances for implementations of this profile.

7.1 HP_Fan

There shall be at least one instance of HP_Fan instantiated.

7.1.1 HP_Fan.FanType

HP_Fan.FanType property shall be implemented. This property describes the type of the fan using an appropriate enumeration value.

7.1.2 HP_Fan.Description

HP_Fan.Description property may optionally be implemented. This property shall contain the detailed description for this fan that includes Caption, Name or ElementName, the corresponding string value of FanType and the corresponding string value of OperationalStatus[0] or StatusDescriptions[0].

7.1.3 HP_Fan.OtherIdentifyingInfo[]

HP_Fan.OtherIdentifyingInfo[] property may optionally be implemented. This property can be used to describe additional information about the element.

7.1.4 HP_Fan.IdentifyingDescriptions[]

HP_Fan.IdentifyingDescriptions[] property may optionally be implemented. This property describes the additional information for the corresponding OtherIndentifyingInfo element.

7.1.5 Current Fan Speed

Current fan speed modeling is conditional. If the appropriate fan speed information is available, the properties described in this section shall be implemented. These properties allow for a lightweight implementation of current fan speed.

Current fan speed may optionally also be implemented by utilizing HP_NumericSensor. Please refer to HP WBEM TC P00104, HP Sensors Profile for requirements.

7.1.5.1 HP_Fan.CurrentSpeed

If the current fan speed can be represented in units available with HP_Fan.CurrentSpeedUnits property, HP_Fan.CurrentSpeed property shall be implemented. This property describes the current fan speed in units represented by HP_FanCurrentSpeedUnits.

If current fan speed cannot be represented in units available with HP_Fan.CurrentSpeedUnits property, HP_Fan.CurrentSpeed shall return a NULL value.

7.1.5.2 HP_Fan.CurrentSpeedUnits

If HP_Fan.CurrentSpeed contains a value, HP_Fan.CurrentSpeedUnits property shall be implemented. This property describes the units of the current fan speed represented by HP_Fan_CurrentSpeed.

If HP_Fan.CurrentSpeed contains a NULL value, HP_Fan.CurrentSpeedUnits shall return a NULL value.

Version 1.3.0 11

7.1.5.3 HP_Fan.CurrentSpeedState

If the current fan speed state can be represented, HP_Fan.CurrentSpeedState property shall be implemented. This property describes the current fan speed state using an appropriate enumeration value

If CurrentSpeedState cannot be represented, the property shall return a NULL value.

7.2 HP_CoolingRedundancySet

Fan redundancy modeling is optional. Even when a managed system supports and implements the redundancy, the redundant fans may co-exist with non-redundant fans. The conditions and requirement placed in this section only refer to the HP_Fan instances representing redundant fans.

Fan redundancy is modeled using HP_CoolingRedundancySet which is associated to the HP_Fan instances through HP_MemberOfCoolingRedundancy associations. Instances of HP_CoolingRedundancySet are associated to its containing instance of CIM_ComputerSystem through the HP_HostedCoolingRedundancySet association.

When fan redundancy is implemented, there shall be at least one instance of HP_CoolingRedundancySet. The HP_MemberOfCoolingRedundancy association shall be used to associate the HP_CoolingRedundancySet instance with the HP_Fan instance.

Multiple instances of HP_CoolingRedundancySet may exist. Furthermore, fan redundancy sets may share fans; instances of HP_Fan may be members of more than one HP_CoolingRedundancySet instance using HP_MemberOfCoolingRedundancy associations.

7.3 HP_CoolingCollection

Fan collection modeling is optional. There may be one or more instance of HP_CoolingCollection instantiated. Instances of HP_Fan are associated to HP_CoolingCollection through the HP_MemberOfCoolingCollection association. Instances of HP_CoolingCollection are associated to its containing instance of CIM_ComputerSystem through the HP_HostedCoolingCollection association.

7.3.1 HP_CoolingCollection.Description

HP_CoolingCollection.Description property shall be implemented. This property shall contain the detailed description for the collection, that includes the corresponding string value of GroupOperationalStatus[0] or GroupStatusDescriptions[0].

7.3.2 HP_CoolingCollection.GroupOperationalStatus

HP_CoolingCollection.GroupOperationalStatus shall comprehend the status of all associated instances of non-redundant fans and associated instances of HP_CoolingRedundancySet, if redundancy is modeled.

Non-redundant Fans OperationalStatus[0]

Cooling RedundancySet RedundancyStatus

GroupOperationalStatus[0]

All OK FullyRedundant

Booted with uninstalled fans: RedundancyDegraded or RedundancyLost and all Fan

OK

12 Version 1.3.0

OperationalStatus OK

Any Not Error Degraded or Redundancy Lost Degraded

Any Error Overall Failure Error

7.4 HP_SystemFan

There shall be one instance of HP_SystemFan instantiated for each instance of HP_Fan. This class associates an instance of HP_Fan with its containing instance of CIM_ComputerSystem.

7.5 HP_MemberOfCoolingRedundancy

When fan redundancy is implemented, there shall be at least one instance of HP_MemberOfCoolingRedundancy instantiated for each instance of HP_Fan that is capable of redundancy. This class associates an instance of redundancy-capable HP_Fan to the respective instance of HP_CoolingRedundancySet.

7.6 HP_HostedCoolingRedundancySet

When fan redundancy is implemented, there shall be one instance of HP_HostedCoolingRedundancySet instantiated for each instance of HP_CoolingRedundancySet. This class associates an instance of HP_CoolingRedundancySet with its containing instance of CIM_ComputerSystem.

7.7 HP_MemberOfCoolingCollection

When fan collection is implemented, there shall be one instance of HP_MemberOfCoolingCollection instantiated for each instance of HP_Fan. This class associates an instance of HP_Fan to the respective instance of HP_CoolingCollection.

7.8 HP_HostedCoolingCollection

When fan collection is implemented, there shall be one instance of HP_HostedCoolingCollection instantiated for each instance of HP_CoolingCollection. This class associates an instance of HP_CoolingCollection with the its containing instance of CIM_ComputerSystem.

7.9 HP_AssociatedCooling

Associated cooling modeling is optional. If associated cooling modeling is implemented, the fan represented by the referenced instance of HP_Fan shall provide cooling for managed system element represented by the referenced instance of CIM_ManagedSystemElement.

There may be one or more instance of HP_AssociatedCooling instantiated. Instances of HP_Fan are associated to CIM_ManagedSystemElement through the HP_AssociatedCooling association.

8 Methods None.

Version 1.3.0 13

9 Use Cases

9.1 Object Diagrams

Figure 3 represents a possible instantiation of the HP Fan Profile. In this case, system1 has two fans, fan1 and fan2. Fan1 and fan2 belong to coolingcollection1, which describes the overall group operational status of the fans as being OK. This diagram also shows an example of the HP_Fan.Description property for fan1 and fan2, constructed from property values for ElementName, FanType and value map string of OperationalStatus[0].

For simplicity most of the properties have been removed from the classes.

system1:CIM_ComputerSystem

fan1:HP_Fan

OperationalStatus: (OK)Element Name: “Fan 1”FanType: 11 (Chassis)Description: Fan 1 provides cooling for the Chassis: Status is OK.

HP_SystemFan

profile1:CIM_RegisteredProfile

RegisteredName: Base System Profile


RegisteredName: Fan Profile

profile1:HP_RegisteredProfile

RegisteredName: HP Fan Profile



HP_ExtendsProfile

coolingcollection1:HP_CoolingCollection

GroupOperationalStatus: (OK)




fan2:HP_Fan


Figure 3 – HP Fan Profile: Object Diagram

Figure 4 represents another possible instantiation of the HP Fan Profile, with modeled redundancy. In this case, system1 has four fans: fan1, fan2, fan3 and fan4. All of the fans belong to coolingcollection1. Fan1 and fan2 belong to coolingredundancyset1. Fan3 and fan4 belong to coolingredundancyset2. Fan2 and Fan3 belong to sharedcoolingredundancyset.

Please note that fan2 and fan3 belong to multiple instances of HP_CoolingRedundancySet.

The overall group operational status of the fans is Error.


14 Version 1.3.0


fan2:HP_Fan

OperationalStatus: (Failed)

fan1:HP_Fan


HP_SystemFan




RegisteredName: Fan Profile


RegisteredName: HP Fan Profile



HP_ExtendsProfile


GroupOperationalStatus:(Error)

fan3:HP_Fan

OperationalStatus: (OK)

fan4:HP_Fan


coolingredundancyset1:HP_CoolingRedundacySet

RedundancyStatus:(Overall Failure)

sharedcoolingredundancyset:HP_CoolingRedundan

cySetRedundancyStatus:(Degraded Redundancy)

coolingredundancyset2:HP_CoolingRedundancySetRedundancyStatus:(Fully Redundant)

HP_MemberOfCoolingRedundancy HP_MemberOfCoolingRedundancyHP_MemberOfCoolingRedundancy




Figure 4 – HP Fan Profile: Fan Redundancy Object Diagram

Figure 5 represents a possible instantiation of the HP Fan Profile. In this case, system1 has a processor and fan, cpu1 and, fan1 respectively. fan1 is associated to cpu1 via HPAssociatedCooling; fan1 provides cooling for cpu1.


Version 1.3.0 15


fan1:HP_Fan


HP_SystemFanCIM_SystemDevice

HP_AssociatedCoolingcpu1:CIM_Processor

Figure 5 – HP Fan Profile: Associated Cooling Object Diagram

16 Version 1.3.0

9.2 Retrieve the Fan Group Operational Status

For the given instance of HP_Fan, select the associated instance of HP_CoolingCollection through HP_MemberOfCoolingCollection association. Retrieve the value of HP_CoolingCollection.GroupOperationalStatus property.

9.3 Retrieve the Fan Redundancy Status

For the given instance of HP_Fan, select the associated instance of HP_CoolingRedundancySet through HP_MemberOfCoolingRedundancy association. Retrieve the value of HP_CoolingRedundancySet.RedundancyStatus property.

9.4 Determine if Fan is shared by Redundancy Sets

For the given instance of HP_Fan, select associated instances of HP_CoolingRedundancySet through HP_MemberOfCoolingRedundancy association. If the instance of HP_Fan is associated to more than one instance HP_CoolingRedundancySet, it is shared by redundancy sets.

9.5 Determine the Type of Cooling Collection

For the given instance of HP_CoolingCollection, select an associated instance of HP_Fan through HP_MemberOfCoolingCollection association. The type of Cooling Collection is described by the associated HP_Fan.FanType property enumeration.

10 CIM Elements The implementation requirements for the classes and properties described in this section are defined in the “Implementation Requirements” section (Section 7).

Table 2 – CIM Elements – HP Fan Profile


HP_Fan Mandatory See Sections 7.1 and 10.1 HP_RegisteredProfile Mandatory See Section 10.2 HP_CoolingCollection Optional See Sections 7.3 and 10.3 HP_CoolingRedundancySet Optional See Sections 7.2 and 10.4 HP_MemberOfCoolingRedundancy Conditional See Sections 7.5 and 10.5 HP_MemberOfCoolingCollection Conditional See Sections 7.7 and 10.7 HP_HostedCoolingRedundancySet Conditional See Sections 7.6 and 10.6 HP_HostedCoolingCollection Conditional See Sections 7.8 and 10.8 HP_SystemFan Mandatory See Sections 7.4 and 10.9 HP_AssociatedCooling Optional See Sections 7.9and 10.10

Indications None defined in this profile

Version 1.3.0 17

10.1 HP_Fan

HP_Fan is used to represent a fan in a managed system.

Table 3 – Class: HP_Fan

Properties Requirement Notes HP_Fan

FanType Mandatory See Section 7.1.1 CurrentSpeed Conditional See Section 7.1.5.1 CurrentSpeedUnits Conditional See Section 7.1.5.2 CurrentSpeedState Conditional See Section 7.1.5.3

CIM_Fan OtherIdentifyingInfo[] Optional See Section 7.1.3 IdentifyingDescriptions[] Optional See Section 7.1.4 Description Optional See Section 7.1.2


The HP_RegisteredProfile class is defined by the HP Profile Registration Profile.


Properties Requirement Description RegisteredName Mandatory "HP Fan" RegisteredVersion Mandatory “1.3.0” RegisteredOrganization Mandatory Other (1) OtherRegisteredOrganization Mandatory “HP WBEM TC”

10.3 HP_CoolingCollection

HP_CoolingCollection is used to represent a fan collection in a managed system.

Table 5 – Class: HP_CoolingCollection

Properties Requirement Notes InstanceID Mandatory Key GroupOperationalStatus Mandatory See Section 7.3 ElementName Mandatory Description Mandatory See Section 7.3.1

18 Version 1.3.0

10.4 HP_CoolingRedundancySet

HP_CoolingRedundancySet is used to represent a fan redundancy set in a managed system.

Table 6 – Class: HP_CoolingReduncancySet

Properties Requirement Notes InstanceID Mandatory Key RedundancyStatus Mandatory See Section 7.2 TypeOfSet Mandatory MinNumberNeeded Mandatory ElementName Mandatory

10.5 HP_MemberOfCoolingRedundancy

HP_MemberOfCoolingRedundancy is used to represent an association between HP_Fan and HP_CoolingRedundancySet.

Table 7 – Class: HP_MemberOfCoolingRedundancy

Properties Requirement Notes Collection Mandatory Key: References HP_CoolingRedundancySet

Member Mandatory Key: References HP_Fan

10.6 HP_HostedCoolingRedundancySet

HP_HostedCoolingRedundancySet is used to represent an association between HP_CoolingRedundancySet and its containing instance of CIM_ComputerSystem.

Table 8 – Class: HP_HostedCoolingRedundancySet

Properties Requirement Notes OwningElement Mandatory Key: References HP_ComputerSystem

OwnedElement Mandatory Key: References HP_CoolingRedundancySet

10.7 HP_MemberOfCoolingCollection

HP_MemberOfCoolingCollection is used to represent an association between HP_Fan and HP_CoolingCollection.

Table 9 – Class: HP_MemberOfCoolingCollection

Properties Requirement Notes Collection Mandatory Key: References HP_CoolingCollection

Member Mandatory Key: References HP_Fan

Version 1.3.0 19

10.8 HP_HostedCoolingCollection

HP_HostedCoolingCollection is used to represent an association between HP_CoolingCollection and its containing instance of CIM_ComputerSystem.

Table 10 – Class: HP_HostedCoolingCollection

Properties Requirement Notes Antecedent Mandatory Key: References HP_ComputerSystem

Dependent Mandatory Key: References HP_CoolingCollection

10.9 HP_SystemFan

HP_SystemFan is used to represent an association between HP_Fan and the its containing instance of CIM_ComputerSystem.

Table 11 – Class: HP_SystemFan

Properties Requirement Notes GroupComponent Mandatory Key: References HP_ComputerSystem

PartComponent Mandatory Key: References HP_Fan

10.10 HP_AssociatedCooling

HP_AssociatedCooling is used to represent an association between HP_Fan and CIM_ManagedSystemElement.

Table 12 – Class: HP_AssociatedCooling

Properties Requirement Notes Antecedent Mandatory Key: References HP_Fan

Dependent Mandatory Key: References CIM_ManagedSystemElement

11 Durable Names and Correlatable IDs Table 13 – Durable Names generated by this Profile

Class Durable Name(s) Source ID Information


None Defined


Class Correlatable ID(s) Source ID Information


None Defined

20 Version 1.3.0

ANNEX A (normative)

Change Log

Version Date Description 0.1 5/9/06 Initial draft

0.2 5/30/06 Updates to properties, removed redundancy/status mapping and referenced physical asset profile

1.0 5/31/06 Updated properties

1.0 11/29/06

Updated the following: • All HP_CoolingRedundancyCollection references now

HP_HostedCoolingRedundancySet o Antecedent and Dependent now OwningElement and

OwnedElement (per parent class) • Removed sections in 8 because there are no methods defined • Durable Names and Correlatable IDs removed because there are really no

such names and IDs generated by this profile • Updated class diagram to update references and for typos • Updated instance diagrams to remove physical model (this is described in

physical asset profile) and for typos • Minor wording updates throughout document

1.1.0 4/2/08

Added properties to HP_Fan, added references to HP WBEM TC P00104, HP Sensors Profile and updated the class diagram to allow for the representation of current fan speed.

Fixed typos throughout document.

1.2.0 7/17/08

Updated the following: • Removed "For each HP_CoolingCollection instance, all associated HP_Fan

instances must have the same value for HP_Fan.FanType, if this property is implemented." in HP_CoolingCollection (7.3). We only have one cooling collection instance in Spinner; can we remove this?

• Added HP_AssociatedCooling (7.9 and 10.10) • Added simple use case for associated cooling (figure 5)

1.3.0 9/11/08

Updated the following: Section 7, Added more detail on the contents of the Description property for

Fan and FanCoolingCollection. Included example in Section 9 Section 7, added algorithm for GroupOperationalStatus Section 10, added missing section references and optional Description

property.

Version 1.3.0 21


Acknowledgments

22 Version 1.3.0



CR

Number Date Title CR00106 5/31/06 Create HP profile for the environmental model CR00143 9/11/08 Detailed string properties

Version 1.3.0 23

Bibliography



Date: 04/28/09

Version: 1.3.0

HP Power Supply Profile

© Copyright 2008, 2009 Hewlett-Packard Development Company, L.P.



2 Version 1.3.0

Contents

Foreword ....................................................................................................................................................... 5 Introduction.................................................................................................................................................... 6 1 Scope .................................................................................................................................................... 7 2 Normative References ........................................................................................................................... 7

2.1 Approved References ................................................................................................................. 7 2.2 References Under Development ................................................................................................ 7 2.3 Other References ........................................................................................................................ 7


7.1 HP_PowerSupply ...................................................................................................................... 11 7.2 HP_PowerRedundancySet ....................................................................................................... 11 7.3 HP_PowerCollection ................................................................................................................. 12 7.4 HP_SystemPowerSupply .......................................................................................................... 12 7.5 HP_MemberOfPowerRedundancy ........................................................................................... 12 7.6 HP_HostedPowerRedundancySet ............................................................................................ 12 7.7 HP_MemberOfPowerCollection ................................................................................................ 12 7.8 HP_HostedPowerCollection ..................................................................................................... 12 7.9 HP_SuppliesPower ................................................................................................................... 12

8 Methods ............................................................................................................................................... 13 9 Use Cases ........................................................................................................................................... 13

9.1 Object Diagrams ....................................................................................................................... 13 Retrieve the Power Supply Group Operational Status ........................................................................ 18 9.2 Retrieve the Power Supply Redundancy Status ....................................................................... 18 9.3 Determine the Type of Power Collection .................................................................................. 18

10 CIM Elements ...................................................................................................................................... 18 10.1 HP_PowerSupply ...................................................................................................................... 18 10.2 HP_RegisteredProfile ............................................................................................................... 19 10.3 HP_PowerCollection ................................................................................................................. 19 10.4 HP_PowerRedundancySet ....................................................................................................... 19 10.5 HP_MemberOfPowerRedundancy (subclassed from CIM_MemberOfCollection) ................... 20 10.6 HP_MemberOfPowerRedundancy (subclassed from CIM_MemberOfPolicyCollection) ......... 20 10.7 HP_HostedPowerRedundancySet ............................................................................................ 20 10.8 HP_MemberOfPowerCollection (subclassed from CIM_MemberOfCollection) ....................... 20 10.9 HP_MemberOfPowerCollection (subclassed from CIM_MemberOfPolicyCollection) .............. 21 10.10 HP_HostedPowerCollection ..................................................................................................... 21 10.11 HP_SystemPower Supply ......................................................................................................... 21 10.12 HP_SuppliesPower ................................................................................................................... 21


Version 1.3.0 3

Figures

Figure 1 – HP Power Supply Profile: Class Diagram .................................................................................. 10 Figure 2 – HP Power Supply Profile: Inheritance Hierarchy Diagram ........................................................ 10 Figure 3 – HP Power Supply Profile: Object Diagram ................................................................................ 14 Figure 4 – HP Power Supply Profile: Power Supply Redundancy Object Diagram.................................... 15 Figure 5 – HP Power Supply Profile: Associated Power Object Diagram .................................................. 16 Figure 6 – HP Power Supply Profile: Power Supply Redundancy with Ignored Status .............................. 17

4 Version 1.3.0

Tables

Table 1 – Related Profiles ............................................................................................................................. 9 Table 2 – CIM Elements – HP Power Supply Profile .................................................................................. 18 Table 3 – Class: HP_PowerSupply ............................................................................................................. 19 Table 4 – Class: HP_RegisteredProfile ..................................................................................................... 19 Table 5 – Class: HP_PowerCollection ........................................................................................................ 19 Table 6 – Class: HP_PowerReduncancySet .............................................................................................. 19 Table 7 – Class: HP_MemberOfPowerRedundancy .................................................................................. 20 Table 8 – Class: HP_MemberOfPowerRedundancy .................................................................................. 20 Table 9 – Class: HP_HostedPowerRedundancySet ................................................................................... 20 Table 10 – Class: HP_MemberOfPowerCollection ..................................................................................... 20 Table 11 – Class: HP_MemberOfPowerCollection ..................................................................................... 21 Table 12 – Class: HP_HostedPowerCollection........................................................................................... 21 Table 13 – Class: HP_SystemPowerSupply ............................................................................................... 21 Table 15 – Durable Names generated by this Profile ................................................................................. 22 Table 16 – Correlatable IDs generated by this Profile ................................................................................ 22

Version 1.3.0 5

Foreword

The HP Power Supply Profile P00103 was prepared by the HP WBEM TC.

6 Version 1.3.0

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 logical Power Supplies in HP systems. 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.

Version 1.3.0 7

1 Scope The HP Power Supply profile extends the management capability of referencing profiles by adding the capability to represent the logical power supplies, power supply redundancy and power supply consolidated status in HP specific ways.






DMTF DSP1017, Power Supply Profile



HP WBEM TC P00116, HP Power Supply Physical Asset Profile









8 Version 1.3.0












None.

Version 1.3.0 9

5 Synopsis Profile Name: HP Power Supply Profile

Version: 1.3.0


CIM Schema Version: 2.17 *

Central Class: HP_PowerSupply

Scoping Class: Same as DSP1015 – Power Supply Profile

Extends: DMTF DSP1015, Power Supply Profile 1.1.0


The HP Power Supply profile extends DMTF DSP1015 and specializes HP WBEM TC P00107 to add power supply, power supply redundancy, and power supply consolidated status characteristics that are specific to HP systems.



DSP1017 – Power Supply Profile DMTF 1.1.0 Mandatory



P00107 – HP Consolidated Status profile


P00116 – HP Power Supply Physical Asset Profile


6 Description The HP Power Supply Profile describes the properties and methods of HP power supplies, power supply collections and redundant power supplies in a managed system. Also included are definitions of associations that describe the relationship of the HP power supply with power supply collections, redundancy sets, profile version information and the computer system.

Figure 1 represents the class schema for the HP Power Supply Profile. Figure 2 represents additional inheritance hierarchies for classes described in this profile.

In the HP Power Supply Profile, the collection of power supplies is represented by an instance of HP_PowerCollection, containing a consolidated status. The redundancy of power supplies is represented by instances of HP_PowerRedundancySet that contains respective HP_PowerSupply instances.

* Schema version 2.18 needed when CIM_MemberOfPolicyCollection implemented for state Propagation Filtering. See P00107 - HP Consolidated Status Profile version 1.0.1.

10 Version 1.3.0

CIM_PowerSupply

see DMTF Power Supply profile

HP_HostedPowerCollection

HP_PowerCollection

HP_PowerSupply

PowerSupplyType

CIM_ComputerSystem


HP_PowerRedundancySet HP_RegisteredProfile


HP_SystemPowerSupply

HP_ElementConformsToProfile(see HP Profile Registration profile)



1

1..*

1..*

0..* 0..1

1..*

1

*

1

0..*

HP_MemberOfPowerCollection

HP_MemberOfPowerRedundancy

HP_HostedPowerRedundancySet

CIM_LogicalDevice


HP_SuppliesPower

1..*

*

HP_PowerMeter

see DMTF Sensors profile HP_AssociatedPowerMeter

1

*

Figure 1 – HP Power Supply Profile: Class Diagram

CIM_MemberOfCollection orCIM_MemberOfPolicyCollection


HP_MemberOfPowerRedundancy HP_MemberOfPowerCollection HP_PowerRedundancySet

CIM_RedundancySet



CIM_SystemDevice

see DMTF Power Supply Profile



see DMTF Power Supply Profile




HP_PowerMeter

CIM_NumericSensor

see DMTF Sensor Profile

HP_AssociatedPowerMeter

CIM_AssociatedSensor

see DMTF Sensor Profile

Figure 2 – HP Power Supply Profile: Inheritance Hierarchy Diagram

Version 1.3.0 11


7.1 HP_PowerSupply

There shall be at least one instance of HP_PowerSupply instantiated.

7.1.1 HP_PowerSupply.PowerSupplyType

HP_PowerSupply.Power SupplyType property shall be implemented. This property describes the type of the power supply using an appropriate enumeration value.

7.1.2 HP_PowerSupply.OtherIdentifyingInfo[]

HP_PowerSupply.OtherIdentifyingInfo[] property may optionally be implemented. This property can be used to describe additional information about the element.

7.1.3 HP_PowerSupply.IdentifyingDescriptions[]

HP_PowerSupply.IdentifyingDescriptions[] property may optionally be implemented. This property describes the additional information for the corresponding OtherIndentifyingInfo element.

7.1.4 HP_PowerSupply.OperationalStatus[]

HP_PowerSupply.OperationalStatus[0] property shall be implemented. This property describes the overall status the power supply. Additional OperationalStatus values in array indices > 0 should be populated to represent additional status information for the power supply if available.

7.2 HP_PowerRedundancySet

Power Supply redundancy modeling is optional. Even when a managed system supports and implements the redundancy, the redundant power supplies may co-exist with non-redundant power supplies. The conditions and requirement placed in this section only refer to the HP_PowerSupply instances representing redundant power supplies.

Power Supply redundancy is modeled using HP_PowerRedundancySet which is associated to the HP_PowerSupply instances through HP_MemberOfPowerRedundancy associations. Instances of HP_PowerRedundancySet are associated to its containing instance of CIM_ComputerSystem through the HP_HostedPowerRedundancySet association.

When power supply redundancy is implemented, there shall be at least one instance of HP_PowerRedundancySet. The HP_MemberOfPowerRedundancy association shall be used to associate the HP_PowerRedundancySet instance with the HP_PowerSupply instance.

If the HP_MemberOfPowerRedundancy inherits from CIM_MemberOfCollection or CIM_MemberOfPolicyCollection and the “Included” property has a value of TRUE; the power supply status SHALL be used in state propagation rollup.

If the HP_MemberOfPowerRedundancy inherits from CIM_MemberOfPolicyCollection and the “Included” property has a value of FALSE; the power supply status SHALL NOT be used in state propagation rollup. The power supply status shall be ignored and considered as “OK” for the purposes of state propagation rollup.

Multiple instances of HP_PowerRedundancySet may exist. Furthermore, power supply redundancy sets may share power supplies; instances of HP_PowerSupply may be members of more than one HP_PowerRedundancySet instance using HP_MemberOfPowerRedundancy associations.

12 Version 1.3.0

7.3 HP_PowerCollection

Power Supply collection modeling is optional. There may be one or more instance of HP_PowerCollection instantiated. Instances of HP_PowerSupply are associated to HP_PowerCollection through the HP_MemberOfPowerCollection association. Instances of HP_PowerCollection are associated to its containing instance of CIM_ComputerSystem through the HP_HostedPowerCollection association.

HP_PowerCollection.GroupOperationalStatus shall comprehend the status of all associated instances of non-redundant power supplies and associated instances of HP_PowerRedundancySet, if redundancy is modeled.

7.4 HP_SystemPowerSupply

There shall be one instance of HP_SystemPower Supply instantiated for each instance of HP_PowerSupply. This class associates an instance of HP_PowerSupply with its containing instance of CIM_ComputerSystem.

7.5 HP_MemberOfPowerRedundancy

When power supply redundancy is implemented, there shall be at least one instance of HP_MemberOfPowerRedundancy instantiated for each instance of HP_PowerSupply that is capable of redundancy. This class associates an instance of redundancy-capable HP_PowerSupply to the respective instance of HP_PowerRedundancySet.

7.6 HP_HostedPowerRedundancySet

When power supply redundancy is implemented, there shall be one instance of HP_HostedPowerRedundancySet instantiated for each instance of HP_PowerRedundancySet. This class associates an instance of HP_PowerRedundancySet with its containing instance of CIM_ComputerSystem.

7.7 HP_MemberOfPowerCollection

When power supply collection is implemented, there shall be one instance of HP_MemberOfPowerCollection instantiated for each instance of HP_PowerSupply. This class associates an instance of HP_PowerSupply to the respective instance of HP_PowerCollection.

If the HP_MemberOfPowerRedundancy inherits from CIM_MemberOfCollection or CIM_MemberOfPolicyCollection and the “Included” property has a value of TRUE; the power supply status SHALL be used in state propagation rollup.

If the HP_MemberOfPowerRedundancy inherits from CIM_MemberOfPolicyCollection and the “Included” property has a value of FALSE; the power supply status SHALL NOT be used in state propagation rollup. The power supply status shall be ignored and considered as “OK” for the purposes of state propagation rollup.

7.8 HP_HostedPowerCollection

When power supply collection is implemented, there shall be one instance of HP_HostedPowerCollection instantiated for each instance of HP_PowerCollection. This class associates an instance of HP_PowerCollection with its containing instance of CIM_ComputerSystem.

7.9 HP_SuppliesPower

Associated Power modeling is optional. If associated Power modeling is implemented, the power supply represented by the referenced instance of HP_PowerSupply shall provide power for managed system element represented by the referenced instance of CIM_ManagedSystemElement.

Version 1.3.0 13

There may be one or more instance of HP_SuppliesPower instantiated. Instances of HP_PowerSupply are associated to CIM_ManagedSystemElement through the HP_SuppliesPower association.

7.10 HP_PowerMeter

When the power supply supports reporting power consumption or power production; there shall be an instance of HP_PowerMeter for each installed power supply capable of reporting power consumption or power production.

7.10.1 HP_PowerMeter.SensorType

HP_PowerMeter.SensorType property shall be implemented. This property describes the type of the power meter supported. This property shall be either 13 (power consumption) or 14 (power production).

The sensor shall follow the mandates specified by DSP1009 – Sensor Profile.

7.11 HP_AssociatedPowerMeter

When the HP_PowerMeter is instantiated, there shall be an instance of HP_AssociatedPowerMeter associating the power meter instance to the power supply instance.

8 Methods None.

9 Use Cases

9.1 Object Diagrams

Figure 3 represents a possible instantiation of the HP Power Supply Profile. In this case, system1 has two power supplies, ps1 and ps2. They belong to powercollection1, which describes the overall group operational status of the power supplies as being OK. Each of the power supplies support reporting power meter sensor information in pm1 and pm2. The power meters are associated to the power supplies via the HP_AssociatedPowerMeter association.


14 Version 1.3.0


ps2:HP_PowerSupply

OperationalStatus:(OK)

ps1:HP_PowerSupply






RegisteredName: Power Supply Profile


RegisteredName: HP Power Supply Profile



HP_ExtendsProfile

powercollection1:HP_PowerCollection



HP_MemberOfPowerCollectio

n

pm2:HP_PowerMeter

pm1:HP_PowerMeter



Figure 3 – HP Power Supply Profile: Object Diagram

Figure 4 represents another possible instantiation of the HP Power Supply Profile, with modeled redundancy. In this case, system1 has four power supplies: ps1, ps2, ps3 and ps4. All of the power supplies belong to powercollection1. Power supplies ps1 and ps2 belong to powerredundancyset1. Power supplies ps3 and ps4 belong to powerredundancyset2.

The overall group operational status of the power supplies is Error.


Version 1.3.0 15

system1:HP_ComputerSystem

ps2:HP_PowerSupply


ps1:HP_PowerSupply











HP_ExtendsProfile

Powercollection1:HP_PowerCollection


ps3:HP_PowerSupply


ps4:HP_PowerSupply


powerredundancyset1:HP_PowerRedundancySet



RedundancyStatus:(Fully Redundant)

HP_MemberOfPowerRedundancy HP_MemberOfPowerRedundancy




Figure 4 – HP Power Supply Profile: Power Supply Redundancy Object Diagram

Figure 5 represents another possible instantiation of the HP Power Supply Profile, with modeled redundancy and support for state propagation filtering. In this case, system1 has four power supplies: ps1, ps2, ps3 and ps4. All of the power supplies belong to powercollection1. Power supplies ps1 and ps2 belong to powerredundancyset1. Power supplies ps3 and ps4 belong to powerredundancyset2.

The overall group operational status of the power supplies is Error.


Figure 5 represents a possible instantiation of the HP Power Supply Profile. In this case, system1 has a processor and power supply, cpu1 and ps1 respectively. Ps1 is associated with cpu1 via HP_SuppliesPower ps1 provides power for cpu1.


16 Version 1.3.0


ps1:HP_PowerSupply


HP_SystemPowerCIM_SystemDevice

HP_SuppliesPowercpu1:CIM_Processor

Figure 5 – HP Power Supply Profile: Supplies Power Object Diagram

Version 1.3.0 17


ps2:HP_PowerSupply


ps1:HP_PowerSupply











HP_ExtendsProfile

Powercollection1:HP_PowerCollection


ps3:HP_PowerSupply


ps4:HP_PowerSupply





RedundancyStatus:(Fully Redundant)




HP_MemberOfPowerRedundancyIncluded: False

HP_MemberOfPowerRedundancyIncluded: True



Figure 6 – HP Power Supply Profile: Power Supply Redundancy with Ignored Status

18 Version 1.3.0

Retrieve the Power Supply Group Operational Status

For the given instance of HP_PowerSupply, select the associated instance of HP_PowerCollection through HP_MemberOfPowerCollection association. Retrieve the value of HP_PowerCollection.GroupOperationalStatus property.

9.2 Retrieve the Power Supply Redundancy Status

For the given instance of HP_PowerSupply, select the associated instance of HP_PowerRedundancySet through HP_MemberOfPowerRedundancy association. Retrieve the value of HP_PowerRedundancySet.RedundancyStatus property.

9.3 Determine the Type of Power Collection

For the given instance of HP_PowerCollection, select an associated instance of HP_PowerSupply through HP_MemberOfPowerCollection association. The type of Power Collection is described by the associated HP_PowerSupply.PowerSupplyType property enumeration.


Table 2 – CIM Elements – HP Power Supply Profile

Element Name Requirement Description

Classes HP_PowerSupply Mandatory See Sections 7.1 and 10.1

HP_RegisteredProfile Mandatory See Section 10.2

HP_PowerCollection Optional See Sections 7.3 and 10.3

HP_PowerRedundancySet Optional See Sections 7.2 and 10.4

HP_MemberOfPowerRedundancy Conditional See Sections 7.5 and 10.5

HP_MemberOfPowerCollection Conditional See Sections 7.7 and 10.8

HP_HostedPowerRedundancySet Conditional See Sections 7.6 and 10.6

HP_HostedPowerCollection Conditional See Sections 7.8 and 10.9

HP_SystemPowerSupply Mandatory See Sections 7.4 and 10.11

HP_SuppliesPower Optional See Sections 7.9 and 10.12 Indications

None defined in this profile

10.1 HP_PowerSupply

HP_PowerSupply is used to represent a power supply in a managed system.

Version 1.3.0 19

Table 3 – Class: HP_PowerSupply


HP_PowerSupply

PowerSupplyType Mandatory See Section 7.1.1

OperationalStatus Mandatory See Section 7.1.4

CIM_PowerSupply

OtherIdentifyingInfo[] Optional See Section 7.1.2

IdentifyingDescriptions[] Optional See Section 7.1.3




Properties Requirement Description

RegisteredName Mandatory "HP Power Supply"

RegisteredVersion Mandatory “1.3.0”

RegisteredOrganization Mandatory Other (1)


10.3 HP_PowerCollection

HP_PowerCollection is used to represent a power supply collection in a managed system.

Table 5 – Class: HP_PowerCollection


InstanceID Mandatory Key GroupOperationalStatus Mandatory See Section 7.3

ElementName Mandatory

Description Mandatory

10.4 HP_PowerRedundancySet

HP_PowerRedundancySet is used to represent a power supply redundancy set in a managed system.

Table 6 – Class: HP_PowerReduncancySet


InstanceID Mandatory Key RedundancyStatus Mandatory See Section 7.2

TypeOfSet Mandatory

MinNumberNeeded Mandatory

ElementName Mandatory

20 Version 1.3.0

10.5 HP_MemberOfPowerRedundancy (subclassed from CIM_MemberOfCollection)

HP_MemberOfPowerRedundancy is used to represent an association between HP_PowerSupply and HP_PowerRedundancySet.

Table 7 – Class: HP_MemberOfPowerRedundancy


Collection Mandatory Key: References HP_PowerRedundancySet

Member Mandatory Key: References HP_PowerSupply

10.6 HP_MemberOfPowerRedundancy (subclassed from CIM_MemberOfPolicyCollection)

HP_MemberOfPowerRedundancy is used to represent an association between HP_PowerSupply and HP_PowerRedundancySet. The settable property “CIM_MemberOfPolicyCollection.Included” SHALL be implemented as a writeable property. If the “Included” value is FALSE; the power supply state shall be ignored. If the “Included” property is TRUE; state will be propagated.

Table 8 – Class: HP_MemberOfPowerRedundancy


Collection Mandatory Key: References HP_PowerRedundancySet


Included Mandatory See section 7.7

10.7 HP_HostedPowerRedundancySet

HP_HostedPowerRedundancySet is used to represent an association between HP_PowerRedundancySet and its containing instance of CIM_ComputerSystem.

Table 9 – Class: HP_HostedPowerRedundancySet


OwningElement Mandatory Key: References HP_ComputerSystem

OwnedElement Mandatory Key: References HP_PowerRedundancySet

10.8 HP_MemberOfPowerCollection (subclassed from CIM_MemberOfCollection)

HP_MemberOfPowerCollection is used to represent an association between HP_PowerSupply and HP_PowerCollection.

Table 10 – Class: HP_MemberOfPowerCollection


Collection Mandatory Key: References HP_PowerCollection


Version 1.3.0 21

10.9 HP_MemberOfPowerCollection (subclassed from CIM_MemberOfPolicyCollection)

HP_MemberOfPowerCollection is used to represent an association between HP_PowerSupply and HP_PowerCollection. The settable property “CIM_MemberOfPolicyCollection.Included” SHALL be implemented as a writeable property. If the “Included” value is FALSE; the power supply state shall be ignored. If the “Included” property is TRUE; state will be propagated.

Table 11 – Class: HP_MemberOfPowerCollection


Collection Mandatory Key: References HP_PowerCollection


Included Mandatory See section 7.7

10.10 HP_HostedPowerCollection

HP_HostedPowerCollection is used to represent an association between HP_PowerCollection and its containing instance of CIM_ComputerSystem.

Table 12 – Class: HP_HostedPowerCollection


Antecedent Mandatory Key: References HP_ComputerSystem

Dependent Mandatory Key: References HP_PowerCollection

10.11 HP_SystemPower Supply

HP_Systempower supply is used to represent an association between HP_PowerSupply and its containing instance of CIM_ComputerSystem.

Table 13 – Class: HP_SystemPowerSupply


GroupComponent Mandatory Key: References HP_ComputerSystem

PartComponent Mandatory Key: References HP_PowerSupply

10.12 HP_SuppliesPower

HP_PowerMeter is used to represent a power meter in a managed system.

Table 14 – Class: HP_PowerMeter


Antecedent Mandatory Key: References HP_PowerSupply


22 Version 1.3.0

10.13 HP_PowerMeter

HP_PowerMeter is used to represent an association between HP_PowerSupply and CIM_ManagedSystemElement.

Table 15 – Class: HP_PowerMeter


SensorType Mandatory One of: 13 (power consumption) 14 (power production)




None Defined




None Defined

Version 1.3.0 23

ANNEX A (normative)

Change Log


0.1 5/9/06 Initial Draft

0.2 5/30/06 Updates to properties, removed redundancy/status mapping and referenced physical asset profile

1.0 5/31/06 Updated properties

1.0 11/29/06

Updated the following: • All HP_PowerRedundancyCollection references now

HP_PowerCoolingRedundancySet o Antecedent and Dependent now OwningElement and

OwnedElement (per parent class) • Removed sections in 8 because there are no methods defined • Durable Names and Correlatable IDs removed because there are really no

such names and IDs generated by this profile • Updated class diagram to update references and for typos • Updated instance diagrams to remove physical model (this is described in

physical asset profile) and for typos • Minor wording updates throughout document

1.1.0 7/24/2008

Updated the following: • Removed "For each HP_PowerCollection instance, all associated

HP_PowerSupply instances must have the same value for HP_PowerSupply.PowerSupplyType, if this property is implemented." in HP_PowerCollection.

• Added HP_SuppliesPower • Added simple use case for associated power • Added State propagation filtering support via

CIM_MemberOfPolicyCollection

1.2.0 7/30/2008 Added the following:

• Added HP_PowerMeter and HP_AssociatedPowerMeter • Changed DMTF Power Profile dependency to version 1.1.0.

1.3.0 4/28/2009 Added the following: • Added section on HP_PowerSupply.OperationalStatus

24 Version 1.3.0


Acknowledgments

Version 1.3.0 25



CR

Number Date Title

CR00106 5/31/06 Create HP profile for the environmental model

26 Version 1.3.0

Bibliography



Date: 04/21/09

Version: 1.2.0

HP Sensors Profile




2 Version 1.2.0

Contents

1 Scope ............................................................................................................................................. 6 2 Normative References ................................................................................................................... 6

2.1 Approved References .................................................................................................................... 6 2.2 References Under Development ................................................................................................... 6 2.3 Other References .......................................................................................................................... 6

3 Terms and Definitions .................................................................................................................... 6 4 Symbols and Abbreviated Terms .................................................................................................. 7 5 Synopsis ........................................................................................................................................ 7 6 Description ..................................................................................................................................... 8 7 Implementation Requirements ..................................................................................................... 10

7.1 HP_NumericSensor ..................................................................................................................... 10 7.1.1 HP_NumericSensor.NumericSensorType ........................................................................... 10 7.1.2 HP_NumericSensor.OperationalStatus ............................................................................... 10

7.2 HP_SensorCollection................................................................................................................... 11 7.3 HP_SensorCollection.GroupOperationalStatus .......................................................................... 11 7.4 HP_SystemSensor ...................................................................................................................... 11 7.5 HP_MemberOfSensorCollection ................................................................................................. 11 7.6 HP_HostedSensorCollection ....................................................................................................... 11 7.7 HP_AssociatedSensor ................................................................................................................. 11

8 Methods ....................................................................................................................................... 11 9 Use Cases ................................................................................................................................... 11

9.1 Object Diagrams .......................................................................................................................... 11 9.2 Retrieve the Sensor Group Operational Status ........................................................................... 14 9.3 Determine the Type of Sensor Collection .................................................................................... 14

10 CIM Elements .............................................................................................................................. 14 10.1 HP_NumericSensor ..................................................................................................................... 14 10.2 HP_RegisteredProfile .................................................................................................................. 14 10.3 HP_SensorCollection................................................................................................................... 15 10.4 HP_MemberOfSensorCollection ................................................................................................. 15 10.5 HP_HostedSensorCollection ....................................................................................................... 15 10.6 HP_SystemSensor ...................................................................................................................... 15 10.7 HP_AssociatedSensor ................................................................................................................. 16

11 Durable Names and Correlatable IDs .......................................................................................... 16

Figures

Figure 1 – HP Sensors Profile: Class Diagram ..................................................................................................... 9 Figure 2 – HP Sensors Profile: Inheritance Hierarchy Diagram ......................................................................... 10 Figure 3 – HP Sensors Profile: Object Diagram ................................................................................................. 12 Figure 4 – HP Fan Profile: Associated Sensor Object Diagram ......................................................................... 13

Tables

Table 1 – Related Profiles ..................................................................................................................................... 8 Table 2 – CIM Elements – HP Sensors Profile ................................................................................................... 14 Table 3 – Class: HP_NumericSensor ................................................................................................................. 14 Table 4 – Class: HP_RegisteredProfile ............................................................................................................. 14 Table 5 – Class: HP_SensorCollection ............................................................................................................... 15

Version 1.2.0 3

Table 6 – Class: HP_MemberOfSensorCollection .............................................................................................. 15 Table 7 – Class: HP_HostedSensorCollection ................................................................................................... 15 Table 8 – Class: HP_SystemSensor ................................................................................................................... 15 Table 9 – Class: HP_AssociatedSensor ............................................................................................................. 16 Table 10 – Durable Names generated by this Profile ......................................................................................... 16 Table 11 – Correlatable IDs generated by this Profile ........................................................................................ 16

4 Version 1.2.0

Foreword

The HP Sensors Profile P00104 was prepared by the HP WBEM TC.

Version 1.2.0 5

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 logical Sensors in HP systems. 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.2.0

1 Scope The HP Sensor profile extends the management capability of referencing profiles by adding the capability to represent the logical Sensors and sensor consolidated status in HP specific ways.






DMTF DSP1009, Sensor Profile












Version 1.2.0 7











None.

5 Synopsis Profile Name: HP Sensors Profile

Version: 1.2.0



Central Class: HP_NumericSensor

8 Version 1.2.0

Scoping Class: Same as DSP1017 – Sensor Profile

Extends: DMTF DSP1017, Sensors Profile 1.0.0


The HP Sensor profile extends DMTF DSP1017 and specializes HP WBEM TC P00107 to add sensor and sensor consolidated status characteristics that are specific to HP systems.


Profile Name Organization Version Relationship Behavior DSP1017 – Sensors Profile DMTF 1.0.0 Mandatory





6 Description The HP Sensors Profile describes the properties and methods of HP sensors and sensor collections in a managed system. Also included are definitions of associations that describe the relationship of the HP sensor with sensor collections, profile version information and the computer system.

Figure 1 represents the class schema for the HP Sensors Profile. Figure 2 represents additional inheritance hierarchies for classes described in this profile.

In the HP Sensors Profile, the collection of sensors is represented by an instance of HP_SensorCollection, containing a consolidated status.

Version 1.2.0 9

CIM_NumericSensor

see DMTF Sensors Profile

HP_HostedSensorCollection

HP_SensorCollection

HP_NumericSensor

NumericSensorType

CIM_ComputerSystem




HP_SystemSensor

HP_ElementConformsToProfile(see HP Profile Registration profile)



1

1..*

1..*

0..1

1

*

1

0..*

HP_MemberOfSensorCollection

CIM_ManagedSystemElement

See referencing profile

HP_AssociatedSensor*

1..*

Figure 1 – HP Sensors Profile: Class Diagram

10 Version 1.2.0



HP_MemberOfSensorCollection HP_SystemSensor

CIM_SystemDevice

see DMTF Sensors Profile




Figure 2 – HP Sensors Profile: Inheritance Hierarchy Diagram


7.1 HP_NumericSensor

There shall be at least one instance of HP_NumericSensor instantiated.

7.1.1 HP_NumericSensor.NumericSensorType

HP_NumericSensor.NumericSensorType property shall be implemented. This property describes the type of the sensor using an appropriate enumeration value.

7.1.2 HP_NumericSensor.OperationalStatus

HP_NumericSensor.OperationalStatus property shall be set based on the meaning of the CurrentState of the sensor, not the operational status of the sensor itself. For example, a sensor that is operating properly but reporting a CurrentState of “Critical” may set the OperationalStatus to Error.

Version 1.2.0 11

7.2 HP_SensorCollection

Sensor collection modeling is optional. There may be one or more instance of HP_SensorCollection instantiated. Instances of HP_NumericSensor are associated to HP_SensorCollection through the HP_MemberOfSensorCollection association. Instances of HP_SensorCollection are associated to its containing instance of CIM_ComputerSystem through the HP_HostedSensorCollection association.

7.3 HP_SensorCollection.GroupOperationalStatus

HP_SensorCollection.GroupOperationalStatus for the HP_SensorCollection shall be calculated using a worst-of mechanism.

7.4 HP_SystemSensor

There shall be one instance of HP_SystemSensor instantiated for each instance of HP_NumericSensor. This class associates an instance of HP_NumericSensor with its containing instance of CIM_ComputerSystem.

7.5 HP_MemberOfSensorCollection

When sensor collection is implemented, there shall be one instance of HP_MemberOfSensorCollection instantiated for each instance of HP_NumericSensor. This class associates an instance of HP_NumericSensor to the respective instance of HP_SensorCollection.

7.6 HP_HostedSensorCollection

When sensor collection is implemented, there shall be one instance of HP_HostedSensorCollection instantiated for each instance of HP_SensorCollection. This class associates an instance of HP_SensorCollection with its containing instance of CIM_ComputerSystem.

7.7 HP_AssociatedSensor

Associated sensor modeling is optional. If associated sensor modeling is implemented, the sensor represented by the referenced instance of HP_NumericSensor shall be a sensor for managed system element represented by the referenced instance of CIM_ManagedSystemElement.

There may be one or more instance of HP_AssociatedSensor instantiated. Instances of HP_NumericSensor are associated to CIM_ManagedSystemElement through the HP_AssociatedSensor association.

8 Methods None.

9 Use Cases

9.1 Object Diagrams

Figure 3 represents a possible instantiation of the HP Sensors Profile. In this case, system1 has two sensors, sensor1 and sensor2. Sensor1 and sensor2 belong to coolingcollection1, which describes the overall group operational status of the sensors as being OK.


12 Version 1.2.0


tempsensor2:HP_NumericSensor


tempsensor1:HP_NumericSensor


HP_SystemSensor




RegisteredName: Sensors Profile


RegisteredName: HP Sensors Profile



HP_ExtendsProfile

sensorcollection1:HP_SensorCollection


HP_MemberOfSensorCollection


Figure 3 – HP Sensors Profile: Object Diagram

Figure 4 represents a possible instantiation of the HP Sensor Profile. In this case, system1 has a fan and tachometer sensor, fan1 and sensor 1 respectively. Sensor1 is associated to fan1 via HP_AssociatedSensor; sensor1 is a tachometer sensor for fan1.


Version 1.2.0 13


fan1:HP_Fan


HP_SystemFan

sensor1:HP_NumericSensor

SensorType: (Tachometer)

HP_SystemSensor

HP_AssociatedSensor

Figure 4 – HP Fan Profile: Associated Sensor Object Diagram

14 Version 1.2.0

9.2 Retrieve the Sensor Group Operational Status

For the given instance of HP_NumericSensor, select the associated instance of HP_SensorCollection through HP_MemberOfSensorCollection association. Retrieve the value of HP_SensorCollection.GroupOperationalStatus property.

9.3 Determine the Type of Sensor Collection

For the given instance of HP_SensorCollection, select an associated instance of HP_NumericSensor through HP_MemberOfSensorCollection association. The type of sensor collection is described by the associated HP_NumericSensor.NumericSensorType property enumeration.


Table 2 – CIM Elements – HP Sensors Profile


HP_NumericSensor Mandatory See Sections 7.1 and 10.1 HP_RegisteredProfile Mandatory See Section 10.2 HP_SensorCollection Optional See Sections 7.2 and 10.3 HP_MemberOfSensorCollection Conditional See Sections 7.5 and 10.4 HP_HostedSensorCollection Conditional See Sections 7.6 and 10.5 HP_SystemSensor Mandatory See Sections 7.4 and 10.6 HP_AssociatedSensor Optional See 7.7 and 10.7


10.1 HP_NumericSensor

HP_NumericSensor is used to represent a sensor in a managed system.

Table 3 – Class: HP_NumericSensor

Properties Requirement Notes NumericSensorType Mandatory See Section 7.1.1




Properties Requirement Description RegisteredName Mandatory "HP Sensors” RegisteredVersion Mandatory “1.2.0” RegisteredOrganization Mandatory Other (1)

Version 1.2.0 15

Properties Requirement Description OtherRegisteredOrganization Mandatory “HP WBEM TC”

10.3 HP_SensorCollection

HP_SensorCollection is used to represent a sensor collection in a managed system.

Table 5 – Class: HP_SensorCollection

Properties Requirement Notes InstanceID Mandatory Key GroupOperationalStatus Mandatory See Section 7.2 ElementName Mandatory Description Mandatory

10.4 HP_MemberOfSensorCollection

HP_MemberOfSensorCollection is used to represent an association between HP_NumericSensor and HP_SensorCollection.

Table 6 – Class: HP_MemberOfSensorCollection

Properties Requirement Notes Collection Mandatory Key: References HP_SensorCollection

Member Mandatory Key: References HP_NumericSensor

10.5 HP_HostedSensorCollection

HP_HostedSensorCollection is used to represent an association between HP_SensorCollection and its containing instance of CIM_ComputerSystem.

Table 7 – Class: HP_HostedSensorCollection


Dependent Mandatory Key: References HP_SensorCollection

10.6 HP_SystemSensor

HP_Systemsensor is used to represent an association between HP_NumericSensor and its containing instance of CIM_ComputerSystem.

Table 8 – Class: HP_SystemSensor

Properties Requirement Notes GroupComponent Mandatory Key: References HP_ComputerSystem

PartComponent Mandatory Key: References HP_NumericSensor

16 Version 1.2.0

10.7 HP_AssociatedSensor

HP_AssociatedSensor is used to represent an association between HP_NumericSensor and CIM_ManagedSystemElement.

Table 9 – Class: HP_AssociatedSensor

Properties Requirement Notes Antecedent Mandatory Key: References HP_NumericSensor





None Defined




None Defined

Version 1.2.0 17

ANNEX A (normative)

Change Log

Version Date Description 0.1 5/9/06 Initial Draft 0.2 5/30/06 Updates to properties 1.0 5/31/06 Updated properties

1.0 11/29/06

Updated the following: • Removed sections in 8 because there are no methods defined • Durable Names and Correlatable IDs removed because there are really no

such names and IDs generated by this profile • Updated class diagram to update references and for typos • Updated instance diagram for typos • Minor wording updates throughout document

1.1.0 7/17/08

Updated the following: • Removed "For each HP_SensorCollection instance, all associated

HP_NumericSensor instances must have the same value for HP_NumericSensor.NumericSensorType, if this property is implemented." in HP_SensorCollection (7.2). We only have one sensor collection instance in Spinner; can we remove this?

• HP_NumericSensor.NumericSensorType now "shall" be implemented, instead of "may optionally" (7.1.1)

• Added HP_AssociatedSensor (7.6) • Added simple use case for associated sensor (figure 4)

18 Version 1.2.0


Acknowledgments

Version 1.2.0 19



CR

Number Date Title CR00106 5/31/06 Create HP profile for the environmental model

20 Version 1.2.0

Bibliography



Date: 3/4/2010

Version: 2.0.0

HP Base Server Profile




Version 2.0.0 2

Contents



3 Terms and Definitions .................................................................................................................... 6 4 Symbols and Abbreviated Terms .................................................................................................. 7 5 Synopsis ........................................................................................................................................ 8 6 Description ..................................................................................................................................... 9 7 Implementation Requirements ....................................................................................................... 9

7.1 HP_ComputerSystem .................................................................................................................... 9 7.1.1 Support of System Contact Information (optional) ................................................................. 9 7.1.2 HP_ComputerSystem.LocationIndicator (optional) ............................................................. 10 7.1.3 HP_ComputerSystem.OtherIdentifyingInfo and IdentifyingDescriptions (optional) ............. 10 7.1.4 HP_ComputerSystem.OperationalStatus (mandatory) ........................................................ 11 7.1.5 HP_ComputerSystem.OperationalStatusClassNames[] (conditional) ................................. 12 7.1.6 HP_ComputerSystem.Dedicated OtherDedicatedDescription (Mandatory) ........................ 12 7.1.7 HP_ComputerSystem physical identifiers (Optional) ........................................................... 14 7.1.8 HP_ComputerSystem Solution identifiers ........................................................................... 15 7.1.8.1 HP_ComputerSystem.IncludedInSolution (Mandatory) ..................................................... 15 7.1.8.2 HP_ComputerSystem.SolutionName (Conditional) ........................................................... 15

8 Methods ....................................................................................................................................... 15 8.1 Method: HP_ComputerSystem.SendTestIndication( ) ................................................................ 15

8.1.1 General Requirements ......................................................................................................... 15 8.2 Profile Conventions for Operations .............................................................................................. 16 8.3 HP_ComputerSystem .................................................................................................................. 17

9 Use Cases ................................................................................................................................... 17 9.1 Object Diagrams .......................................................................................................................... 17 9.2 Determine if the HP Base Server Profile has been Implemented and Find top level

instance of HP_ComputerSystem ..................................................................................................... 21 9.3 Determine Status of Top Level HP_ComputerSystem ................................................................ 22

10 CIM Elements .............................................................................................................................. 22 10.1 HP_ComputerSystem .................................................................................................................. 22 10.2 HP_RegisteredProfile .................................................................................................................. 23


Figures

Figure 1 – HP Base Server Physical Asset profile: Class Diagram ...................................................................... 9 Figure 2 – HP Base Server Profile: Base System with Fans and Processors .................................................... 18 Figure 3 – HP Base Server Profile: Base System with 1 CPU and 1 Memory ................................................... 19 Figure 4 – HP Base Server profile: Consolidated Status .................................................................................... 21

Tables

Table 1 – Related Profiles ..................................................................................................................................... 8

Table 2 – Mapping from subsystem OperationalStatus to computer system OperationalStatus ....................... 11 Table 3 – HP_ComputerSystem.SendTestIndication( ) Method: Return Code Values ...................................... 15 Table 4 – HP_ComputerSystem.SendTestIndication( ) Method: Parameters .................................................... 15 Table 5 – Test Indications ................................................................................................................................... 16 Table 6 – CIM Elements – HP Profile Registration Profile .................................................................................. 22 Table 7 – Class: HP_ComputerSystem .............................................................................................................. 23 Table 8 – Class: HP_RegisteredProfile .............................................................................................................. 23 Table 9 – Durable Names generated by this Profile ........................................................................................... 23 Table 10 – Correlatable IDs generated by this Profile ........................................................................................ 24

4 Version 2.0.0

Foreword

The HP Base Server Profile (P00105) was prepared by the HP WBEM TC.

5 Version 2.0.0

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 an HP Base Server. 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 2.0.0

1 Scope The HP Base Server profile extends the management capability of referencing profiles by adding the capability to represent HP base servers.






DMTF DSP1033, Profile Registration profile

DMTF DSP1004, Base Server profile

HP WBEM TC P00114, HP Base Server Physical Asset profile

HP WBEM TC P00100, HP Profile Registration profile

HP WBEM TC P00113, HP Consolidated Status profile









7 Version 2.0.0












None.

8 Version 2.0.0

5 Synopsis Profile Name: HP Base Server Profile

Version: 2.0.0



Central Class: HP_ComputerSystem

Extends: DMTF DSP1004, Base Server profile 1.0.0

The HP Base Server Profile extends DMTF DSP1004 to add the capability to model HP servers.


Profile Name Organization Version Relationship Behavior DSP1004 – Base Server profile DMTF 1.0.0 Extends



P00101 – HP Management Processor Lite Profile


P00114 – HP Base Server Physical Asset Profile




P00117 – HP Ethernet Teaming Profile


9 Version 2.0.0

6 Description

ComputerSystem

(see DMTF Base Server profile)

HP_ComputerSystem

SecondaryOwnerPagerSecondaryOwnerContactSecondaryOwnerName

PrimaryOwnerPager

HP_ComputerSystemChassis

(see HP Base Server Physical Asset profile)

HP_ComputerSystemPakcage(see HP Base Server Physical

Asset profile)

HP_ProcessorCollection

(see HP CPU Consolidated Status profile)


1

*

1

1

HP_ManagementProcessor

(see HP Management Processor Lite profile)

HP_MPComponentCS

HP_EthernetPort

(see HP Ethernet Teaming profile)

HP_EthernetDevice

HP_BladeEnclosureCS

(see HP Blade System Lite profile)

HP_BladeSystemComponent


(see HP Consolidated Status profile)

HP_GroupHostedCollection1

*

1

*

1

1

1

*

Figure 1 – HP Base Server Physical Asset profile: Class Diagram

HP server systems are represented in the implementation namespace as instances of HP_ComputerSystem. Figure 1 shows the class diagram for HP Base Server profile. Implementations must implement the physical asset elements of the system by associating the instance of HP_ComputerSystem with an instance of HP_ComputerSystemChassis via the HP_ComputerSystemPackage association. Both HP_ComputerSystemChassis and HP_ComputerSystemPackage are described in the HP Base Server Physical Asset profile.

HP_GroupSystemSpecificCollection instances are associated to the main instance of HP_ComputerSystem via instances of the association HP_GroupHostedCollection. Each collection represents a collection of managed elements that participate and contribute to the roll-up status of the HP_ComputerSystem instances. The overall status of all collections in the system (associated to HP_ComputerSystem via Hp_GroupHostedCollection) is reflected into the HP_ComputerSystem’s OperationalStatus array property (see Section 7.1.8).


7.1 HP_ComputerSystem


7.1.1 Support of System Contact Information (optional)

The following properties are used to store contact information for the server. System administrators can use these properties to store the contact information for the primary and secondary owners of the system.

10 Version 2.0.0

Support for these properties is optional. If supported, these properties must be supported as writeable. In addition, the values written to these properties must be persisted across reboots. Clients determine that this property is supported by querying a non-null, non-empty string contained in the property. If implemented, providers must initialize the property to the string value “not set” if a client has not yet initialized or set a value for the property for the first time.

• HP_ComputerSystem.PrimaryOwnerContact

• HP_ComputerSystem.PrimaryOwnerName

• HP_ComputerSystem.PrimaryOwnerPager

• HP_ComptuerSystem.SecondaryOwnerContact

• HP_ComputerSystem.SecondaryOwnerName

• HP_ComputerSystem.SecondaryOwnerPager

7.1.2 HP_ComputerSystem.LocationIndicator (optional)

Implementations that conform to this profile may populate LocationIndicator as follows:

LocationIndicator will have a read only value 4 (Not Supported) if a server has no location indicator (e.g., LED). This property will have a read only value 0 (Unknown) if the location indicator status is unknown. If implemented for any other values, this property must reflect the current state of the location indicator on the server. In addition, this property may be implemented as writeable for these other values. Writing values reflecting a state change not supported by the server’s location indicator shall fail by retaining the previous value.

7.1.3 HP_ComputerSystem.OtherIdentifyingInfo and IdentifyingDescriptions (optional)

Implementations that conform to this profile may populate OtherIdentifyingInfo and IdentifyingDescriptions with information about the ProductID for the physical system. If implemented, IdentifyingDescription shall contain the value HPQ:ProductID in any array location. The corresponding OtherIdentifyingInfo array location shall contain the ProductID for the system. This value shall be the same value that is or could be populated in the HP_ComputerSystemChassis.ProductID property. That is, the same semantics apply for both values.

Implementations that conform to this profile may populate OtherIdentifyingInfo and IdentifyingDescriptions with information about the Serial Number for the chassis containing the physical system. If implemented, IdentifyingDescription shall contain the value HPQ:ChassisSerialNumber in any array location. The corresponding OtherIdentifyingInfo array location shall contain the Serial Number for the chassis containing the system. This value shall be the same value that is or could be populated in the CIM_ComputerSystemChassis.SerialNumber property for the chassis that contains the physical package for the system. That is, the same semantics apply for both values.

11 Version 2.0.0

7.1.4 HP_ComputerSystem.OperationalStatus (mandatory)

The value of the OperationalStatus property is determined by iterating over all HP_GroupSystemSpecificCollection instances and applying a “smarter” worst-of algorithm. This algorithm takes the worst zeroth element of the GroupOperationalStatus property of each collection and applies the following table (in order of increasing severity):

Table 2 – Mapping from subsystem OperationalStatus to computer system OperationalStatus

Subsystem GroupOperationalStatus ComputerSystem OperationalStatus

HP SIM Status

Other(1)

Starting(8)

Stopping(9)

In Service(11)

Dormant(15)

Power Mode(18)

Other Informational

Unknown(0)

No Contact(12)

Unknown Unknown

OK(2)

Completed(17)

OK Normal

Degraded(3)

Stressed(4)

Stopped(10)

Degraded Minor

Predictive Failure(5)

Error(6)

Non-Recoverable Error(7)

Lost Communication(13)

Aborted(14)

Supporting Entity in Error(16)

Error Major

This mapping has the effect of filtering the larger range of possible values into a smaller range of more understandable but less descriptive operational status values. The algorithm for calculating the computer system's OperationalStatus[0] value is as follows:

1. If all the subsystems associated with the Computer System provider via the

HP_GroupHostedCollection association have a value in GroupOperationalStatus[0] of “OK”

12 Version 2.0.0

or “Completed” then the Computer System provider will set its OperationalStatus[0] to “OK”.

2. If one or more of the subsystems associated with the Computer System provider via the HP_GroupHostedCollection association have a value in GroupOperationalStatus[0] of “Unknown” or “No Contact”, then the Computer System provider will set its OperationalStatus[0] to “Unknown”.

3. If one or more of the subsystems associated with the Computer System provider via the HP_GroupHostedCollection association have a value in GroupOperationalStatus[0] of “Degraded”, “Stressed” or “Stopped”, then the Computer System provider will set its OperationalStatus[0] to Degraded”.

4. If one or more of the subsystems associated with the Computer System provider via the HP_GroupHostedCollection association have a value in GroupOperationalStatus[0] of “Error”, “Aborted”, “Predictive Failure”, “Supporting Entity in Error”, “Non-recoverable Error” or “Lost Communication” then the Computer System provider will set its OperationalStatus[0] to “Error”.

5. If one or more of the subsystems associated with the Computer System provider via the HP_GroupHostedCollection association have a value in GroupOperationalStatus[0] of “Other”, “Starting”, “Stopping”, “In Service”, “Dormant” or “Power Mode” then the Computer System provider will set its OperationalStatus[0] to “Other”.

For Computer System OperationalStatus[0] values other than “OK”, the OtherStatusDescriptions string property should be set to the string “One or more of the components that make up this computer system have an OperationalStatus value of X, Y or Z” where the placeholders X, Y and Z represent the subsystem OperationalStatus values that produced the overall status value.

The remaining elements 1 through N of the Computer System OperationalStatus property array will be populated with the value of GroupOperationalStatus[0] for each collection that contributes to Computer System OperationalStatus[0].

7.1.5 HP_ComputerSystem.OperationalStatusClassNames[] (conditional)

If Consolidated Status Profile is implemented, OperationalStatusClassNames property array shall be implemented. This property array is an indexed array mapping to each element in the OperationalStatus array.

Each element of OperationalStatusClassNames shall contain the value of the Classname property for the HP_GroupSystemSpecificCollection instance represented in the OperationalStatus array. Array index 0 shall be ‘HP_ComputerSystem’.

7.1.6 HP_ComputerSystem.Dedicated OtherDedicatedDescription (Mandatory)

The following vendor specific range (32568..65535) of values can be used in addition to what is defined by DMTF.

Enumeration Value

32568 Virtual Partition

32569 Physical Partition

32570 Virtual System

13 Version 2.0.0

32571 Cell Board

32572 Blade

HP_ComputerSystem.Dedicated[ ] and HP_ComputerSystem.OtherDedicatedDescription[ ] arrays must be populated as follows:

System HP_ComputerSystem. Dedicated[ ]

HP_ComputerSystem. OtherDedicatedDescription[0]

Single blade

Examples: - BL860c - BL870c - Kauai COP1

Dedicated[0]: 2 (Other)

“Modular”

Conjoined blades – Non-partitionable Examples: - Kauai COP2 non-npar - Kauai COP4 non-npar


“Modular”

Conjoined blades –Partitionable Examples: - nPar with 1 blade in a Kauai COP2 or COP4 - nPar with multi blades in a Kauai COP2 or COP4


Dedicated[1]: 32569 (Physical Partition)

Dedicated[2]: 32572 (Blade)

“Modular”

Cell blades – Non-partitionable

(No example, as there’s currently no such system config)


“Modular”

Cell blades – Partitionable

Examples: - nPar with 1 cell blade in a Superdome2 - nPar with multi cell blades in a Superdome2


Dedicated[1]: 32569 (Physical Partition)

Dedicated[2]: 32572 (Blade)

“Modular”

Cellular partition (single-cell or multi-cell)


Dedicated[1]: 32569

“Cellular”

14 Version 2.0.0

Examples: - nPar with 1 cell board in a Superdome - nPar with multi cell boards in a Superdome

(Physical Partition)

Dedicated[2]: 32571 (Cell Board)

Single-node

(Non-cellular servers) Examples: - Proliant DL585 - Integrity rx6600

Dedicated[0]: 0 (Not Dedicated)

Empty

Multi-node

(Single chassis with multiple servers)

Examples: - Proliant 100 series - T2 Spartan


“Multi-node”

Virtual partition Example: - vPar

Dedicated[0]: 32568 (Virtual Partition)

Empty

Virtual system Examples: - HPVM guest - Xen guest

Dedicated[0]: 32570 (Virtual System)

Empty

7.1.7 HP_ComputerSystem physical identifiers (Optional)

Implementations that conform to this profile may populate Model with the model for the physical system. This value shall be the same value that is or could be populated in the HP_ComputerSystemChassis.Model property. That is, the same semantics apply for both values.

Implementations that conform to this profile may populate SerialNumber with the serial number for the physical system. This value shall be the same value that is or could be populated in the HP_ComputerSystemChassis.SerialNumber property. That is, the same semantics apply for both values.

Implementations that conform to this profile may populate IdentifyingNumber with the UUID for the physical system. This value shall be the same value that is or could be populated in the HP_ComputerSystemPackage.PlatformGUID property. That is, the same semantics apply for both values.

15 Version 2.0.0

7.1.8 HP_ComputerSystem Solution identifiers

7.1.8.1 HP_ComputerSystem.IncludedInSolution (Mandatory)

Boolean property that indicates whether the system is part of aggregate systems. Value of True will indicate that the system is participating in the aggregate systems. Default value is False.

7.1.8.2 HP_ComputerSystem.SolutionName (Conditional)

This property is a string that shall contain a unique name that describes the product family for the aggregate product along with the version. Notation: “<Solution Name> vX.Y.Z” where X is Major number, Y is Minor number and Z is Update number Eg. “BladeSystem Matrix v6.3.1a”. This property is only implemented if HP_ComputerSystem.IncludedInSolution is True.

8 Methods

8.1 Method: HP_ComputerSystem.SendTestIndication( )

Return values for SendTestIndication( ) shall be as specified in Table 3 where the method-execution behavior matches the return-code description. SendTestIndication( ) method’s parameters are specified in Table 2.

No standard messages are defined for this method.

Table 3 – HP_ComputerSystem.SendTestIndication( ) Method: Return Code Values

Value Description 0 Request to send test indication was accepted

1 Method is not supported in the implementation

2 Internal error occurred, request to send indication failed.

3 Method is busy servicing previous requests

Table 4 – HP_ComputerSystem.SendTestIndication( ) Method: Parameters

Qualifiers Name Type Description/Values IN EventID Uint32 Test indication to send

101 – Informational Test Indication 102 - Warning Test Indication 103 – Critical Test Indication

8.1.1 General Requirements

If the EventID parameter is not a valid value for a test indication, the HP_ComputerSystem.SendTestIndication() method shall throw an INVALID_PARAMETER exception. Caller should change the parameter to a valid value and retry the request.

The HP_ComputerSystem.SendTestIndication() method shall return 3 (Busy) if the method is in the process of sending a test indication from a previous request. Caller should retry the request. The method shall delay generation of test indications requested to reduce the possibility of flooding.

16 Version 2.0.0

The HP_ComputerSystem.SendTestIndication() method shall return 2 (Failed) if the request to send the indication could not be processed due to an internal error. Caller should not retry the request.

The HP_ComputerSystem.SendTestIndication() method shall return 0 (OK) if the request to send the indication was accepted. Table 3 defines the indications that shall be sent.

Table 5 – Test Indications

Property Name Property Implementation CIM_Indication

PerceivedSeverity 2 (Informational) 3 (Warning) 6 (Critical)

CIM_AlertIndication Description “This is an Informational Test Event.”

“This is a Warning Test Event.” “This is a Critical Test Event.”

AlertType 5 (Device Alert) EventID “1”

“2” “3”

ProviderName “HP Test” RecommendedActions “No action is recommended.”

HP_AlertIndication Summary “Test Event” ProbableCause 1 (Other) ProbableCauseDescription “Test Indication”




• GetInstance

• Associators

• AssociatorNames

• References

• ReferenceNames



17 Version 2.0.0




9 Use Cases

9.1 Object Diagrams

Figure 2 shows a simple implementation of a system containing 3 fans and 2 processors. The fans, processors, and base system have been extended via HP extension profiles. This example also shows that the DMTF physical asset profile has been implemented and has been extended to include base server physical asset information by the HP Base Server Physical Asset profile.

The example uses the scoping class methodology for registering compliance to profiles. Using the methodology only one CIM_ElementConformsToProfile is required to associate the single autonomous profile (DMTF Base Server in this case) with the central class instance (HP_ComputerSystem in this case) in the implementation namespace. Note that even though the scoping class is of type HP_ComputerSystem, generic SMASH based clients would see an instance of CIM_ComputerSystem because HP_ComputerSystem sub-classed off of CIM_ComputerSystem.

The interop namespace contains the same referenced profiles as you would expect given the description contained in the Profile Registration Profile (DSP1033). The registered DMTF Base Server profile references the DMTF CPU, Fan and Physical Asset profiles because the implementation namespace contains implementations for each. In addition, the interop namespace contains the registrations for extensions to the base model because the DMTF Base Server, CPU, Physical Asset, and Fan profiles have been extended with HP specific profiles (HP Base Server, HP CPU, HP Base Server Physical Asset and HP Fan). From the interop namespace clients can tell which autonomous and component profiles are implemented and which of those profiles have been extended via HP extension profiles.

18 Version 2.0.0

system1: HP_ComputerSystem:

chassis1: HP_ComputerSystemChassis

proc1: HP_Processor

proc2: HP_Processor

HP_SystemProcessor


fan1: HP_Fan

fan2: HP_Fan

fan3: HP_Fan

HP_SystemFan


RegisteredOrg: DMTF (2)RegisteredName: Base Server


RegisteredOrg: DMTF (2)RegisteredName: Physical Asset


RegisteredOrg: DMTFRegisteredName: Fan


RegisteredOrg: Other (1)OtherRegOrg:HP WBEM TCRegisteredName: HP Base Server


RegisteredOrg: Other (1)OtherRegOrg: HP WBEM TCRegisteredName: HP Base Server

Physical Asset

HP_ExtendsProfile


RegisteredOrg: Other (1)OtherRegOrg: HP WBEM TCRegisteredName: HP Fan

HP_ExtendsProfile

Interop Namespace

CIM_ReferencedProfileCIM_ReferencedProfile


RegisteredOrg: Other (1)OtherRegOrg: HP WBEM TCRegisteredName: HP CPU


RegisteredOrg: DMTFRegisteredName: CPU


HP_ExtendsProfileHP_ExtendsProfile


Figure 2 – HP Base Server Profile: Base System with Fans and Processors

Figure 3 shows a system containing 1 memory module and 1 CPU. The system also contains 2 memory board slots. The physical side of the CPU, Memory, and Base server models have been implemented. HP_ComputerSystem is associated with its physical chassis (HP_ComputerSystemChassis) via the association instance HP_ComputerSystemPackage. HP_Memory and HP_Processor have associations to their physical model via realizes associations (HP_RealizesMemory and HP_RealizesProcessor respectively).

The single memory module (HP_PhysicalMemory) is installed on a memory board, shown here as an instance of HP_PhysicalMemory associated with HP_MemoryBoard via an HP_ModuleOnBoard association. The memory board is in turn associated with the slot it is installed in, shown as an instance of HP_MemoryBoardInSlot associating HP_MemoryBoard and CIM_Slot.

19 Version 2.0.0

Clients can determine that the physical sides of the CPU, Memory, and Base Server models have been extended by discovering an HP_ExtendsProfile instance associating CIM_RegisteredProfile for the DMTF Physical Asset profile with the 3 extension profiles; HP Base Server Physical Asset profile, HP CPU Physical Asset profile, and HP Memory Physical Asset profile.

HP_ComputerSystem:system1

HP_ComputerSystemChassis:chasssis1

HP_Processor:proc1

HP_ProcessorChip:procchip1

HP_SystemProcessor



HP_Memory:mem1

CIM_Slot:slot1

ConnectorType: 78 (Proprietary Memory Card Slot)

CIM_Slot:slot2

ConnectorOnPackage

HP_SystemMemory

HP_PhysicalMemory:physmem1

HP_MemoryBoard:membrd1

HP_ModuleOnBoard

HP_MemoryBoardInSlot

HP_RealizesMemory




RegisteredOrg: DMTF (2)RegisteredName: Physical Asset


RegisteredOrg: DMTFRegisteredName: Memory




RegisteredOrg: Other (1)OtherRegOrg: HP WBEM TCRegisteredName: HP Base Server

Physical Asset

HP_ExtendsProfile


RegisteredOrg: Other (1)OtherRegOrg: HP WBEM TCRegisteredName: HP Memory

HP_ExtendsProfile

Interop Namespace

CIM_ReferencedProfileCIM_ReferencedProfile


RegisteredOrg: Other (1)OtherRegOrg: HP WBEM TCRegisteredName: HP CPU


RegisteredOrg: DMTFRegisteredName: CPU


HP_ExtendsProfileHP_ExtendsProfile



RegisteredOrg: Other (1)OtherRegOrg: HP WBEM TCRegisteredName: HP CPU Physical Asset


RegisteredOrg: Other (1)OtherRegOrg: HP WBEM TCRegisteredName: HP Memory Physical Asset

Figure 3 – HP Base Server Profile: Base System with 1 CPU and 1 Memory

20 Version 2.0.0

Figure 4 shows an example of how HP Consolidate Status works with an instance of HP_ComputerSystem. The instance of HP_ComputerSystem has 2 subsystems (power and cooling) represented by instances of HP_PowerSupplyCollection and HP_CoolingCollection. Each subsystem is associated with HP_ComputerSystem with associations that subclass from HP_GroupHostedCollection (HP_HostedCollingCollection and HP_HostedPowerCollection in this case). The system contains three fans and two power supplies associated to the instance of HP_CompuerSystem via associations HP_SystemFan and HP_SystemPowerSupply respectively. The status of a bottom level element bubbles up to the collection then in turn bubbles up to the HP_ComputerSystem instance. For example, the status of the instances of HP_Fan.OperationStatus[0] bubbles up to the instance of HP_CoolingCollection.GroupOperationStatus[0] which in turn bubbles up to the instance of HP_Coputersystem.OperationStatus[0]. In this example, the overall status of the HP_ComputerSystem is 4(stressed) because one power supply’s OperationalStatus is 4(stressed) causing the HP_PowerSupplyCollection’s GroupOperationalStatus to be 4(stressed). This in turn bubbles up to the HP_ComputerSystem as to worst-of value of any collection associated with it.

21 Version 2.0.0

system1: HP_ComputerSystem:OperationalStatus[0]:

Degraded

ps1: HP_PowerSupply

OperationalStatus[0]: OK

ps2: HP_PowerSupply



fan1: HP_Fan

OperationalStatus[0]: Degraded

fan2: HP_Fan


fan3: HP_Fan





RegisteredOrg: DMTFRegisteredName: Fan



HP_ExtendsProfile


RegisteredOrg: Other (1)OtherRegOrg: HP WBEM TCRegisteredName: HP Fan

HP_ExtendsProfile

Interop Namespace



RegisteredOrg: Other (1)OtherRegOrg: HP WBEM TCRegisteredName: HP Power supply


RegisteredOrg: DMTFRegisteredName: Power Supply


HP_ExtendsProfile


HP_SystemFan

col1 : HP_CoolingCollection


col2: HP_PowerSupplyCollection




HP_HostedPowerCollectionHP_HostedCoolingCollection

Figure 4 – HP Base Server profile: Consolidated Status

9.2 Determine if the HP Base Server Profile has been Implemented and Find top level instance of HP_ComputerSystem

Clients can follow this algorithm to find the top level instance of HP_ComputerSystem that represents the top level system:

• Query the interop namespace for an instance of CIM_RegisteredProfile with the RegisteredOrganization set to 2 (DMTF) and RegisteredName set to “Base Server”.

22 Version 2.0.0

• Query for all instances of HP_RegisterdProfile associated with this instance of CIM_RegisteredProfile via the association HP_ExtendsProfile that have the following property values:

• RegisteredOrganization – 1 (other)

• OtherRegisteredOrganization – “HP WBEM TC”

• RegisteredName – “HP Base Server”

• If an instance of HP_RegisteredProfile is found in the previous step, the client knows that the implementation namespace’s Base Server instance has been extended with the HP specific elements defined in this profile. The client would then follow the methods defined in the DMTF Profile Registration (DSP 1033) and HP Profile Registration (P00100) profiles to find the central class of the instances of CIM_RegisteredProfile and HP_RegisteredProfile found in the first two steps.

9.3 Determine Status of Top Level HP_ComputerSystem

Clients determine the status of the top level instance of HP_ComputerSystem by querying the value of OperationalStatus and looking at the first array element (index 0). This is the primary status of the computer system and reflects that status of all sub-components of the system.

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).



HP_ComputerSystem Mandatory see Section 7.1 HP_RegisteredProfile Mandatory see section 10.2 HP_ComputerSystemPackage Mandatory (see HP Base Server Physical Asset profile)

Indications Test Indications Optional See section 8.1


The HP_ComputerSystem is used to model an HP computer system. Table 4 shows the properties that shall be implemented for the HP_ComputerSystem class and its subclasses.

23 Version 2.0.0

Table 7 – Class: HP_ComputerSystem

Properties Requirement

Notes

PrimaryOwnerName O (see section 7.1.1)

PrimaryOwnerContact O (see section 7.1.1)

PrimaryOwnerPager O (see section 7.1.1)

SecondaryOwnerPager O (see section 7.1.1)

SecondaryOwnerName O (see section 7.1.1)

SecondaryOwnerPager O (see section 7.1.1)

LocationIndicator O (see section 7.1.2)

OtherIdentifyingInfo O (see section 7.1.3)

IdentifyingDescriptions O (see section 7.1.3)

OperationalStatus M (see section 7.1.4)

OperationalStatusClassNames C (see section 7.1.5)

Dedicated O (see section 7.1.6)

OtherDedicatedDescriptions O (see section 7.1.6)

IdentifyingNumber O (see section 7.1.7) SerialNumber O (see section 7.1.7) Model O (see section 7.1.7) SendTestIndication() O (see section 8.1)

IncludedInSolution M (see section 7.1.8.1)

SolutionName C (see section 7.1.8.2)


Implementation shall implement an instance of HP_RegisteredProfile in the interop namespace with the values specified.


Properties Requirement Notes RegisteredOrganization M Other (1)

OtherRegisteredOrganization M “HP WBEM TC”

RegisteredName M “HP Base Server”

RegisteredVersion M “1.5.1”




24 Version 2.0.0



None Defined




None Defined

25 Version 2.0.0

ANNEX A (normative)

Change Log

26 Version 2.0.0


Acknowledgments

27 Version 2.0.0



CR

Number Date Title CR00103 6/14/06 Create HP Profile for the logical and physical base server model.

CR00142 10/20/2008 Changes related to Blade System Lite profile updates for supporting multiple enclosures

CR00144 02/19/2009 Add SendTestIndication() method , definition of test indications and HPQ:ChassisSerialNumber tag.

CR00152 07/30/2009 Update section 7.1.5 (HP_ComputerSystem.Dedicated) to clarify the data to be populated

CR00155 10/08/2009 Clarify usage of Dedicated and OtherDedicated.

CR00159 02/18/2010 Added OperationalStatusClassNames. Added optional reference to consolidated status profile. Added description of Computer System OperationaStatus[1..N].

CR00171 03/25/2011 Added IncludedInSolution and SolutionName to support aggregate systems.

28 Version 2.0.0

Bibliography



Date: 3/04/2011

Version: 1.1.0

HP CPU Profile




2 1.1.0

Contents



3 Terms and Definitions ........................................................................................................................... 7 4 Symbols and Abbreviated Terms .......................................................................................................... 8 5 Synopsis ................................................................................................................................................ 9 6 Description .......................................................................................................................................... 10 7 Implementation Requirements ............................................................................................................ 12

7.1 HP_ProcessorCore ................................................................................................................... 12 8 Methods ............................................................................................................................................... 13

8.1 Profile Conventions for Operations ........................................................................................... 13 8.2 HP_Processor ........................................................................................................................... 13 8.3 HP_ProcessorCore ................................................................................................................... 13 8.4 HP_HardwareThread ................................................................................................................ 14

9 Use Cases ........................................................................................................................................... 15 9.1 Object Diagrams ....................................................................................................................... 15

10 CIM Elements ...................................................................................................................................... 16 10.1 HP_AssociatedProcessorCacheMemory.................................................................................. 16 10.2 HP_HWThreadComponent ....................................................................................................... 16 10.3 HP_ProcessorCoreComponent ................................................................................................ 17 10.4 HP_Processor ........................................................................................................................... 17 10.5 HP_ProcessorCore ................................................................................................................... 17 10.6 HP_HardwareThread ................................................................................................................ 17 10.7 HP_CacheMemory .................................................................................................................... 17 10.8 HP_SystemProcessor ............................................................................................................... 18 10.9 HP_RegisteredProfile ............................................................................................................... 18 10.10 HP_ProcessorCapabilities (Conditional)................................................................................... 18 10.11 HP_ProcessorElementCapabilities (Conditional) ..................................................................... 19


1.1.0 3

Figures

Figure 1 – CPU Profile: Class Diagram ...................................................................................................... 10 Figure 2 – CPU Profile: Hierarchy Diagram ................................................................................................ 11 Figure 3 – HP CPU Profile: Object diagram with cores and threads .......................................................... 15

4 1.1.0

Tables

Table 1 – Related Profiles ............................................................................................................................. 9 Table 2 – Processor Status Mapping Table ................................................................................................ 12 Table 3 – Operations: HP_Processor ........................................................................................................ 13 Table 4 – Operations: HP_ProcessorCore ................................................................................................ 14 Table 5 – Operations: HP_HardwareThread ............................................................................................. 14 Table 6 – CIM Elements – HP CPU Profile ................................................................................................. 16 Table 7 – Class: HP_AssociatedProcessorCacheMemory ......................................................................... 16 Table 8 – Class: HP_HWThreadComponent .............................................................................................. 16 Table 9 – Class: HP_ProcessorCoreComponent ....................................................................................... 17 Table 10 – Class: HP_Processor ................................................................................................................ 17 Table 11 – Class: HP_ProcessorCore ........................................................................................................ 17 Table 12 – Class: HP_HardwareThread ..................................................................................................... 17 Table 13 – Class: HP_CacheMemory ......................................................................................................... 18 Table 14 – Class: HP_SystemProcessor .................................................................................................... 18 Table 15 – Class: HP_RegisteredProfile .................................................................................................... 18 Table 16 – Class: HP_ProcessorCapabilities ............................................................................................. 19 Table 17 – Class: HP_ProcessorElementCapabilities ................................................................................ 19 Table 18 – Durable Names generated by this Profile ................................................................................. 19 Table 19 – Correlatable IDs generated by this Profile ................................................................................ 19

1.1.0 5

Foreword

The HP CPU Profile P00106 was prepared by the HP WBEM TC.

6 1.1.0

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 logical CPUs in HP systems (support for physical CPU information is optional). 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.

1.1.0 7

1 Scope The HP CPU profile extends the management capability of referencing profiles by adding the capability to represent the logical CPUs in HP specific ways.






DMTF DSP1022, CPU Profile

HP WBEM TC P00108, HP CPU Physical Asset Profile

HP WBEM TC P00107, HP CPU Consolidated Status profile










8 1.1.0











None.

1.1.0 9

5 Synopsis Profile Name: HP CPU Profile

Version: 1.1.0



Central Class: HP_Processor

Scoping Class: Same as parent profile

Extends: DMTF DSP1022, CPU Profile 1.0.0

The HP CPU profile extends DMTF DSP1022 to add CPU characteristics that are specific to HP systems.





P00108 – HP CPU Physical Asset Profile


DSP1022 – CPU Profile DMTF 1.0.0 Extends

P00107 – HP CPU Consolidated Status profile


10 1.1.0

6 Description

HP_Processor

HP_CacheMemory

HP_RealizesProcessor(see HP CPU Physical

Asset Profile)

HP_RealizesProcessorCache (see HP CPU Physical Asset

Profile)

HP_ProcessorChip

(see HP CPU Physical Asset

Profile)

HP_PhysicalCacheMemory

(see HP CPU Physical Asset Profile)


(see HP Profile Registration Profile)


profile)

*

0..1

*

* * 1

0..1

1


(see HP CPU Consolidated Status profile)

HP_LogicalMemberOfProcessorCollection(see HP CPU Consolidated Status profile)

*

1

HP_ComputerSystem

(see HP Base Server Profile)

1..*

1

HP_ProcessorCore

HP_HardwareThread

1

*

HP_AssociatedProcessorCacheMemory

*

*1

HP_SystemProcessor

HP_ProcessorElementCapabilities

HP_ProcessorCapabilities

NumberOfProcessorCoresNumberOfHardwareThreadsVirtualizationTechnologyStatus

1

1

HP_HWThreadComponent

HP_ProcessorCoreComponent

Figure 1 – CPU Profile: Class Diagram

1.1.0 11

CIM_AssociatedCacheMemory

(see DMTF CPU Profile)

HP_AssociatedCacheMemory

CIM_SystemDevice


HP_SystemProcessor

Memory


HP_CacheMemory

Processor


HP_Processor

ProcessorCapabilities

HP_ProcessorCapabilities

ProcessorCore


HP_ProcessorCore

HardwareThread


HP_HardwareThread

ConcreteComponent


HP_HWThreadComponent

ElementCapabilities



Figure 2 – CPU Profile: Hierarchy Diagram

The HP CPU profile extends the DMTF CPU profile defined in DSP1022 to add the HP capability of reporting the consolidated status (see HP CPU Consolidated Status Profile) and optionally the CPU physical asset information (see HP CPU Physical Asset Profile).

Figure 1 shows the class diagram for the HP CPU profile.

12 1.1.0

A relationship between a logical processor (HP_Processor) or a logical processor core (HP_ProcessorCore) and a cache memory (HP_CacheMemory) that is used by the processor is represented by the HP_AssociatedProcessorCacheMemory class.

The physical processor is represented by the HP_ProcessorChip class.

The HP_PhysicalCacheMemory class is used when the cache is external to the processor.

Each logical processor core (HP_ProcessorCore) in a multi-core CPU is associated to the logical processor (HP_Processor) via the HP_ProcessorCoreComponent class.

Each hardware thread (HP_HardwareThread) within a CPU core is associated to the logical processor core (HP_ProcessorCore) via the HP_HWThreadComponent class.

Each logical processor core will propagate its status via the HP_ProcessorCollection aggregation class (as defined in the HP CPU Consolidated Status profile).

Each logical processor may have an HP_ProcessorCapabilities instance associated to the HP_Processor by way of the HP_ProcessorElementCapabilities association.


7.1 HP_ProcessorCore


7.1.1 HP_ProcessorCore.Bootstrap (Optional)

This optional property shall contain a boolean value indicating the processor was the bootstrap (or monarch) processor for the system.

7.1.2 HP_ProcessorCore.OperationalStatus

The first element of this array shall contain the overall status of the processor core and shall contain one of the values from Table 2. Additional status may also be provided in subsequent elements. All additional elements would be for additional status information, but not used for aggregate status. Refer to the HP WBEM TC P00107, HP CPU Consolidated Status profile for more information.

Table 2 – Processor Status Mapping Table

Processor status Operational status value element 0

Operational status value element 1 (may not exist)

Processor OK OK(2) (empty)

Predictive failure Degraded(3) PredictiveFailure(5)

De-configured by power-on-self-test error or other detected errors

Error(6) (empty)

De-configured by BIOS setup OK(2) Stopped(10)

1.1.0 13

8 Methods None.




• GetInstance

• Associators

• AssociatorNames

• References

• ReferenceNames




8.2 HP_Processor

The table below lists operations that either have special requirements beyond those from DSP0200 or shall not be supported. All other operations may be supported as defined in DSP0200.

Table 3 – Operations: HP_Processor









8.3 HP_ProcessorCore


14 1.1.0

Table 4 – Operations: HP_ProcessorCore









8.4 HP_HardwareThread


Table 5 – Operations: HP_HardwareThread









1.1.0 15

9 Use Cases

9.1 Object Diagrams

The following represents a possible instantiation of the HP CPU Profile. In this case, system1 has one processor with 2 cores. Each of the cores has one hardware thread.


system1 : HP_ComputerSystem

cpu1 : HP_Processor

NumberOfEnabledCores : 2

memory1:HP_CacheMemory

HP_AssociatedCacheMemoryLevel : 4 (Secondary)

memory2::HP_CacheMemory

HP_AssociatedCacheMemoryLevel : 4 (Secondary)

HP_ComputerSystemProcessor

core2 : HP_ProcessorCore

EnabledState : 2 (Enabled)CoreEnabledState : 2 (Core Enabled)Characteristics : 3 (32 bit Capable)

core1 : HP_ProcessorCore

EnabledState : 2 (Enabled)CoreEnabledState : 2 (Core Enabled)Characteristics : 3 (32 bit Capable)

capabilities1 : HP_ProcessorCapabilities

NumberOfProcessorCores : 2NumberOfProcessorThreads : 2RequestedStatesSupported[] : { } VirtualizationTechnologyStatus : 0


thread1 : HP_HardwareThread thread2 : HP_HardwareThread


HP_HWThreadComponentHP_HWThreadComponent

Figure 3 – HP CPU Profile: Object diagram with cores and threads

16 1.1.0

10 CIM Elements Table 6 – CIM Elements – HP CPU Profile


Classes HP_AssociatedProcessorCacheMemory Conditional See section 10.1

HP_HWThreadComponent Conditional See section 10.2

HP_ProcessorCoreComponent Conditional See section 10.3

HP_HardwareThread Conditional See section 10.6

HP_CacheMemory Optional See section 10.7

HP_Processor Mandatory See section 10.4

HP_ProcessorCore Mandatory See section 7.1 and 10.5

HP_RegisteredProfile Mandatory See section 10.9

HP_SystemProcessor Mandatory See section 10.8

HP_ProcessorCapabilities Conditional See section 10.10

HP_ProcessorElementCapabilities Conditional See section 10.11 Indications


10.1 HP_AssociatedProcessorCacheMemory HP_AssociatedProcessorCacheMemory extends the association class CIM_AssociatedCacheMemory in ways that are specific to HP systems. Implementations shall adhere to the requirements defined in DSP1022 for the class CIM_AssociatedCacheMemory as well as additional requirements defined in this section.

Table 7 – Class: HP_AssociatedProcessorCacheMemory

Properties Requirement Notes Antecedent Mandatory REF:HP_CacheMemory

Dependent Mandatory REF:CIM_EnabledLogicalElement (it can reference either HP_Processor or HP_ProcessorCore)

10.2 HP_HWThreadComponent HP_HWThreadComponent extends the class CIM_ConcreteComponent for use only with HP_HardwareThread and HP_ProcessorCore. Implementations shall adhere to the requirements defined in DSP1022 for the class CIM_ConcreteComponent as well as additional requirements defined in this section.

Table 8 – Class: HP_HWThreadComponent

Properties Requirement Notes PartComponent Mandatory REF:HP_HardwareThread

GroupComponent Mandatory REF:HP_ProcessorCore

1.1.0 17

10.3 HP_ProcessorCoreComponent HP_ProcessorCoreComponent extends the class CIM_ConcreteComponent for use only with HP_ProcessorCore and HP_Processor. Implementations shall adhere to the requirements defined in DSP1022 for the class CIM_ConcreteComponent as well as additional requirements defined in this section.

Table 9 – Class: HP_ProcessorCoreComponent

Properties Requirement Notes PartComponent Mandatory REF:HP_ProcessorCore

GroupComponent Mandatory REF:HP_Processor

10.4 HP_Processor HP_Processor extends the class CIM_Processor in ways that are specific to HP systems. Implementations shall adhere to the requirements defined in DSP1022 for the class CIM_Processor as well as additional requirements defined in this section.

Table 10 – Class: HP_Processor


None new

10.5 HP_ProcessorCore HP_ProcessorCore extends the class CIM_ProcessorCore in ways that are specific to HP systems. Implementations shall adhere to the requirements defined in DSP1022 for the class CIM_ProcessorCore as well as additional requirements defined in this section. Single-core / single-thread processors may not support this class. Multi-core processors shall support this class.

Table 11 – Class: HP_ProcessorCore


Bootstrap Optional See section 7.1.1

10.6 HP_HardwareThread HP_HardwareThread extends the class CIM_HardwareThread in ways that are specific to HP systems. Implementations shall adhere to the requirements defined in DSP1022 for the class CIM_HardwareThread as well as additional requirements defined in this section. Single-core / single-thread processors may not support this class. Multi-thread processors shall support this class.

Table 12 – Class: HP_HardwareThread


None new

10.7 HP_CacheMemory HP_CacheMemory extends the class CIM_Memory in ways that are specific to HP systems. Implementations shall adhere to the requirements defined in DSP1022 for the class CIM_Memory as well as additional requirements defined in this section.

18 1.1.0

Table 13 – Class: HP_CacheMemory


None new

10.8 HP_SystemProcessor HP_SystemProcessor extends the class CIM_SystemDevice for use only with HP_ComputerSystem and HP_Processor. Implementations shall adhere to the requirements defined in DSP1022 for the class CIM_SystemDevice as well as additional requirements defined in this section.

Table 14 – Class: HP_SystemProcessor

Properties Requirement Notes GroupComponent Mandatory REF:HP_ComputerSystem

PartComponent Mandatory REF:HP_Processor


Implementation shall implement an instance of HP_RegisteredProfile in the Interop namespace with the values specified.





RegisteredName Mandatory “HP CPU”


10.10 HP_ProcessorCapabilities (Conditional) HP_ProcessorCapabilities extends the class CIM_ProcessorCapabilities in ways that are specific to HP systems. Implementations shall adhere to the requirements defined in DSP1022 for the class CIM_ProcessorCapabilities as well as additional requirements defined in this section.

This class is optionally supported on systems that have single-core and single-thread processors. This class is mandatory on systems that have multi-core or multi-thread processors.

This class is optionally supported on systems that don’t have Intel VT technology. This class is mandatory on systems that have Intel VT technology Supported.

1.1.0 19

Table 16 – Class: HP_ProcessorCapabilities


VirtualizationTechnologyStatus Conditional Value: 0 – Disabled 1 – Enabled Note: Default value is Disabled

10.11 HP_ProcessorElementCapabilities (Conditional) HP_ProcessorelementCapabilities extends the class CIM_ElementCapabilities for use only with HP_ProcessorCapabilities and HP_Processor. Implementations shall adhere to the requirements defined in DSP1022 for the class CIM_ElementCapabilities as well as additional requirements defined in this section. This class is conditionally instantiated depending on if the HP_ProcessorCapabilities class is instantiated.

Table 17 – Class: HP_ProcessorElementCapabilities

Properties Requirement Notes Capabilities Mandatory REF:HP_ProcessorCapabilities

ManagedElement Mandatory REF:HP_Processor




None defined




None defined

20 1.1.0

ANNEX A (normative)

Change Log


0.1 3/15/06 Initial Draft 0.2 6/7/06 Updates to match DMTF CPU profile 0.9.3.

1.0 7/11/06

Updates based on HP WBEM TC review on 7/10/06. Also removed references to HP_ProcessorCacheMemory – use only HP_CacheMemory from the HP-UX profile Also added HP_ProcessorCapabilities and HP_ProcessorElementCapabilities sections

1.0 7/27/06 Updates based on Brady Evans review.

1.0 4/18/07 Changed HP_AssociatedCacheMemory to HP_AssociatedProcessorCacheMemory (HP_AssociatedCacheMemory still defined in figure 2.

1.0 3/04/2011 Fix diagram where HP_ProcessorCacheMemory was still referenced. 1.1.0 4/13/2011 Updated ProcessorCapability with VirtualizationTechnologyStatus

1.1.0 21


Acknowledgments

22 1.1.0



CR

Number Date Title

CR00104 6/28/2006 Create HP Profiles for the CPU model.

1.1.0 23

Bibliography



Date: 8/2/06

Version: 1.0.0

HP CPU Consolidated Status Profile




2 Version 1.0.0

Contents




7.1 HP_ProcessorCollection ........................................................................................................... 11 7.2 HP_PhysicalMemberOfProcessorCollection (Conditional) ....................................................... 11 7.3 HP_LogicalMemberOfProcessorCollection (Conditional) ......................................................... 11

8 Methods ............................................................................................................................................... 11 8.1 Profile Conventions for Operations ........................................................................................... 11 8.2 HP_ProcessorCollection ........................................................................................................... 12


10 CIM Elements ...................................................................................................................................... 14 10.1 HP_ProcessorCollection ........................................................................................................... 14 10.2 HP_ProcessorGroupHostedCollection ..................................................................................... 15 10.3 HP_LogicalMemberOfProcessorCollection .............................................................................. 15 10.4 HP_PhysicalMemberOfProcessorCollection ............................................................................ 15 10.5 HP_RegisteredProfile ............................................................................................................... 16


Version 1.0.0 3

Figures

Figure 1 – CPU Consolidated Status Profile: Class Diagram ..................................................................... 10Figure 2 – CPU Consolidated Status Profile: Inheritance Hierarchy .......................................................... 10Figure 3 – CPU Consolidated Status Profile (Logical CPU Propagation) ................................................... 13Figure 4 – CPU Consolidated Status Profile (Physical CPU Propagation) ................................................. 14

4 Version 1.0.0

Tables

Table 1 – Related Profiles ............................................................................................................................. 9Table 2 – Operations: HP_ProcessorCollection ........................................................................................ 12Table 3 – CIM Elements – HP CPU Consolidated Status Profile ............................................................... 14Table 4 – Class: HP_ProcessorCollection .................................................................................................. 15Table 5 – Class: HP_ProcessorGroupHostedCollection ............................................................................ 15Table 6 – Class: HP_LogicalMemberOfProcessorCollection ..................................................................... 15Table 7 – Class: HP_PhysicalMemberOfProcessorCollection ................................................................... 16Table 8 – Class: HP_RegisteredProfile ...................................................................................................... 16Table 9 – Durable Names generated by this Profile ................................................................................... 16Table 10 – Correlatable IDs generated by this Profile ................................................................................ 16

Version 1.0.0 5

Foreword

The HP CPU Consolidated Status Profile P00107 was prepared by the HP WBEM TC.

6 Version 1.0.0

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 and manage the state and health of logical and physical CPU subsystems. 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.

Version 1.0.0 7

1 Scope The HP CPU Consolidated Status profile extends the management capability of referencing profiles by adding the capability to represent the state of logical and physical CPU subsystems in a system.







HP WBEM TC P00106, HP CPU profile

HP WBEM TC P00108, HP CPU Physical Asset profile








http://isotc.iso.org/livelink/livelink.exe?func=ll&objId=4230456&objAction=browse&sort=subtype�

http://www.omg.org/technology/documents/modeling_spec_catalog.htm#UML�

8 Version 1.0.0











None.

Version 1.0.0 9

5 Synopsis Profile Name: HP CPU Consolidated Status profile

Version: 1.0.0



Central Class: HP_ProcessorCollection


Specializes: WBEM TC – P00113, HP Consolidated Status profile 1.0.0

The HP CPU Consolidated Status profile specializes the HP Consolidated Status profile for logical and physical CPUs.







P00105 – HP Base Server profile


P00106 – HP CPU Profile HP WBEM TC 1.0.0 Conditional Conditional on status propagation occurring based on the logical HP_ProcessorCore class

P00108 – HP CPU Physical Asset Profile

HP WBEM TC 1.0.0 Conditional Conditional on status propagation occurring based on the physical HP_ProcessorChip class

6 Description

10 Version 1.0.0



HP_ComputerSystem



HP_ProcessorChip

(see HP CPU Physical Asset Profile)

HP_ProcessorCore

(see HP CPU Profile)





1

*

1

*

11

**


(see HP Consolidated Status profile)

Figure 1 – CPU Consolidated Status Profile: Class Diagram



CIM_MemberOfCollection HP_GroupHostedCollection



Figure 2 – CPU Consolidated Status Profile: Inheritance Hierarchy

Each processor chip (via the HP_PhysicalMemberOfProcessorCollection association) and/or processor (via the HP_LogicalMemberOfProcessorCollection association) propagates its operational status through the HP_ProcessorCollection class to the singleton instance of HP_ComputerSystem. It populates the

Version 1.0.0 11

properties GroupOperationalStatus and GroupStatusDescription which are used by the HP_ComputerSystem class provider to update its overall status.


7.1 HP_ProcessorCollection

There may be one or more instance of HP_ProcessorCollection instantiated. Instances of HP_ProcessorChip and HP_ProcessorCore (depending on whether physical or logical processors are used for the collection) shall be associated to HP_ProcessorCollection through the HP_PhysicalMemberOfProcessorCollection and HP_LogicalMemberOfProcessorCollection association respectively. Instances of HP_ProcessorCollection shall be associated to the containing computer system instance (HP_ComputerSystem) through the HP_ProcessorGroupHostedCollection association.

The HP_ProcessorCollection shall support aggregation of logical CPU’s or physical CPU’s in the collection or both.

7.1.1 HP_ProcecorCollection.GroupOperationalStatus

The Processor Collection’s GroupOperationalStatus shall be computed from the worst case OperationalStatus[0] element of each of the members of the collection.

7.2 HP_PhysicalMemberOfProcessorCollection (Conditional)

When a physical processor collection is implemented, there shall be one instance of HP_PhysicalMemberOfProcessorCollection instantiated for each instance of HP_ProcessorChip. This class associates an instance of HP_ProcessorChip to the respective instance of HP_ProcessorCollection.

7.3 HP_LogicalMemberOfProcessorCollection (Conditional)

When a logical processor collection is implemented, there shall be one instance of HP_LogicalMemberOfProcessorCollection instantiated for each instance of HP_ProcessorCore. This class associates an instance of HP_ProcessorCore to the respective instance of HP_ProcessorCollection.

8 Methods None.




• GetInstance

• Associators

• AssociatorNames

12 Version 1.0.0

• References

• ReferenceNames




8.2 HP_ProcessorCollection


Table 2 – Operations: HP_ProcessorCollection









Version 1.0.0 13

9 Use Cases

9.1 Object Diagrams

Figure 3 below represents a possible instantiation of the CPU Consolidated Status Profile propagating the status of the logical processor cores. The worst case OperationalStatus condition from each of the processor core instances “core1” and “core2” is propagated to the GroupOperationalStatus of the HP_ProcessorCollection instance “coll1”.

coll1: HP_ProcessorCollection

GroupOperationalStatus[0]: Failed



core1: HP_ProcessorCore



core2: HP_ProcessorCore

OperationalStatus[0]: Failed

Figure 3 – CPU Consolidated Status Profile (Logical CPU Propagation)

Figure 4 below represents a possible instantiation of the CPU Consolidated Status Profile propagating the status of the physical processor chips. The worst case OperationalStatus condition from each of the processor chips instances “chip1” and “chip2” is propagated to the GroupOperationalStatus of the HP_ProcessorCollection instance “coll1”.

14 Version 1.0.0

coll1: HP_ProcessorCollection




chip1: HP_ProcessorChip





Figure 4 – CPU Consolidated Status Profile (Physical CPU Propagation)

10 CIM Elements Table 3 – CIM Elements – HP CPU Consolidated Status Profile


Classes HP_ProcessorCollection Mandatory See sections 7.1 and 10.1

HP_ProcessorGroupHostedCollection Mandatory See section 10.2

HP_PhysicalMemberOfProcessorCollection Conditional See sections 7.2 and 10.4

HP_LogicalMemberOfProessorCollection Conditional See sections 7.3 and 10.3

HP_Registeredprofile Mandatory See section 10.5 Indications


10.1 HP_ProcessorCollection HP_ProcessorCollection extends the class HP_GroupSystemSpecificCollection in ways that are specific to HP processor implementations. Implementations shall adhere to the requirements defined in HP WBEM TC P00113, HP Consolidated Status profile for the class HP_GroupSystemSpecificCollection as well as additional requirements defined in this section.

Version 1.0.0 15

Table 4 – Class: HP_ProcessorCollection

Properties Requirement Notes InstanceID Mandatory Key:

GroupOperationalStatus Mandatory See section 7.1.1

10.2 HP_ProcessorGroupHostedCollection HP_ProcessorGroupHostedCollection extends the class HP_GroupHostedCollection in ways that are specific to HP processor implementations. Implementations shall adhere to the requirements defined in HP WBEM TC P00113, HP Consolidated Status profile for the class HP_GroupHostedCollection as well as additional requirements defined in this section.

Table 5 – Class: HP_ProcessorGroupHostedCollection



Dependent Mandatory Key: References HP_ProcessorCollection

10.3 HP_LogicalMemberOfProcessorCollection

HP_LogicalMemberOfProcessorCollection extends the class CIM_MemberOfCollection in ways that are specific to HP processor implementations. Implementations shall adhere to the requirements defined in HP WBEM TC P00113, HP Consolidated Status profile for the class CIM_MemberOfCollection as well as additional requirements defined in this section.

Table 6 – Class: HP_LogicalMemberOfProcessorCollection

Properties Requirement Notes Collection Mandatory Key: References HP_ProcessorCollection

Member Mandatory Key: References HP_ProcessorCore

10.4 HP_PhysicalMemberOfProcessorCollection

HP_PhysicalMemberOfProcessorCollection extends the class CIM_MemberOfCollection in ways that are specific to HP processor implementations. Implementations shall adhere to the requirements defined in HP WBEM TC P00113, HP Consolidated Status profile for the class CIM_MemberOfCollection as well as additional requirements defined in this section.

16 Version 1.0.0

Table 7 – Class: HP_PhysicalMemberOfProcessorCollection

Properties Requirement Notes Collection Mandatory Key: References HP_ProcessorCollection

Member Mandatory Key: References HP_ProcessorChip







RegisteredName Mandatory “HP CPU Consolidated Status”





None




None

Version 1.0.0 17

ANNEX A (normative)

Change Log


0.1 3/15/06 Initial Draft 1.0 7/27/06 Changes from Brady Evans. 1.0 8/2/06 Changes from 8/1/06 WBEM TC review; section 7.1 allow both types of collections.

18 Version 1.0.0


Acknowledgments

Version 1.0.0 19



CR

Number Date Title


20 Version 1.0.0

Bibliography


HP WBEM TC

Document Number: P00108

Date: 4/18/07

Version: 1.0.0

HP CPU Physical Asset Profile




2 Version 1.0.0

Contents

Foreword ....................................................................................................................................................... 5 Introduction.................................................................................................................................................... 6 1 Scope .................................................................................................................................................... 7 2 Normative References........................................................................................................................... 7

2.1 Approved References ................................................................................................................. 7 2.2 References Under Development ................................................................................................ 7 2.3 Other References........................................................................................................................ 7

3 Terms and Definitions ........................................................................................................................... 7 4 Symbols and Abbreviated Terms .......................................................................................................... 8 5 Synopsis ................................................................................................................................................ 9 6 Description .......................................................................................................................................... 10 7 Implementation Requirements ............................................................................................................ 11

7.1 HP_ProcessorChip ................................................................................................................... 11 7.2 HP_PhysicalCacheMemory (Optional) ..................................................................................... 11 7.3 HP_RealizesProcessor ............................................................................................................. 11 7.4 HP_RealizesProcessorCache (Conditional) ............................................................................. 11

8 Methods............................................................................................................................................... 11 8.1 Profile Conventions for Operations ........................................................................................... 11 8.2 HP_ProcessorChip ................................................................................................................... 12 8.3 HP_PhysicalCacheMemory (Optional) ..................................................................................... 12


10 CIM Elements ...................................................................................................................................... 15 10.1 HP_ProcessorChip ................................................................................................................... 15 10.2 HP_RegisteredProfile ............................................................................................................... 15 10.3 HP_SystemPhysicalProcessor ................................................................................................. 15


Version 1.0.0 3

Figures

Figure 1 – HP CPU Physical Asset Profile: Class Diagram ........................................................................ 10 Figure 2 – HP CPU Physical Asset Profile: Inheritance Hierarchy ............................................................. 11 Figure 3 – HP CPU Physical Asset Profile: Object Diagram ...................................................................... 13 Figure 4 – HP CPU Physical Asset Profile: Object Diagram with External Cache ..................................... 14

4 Version 1.0.0

Tables

Table 1 – Related Profiles ............................................................................................................................. 9 Table 2 – Operations: HP_ProcessorChip .................................................................................................. 12 Table 3 – Operations: HP_PhysicalCacheMemory .................................................................................... 12 Table 4 – CIM Elements – HP CPU Physical Asset Profile ........................................................................ 15 Table 5 – Class: HP_ProcessorChip .......................................................................................................... 15 Table 6 – Class: HP_RegisteredProfile ...................................................................................................... 15 Table 7 – Class: HP_SystemPhysicalProcessor ........................................................................................ 16 Table 8 – Durable Names generated by this Profile ................................................................................... 16 Table 9 – Correlatable IDs generated by this Profile .................................................................................. 16

Version 1.0.0 5

Foreword

The HP CPU Physical Asset Profile P00108 was prepared by the HP WBEM TC.

6 Version 1.0.0

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 and physical CPUs on HP systems. 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.

Version 1.0.0 7

1 Scope

The HP CPU Physical Asset profile extends the management capability of referencing profiles by adding the capability to represent physical CPUs on HP systems.








DMTF DSP1011, Physical Asset Profile

HP WBEM TC P00106, HP CPU Profile

HP WBEM TC P00107, HP CPU Consolidated Status profile



2.3 Other References

ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards – Downloadable from http://isotc.iso.org/livelink/livelink.exe?func=ll&objId=4230456&objAction=browse&sort=subtype








8 Version 1.0.0












None.

Version 1.0.0 9

5 Synopsis

Profile Name: HP CPU Physical Asset Profile

Version: 1.0.0



Central Class: HP_ProcessorChip


Extends: DMTF DSP1011, Physical Asset Profile 1.0.0

The HP CPU Physical Asset profile extends DMTF DSP1011 to add physical CPU characteristics that are specific to HP systems.


Profile Name Organization Version Relationship Behavior P00100 – HP Profile Registration Profile


P00106 – HP CPU Profile HP WBEM TC 1.0.0 Mandatory DSP1011 – Physical Asset Profile

DMTF 1.0.0 Extends

P00107 – HP CPU Consolidated Status profile


10 Version 1.0.0


6 Description




See HP CPU Consolidated Status profile

1

0..1

HP_ElementConformsToProfile (see HP Profile Registration

profile)

Chip

(see DMTF Physical Asset

Profile)


(see HP Base Server Physical Asset profile)


1..*

HP_ProcessorChip


ProcessorChipRevision

1 *


* HP_Processor


HP_CacheMemory


*

CIM_PhysicalMemory

(see DMTF Physical

Asset Profile)

HP_RealizesProcessorCache 1

HP_PhysicalCacheMemory

Figure 1 – HP CPU Physical Asset Profile: Class Diagram

CIM_Realizes CIM_Container

see DMTF Physical Asset profile


HP_RealizesProcessorCach e


Version 1.0.0 11

Figure 2 – HP CPU Physical Asset Profile: Inheritance Hierarchy

HP Processor Chips are represented in the implementation namespace as instances of HP_ProcessorChip. An implementation can optionally implement the physical asset elements of the CPU by associating the appropriate instances of HP_Processor to an instance of HP_ProcessorChip via the HP_RealizesProcessor association class. Both HP_ProcessorChip and HP_RealizesProcessor are described in this profile.

An implementation can also optionally implement the physical asset elements of the CPU external cache by associating the appropriate instances of HP_CacheMemory to an instance of HP_PhysicalCacheMemory via the HP_RealizesProcessorCache association class. Both HP_PhysicalCacheMemory and HP_RealizesProcessorCache are described in this profile.



7.1 HP_ProcessorChip

There shall be one instance of HP_ProcessorChip for each physical processor in the system regardless of the number of cores and/or threads within the processor chip.

7.1.1 HP_ProcessorChip.ProcessorChipRevision (Optional)

This property is the chip revision of the processor. This shall be the processor stepping or hardware revision level.

7.2 HP_PhysicalCacheMemory (Optional)

HP_PhysicalCacheMemory shall be instantiated for each instance of cache memory used by an instance of HP_Processor or HP_ProcessorCore (refer to the HP WBEM TC P00106, HP CPU Profile for more information) only if the cache resides external of the CPU.

7.3 HP_RealizesProcessor

There shall be one instance of HP_RealizesProcessor instantiated for each instance of HP_Processor. This class associates instances of HP_Processor (refer to the HP WBEM TC P00106, HP CPU Profile for more information) with a corresponding instance of HP_ProcessorChip.

7.4 HP_RealizesProcessorCache (Conditional)

This class associates instances of HP_CacheMemory with corresponding instances of HP_PhysicalCacheMemory. This class shall be instantiated when the optional class HP_PhysicalCacheMemory is instantiated.

8 Methods

None.


Support for operations for each profile class (including associations) is specified in the following sub- clauses. Each sub-clause includes either a statement “All operations are supported as described by

12 Version 1.0.0

DSP200 v1.2” or a table listing all the operations that are Unspecified by this profile or where the profile requires behavior other that described by DSP200.


• GetInstance

• Associators

• AssociatorNames

• References

• ReferenceNames






Table 2 – Operations: HP_ProcessorChip

Operation Requirement Messages GetInstance Mandatory None Associators Unspecified None AssociatorNames Unspecified None References Unspecified None ReferenceNames Unspecified None EnumerateInstances Unspecified None EnumerateInstanceNames Unspecified None

8.3 HP_PhysicalCacheMemory (Optional)


Table 3 – Operations: HP_PhysicalCacheMemory


Version 1.0.0 13

9 Use Cases

9.1 Object Diagrams

Figure 3 below represents a possible instantiation of the HP CPU Physical Asset Profile containing two physical processor chips each realizing an instance of the HP_Processor class. The HP_SystemPhysicalProcessor aggregation association class will associate the processor chip instances to the computer system chassis instance.


(see HP Base Server Physical Asset Profile)


chip1: HP_ProcessorChip chip2: HP_ProcessorChip

HP_RealizesProcessor HP_RealizesProcessor

proc1: HP_Processor proc1: HP_Processor

(see HP CPU Profile) (see HP CPU Profile)

Figure 3 – HP CPU Physical Asset Profile: Object Diagram

Figure 4 below represents a possible instantiation of the HP CPU Physical Asset Profile containing one physical processor chip also realizing an instance of the HP_Processor class. The HP_SystemPhysicalProcessor aggregation association class will associate the processor chip instance to the computer system chassis instance. This figure also models an external cache represented by an instance of HP_PhysicalCacheMemory.

14 Version 1.0.0







proc1: HP_Processor


HP_CacheMemory

(see HP CPU Profile) HP_RealizesProcessorCache

pcache1:

HP_PhysicalMemoryCache

Figure 4 – HP CPU Physical Asset Profile: Object Diagram with External Cache

Version 1.0.0 15

10 CIM Elements

The implementation requirements for the classes properties described in this section are described in the “Implementation Requirements” section (see section 10).

Table 4 – CIM Elements – HP CPU Physical Asset Profile


HP_ProcessorChip Mandatory See Section 7.1 and 10.1 HP_RegisteredProfile Mandatory See section 10.2 HP_RealizesProcessor Mandatory See section 7.3 HP_PhysicalCacheMemory Optional See section 7.2 HP_RealizesProcessorCache Conditional See section 7.4 HP_SystemPhysicalProcessor Mandatory See section 10.3

Indications None defined


HP_ProccessorChip is used to represent a physical processor chip in a managed system.

Table 5 – Class: HP_ProcessorChip

Properties Requirement Notes ProcessorChipRevision Optional See section 7.1.1


The implementation shall implement an instance of the HP_RegisteredProfile in the Interop namespace with the values specified.


Properties Requirement Notes RegisteredOrganization Mandatory Other (1) OtherRegisteredOrganization Mandatory “HP WBEM TC” RegisteredName Mandatory “HP CPU Physical Asset” RegisteredVersion Mandatory “1.0.0”

10.3 HP_SystemPhysicalProcessor

HP_SystemPhysicalProccessor is used to represent the association between HP_ComputerSystemChassis and HP_ProccesorChip.

16 Version 1.0.0

Table 7 – Class: HP_SystemPhysicalProcessor

Properties Requirement Notes GroupComponent Mandatory REF:HP_ComputerSystemChassis PartComponent Mandatory REF:HP_ProcessorChip



Class

Durable Name(s)

Source ID

Information

Circumstances for

Change None


Class

Correlatable ID(s)


Circumstances for

Change None

Version 1.0.0 17

ANNEX A (normative)

Change Log

Version Date Description 0.1 3/15/06 Initial Draft 1.0 7/11/06 Updates based on HP WBEM TC review on 7/10/06. 1.0 7/27/06 Updates based on Brady Evans’s comments. 1.0 4/18/07 Figure 1 updated to match mof for HP_ProcessorChip

18 Version 1.0.0


Acknowledgments

Version 1.0.0 19



CR Number

Date

Title


20 Version 1.0.0

Bibliography



Date: 12/19/08

Version: 1.1.0

HP Record Log Profile





2 Version 1.1.0

Contents




7.1 HP_CommonRecordLog ........................................................................................................... 12 7.2 HP_CommonLogEntry .............................................................................................................. 12 7.3 Indication: HP_CommonRecordLogIndication (Optional) ......................................................... 15

8 Methods ............................................................................................................................................... 16 8.1 Method: HP_CommonRecordLog.ClearLog() .......................................................................... 16 8.2 Method: HP_CommonRecordLog.RequestStateChange()....................................................... 16 8.3 Method: HP_CommonRecordLog.RepairAll() (Conditional) ..................................................... 16 8.4 Method: HP_CommonLogEntry.Repair() (Conditional) ............................................................ 16 8.5 Profile Conventions for Operations ........................................................................................... 17 8.6 HP_CommonRecordLog ........................................................................................................... 17 8.7 HP_CommonLogEntry .............................................................................................................. 17 8.8 HP_EnabledElementCapabilities .............................................................................................. 17

9 Use Cases ........................................................................................................................................... 18 9.1 Object Diagrams ....................................................................................................................... 18 9.2 Identify the Logs by Name ........................................................................................................ 19 9.3 Actions based on HP_CommonRecordLog.LogPercentFull..................................................... 19 9.4 Actions based on HP_CommonRecordLog.LastLogClearedTime ........................................... 19 9.5 HP_CommonRecordLog.LogBackUpDays ............................................................................... 19 9.6 Browse through the Log Records of the Log ............................................................................ 19 9.7 Sort the Log Record Based on the CreationTimestamp of the Log Entry ................................ 19 9.8 Delete the Log Entry ................................................................................................................. 19 9.9 Actions based on HP_CommonLogEntry.Actionable ............................................................... 20 9.10 HP_CommonLogEntry.ReportingEntity .................................................................................... 20 9.11 Actions based on HP_CommonLogEntry.ImpactedDomain ..................................................... 20 9.12 Clear the Log ............................................................................................................................ 20 9.13 Determine if new entries have been added .............................................................................. 20 9.14 Representing soft copy and backup copy as RecordLog ......................................................... 21

10 CIM Elements ...................................................................................................................................... 23 10.1 HP_LogManagesRecord .......................................................................................................... 23 10.2 HP_CommonLogEntry .............................................................................................................. 23 10.3 HP_CommonRecordLog ........................................................................................................... 24 10.4 HP_UseOfLog ........................................................................................................................... 25 10.5 HP_RegisteredProfile ............................................................................................................... 25 10.6 HP_CommonRecordLogIndication (Optional) .......................................................................... 25



Version 1.1.0 3

Figures

Figure 1 – Record Log Profile: Class Diagram ............................................................................................. 9 Figure 2 – Record Log Profile: Indication Class Diagram ............................................................................. 9 Figure 3 – Record Log Profile: Object Diagram .......................................................................................... 18 Figure 4 – Record Log Profile: Indication Object Diagram ......................................................................... 18

Tables

Table 1 – Related Profiles ............................................................................................................................. 8 Table 2 – HP_CommonRecordLog.RepairAll() Method Return Values ...................................................... 16 Table 3 – HP_CommonLogEntry.Repair() Method Return Values ............................................................. 17 Table 4 – CIM Elements – HP Record Log Profile ..................................................................................... 23 Table 5 – Class – HP_LogManagesRecord ................................................................................................ 23 Table 6 – Class – HP_CommonLogEntry ................................................................................................... 24 Table 7 – Class – HP_CommonRecordLog ................................................................................................ 25 Table 8 – Class – HP_UseOfLog ................................................................................................................ 25 Table 9 – Class – HP_RegisteredProfile .................................................................................................... 25 Table 10 – Durable Names generated by this Profile ................................................................................. 26 Table 11 – Correlatable IDs generated by this Profile ................................................................................ 27


4 Version 1.1.0

Foreword

The HP Record Log Profile P00109 was prepared by the HP WBEM TC.


Version 1.1.0 5

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 Logs and their included Records in HP systems. 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.0

1 Scope The HP Record Log profile extends the management capability of referencing profiles by adding the capability to represent the Record Log in HP specific ways.






DMTF DSP1010, Record Log Profile












Version 1.1.0 7











None.


8 Version 1.1.0

5 Synopsis Profile Name: HP Record Log Profile

Version: 1.1.0



Central Class: HP_CommonRecordLog


Extends: DMTF DSP1010, Record Log Profile 1.0

The HP Record Log Profile extends DMTF DSP1010 to add Record Log characteristics that are specific to HP systems.




HP WBEM TC 1.0 Mandatory

P00002 – Hardware Alert Indication

HP WBEM TC 1.10 Optional

DSP1010 – Record Log Profile DMTF 1.0 Mandatory


Version 1.1.0 9

6 Description

LogEntry

(see DMTF Record Log Profile)

RecordLog

(see DMTF Record Log Profile)

HP_CommonRecordLog

HP_CommonLogEntry




profile)

1..*

0..1

*

ManagedSystemElement


HP_UseOfLog

1..*

1..*

1

HP_LogManagesRecord

Log RecordForLog

Figure 1 – Record Log Profile: Class Diagram

HP_CommonRecordLogIndication

HP_AlertIndication

Figure 2 – Record Log Profile: Indication Class Diagram

The HP Record Log profile extends the DMTF Record Log profile defined in DSP1010 to add the HP capabilities of reporting the log information that can be consumed by HP specific clients including HP SIM and the HP Service Tools..

Figure 1 shows the class diagram for the HP Record Log profile.

A relationship between a record log (HP_CommonRecordLog) and a managed system element is represented by the HP_UseOfLog class. For hardware based logs, this managed system element may be the HP_ComputerSystem central class. For software based logs, this may be some other managed system element.

Each log entry (HP_CommonLogEntry) contained in the record log (HP_CommonRecordLog) shall be represented by an aggregation association via the LogManagesRecord class.


10 Version 1.1.0

Also described in this document is the HP_CommonRecordLogIndication for alerting a management client when log entries have been added/deleted/updated.

This profile describes the initial set of log objects for the WBEM Providers for HP Server and Storage implementations. The objects provide specific information for the logs that will be used by the Multi-OS WBEM Indication (MOWI) analyzer as well as indications to notify the analyzer when new entries are added to the logs or entries are significantly modified. This analyzer will retrieve the entries in the individual logs and perform analysis to determine whether a Service Incident needs to be generated. The indications are intended to be used for notification to the analyzer of entries that should be retrieved (or retrieved in the case of modified entries) and analyzed. The severity of the indication determines how soon the entries should be retrieved.

Record Log providers that are intended to be used by the MOWI analyzer are expected to create subclasses of the HP_CommonLogEntry and HP_CommonRecordLog, as well as subclasses of the CIM classes described in this profile for their specific implementation and to be compliant with this profile.


Version 1.1.0 11

7 Implementation Requirements TimeOfLastChange property must be updated whenever records are added, deleted or modified in the RecordLog. If the log supports the UpdateTimestamp property (i.e., the log entries keep both the creation and update time stamps), modified records must update the UpdateTimestamp if they are modified such that the MOWI analyzer must re-consider the records in its analysis.

Support of the HP_CommonRecordLogIndication class and the related subscription to indications is optional. These indications are sent to inform the client of new entries added to the log or when entries are significantly modified such that they should be retrieved and re-analyzed. If the indication is supported, the provider will determine the severity of the indications generated when entries are added or modified, based on its determination of the severity of the entry and how critical it is for the MOWI analyzer to consider the entry. The provider will support subscriptions as well as generation of the indications, as appropriate. The indication contains the keys for the RecordLog and the keys for the records, to allow a client to determine which log is sending the indication and which entries have been added or modified.

Properties in the schema that have ModelCorrespondence to other properties in other classes are expected to be filled in by the indication provider by one of the following methods:

1) Retrieve the property directly from instance provider for the class for the instance that is related to this indication

2) Use the exact same mechanisms used by the instance provider for the class that is related to this indication to retrieve the information directly from the hardware and format it.

If there is no instance provider for the class, the indication provider can use whatever mechanism necessary to retrieve the information directly from the hardware. However, when an instance provider becomes available, the indication provider must work with the instance provider to coordinate the mechanisms used to retrieve the information or modify the instance provider to retrieve the information from the instance provider. This coordination should occur prior to actual ship of the instance provider.

There are no requirements on the persistence of Indications, once they are sent to the CIMOM for distribution to the clients with matching subscriptions. It is the responsibility of the client to archive the indications of interest.

The 3 Variable property arrays, VariableNames[], VariableTypes[] and VariableValues[] are used by the provider to supply error specific information. For example, if an error was logged concerning a SCSI error, the Variable property arrays could be used to contain the SCSI Sense key, Sense code and Sense qualifier in the following manner (example is for an illegal request 0x05, Invalid field in CDB 0x24, 0x00):

VariableNames[0] = “SCSI Sense Key”

VariableNames[1] = “SCSI Sense Code”

VariableNames[2] = “SCSI Sense Qualifier”

VariableTypes[0] = uint8



VariableValues[0] = 0x05




12 Version 1.1.0

The other option to using the Variable Arrays would be to subclass off HP_CommonLogEntry, if the error specific information is decided to be of enough general interest to warrant a subclass.

Providers for components that do not have unique serial numbers must provide both the SerialNumber and ProductID if they expect to uniquely identify the component. This applies to both the system reporting the indication and the hardware associated with the indication.

7.1 HP_CommonRecordLog


7.1.1 HP_CommonRecordLog.TimeOfLastChange

This property shall be supported by containing the date and time of the most recent add / delete / modification of the log entries. This is intended for log entry changes and not changes of the log itself. If the log supports both the CreationTimestamp and UpdateTimestamp, then this property shall reflect the time of the latest event creation (in CreationTimestamp) or update (in UpdateTimestamp). This property is implementation specific as to whether the timestamps are changed for any event modification or just for “significant” events.

The TimeOfLastStateChange property (see the DMTF DSP1010, Record Log Profile) is used to track changes of the enabled state of the log.

7.1.2 HP_CommonRecordLog.Caption

This property shall be supported by providing a short string describing the record log.

7.1.3 HP_CommonRecordLog.Description

This property shall be supported by providing a string describing the record log.

7.1.4 HP_CommonRecordLog.LogPercentFull (Optional)

LogPercentFull is the amount of log space consumed in percentage.

7.1.5 HP_CommonRecordLog.LastLogClearedTime (Optional)

LastLogClearedTime is the date and time, when the log was cleared recently.

7.1.6 HP_CommonRecordLog.LogBackUpDays (Optional)

LogBackUpDays is the number of days the backed up log will be saved.

7.2 HP_CommonLogEntry


7.2.1 HP_CommonLogEntry.Caption

This property shall be supported by providing a short string describing the log entry.

7.2.2 HP_CommonLogEntry.Description

This property shall be supported by providing a string describing the log entry.


Version 1.1.0 13

7.2.3 HP_CommonLogEntry.DeviceManufacturer (Conditional)

This property shall be conditionally supported when the device manufacturer is known and there is a device reporting the log entry event.

7.2.4 HP_CommonLogEntry.DeviceModel (Conditional)

This property shall be conditionally supported when the device model is known and there is a device reporting the log entry event.

7.2.5 HP_CommonLogEntry.DeviceProductID (Conditional)

This property shall be conditionally supported when the device product id is known and there is a device reporting the log entry event.

7.2.6 HP_CommonLogEntry.DeviceSerialNumber (Conditional)

This property shall be conditionally supported when the device serial number is known and there is a device reporting the log entry event.

7.2.7 HP_CommonLogEntry.DeviceType (Conditional)

This property shall be conditionally supported when the device type is known and there is a device reporting the log entry event.

7.2.8 HP_CommonLogEntry.DeviceVersion (Conditional)

This property shall be conditionally supported when the device version is known and there is a device reporting the log entry event.

7.2.9 HP_CommonLogEntry.LoggerType

This property shall be supported by providing logger type of the log entry.

7.2.10 HP_CommonLogEntry.MajorClass

This property shall be supported by providing major class enumeration of the log entry.

7.2.11 HP_CommonLogEntry.MinorClass

This property shall be supported by providing minor class enumeration of the log entry.

7.2.12 HP_CommonLogEntry.OccurrenceCount (Conditional)

This property shall be conditionally supported when the log is capable of incrementing an occurrence count for a logged event when the exact same event is logged within a certain amount of time. If the occurrence count is incremented; the UpdateTimestamp will be updated to the time of the new occurrence.

7.2.13 HP_CommonLogEntry.OSType

This property shall be supported by providing the OS type that logged the error or the OS type of the provider exposing the log.

7.2.14 HP_CommonLogEntry.OtherDeviceType (Conditional)

This property shall be supported conditionally when the DeviceType property is other and the device type is known.


14 Version 1.1.0

7.2.15 HP_CommonLogEntry.RawData

This property shall be supported by providing raw binary data of the log entry suitable for programmatic consumption.

7.2.16 HP_CommonLogEntry.RecordDataType

This property shall be supported by providing the format of the data returned in the RecordData property.

7.2.17 HP_CommonLogEntry.ServerHardwareArchitecture (Conditional)

This property shall be conditionally supported when the log entry is a server log entry.

7.2.18 HP_CommonLogEntry.Severity (Conditional)

This property shall be conditionally supported when the log supports reporting the severity of the event causing the log entry.

7.2.19 HP_CommonLogEntry.StorageLogType (Conditional)

This property shall be conditionally supported when the log is a storage centric log.

7.2.20 HP_CommonLogEntry.SystemModel

This property shall be supported by providing model of the system where the error was logged.

7.2.21 HP_CommonLogEntry.SystemName

This property shall be supported by providing name of the system where the error was logged.

7.2.22 HP_CommonLogEntry.SystemSerialNumber

This property shall be supported by providing serial number of the system where the error was logged.

7.2.23 HP_CommonLogEntry.UpdateTimestamp (Conditional)

This property shall be conditionally supported when the log supports both a CreationTimestamp and a separate UpdateTimestamp for when the record was modified. The UpdatedTimestamp may be changed when a record is repaired or when the same event is logged again by incrementing the OccurrenceCount.

7.2.24 HP_CommonLogEntry.VendorID

This property shall be supported by providing vendor id of the system where the error was logged.

7.2.25 HP_CommonLogEntry. Actionable (Optional)

Actionable is an enumerated value indicating whether an action can be taken against this event. Unknown (0), Yes (1), No (2)

7.2.26 HP_CommonLogEntry. ReportingEntity (Optional)

ReportingEntity indicates the reporting source of the entity that logged this event.

7.2.27 HP_CommonLogEntry. ImpactedDomain (Optional)

ImpactedDomain is an enumerated value indicating the domain this event affects. Unknown (0), Cluster (1), Complex (2), Enclosure (3), System (4).


Version 1.1.0 15

7.2.28 HP_CommonLogEntry. RecommendedActions[ ] (Optional)

RecommendedActions are the actions to be taken to resolve the cause of the event.

7.2.29 HP_CommonLogEntry. ProbableCauseDescriptions[ ] (Optional)

ProbableCauseDescriptions are the probable causes of the situation, which resulted in this event.

7.3 Indication: HP_CommonRecordLogIndication (Optional)

This section details the requirements related to the arrangement of indication instances and properties of the indication instances for implementations of this profile.

7.3.1 HP_CommonRecordLogIndication.PerceivedSeverity

This property shall be supported by containing the Severity of the entry from the perspective of the log provider.

7.3.2 HP_CommonRecordLogIndication.RecordLogInstanceID

This property shall be supported by containing the InstanceID of the record log generating the indication.

7.3.3 HP_CommonRecordLogIndication.LogEntryInstanceIDs

This property shall be supported by containing the array InstanceIDs of the log record or records generating the indication.

7.3.4 HP_CommonRecordLogIndication.IndicationIdentifier

This property shall be supported by containing the unique indication identifier of the specific event causing the indication.

7.3.5 HP_CommonRecordLogIndication.IndicationTime

This property shall be supported by containing the date and time of when the indication was generated.


16 Version 1.1.0

8 Methods

8.1 Method: HP_CommonRecordLog.ClearLog() Implementations shall adhere to the requirements defined in DSP1010 for the method CIM_RecordLog.ClearLog() as inherited by HP_CommonRecordLog.

8.2 Method: HP_CommonRecordLog.RequestStateChange() Implementations shall adhere to the requirements defined in DSP1010 for the method CIM_RecordLog.RequestStateChange() as inherited by HP_CommonRecordLog.

In some implementations, a log can freeze itself when it is full, using the “Enabled But Offline” state. In this case, if a user requests a state change to “Enabled”, the method should return “Failed”.

8.3 Method: HP_CommonRecordLog.RepairAll() (Conditional)

The HP_CommonRecordLog.RepairAll() method is conditionally supported on logs that support the Severity property.

HP_CommonRecordLog.RepairAll() method requests to mark as OK all non-OK and non-Informational log entries for the instance of HP_CommonRecordLog. In case of success, all the instances of HP_CommonLogEntry associated to the instance of of HP_CommonRecordLog shall be marked as repaired. Log records with a severity of Degraded/warning (4) or greater will have their Severity changed to Repaired (3).

HP_CommonRecordLog.RepairAll() return values shall be as specified in the table below where the method execution behavior matches the return code description. No parameters and messages are specified for this method. If the RepairAll method and the UpdateTimestamp and Severity properties are supported, then the UpdateTimestamp shall reflect the time of the record’s modification.

Table 2 – HP_CommonRecordLog.RepairAll() Method Return Values

Value Description

0 Request was successfully executed 1 Method is not supported in the implementation 2 Error occurred 3 Timeout 4 Failed

8.4 Method: HP_CommonLogEntry.Repair() (Conditional)

The HP_CommonLogEntry.Repair() method is conditionally supported on logs that support the Severity property.

HP_CommonLogEntry.Repair() method requests to mark as OK the non-OK and non-Informational log entry for the instance of HP_CommonLogEntry. Log records with a severity of Degraded/warning (4) or greater will have their Severity changed to Repaired (3).

HP_CommonLogEntry.Repair() return values shall be as specified in the table below where the method execution behavior matches the return code description. No parameters and messages are specified for this method. If the Repair method and the UpdateTimestamp and Severity properties are supported, then the UpdateTimestamp shall reflect the time of the record’s modification.


Version 1.1.0 17

Table 3 – HP_CommonLogEntry.Repair() Method Return Values

Value Description

0 Request was successfully executed 1 Method is not supported in the implementation 2 Error occurred 3 Timeout 4 Failed




• GetInstance

• Associators

• AssociatorNames

• References

• ReferenceNames




8.6 HP_CommonRecordLog

All other operations are supported as defined in DSP0200 v1.2.

8.7 HP_CommonLogEntry


8.8 HP_EnabledElementCapabilities



18 Version 1.1.0

9 Use Cases

9.1 Object Diagrams

log1: HP_CommonRecordLog

rec1: HP_CommonLogEntry

InstanceID: HPQ: log1.rec1CreationTimeStamp: 2006.06.01 14:34RecordFormat: *string DeviceID*uint8 Record*RecordData: *10.0.32*1


HP_UseOfLog

HP_LogManagesRecord

InstanceID: HPQ: log1MaxNumberOfRecords: 64CurrentNumberOfRecords:2EnabledState: Enabled (2)RequestedState: Enabled (2)EnabledDefault: Enabled (2)Name: log1TimeOfLastChange: 2006.06.01 14:34

rec2: HP_CommonLogEntry

InstanceID: HPQ: log1.rec2CreationTimeStamp: 2006.05.31 04:56RecordFormat: *string DeviceID*uint8 Record*RecordData: *10.0.21*2

HP_LogManagesRecord


RegisteredName: Base System


RegisteredName: Record Log


RegisteredName: HP Record Log



HP_ExtendsProfile

Figure 3 – Record Log Profile: Object Diagram

The above picture shows an instance of HP_CommonRecordLog with an instance id of “HP Hardware Log” containing two instances of the HP_CommonLogEntry with instance id’s of “HPQ: log1.rec 1” and “HPQ: log1.rec 2”. Each log entry is associated to the record log by an instance of the HP_LogManagesRecord aggregation association. The log is associated to the HP_ComputerSystem instance “System1” via the HP_UseOfLog association.


IndicationIdentifier: indication1IndicationTime: 2006.06.01 14:34LogEntryInstanceID[0] : "HPQ: log1.rec1"PerceivedSeverity: CriticalRecordLogInstanceID: “HPQ: log1"

Figure 4 – Record Log Profile: Indication Object Diagram

The above figure shows an instance of a Record Log indication. The above indication would be generated when the log entry with the InstanceID of “HPQ: log1.rec1” was written to the log with the InstanceID of “HPQ: log1”.


Version 1.1.0 19

9.2 Identify the Logs by Name

Select the HP_CommonRecordLog instances which Name property corresponds to the given name.

9.3 Actions based on HP_CommonRecordLog.LogPercentFull

Management application can check the LogPercentFull and determine when to clear the log. If 85% of the log is full and no new events were received within next two minutes, then the management application clears the log. When the log is over 95% full, then the management application clears the log.

9.4 Actions based on HP_CommonRecordLog.LastLogClearedTime

Logs can be cleared from various places, like Management Processor pages, Management Application or manually by a user from a telnet session etc. Based on the time when the log was cleared, applications can synchronize with the latest state.

9.5 HP_CommonRecordLog.LogBackUpDays

If a ClearLog() method also saves a soft copy of the log, LogBackupDays may be used to represent the time a previously saved soft copy is retained. The most recent soft copy is saved indefinitely.

9.6 Browse through the Log Records of the Log

Iterate through all the instances of HP_CommonLogEntry that are associated through CIM_LogManagesRecord to the given instance of HP_CommonRecordLog and sort them based on the InstanceID.

Another option. Find the HP_CommonRecordLog of interest and save the InstanceID. Perform a query for HP_CommonLogEntry instances, using a filter with the LogInstanceID previously saved, to retrieve all the instances of HP_CommonLogEntry managed by the RecordLog identified by the LogInstanceID.

If it is possible that there are a large number of instances that can be returned, based on the HP_CommonRecordLog.MaxNumberOfRecords or CurrentNumberOfRecords, find the HP_CommonRecordLog of interest and save the InstanceID. Perform a query, using a filter with the LogInstanceID previously saved and a range of CreationTimeStamp values based on HP_CommonRecordLog.TimeOfLastChange, to retrieve a subset of the instances of HP_CommonLogEntry managed by the RecordLog identified by the LogInstanceID.

9.7 Sort the Log Record Based on the CreationTimestamp of the Log Entry

Iterate through all the instances of HP_CommonLogEntry that are associated through CIM_LogManagesRecord to the given instance of HP_CommonRecordLog representing the log record. Sort the instances of HP_CommonLogEntry based on CreationTimestamp property value in LIFO order.

9.8 Delete the Log Entry

Select the instance of HP_CommonLogEntry that represents the log entry. Execute DeleteInstance operation on the selected instance of HP_CommonLogEntry. If the instrumentation does not support individual deletion, the DeleteInstance operation will return a value indicating Not Supported.


20 Version 1.1.0

9.9 Actions based on HP_CommonLogEntry.Actionable

In modular systems, management application can provide an option for repairing an event or not based on the Actionable property value.

9.10 HP_CommonLogEntry.ReportingEntity

In a modular system, System Firmware on a particular partition could log an event related to some component in that partition. This property will reflect the details about the System Firmware, which is the actual entity that logged this event.

9.11 Actions based on HP_CommonLogEntry.ImpactedDomain

In modular systems, there will be one SEL (System Event Log) log for the entire Complex. There can be multiple partitions in a Complex. Each partition is a separate system. Events that do not belong to the local partition will have this property reflect “Complex (2)” and the events that are local to the partition will reflect “System (4)”. ImpactedDomain property value can be used by management application to decide on the actions to be taken.

9.12 Clear the Log

For the given instance HP_CommonRecordLog execute ClearLog() method. The implementation may log an event indicating the log was cleared by the provider.

If a ClearLog() method also saves a soft copy of the log, LogBackupDays may be used to represent the time a previously saved soft copy is retained. The most recent soft copy is saved indefinitely.

9.13 Determine if new entries have been added

Subscribe to the LogRecordIndication for the log of interest. When an indication is received, new entries have been added or modified. Repairing an event may also cause the event to be modified. A client can subscribe to receive indications via the standard WBEM subscription mechanisms and can use any properties that are part of the HP_CommonLogEntryIndication class in the filter portion of the Query to specify the set of indications it will receive. For example, if the client only wants to receive indications when the PerceivedSeverity is Major (5) or Critical (6) and the Query Language was WQL, they could set the Query property to "SELECT * FROM HP_CommonLogEntryIndication WHERE PerceivedSeverity > 5".

The general sequence of events for the client, CIMOM and provider for subscribing to, generating, receiving and processing an indication would be as follows:

Client creates a subscription, consisting of a filter and handler instances and subscription association between them

Client registers subscription with the CIMOM

Provider determines an indication needs to be sent when records are added or modified

Provider creates Indication instance

Provider fills in appropriate properties

Provider retrieves properties from device instance or log entries

Provider retrieves system properties from appropriate system class or log entries

Provider sends indication to CIMOM


Version 1.1.0 21

CIMOM matches indication information with filters and subscription

If there is a match

CIMOM sets properties to values defined by SET command in filter

CIMOM forwards indication to handler

Client receives indication via handler

Client processes indication

Client can call getInstance() using the information in the RecordLogInstanceID to find the RecordLog that had the entry instance or instances matching the query criteria.

Client can call getInstance() using the information in LogEntryInstanceIDs property to get instance (or instances) of the records added or modified

The client should save the IDs of the records previously examined and compare the IDs of the instances to differentiate between new and modified records.

Periodically poll the value of HP_CommonRecordLog.TimeOfLastChange and compare against a previously saved value. If the value is new, client queries for LogEntry instances with a CreationTimestamp (and if supported the UpdateTimestamp) newer than the previously saved TimeOfLastChange. As TimeOfLastChange can be modified for deletion or modification of records, the query could return no records.

Since the UpdateTimestamp is updated for modifications to the record, the client should save the IDs of the records previously examined and compare the IDs of the instances to differentiate between new and modified records.

Display Variable arrays

For each element in Variable arrays

Convert VariableValue into a string using VariableType

Display variable element as VariableName : string value

So, if VariableName[0] = “SCSI Sense Key”



The client could display “SCSI Sense Key : 0x02

9.14 Representing soft copy and backup copy as RecordLog

If a ClearLog() method also saves a soft copy of the log, the soft copy and the backup copy may be represented as additional RecordLogs. Figure 5 shows two instances of HP_CommonRecordLog. The active SEL has a Name of “HP Hardware Log”, while the soft copy has a Name of “Copy HP Hardware Log”. The copy contains two instances of the HP_CommonLogEntry. Each log entry is associated to the record log by an instance of the HP_LogManagesRecord aggregation association. The log is associated to the HP_ComputerSystem instance “System1” via the HP_UseOfLog association.


22 Version 1.1.0

*

*

HP_UseOfLog

Log1: HP_CommonRecordLog

Name: “HP Hardware Log”

Log2 : HP_CommonRecordLog

Name: “Copy HP Hardware Log”

System1: HP_ComputerSystem

*

*

HP_UseOfLog

Rec2 : HP_CommonLogRecordCreationTimeStamp:2006.05.31 04:56

Rec1 :HP_CommonLogRecordCreationTimeStamp:2006.05.31 14:34

1

*

HP_LogManagesRecord1

*

HP_LogManagesRecord

Figure 5 – Copy of SEL instance diagram


Version 1.1.0 23

10 CIM Elements Table 4 – CIM Elements – HP Record Log Profile


Classes HP_LogManagesRecord Mandatory See section 10.1

HP_CommonRecordLog Mandatory See section 0

HP_CommonLogEntry Mandatory See section 10.2

HP_RegisteredProfile Mandatory See section 10.5

HP_UseOfLog Mandatory See section 0 Indications

HP_CommonRecordLogIndication Optional See sections 7.3 and 10.6

10.1 HP_LogManagesRecord HP_LogManagesRecord extends the class CIM_LogManagesRecord for use only with HP_CommonRecordLog and HP_CommonLogEntry. Implementations shall adhere to the requirements defined in DSP1010 for the class CIM_LogManagesRecord as well as additional requirements defined in this section.

Table 5 – Class – HP_LogManagesRecord

Properties Requirement Notes Log Mandatory REF:HP_CommonRecordLog

Record Mandatory REF:HP_CommonLogEntry

10.2 HP_CommonLogEntry HP_CommonLogEntry extends the class CIM_LogEntry to model logs records within a log in a way suitable for service tools to use. Implementations shall adhere to the requirements defined in DSP1010 for the class CIM_LogEntry as well as additional requirements defined in this section.


24 Version 1.1.0

Table 6 – Class – HP_CommonLogEntry

Properties Requirement Notes Caption Mandatory See section 7.2.1

Description Mandatory See section 7.2.2

DeviceManufacturer Conditional See section 7.2.3

DeviceModel Conditional See section 7.2.4

DeviceProductID Conditional See section 7.2.5

DeviceSerialNumber Conditional See section 7.2.6

DeviceType Conditional See section 7.2.7

DeviceVersion Conditional See section 7.2.8

LoggerType Mandatory See section 7.2.9

MajorClass Mandatory See section 7.2.10

MinorClass Mandatory See section 7.2.11

OccurrenceCount Conditional See section 7.2.12

OSType Mandatory See section 7.2.13

OtherDeviceType Conditional See section 7.2.14

RawData Mandatory See section 7.2.15

RecordDataType Mandatory See section 7.2.16

ServerHardwareArchitecture Conditional See section 7.2.17

Severity Conditional See section 7.2.18

StorageLogType Conditional See section 7.2.19

SystemModel Mandatory See section 7.2.20

SystemName Mandatory See section 7.2.21

SystemSerialNumber Mandatory See section 7.2.22

UpdateTimestamp Conditional See section 7.2.23

VendorID Mandatory See section 7.2.24

Actionable Optional See section 7.2.245

ReportingEntity Optional See section 7.2.246

ImpactedDomain Optional See section 7.2.247

RecommendedActions[ ] Optional See section 7.2.248

ProbableCauseDescriptions[ ] Optional See section 7.2.249

10.3 HP_CommonRecordLog HP_CommonRecordLog extends the class CIM_RecordLog to model record logs in a way suitable for service tools to use. Implementations shall adhere to the requirements defined in DSP1010 for the class CIM_RecordLog as well as additional requirements defined in this section.


Version 1.1.0 25

Table 7 – Class – HP_CommonRecordLog

Properties Requirement Notes TimeOfLastChange Mandatory See section 7.1.1

Caption Mandatory See section 7.1.2

Description Mandatory See section 7.1.3

LogPercentFull Optional See section 7.1.34

LastLogClearedTime Optional See section 7.1.35

LogBackUpDays Optional See section 7.1.36

10.4 HP_UseOfLog HP_UseOfLog extends the class CIM_UseOfLog for use only with HP_CommonRecordLog and HP_ComputerSystem. Implementations shall adhere to the requirements defined in DSP1010 for the class CIM_UseOfLog as well as additional requirements defined in this section.

Table 8 – Class – HP_UseOfLog

Properties Requirement Notes Antecedent Mandatory REF:HP_CommonRecordLog

Dependent Mandatory REF:HP_ComputerSystem



Table 9 – Class – HP_RegisteredProfile




RegisteredName Mandatory “HP Record Log”

RegisteredVersion Mandatory 1.0

10.6 HP_CommonRecordLogIndication (Optional)

The implementation can optionally implement the HP_CommonRecordLogIndication class to generate indications when log entries are added, deleted, or modified.


26 Version 1.1.0


Class Durable Name(s) Source ID Information Circumstances for Change

HP_CommonRecordLog SystemSerialNumber/ SystemProductID

Serial number (and also the SystemProductID if serial number is not unique) for the system. This is a separate serial number than the one associated with any specific component in the system, such as CPUs, cells, chassis. This serial number is set by manufacturing for the system when it is shipped. It is used by support to identify systems that are under warranty or support contract. The model correspondence for this property is CIM_PhysicalElement.SerialNumber when associated with the instance representing the system.

System board replacement

HP_CommonRecordLog DeviceSerialNumber/ DeviceProductID

The serial number (and also the DeviceProductID if serial number is not unique) of the hardware. This serial number is set by manufacturing for the hardware when it is shipped. It is used by support to identify hardware that is under warrenty or support contract. The model correspondence for this property is CIM_PhysicalElement.SerialNumber when associated with the instance representing the hardware generating the indication.

Device replacement


Version 1.1.0 27




CIM_RecordForLog

InstanceID Identifier of the instance of the Record.

Log Cleared, record deleted.

CIM_Indication IndicationIdentifier Unique identification of this instance of an indication on the system. While the DMTF MOF indicated this ID can be reused or NULL if it is not used in a Correlated Indications array, the intention for this profile is that this property will ALWAYS be set and will ALWAYS be unique on the system. This property will be used to identify this indication in an archive of all indications that have occurred on the system. The format of the property is not important as long as it is unique on the system.

CIM_Indication CorrelatedIndications[] Array of indication identifiers that are related to this indication. The entries in this array can be used to search the indication archive for the related indications by matching them to the entry in the archive with the same IndicationIdentifier value. For example, an event indicating a particular error condition has been fixed, such as a fan


28 Version 1.1.0



failure, would include in this array the IndicationIdentifier for the original indication for the failure.


RecordLogInstanceID Identifier of the instance of the entry in the RecordLog. This can be used to identify the RecordLog with the new entries.


LogRecordInstanceIDs[] Array of identifiers of of the instances of LogRecords. This can be used to identify the new entries in the RecordLog.

HP_CommonRecordLog

DevicePartNumber The part number of the device. It is used by support personnel to know what part to order if it needs to be replaced as a result of the indication. The model correspondence for this property is CIM_PhysicalElement.PartNumber, when associated with the instance representing the hardware generating the indication.

HP_CommonRecordLog

DeviceManufacturer Manufacturer of the hardware as reported by the hardware. It is used to identify hardware that is supported. The model correspondence for this property is CIM_PhysicalElement.Manufacturer, when associated with the instance representing the hardware generating the


Version 1.1.0 29



indication.


30 Version 1.1.0

ANNEX A (normative)

Change Log


0.1 5/15/06 Initial Draft 0.2 6/1/06 Changes suggested by Barb Craig. Added use cases; Durable and Correlatable id’s. 0.3 6/2/06 Added Severity property for CommonLogEntry; minor formatting changes. 0.4 6/9/06 Updated object diagram profile instances.

0.5 6/21/06 Removed the HP_EnabledLogicalElementCapabilities and HP_ElementCapabilities classes (no new information in the HP profile vs. the DMTF profile); Barb Craig’s comments addressed.

0.6 6/23/06 More comments from Barb Craig.

1.0 6/27/06 Changed RepairAll (section 8.3) and Repair (section 8.4) methods to document the Severity value changes based on Steve Marzulla’s comments.

1.0b 7/12/06 Removed references to default sort of LIFO. These were removed from the DMTF Record Log profile as well in version 0.9.3.

1.0c 5/23/07 Added new properties to HP_CommonLogEntry and HP_CommonRecordLog 1.1.0 12/19/08 Change indication to be subclass of HP_AlertIndication. Correct version format


Version 1.1.0 31


Acknowledgments


32 Version 1.1.0



CR

Number Date Title


Version 1.1.0 33

Bibliography


HP Confidential


Date: 08/01/06

Version: 1.0

HP Memory Profile

HP Memory Profile

2 HP Confidential Version 1.0

© Copyright Hewlett-Packard Company 2006

<TBD: HP Legal Stuff here>

HP Memory Profile

Version 1.0 HP Confidential 3

Contents

Foreword ...................................................................................................................................................... 4 Introduction .................................................................................................................................................. 5 1 Scope ......................................................................................................................................................... 6 2 Normative References ............................................................................................................................... 6 3 Terms and Definitions ................................................................................................................................ 6 4 Symbols and Abbreviated Terms ............................................................................................................... 8 5 Synopsis ..................................................................................................................................................... 8 6 Description ................................................................................................................................................ 9 7 Implementation Requirements ................................................................................................................. 10 8 Methods.................................................................................................................................................... 11 9 Use Cases ................................................................................................................................................ 12 10 CIM Elements ......................................................................................................................................... 13 11 Durable Names and Correlatable IDs ................................................................................................... 14 Bibliography .............................................................................................................................................. 18

Figures

Figure 1 – Memory Profile: Class Diagram ................................................................................................... 9 Figure 2 – Memory Profile: Hierarchy Diagram............................................................................................. 9 Figure 3 – HP Memory Profile: Object diagram with two memory modules ............................................... 12

Tables

Table 1 – Related Profiles ............................................................................................................................. 8 Table 2 – Operations: HP_Memory ........................................................................................................... 11 Table 3 – CIM Elements – HP Memory Profile ........................................................................................... 13 Table 4 – Class: HP_Memory ..................................................................................................................... 13 Table 5 – Class: HP_SystemMemory ......................................................................................................... 13 Table 6 – Class: HP_RegisteredProfile ...................................................................................................... 14 Table 7 – Durable Names generated by this Profile ................................................................................... 14 Table 8 – Correlatable IDs generated by this Profile .................................................................................. 14

HP Memory Profile


Foreword

The HP Memory Profile P00110 was prepared by the HP WBEM TC.

HP Memory Profile


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 logical Memory in HP systems (support for physical memory information is optional). 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.

HP Memory Profile


1 Scope The HP Memory profile extends the management capability of referencing profiles by adding the capability to represent the logical Memory in HP specific ways.






DMTF DSP1026, System Memory Profile

HP WBEM TC P00111, HP Memory Physical Asset Profile










HP Memory Profile












None.

5 Synopsis Profile Name: HP Memory Profile

Version: 1.0


HP Memory Profile



Central Class: HP_Memory


Extends: DMTF DSP1026, System Memory Profile 1.0

The HP Memory profile extends DMTF DSP1026 to add Memory characteristics that are specific to HP systems.




DSP1026 – System Memory Profile

DMTF 1.0 Mandatory

P00111 – HP Memory Physical Asset profile

HP WBEM TC 1.0 Optional

6 Description

HP_Memory

HP_RealizesMemoryModule(see HP Memory Physical

Asset Profile)

HP_MemoryModule

(see HP Memory Physical Asset

Profile)




Profile)

1

0..1

1

*

HP_ComputerSystem


1

1

HP_SystemMemory

CIM_Memory

(see DMTF System Memory Profile)

Figure 1 – Memory Profile: Class Diagram

HP Memory Profile


CIM_SystemDevice


HP_SystemMemory

Figure 2 – Memory Profile: Hierarchy Diagram

Figure 1 represents the class diagram for the HP Memory Profile.

The HP_Memory class describes logical aspects of system memory. The physical aspects of system memory is optionally described using the HP_MemoryModule class, defined in the HP Memory Physical Asset Profile.

The relationship between the computer system (HP_ComputerSystem) and logical memory is described using the HP_SystemMemory association class.

Figure 2 represents the association hierarchy of for the HP Memory Profile.


7.1 HP_Memory

There shall be one single instance of HP_Memory per the profile instantiation. This instance shall represent the logical memory in the managed system.

7.1.1 HP_Memory.DeviceID

This property shall be set to the following value: “HPQ:<provider name>:000” where <provider name> is the name of the provider that implements this class.

7.1.2 HP_Memory.ElementName

This property shall be set to the following value: “HP System Memory”

7.2 HP_SystemMemory

There shall be one single instance of HP_SystemMemory per the profile instantiation. HP_SystemMemory represents the association between the HP_ComputerSystem instance and the HP_Memory instance.

HP Memory Profile


8 Methods None.




• GetInstance

• Associators

• AssociatorNames

• References

• ReferenceNames




8.2 HP_Memory


Table 2 – Operations: HP_Memory


HP Memory Profile


9 Use Cases

9.1 Object Diagrams

The following represents a possible instantiation of the HP Memory Profile. In this case, “system1” has two memory modules.

For simplicity the properties have been removed from the classes.

memory1 : HP_Memory

HP_RealizesMemoryModule

mm1 : HP_MemoryModule

system1 : HP_ComputerSystem

mm2 : HP_MemoryModule


HP_SystemMemory

Figure 3 – HP Memory Profile: Object diagram with two memory modules

HP Memory Profile


10 CIM Elements Table 3 – CIM Elements – HP Memory Profile


HP_Memory Mandatory See section 7.1 and 10.1 HP_SystemMemory Mandatory See section 7.2 and 10.2 HP_RegisteredProfile Mandatory See section 10.3


10.1 HP_Memory HP_Memory extends the class CIM_Memory in ways that are specific to HP systems. Implementations shall adhere to the requirements defined in DSP1026 for the class CIM_Memory as well as additional requirements defined in this section. Implementation shall implement an instance of HP_Memory with the values specified.

Table 4 – Class: HP_Memory

Properties Requirement Notes DeviceID Mandatory “HPQ:<provider name>:000” where

<provider name> is the name of the provider that implements this class.

ElementName Mandatory “HP System Memory”

10.2 HP_SystemMemory HP_SystemMemory extends the class CIM_SystemDevice for use only with HP_ComputerSystem and HP_Memory.

Table 5 – Class: HP_SystemMemory

Properties Requirement Notes GroupComponent Mandatory REF:HP_ComputerSystem PartComponent Mandatory REF:HP_Memory




HP Memory Profile


Properties Requirement Notes RegisteredOrganization Mandatory Other (1)


RegisteredName Mandatory “HP Memory”

RegisteredVersion Mandatory “1.0”




None defined




None defined

HP Memory Profile


ANNEX A (normative)

Change Log

Version Date Description 0.1 6/28/06 Initial Draft 0.2 7/26/06 Resolved various typographical errors based on WBEM TC sub-team review 0.3 7/28/06 Updated broken hyperlinks and revised property format 1.0 8/1/06 Updated document version

HP Memory Profile



Acknowledgments

HP Memory Profile




CR

Number Date Title CR00106 7/26/06 Create HP profile for the logical and physical system memory model

HP Memory Profile


Bibliography



Date: 05/25/2012

Version: 2.1.0

HP Memory Physical Asset Profile




2 2.1.0

Contents



3 Terms and Definitions ........................................................................................................................... 8 4 Symbols and Abbreviated Terms .......................................................................................................... 9 5 Synopsis .............................................................................................................................................. 10 6 Description .......................................................................................................................................... 10 7 Implementation Requirements ............................................................................................................ 12

7.1 HP_MemoryCollection (Optional) ............................................................................................. 13 7.2 HP_MemoryRedundancySet (Optional) ................................................................................... 13 7.3 HP_MemberOfMemoryCollection (Conditional) ....................................................................... 14 7.4 HP_MemberOfMemoryRedundancySet (Conditional) .............................................................. 14 7.5 HP_HostedMemoryCollection (Conditional) ............................................................................. 14 7.6 HP_HostedMemoryRedundancySet (Conditional) ................................................................... 14 7.7 HP_MemoryModule (Mandatory) .............................................................................................. 14 7.8 HP_MemoryBoard (Optional) ................................................................................................... 16 7.9 HP_RealizesMemoryModule (Mandatory) ................................................................................ 17 7.10 HP_MemoryModuleInSlot (Conditional) ................................................................................... 17 7.11 HP_MemoryBoardInSlot (Conditional)...................................................................................... 17 7.12 HP_MemoryModuleOnBoard (Conditional) .............................................................................. 17 7.13 HP_SystemMemoryModule ...................................................................................................... 17 7.14 HP_SystemMemoryBoard (Conditional) ................................................................................... 17 7.15 HP_MemoryModuleSlot (Optional) ........................................................................................... 17 7.16 HP_MemoryBoardSlot (Optional) ............................................................................................. 18 7.17 HP_SystemMemoryModuleSlot (Optional) ............................................................................... 19 7.18 HP_SystemMemoryBoardSlot (Optional) ................................................................................. 19 7.19 HP_MemoryModuleSlotOnBoard (Conditional) ........................................................................ 19

8 Methods ............................................................................................................................................... 19 9 Use Cases ........................................................................................................................................... 19

9.1 Object Diagrams ....................................................................................................................... 19 9.2 Determine Maximum Memory Speed ....................................................................................... 21

10 CIM Elements ...................................................................................................................................... 24 10.1 HP_MemoryCollection .............................................................................................................. 24 10.2 HP_MemoryRedundancySet .................................................................................................... 25 10.3 HP_MemberOfMemoryCollection ............................................................................................. 25 10.4 HP_MemberOfMemoryRedundancySet ................................................................................... 25 10.5 HP_HostedMemoryCollection ................................................................................................... 26 10.6 HP_HostedMemoryRedundancySet ......................................................................................... 26 10.7 HP_MemoryModule .................................................................................................................. 26 10.8 HP_MemoryBoard .................................................................................................................... 27 10.9 HP_RealizesMemoryModule .................................................................................................... 28 10.10 HP_MemoryModuleInSlot ......................................................................................................... 28 10.11 HP_MemoryBoardInSlot ........................................................................................................... 28 10.12 HP_MemoryModuleOnBoard .................................................................................................... 29 10.13 HP_SystemMemoryModule ...................................................................................................... 29 10.14 HP_SystemMemoryBoard ........................................................................................................ 29 10.15 HP_MemoryModuleSlot ............................................................................................................ 29 10.16 HP_MemoryBoardSlot .............................................................................................................. 30

2.1.0 3

10.17 HP_SystemMemoryModuleSlot ................................................................................................ 31 10.18 HP_SystemMemoryBoardSlot .................................................................................................. 31 10.19 HP_MemoryModuleSlotOnBoard ............................................................................................. 32 10.20 HP_RegisteredProfile ............................................................................................................... 32


4 2.1.0

Figures

Figure 1 – Memory Physical Asset Profile: Class Diagram ........................................................................ 11 Figure 2 – Memory Physical Asset Profile: Inheritance Hierarchy .............................................................. 12 Figure 3 – Memory Physical Asset Profile (Physical memory propagation) ............................................... 20 Figure 4 – Memory Physical Asset Profile (Memory board instances) ....................................................... 22 Figure 5 – Memory Physical Asset Profile (Memory board instances with redundancy) ............................ 23

2.1.0 5

Tables

Table 1 – Related Profiles ........................................................................................................................... 10 Table 2 Memory type .................................................................................................................................. 15 Table 3 Memory Technology....................................................................................................................... 15 Table 6 – Class: HP_MemoryCollection ..................................................................................................... 25 Table 7 – Class: HP_ MemoryRedundancySet .......................................................................................... 25 Table 8 – Class: HP_ MemberOfMemoryCollection ................................................................................... 25 Table 9 – Class: HP_ MemberOfMemoryRedundancySet ......................................................................... 26 Table 10 – Class: HP_ HostedMemoryCollection ....................................................................................... 26 Table 11 – Class: HP_HostedMemoryRedundancySet .............................................................................. 26 Table 12 – Class: HP_ MemoryModule ...................................................................................................... 27 Table 13 – Class: HP_MemoryBoard ......................................................................................................... 28 Table 14 – Class: HP_RealizesMemoryModule ......................................................................................... 28 Table 15 – Class: HP_MemoryModuleInSlot .............................................................................................. 28 Table 16 – Class: HP_MemoryBoardInSlot ................................................................................................ 29 Table 17 – Class: HP_MemoryModuleOnBoard ......................................................................................... 29 Table 18 – Class: HP_SystemMemoryModule ........................................................................................... 29 Table 19 – Class: HP_SystemMemoryBoard ............................................................................................. 29 Table 20 – Class: HP_MemoryModuleSlot ................................................................................................. 30 Table 21 – Class: HP_MemoryBoardSlot ................................................................................................... 31 Table 22 – Class: HP_SystemMemoryModuleSlot ..................................................................................... 31 Table 23 – Class: HP_SystemMemoryBoardSlot ....................................................................................... 31 Table 24 – Class: HP_MemoryModuleSlotOnBoard .................................................................................. 32 Table 25 – Class: HP_RegisteredProfile .................................................................................................... 32 Table 26 – Durable Names generated by this Profile ................................................................................. 32 Table 27 – Correlatable IDs generated by this Profile ................................................................................ 32

6 2.1.0

Foreword

The HP Memory Physical Asset Profile P00111 was prepared by the HP WBEM TC.

2.1.0 7

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 and manage the state and health of logical and physical Memory subsystems. 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.

8 2.1.0

1 Scope The HP Memory Physical Asset Profile extends the management capability of referencing profiles by adding the capability to represent the state of logical and physical Memory subsystems in a system.









HP WBEM TC P00110, HP Memory Profile










2.1.0 9












None.

10 2.1.0

5 Synopsis Profile Name: HP Memory Physical Asset Profile

Version: 2.1.0



Central Class: HP_MemoryModule


Specializes: WBEM TC, P00113, HP Consolidated Status Profile 1.0.0

Extends: DMTF DSP1011, Physical Asset Profile

The HP Memory Physical Asset Profile extends the DMTF Physical Asset Profile and specializes the HP Consolidated Status Profile for system memory.







P00110 – HP Memory Profile HP WBEM TC 1.0.0 Mandatory

DSP1011 – Physical Asset Profile

DMTF 1.0.0 Extends

6 Description

2.1.0 11

HP

_Mem

berOfM

emoryR

edundancySet

CIM_ComputerSystem

(see referencing profile)

HP_HostedMemoryRedundancySet

HP_MemoryModule



HP

_Elem

entConform

sToProfile

1

*

**


(see HP Consolidated Status Profile)

HP_MemoryCollection HP_MemoryRedundancySet

*

*

*

*

1

HP

_Mem

berOfM

emoryC

ollection

HP_HostedMemoryCollection

HP_MemoryModuleSlot



HP_SystemMemoryModuleSlot

HP

_System

Mem

oryBoard

HP

_System

Mem

oryModule

HP

_Mem

oryBoardInS

lot

CIM_PhysicalMemory

(see DMTF Physical Asset Profile)CIM_Card

(see DMTF Physical Asset Profile)HP_Memory

(see HP Memory Profile)


1

*HP_MemoryModuleOnBoard

* 1H

P_M

emoryM

oduleInSlot

HP_MemoryBoardSlot

CIM_Slot

(see DMTF Physical Asset

Profile)

*

1

1

1

1

1

*

1

1

*

*

1

HP_SystemMemoryBoardSlot

HP_MemoryBoard

1

*

HP

_Mem

oryM

odul

eSlo

tOnB

oard

CIM_RedundancySet

(see HP Consolidated Status Profile)

0..1

1..*

Figure 1 – Memory Physical Asset Profile: Class Diagram

12 2.1.0



HP_MemberOfMemoryCollection

HP_MemoryRedundancySet

CIM_RedundancySet








HP_MemberOfMemoryRedundancySet

CIM_Realizes



HP_SystemMemoryModule

CIM_Container


HP_SystemMemoryBoard

HP_MemoryBoardInSlot

HP_MemoryModuleOnBoard

CIM_PackageInConnector


HP_MemoryModuleInSlot

HP_SystemMemoryModuleSlot HP_SystemMemoryBoardSlot HP_MemoryModuleSlotOnBoard

CIM_ElementInConnector


Figure 2 – Memory Physical Asset Profile: Inheritance Hierarchy

Figure 1 represents the class diagram for the HP Memory Physical Asset Profile.

Each HP_MemoryModule instance propagates its operational status through the HP_MemoryCollection class to the singleton instance of HP_ComputerSystem. This collection class populates the GroupOperationalStatus property, which is used to describe the overall status in the HP_ComputerSystem instance. HP_MemoryModule instances can be associated to HP_MemoryModuleSlot instances via HP_MemoryModuleInSlot.

Each HP_MemoryBoard instance propagates its operational status through the HP_MemoryCollection class to the singleton instance of HP_ComputerSystem. This collection class populates the GroupOperationalStatus property, which is used to describe the overall status in the HP_ComputerSystem instance. HP_MemoryBoard instances can be associated to HP_MemoryBoardSlot instances via HP_MemoryBoardInSlot.

HP_MemoryBoard instances that are part of a redundancy set are associated to an instance of HP_MemoryRedundancySet via HP_MemberOfMemoryRedundancySet

Figure 2 represents the inheritance hierarchy for HP Memory Physical Asset.


2.1.0 13

7.1 HP_MemoryCollection (Optional)

There may be one or more instances of HP_MemoryCollection instantiated. Instances of HP_MemoryModule and HP_MemoryBoard are associated to HP_MemoryCollection through the HP_MemberOfMemoryCollection association. The HP_MemoryCollection instance is associated to the HP_ComputerSystem instance through the HP_HostedMemoryCollection association.

7.1.1 HP_MemoryCollection.InstanceID

This property shall be set to the following value: “HPQ:<provider name>:<unique ID>” where <provider name> is the name of the provider that implements this class and <unique ID> is a unique value for the instance.

7.2 HP_MemoryRedundancySet (Optional)

There may be one or more instances of HP_MemoryRedundancySet instantiated. Instances of HP_MemoryBoard are associated to HP_MemoryRedundancySet through the HP_MemberOfMemoryRedundancySet association. Instances of HP_MemoryRedundancySet are associated to the HP_ComputerSystem instance through the HP_HostedMemoryRedundancySet association.

7.2.1 HP_MemoryRedundancySet.InstanceID


7.2.2 HP_MemoryRedundancySet.AvailableMemory

This property may be set to a value that specifies the size of memory seen by the Operating System. Please see MOF for details.

7.2.3 HP_MemoryRedundancySet.TotalMemory

This property may be set to a value that specifies the total size of memory including memory seen by the Operating System and the memory used for spare, mirrored, or RAID configurations in MB. Please see MOF for details.

7.2.4 HP_MemoryRedundancySet.OperatingSpeed

This property may be set to a value that specifies the current operating speed of the Advanced Memory Protection subsystem in MHz. Please see MOF for details.

7.2.5 HP_MemoryRedundancySet.ConfigurationsAvailable

This property may be set values that specify the Advanced Memory Protection Fault Tolerance configurations available on the system. Please see MOF for details.

7.2.6 HP_MemoryRedundancySet.TargetConfiguration

This property may be set to a value contained in HP_MemoryRedundancySet.ConfigurationsAvailable that specifies the selected configuration of the Advanced Memory Protection subsystem. Please see MOF for details.

14 2.1.0

7.2.7 HP_MemoryRedundancySet.CurrentConfiguration

This property may be set to a value contained in HP_MemoryRedundancySet.ConfigurationsAvailable that specifies the current configuration of the Advanced Memory Protection subsystem. Please see MOF for details.

7.2.8 HP_MemoryRedundancySet.OperatingVoltage

This property may be set to a value that specifies the current operating memory voltage of the Advanced Memory Protection subsystem in millivolts. Please see MOF for details.

7.3 HP_MemberOfMemoryCollection (Conditional)

If an instance of HP_MemoryCollection exists, there shall be instances of HP_MemberOfMemoryCollection for each instance of HP_MemoryModule. In this case, there may also be instances of HP_MemberOfMemoryCollection for each instance of HP_MemoryBoard. This class represents the association from HP_MemoryModule and HP_MemoryBoard to HP_MemoryCollection.

7.4 HP_MemberOfMemoryRedundancySet (Conditional)

If an instance of HP_MemoryRedundancySet exists, there shall be instances of HP_MemberOfMemoryRedundancySet for each instance of HP_MemoryBoard that participates in that respective redundancy set. This class represents the association from HP_MemoryBoard to HP_MemoryRedundancySet.

7.5 HP_HostedMemoryCollection (Conditional)

If an instance of HP_MemoryCollection exists, there shall be one instance of HP_HostedMemoryCollection. This class represents the association from HP_ComputerSystem to HP_MemoryCollection.

7.6 HP_HostedMemoryRedundancySet (Conditional)

If one or more instances of HP_MemoryRedundancySet exist, there shall be an instance of HP_HostedMemoryRedundancySet for each instance of HP_MemoryRedundancySet. This class represents the association from HP_ComputerSystem to HP_MemoryRedundanySet.

7.7 HP_MemoryModule (Mandatory)

There shall be an instance of HP_MemoryModule for each memory module that exists in the managed system.

7.7.1 HP_MemoryModule.Tag


7.7.2 HP_MemoryModule.SPD

This property may be set to raw Serial Presence Detect information contained in the memory module. Please see MOF for details.

2.1.0 15

7.7.3 HP_MemoryModule.MemoryChipStatus

This property may be set to enumeration values describing the status of volatile memory chip. Please see MOF for details

7.7.4 HP_MemoryModule.MemoryChipStatusDescription

This property may be set to a value that further describes the memory chip status. Please see MOF for details.

7.7.5 HP_MemoryModule.ArtworkRevision

This property may be set to a value that describes the artwork revision of the memory chip. Please see MOF for details.

7.7.6 HP_MemoryModule.EngineeringDateCode

This property may be set to a value that describes the engineering date code of the memory chip. Please see MOF for details.

7.7.7 HP_MemoryModule.ScanRevision

This property may be set to a value that describes the scan revision of the memory chip. Please see MOF for details.

7.7.8 HP_MemoryModule.Type

This property shall be set to a value that describes the memory module type and can take one of the value as in table. Please see MOF for details.

Table 2 Memory type

Value ValueMap 0 Unknown 1 Other 2 HP DIMM .. Reserved

7.7.9 HP_MemoryModule.MinimumVoltage

This property may be set to a value that specifies the minimum voltage required for the memory module to operate in millivolts. Please see MOF for details.

7.7.10 HP_MemoryModule.Ranks

This property may be set to a value that describes the number of physical ranks on the module Please see MOF for details.

7.7.11 HP_MemoryModule.Technology

This property shall be set to a value that describes the memory module technology and can take one of the value as in table. Please see MOF for details.

Table 3 Memory Technology

Value ValueMap 0 Unknown 1 Other

16 2.1.0

Value ValueMap 2 FastPageMode 3 EdoPageMode 4 BurstEdoPageMode 5 Synchronous 6 RDRAM 7 RDIMM 8 UDIMM 9 LRDIMM .. Reserved

Note: The following properties (Section 7.7.12 through Section 7.7.14) are part of standard CIM schema but are experimental as of 2.32 so adding to the HP MOF for use and HP is working with DMTF to move them to final.

7.7.12 HP_MemoryModule. IsSpeedInMhz

This property shall be set to indicate if the Maximum memory Speed is to be represented in Nanoseconds or MHz. A value of TRUE shall indicate that the speed is represented by the MaxMemorySpeed property. A value of FALSE shall indicate that the speed is represented by the Speed property. Please see MOF for details.

7.7.13 HP_MemoryModule.MaxMemorySpeed

This property shall be set to a value that describes the maximum speed (in MHz) of the module Please see MOF for details.

7.7.14 HP_MemoryModule.ConfiguredMemoryClockSpeed

7.8 This property may be set to a value that specifies the configured clock speed (in MHz) of the module. Please see MOF for details.HP_MemoryBoard (Optional)

There may be one or more instances of HP_MemoryBoard for each memory board that exists in the managed system. A memory board contains memory modules.

7.8.1 HP_MemoryBoard.Tag


7.8.2 HP_MemoryBoard.Locked

This property may be set to an enumeration value that describes the locked state of the Advanced Memory Protection board. Please see MOF for details.

7.8.3 HP_MemoryBoard.NumberOfSockets

This property may be set to a value that describes the total number of memory sockets for this memory board. Please see MOF for details.

2.1.0 17

7.8.4 HP_MemoryBoard.AvailableMemory

This property may be set to a value that specifies the size of memory for this board as seen by the Operating System in MB. Please see MOF for details.

7.8.5 HP_MemoryBoard.TotalMemory

This property may be set to a value that specifies the size of memory for the board including memory seen by the Operating System and the memory used for spare, mirrored, or RAID configurations in MB. Please see MOF for details.

7.9 HP_RealizesMemoryModule (Mandatory)

There shall be an instance of HP_RealizesMemoryModule for each instance of HP_MemoryModule. This class represents the association from HP_Memory to HP_MemoryModule.

7.10 HP_MemoryModuleInSlot (Conditional)

If instances of HP_MemoryModule and HP_MemoryModuleSlot exist, there shall be an instance of HP_MemoryModuleInSlot for each instance of HP_MemoryModule that resides in a respective memory slot. This class represents the association from HP_MemoryModule to HP_MemoryModuleSlot.

7.11 HP_MemoryBoardInSlot (Conditional)

If instances of HP_MemoryBoardSlot exist, there shall be an instance of HP_MemoryBoardInSlot for each such instance of HP_MemoryBoardSlot. This class represents the association from HP_MemoryBoard to HP_MemoryBoardSlot.

7.12 HP_MemoryModuleOnBoard (Conditional)

If instances of HP_MemoryBoard exist, there shall be an instance of HP_MemoryModuleOnBoard for each instance of HP_MemoryModule that exists for the respective memory board. A memory module cannot exist in multiple memory boards. This class represents the association from HP_MemoryModule to HP_MemoryBoardfs.

7.13 HP_SystemMemoryModule

There shall be an instance of HP_SystemMemoryModule for each instance of HP_MemoryModule that exists in the managed system. This class represents the association from HP_MemoryModule to HP_ComputerSystemChassis.

7.14 HP_SystemMemoryBoard (Conditional)

If an instance of HP_MemoryBoard exists, there shall be an instance of HP_SystemMemoryBoard for each instance of HP_MemoryBoard that exists. This class represents the association from HP_MemoryBoard to HP_ComputerSystemChassis.

7.15 HP_MemoryModuleSlot (Optional)

There may be one or more instances of HP_MemoryModuleSlot for each memory slot that exists in the managed system.

7.15.1 HP_MemoryModuleSlot.Tag


18 2.1.0

7.15.2 HP_MemoryModuleSlot.Name

This property shall be set to the following value: “Memory Slot n” where n represents the slot number.

7.15.3 HP_MemoryModuleSlot.Number

This property shall be set to a value that describes the slot number printed on the computer system.

7.15.4 HP_MemoryModuleSlot.Caption

This property shall be set to the following value: “Memory Slot n” where n represents the slot number.

7.15.5 HP_MemoryModuleSlot.Description

This property shall be set to the following value: “Memory Slot n” where n represents the slot number. After this string, this property can optionally contain additional information about the slot.

7.15.6 HP_MemoryModuleSlot.ConnectorLayout

This property shall be set to the following enumeration value: Other(1)

7.15.7 HP_MemoryModuleSlot.ConnectorDescription

This property shall be set to the following value: “Memory Slot”.

7.15.8 HP_MemoryModuleSlot.OtherIdentifyingInfo

This property shall be set to the following value: if slot is on a memory board: “Memory Board n” where n represents the memory board number. If slot is not on a memory board, this can optionally contain other identifying information such as cell information.

7.16 HP_MemoryBoardSlot (Optional)

If an instance of HP_MemoryBoard exists, there may be an instance of HP_MemoryBoardSlot for each instance of HP_MemoryBoard that exists.

7.16.1 HP_MemoryBoardSlot.Tag


7.16.2 HP_MemoryBoardSlot.Name

This property shall be set to the following value: “Memory Board n” where n represents the board slot number.

7.16.3 HP_MemoryBoardSlot.Number

This property shall be set to a value that describes the memory board slot number printed on the computer system.

7.16.4 HP_MemoryBoardSlot.Caption

This property shall be set to the following value: “Memory Board n” where n represents the board slot number.

2.1.0 19

7.16.5 HP_MemoryBoardSlot.Description

This property shall be set to the following value: “Memory Board n” where n represents the board slot number. After this string, this property can optionally contain additional information about the slot.

7.16.6 HP_MemoryBoardSlot.ConnectorLayout

This property shall be set to the following enumeration value: Other(1)

7.16.7 HP_MemoryBoardSlot.ConnectorDescription

This property shall be set to the following value: “Memory Board”

7.17 HP_SystemMemoryModuleSlot (Optional)

If an instance of HP_MemoryModuleSlot exists that is not associated to a memory board via HP_MemoryModuleSlotOnBoard, there may be an instance of HP_SystemMemoryModuleSlot for each such instance of HP_MemoryModuleSlot. This class represents the association from HP_MemoryModuleSlot to HP_ComputerSystemChassis.

7.18 HP_SystemMemoryBoardSlot (Optional)

If an instance of HP_MemoryBoardSlot exists, there may be an instance of HP_SystemMemoryBoardSlot for each instance of HP_MemoryBoard that exists. This class represents the association from HP_MemoryBoardSlot to HP_ComputerSystemChassis.

7.19 HP_MemoryModuleSlotOnBoard (Conditional)

If instances of HP_MemoryModuleSlot and HP_MemoryBoard exist, where a memory slot resides on the memory board, there shall be an instance of HP_MemoryModuleSlotOnBoard for each such instance of HP_MemoryModuleSlot that exists. This class represents the association from HP_MemoryModuleSlot to HP_MemoryBoard.

8 Methods None.

9 Use Cases

9.1 Object Diagrams

Figure 3 below represents a possible instantiation of the Memory Physical Asset Profile propagating the status of the physical memory modules. The worst case OperationalStatus condition from each of the memory module instances “Mm1” and “Mm2” is propagated to the GroupOperationalStatus of the HP_MemoryCollection instance “Mmcol1”.

Memory module instances “Mm1” and “Mm2” reside in slots “Ms1” and “Ms2”, respectively, via HP_MemoryModuleInSlot associations. Slot instances “Ms3” and “Ms4” are empty because they do not have any associations to memory modules.

20 2.1.0

Mmcol1: HP_MemoryCollection




Mm1: HP_MemoryModule





Ms1: HP_MemoryModuleSlot Ms2_HP_MemoryModuleSlot

HP

_Mem

oryModuleInS

lot

Csc1: HP_ComputerSystemChassis

HP

_System

Mem

oryModule

HP

_System

Mem

oryModule

Ms3: HP_MemoryModuleSlot Ms4: HP_MemoryModuleSlot

HP

_Mem

oryModuleInS

lot

HP_SystemMemoryModuleSlot

Figure 3 – Memory Physical Asset Profile (Physical memory propagation)

2.1.0 21

Figure 4 below represents a possible instantiation of the Memory Physical Asset Profile propagating the status of the physical memory modules and a memory board.

The worst case OperationalStatus condition from each of the memory module instances “Mm1” and “Mm2” is propagated to the GroupOperationalStatus of the HP_MemoryCollection instance “Mmcol1”.

The worst case OperationalStatus condition from each of the memory board instance “Mb1” is propagated to the GroupOperationalStatus of the HP_MemoryCollection instance “Mmcol1”.

Memory module instance “Mm1” and “Mm2” reside in memory board “Mb1” via the HP_MemoryModuleOnBoard association. These modules are in memory slots “Ms1” and “Ms2” which are on memory board “Mb1”.

Memory module instances “Mm1” and “Mm2” reside in slots “Ms1” and “Ms2”, respectively, via HP_MemoryModuleInSlot associations.

9.2 Determine Maximum Memory Speed

When a physical memory is modeled as an instance of CIM_PhysicalMemory, retrieve the maximum memory speed from CIM_PhysicalMemory.Speed property represented in nanoseconds if CIM_PhysicalMemory. IsSpeedInMhz is true else retrieve the maximum memory speed from CIM_PhysicalMemory. MaxMemorySpeed property represented in MHz.

22 2.1.0









Mb1 : HP_MemoryBoard


Mbs1: HP_MemoryBoardSlot

HP

_Mem

oryBoardInS

lot Csc1: HP_ComputerSystemChassis








HP_MemoryModuleSlotOnBoard



Figure 4 – Memory Physical Asset Profile (Memory board instances)

Figure 5 below represents a possible instantiation of the Memory Physical Asset Profile propagating the status of the physical memory modules and a memory board with redundancy.

Because the memory board instances that are associated to the memory collection are also associated to the memory board redundancy set, the memory collection “Mmcol1” derives its GroupOperationalStatus from the redundancy set “Mbred1” RedundancyStatus condition.

Memory module instance “Mm1” and “Mm2” reside in memory board “Mb1” via the HP_MemoryModuleOnBoard association. These modules are in memory slots “Ms1” and “Ms2” which are on memory board “Mb1” via HP_MemoryModuleSlotOnBoard.

Memory board instance “Mb1” belongs to redundancy set “Mbred1” via HP_MemberOfMemoryRedundancySet associations. This memory board resides in slot “Mbs1” via HP_MemoryBoardInSlot.

2.1.0 23











Mb1 : HP_MemoryBoard


Mbred1:HP_MemoryRedundancySet

RedundancyStatus: Degraded Redundancy


Mbs1: HP_MemoryBoardSlot


HP

_Mem

oryBoardInS

lot

Csc1: HP_ComputerSystemChassis








HP_MemoryModuleSlotOnBoard

Figure 5 – Memory Physical Asset Profile (Memory board instances with redundancy)

24 2.1.0

10 CIM Elements Table 4 – CIM Elements – HP Memory Physical Asset Profile


Classes HP_MemoryCollection Optional See sections 7.1 and 10.1

HP_MemoryRedundancySet Optional See sections 7.2 and 10.2

HP_MemberOfMemoryCollection Conditional See sections 0 and 10.3

HP_MemberOfMemoryRedundancySet Conditional See sections 7.4 and 10.4

HP_HostedMemoryCollection Conditional See sections 7.5 and 10.5

HP_HostedMemoryRedundancySet Conditional See sections 7.6 and 10.6

HP_MemoryModule Mandatory See sections 7.7 and 10.7

HP_MemoryBoard Optional See sections 7.8 and 10.8

HP_RealizesMemoryModule Mandatory See sections 0 and 10.9

HP_MemoryModuleInSlot Conditional See sections 7.10 and 10.10

HP_MemoryBoardInSlot Conditional See sections 7.11 and 10.11

HP_MemoryModuleOnBoard Conditional See sections 7.12 and 10.12

HP_SystemMemoryModule Mandatory See sections 7.13 and 10.13

HP_SystemMemoryBoard Conditional See sections 7.14 and 10.14

HP_MemoryModuleSlot Optional See sections 7.15 and 10.15

HP_MemoryBoardSlot Optional See sections 7.16 and 10.16

HP_SystemMemoryModuleSlot Optional See sections 7.17 and 10.17

HP_SystemMemoryBoardSlot Optional See sections 7.18 and 10.18

HP_MemoryModuleSlotOnBoard Conditional See sections 7.19 and 10.19

HP_RegisteredProfile Mandatory See section 10.20 Indications


10.1 HP_MemoryCollection HP_ModuleCollection extends the class HP_GroupSystemSpecificCollection in ways that are specific to HP memory implementations. Implementations shall adhere to the requirements defined in HP WBEM TC P00113, HP Consolidated Status profile for the class HP_GroupSystemSpecificCollection as well as additional requirements defined in this section. Implementations shall implement an instance of HP_MemoryCollection with the values specified.

2.1.0 25

Table 5 – Class: HP_MemoryCollection

Properties Requirement Notes InstanceID Mandatory Key: “HPQ:<provider name>:<unique

ID>” where <provider name> is the name of the provider that implements this class and <unique ID> is a unique value for the instance.

10.2 HP_MemoryRedundancySet

HP_ MemoryRedundancySet extends the class CIM_RedundancySet in ways that are specific to HP memory implementations. Implementations shall adhere to the requirements defined in HP WBEM TC P00113, HP Consolidated Status profile for the class CIM_RedundancySet as well as additional requirements defined in this section. Implementations shall implement instances of HP_MemoryRedundancySet with the values specified.

Table 6 – Class: HP_ MemoryRedundancySet

Properties Requirement Notes InstanceID Mandatory Key: “HPQ:<provider name>:<unique


AvailableMemory Optional See section 7.2.2

TotalMemory Optional See section 7.2.3

OperatingSpeed Optional See section 7.2.4

ConfigurationsAvailable Optional See section 7.2.5

TargetConfiguration Optional See section 7.2.6

CurrentConfiguration Optional See section 7.2.7

OperatingVoltage Optional See section 7.2.7

10.3 HP_MemberOfMemoryCollection

HP_ MemberOfMemoryCollection extends the class CIM_MemberOfCollection in ways that are specific to HP memory implementation.

Table 7 – Class: HP_ MemberOfMemoryCollection

Properties Requirement Notes Collection Mandatory Key: References HP_MemoryCollection

Member Mandatory Key: References CIM_PhysicalElement

10.4 HP_MemberOfMemoryRedundancySet

HP_ MemberOfMemoryRedundancySet extends the class CIM_MemberOfCollection in ways that are specific to HP memory implementation.

26 2.1.0

Table 8 – Class: HP_ MemberOfMemoryRedundancySet

Properties Requirement Notes Collection Mandatory Key: References

HP_MemoryRedundancySet

Member Mandatory Key: References HP_MemoryBoard

10.5 HP_HostedMemoryCollection

HP_HostedMemoryCollection extends the class HP_GroupHostedCollection in ways that are specific to HP memory implementation.

Table 9 – Class: HP_ HostedMemoryCollection


Dependent Mandatory Key: References HP_MemoryCollection

10.6 HP_HostedMemoryRedundancySet

HP_HostedMemoryRedundancySet extends the class CIM_OwningCollectionElement in ways that are specific to HP memory implementation.

Table 10 – Class: HP_HostedMemoryRedundancySet

Properties Requirement Notes OwningElement Mandatory Key: References HP_ComputerSystem

OwnedElement Mandatory Key: References HP_MemoryRedundancySet

10.7 HP_MemoryModule

HP_ MemoryModule extends the class CIM_PhysicalMemory in ways that are specific to HP memory implementation. Implementations shall adhere to the requirements defined in DMTF DSP1011, Physical Asset Profile for the class CIM_PhysicalMemory as well as additional requirements defined in this section. Implementations shall implement instances of HP_MemoryModule with the values specified.

2.1.0 27

Table 11 – Class: HP_ MemoryModule

Properties Requirement Notes Tag Mandatory Key: “HPQ:<provider name>:<unique


SPD Optional See section 7.7.2

MemoryChipStatus Optional See section 7.7.3

MemoryChipStatusDescription Optional See section 7.7.4

ArtworkRevision Optional See section 7.7.5

EngineeringDateCode Optional See section 7.7.6

ScanRevision Optional See section 7.7.7

Type Mandatory See section 7.7.8

MinimumVoltage Optional See section 7.7.9

Ranks Optional See section 7.7.10

Technology Optional See section 7.7.11

IsSpeedInMhz Mandatory See section 7.7.12

MaxMemorySpeed Conditional See section 7.7.13

ConfiguredMemoryClockSpeed Optional See section 7.7.14

10.8 HP_MemoryBoard

HP_MemoryBoard extends the class CIM_Card in ways that are specific to HP memory implementation. Implementations shall adhere to the requirements defined in DMTF DSP1011, Physical Asset Profile for the class CIM_Card as well as additional requirements defined in this section. Implementations shall implement instances of HP_MemoryBoard with the values specified.

28 2.1.0

Table 12 – Class: HP_MemoryBoard



Locked Optional See section 7.8.2

NumberOfSockets Optional See section 7.8.3

AvailableMemory Optional See section 7.8.4

TotalMemory Optional See section 7.8.5

10.9 HP_RealizesMemoryModule

HP_RealizesMemoryModule extends the class CIM_Realizes in ways that are specific to HP memory implementation.

Table 13 – Class: HP_RealizesMemoryModule

Properties Requirement Notes Antecedent Mandatory Key: References HP_MemoryModule

Dependent Mandatory Key: References HP_Memory

10.10 HP_MemoryModuleInSlot

HP_MemoryModuleInSlot extends the class CIM_ElementInConnector in ways that are specific to HP memory implementation.

Table 14 – Class: HP_MemoryModuleInSlot

Properties Requirement Notes Antecedent Mandatory Key: References HP_MemoryModuleSlot

Dependent Mandatory Key: References HP_MemoryModule

10.11 HP_MemoryBoardInSlot

HP_MemoryBoardInSlot extends the class CIM_PackageInConnector in ways that are specific to HP memory implementation.

2.1.0 29

Table 15 – Class: HP_MemoryBoardInSlot

Properties Requirement Notes Antecedent Mandatory Key: References HP_MemoryBoardSlot

Dependent Mandatory Key: References HP_MemoryBoard

10.12 HP_MemoryModuleOnBoard

HP_MemoryModuleOnBoard extends the class CIM_Container in ways that are specific to HP memory implementation.

Table 16 – Class: HP_MemoryModuleOnBoard

Properties Requirement Notes GroupComponent Mandatory Key: References HP_MemoryBoard

PartComponent Mandatory Key: References HP_MemoryModule

10.13 HP_SystemMemoryModule

HP_SystemMemoryModule extends the class CIM_Container in ways that are specific to HP memory implementation.

Table 17 – Class: HP_SystemMemoryModule

Properties Requirement Notes GroupComponent Mandatory Key: References


PartComponent Mandatory Key: References HP_MemoryModule

10.14 HP_SystemMemoryBoard

HP_SystemMemoryBoard extends the class CIM_Container in ways that are specific to HP memory implementation.

Table 18 – Class: HP_SystemMemoryBoard



PartComponent Mandatory Key: References HP_MemoryBoard

10.15 HP_MemoryModuleSlot

HP_MemoryModuleSlot extends the class CIM_Slot in ways that are specific to HP memory implementation. Implementations shall adhere to the requirements defined in DMTF DSP1011, Physical Asset Profile for the class CIM_Slot as well as additional requirements defined in this section. Implementations shall implement instances of HP_MemoryModuleSlot with the values specified.

30 2.1.0

Table 19 – Class: HP_MemoryModuleSlot



Name Mandatory “Memory Module Slot n” where n represents the slot number.

Number Mandatory The slot number that corresponds to the slot value printed on the computer system.

Caption Mandatory “Memory Module Slot n” where n represents the slot number.

Description Mandatory “Memory Module Slot n” where n represents the slot number. After this string, this property can optionally contain additional information about the slot.

ConnectorLayout Mandatory Other(1)

ConnectorDescription Mandatory “Memory Module Slot”

OtherIdentifyingInfo Conditional If slot is on a memory board: “Memory Board n” where n represents the memory board number. If slot is not on a memory board, this can optionally contain other identifying information such as cell information.

10.16 HP_MemoryBoardSlot

HP_MemoryBoardSlot extends the class CIM_Slot in ways that are specific to HP memory implementation. Implementations shall adhere to the requirements defined in DMTF DSP1011, Physical Asset Profile for the class CIM_Slot as well as additional requirements defined in this section. Implementations shall implement instances of HP_MemoryBoardSlot with the values specified.

2.1.0 31

Table 20 – Class: HP_MemoryBoardSlot



Name Mandatory “Memory Board n” where n represents the board slot number.

Number Mandatory The board slot number that corresponds to the memory board slot value printed on the computer system.

Caption Mandatory “Memory Board n” where n represents the board slot number.

Description Mandatory “Memory Board n” where n represents the board slot number. After this string, this property can optionally contain additional information about the slot.

ConnectorLayout Mandatory Other(1)

ConnectorDescription Mandatory “Memory Board”

10.17 HP_SystemMemoryModuleSlot

HP_SystemMemoryModuleSlot extends the class CIM_Container in ways that are specific to HP memory implementation.

Table 21 – Class: HP_SystemMemoryModuleSlot



PartComponent Mandatory Key: References HP_MemoryModuleSlot

10.18 HP_SystemMemoryBoardSlot

HP_SystemMemoryBoardSlot extends the class CIM_Container in ways that are specific to HP memory implementation.

Table 22 – Class: HP_SystemMemoryBoardSlot



PartComponent Mandatory Key: References HP_MemoryBoardSlot

32 2.1.0

10.19 HP_MemoryModuleSlotOnBoard

HP_MemoryModuleSlotOnBoard extends the class CIM_Container in ways that are specific to HP memory implementation.

Table 23 – Class: HP_MemoryModuleSlotOnBoard

Properties Requirement Notes GroupComponent Mandatory Key: References HP_MemoryBoard

PartComponent Mandatory Key: References HP_MemoryModuleSlot







RegisteredName Mandatory “HP Memory Physical Asset”





None defined




None defined

2.1.0 33

ANNEX A (normative)

Change Log


0.1 7/12/06 Initial Draft 0.2 7/20/06 Updates made based on feedback from the WBEM TC

0.3 7/26/06

Updates made based on feedback from WBEM TC sub-team review:

• Renamed profile to “HP Memory Physical Asset Profile” • Central class is now HP_MemoryModule

• Collections are now optional • Updated class diagram and association hierarchy to use proper

aggregation associations and resolved typographical errors

• Added additional property descriptions

• Updated various typographical errors through document, particularly in Section 10

• Resolved broken hyperlinks

0.4 7/28/06

Additional updates based on feedback from WBEM TC sub-team: • Added HP_MemoryModuleSlotOnBoard association

• Renamed HP_ModuleOnBoard to HP_MemoryModuleOnBoard • Updated to allow for multiple collections.

• Revised property formats

• Adjusted class diagram, association hierarchy and use cases accordingly

0.5 8/1/06

Updates based on suggestion from HP SMASH Forum (based on DMTF CR): • Remove HP_PackagedMemoryModule, HP_MemoryCard and

HP_MemoryCardInSlot

• Add HP_MemoryModuleInSlot

1.0 8/1/06

Updates based on WBEM TC review: • Classes renamed:

o HP_RealizesMemory now HP_RealizesMemoryModule o HP_MemorySlot now HP_MemoryModuleSlot o HP_SysteMemorySlot now HP_SystemMemoryModuleSlot o HP_MemorySlotOnBoard now HP_MemoryModuleSlotOnBoard

• HP_SystemMemoryModule and HP_SysytemMemoryBoard are now optional

1.0 11/29/06

Updates based on implementation review:

• Memory module collection and memory board collection are combined to one collection.

• Class diagram and instance diagrams updated. • Sections in 7 and 10 updated to reflect combined collection class,

renaming and adjusted properties.

• Sections in 8 are removed because no methods are defined.

• Use cases in 9 updated to reflect combined collection class, renaming and adjusted properties.

• HP_MemberOfMemoryCollection.Member now references

34 2.1.0

Version Date Description CIM_PhysicalElement

• Properties are adjusted for HP_MemoryBoard and HP_MemoryRedundancySet

o HP_MemoryRedundancySet Added: AvailableMemory, TotalMemory,

ConfigurationsAvailable, TargetConfiguration, CurrentConfiguration

Removed: OSMemSize, TypeAvailable, RivState, SubSystemStatus, TotalMemSize

o HP_MemoryBoard: Added: AvailableMemory, TotalMemory Removed: TotalMemorySize, OSMemorySize

• Classes renamed: o HP_MemoryModuleCollection now HP_MemoryCollection o HP_HostedMemoryModuleCollection now

HP_HostedMemoryCollection o HP_MemberOfMemoryModuleCollection now

HP_MemberOfMemoryCollection o HP_MemoryBoardRedundancySet now

HP_MemoryRedundancySet o HP_HostedMemoryBoardRedundancySet now

HP_HostedMemoryRedundancySet o HP_MemberOfMemoryBoardRedundancySet now


• Classes removed: o HP_MemoryBoardCollection o HP_MemberOfMemoryBoardCollection o HP_HostedMemoryBoardCollection

2.1.0 054/25/2012

New properties added to the following classes HP_MemoryRedundancySet

• OperatingVoltage HP_MemoryModule

• MaximumSpeed

• MinimumVoltage • Ranks

• Technology

Added following CIM experimental properties to HP Profile until they are finalized by DMTF

• IsSpeedInMhz

• MaxMemorySpeed • ConfiguredMemoryClockSpeed

2.1.0 35


Acknowledgments

36 2.1.0



CR

Number Date Title

CR00106 7/26/06 Create HP profile for the logical and physical system memory model CR00117 11/21/06 Update HP profile to combine memory collection classes and revise properties CR00179 02/28/2012 Added HP_MemoryModule.Type to indicate if it is HP DIMM

CR00183 05/25/2012

New properties added to the following classes HP_MemoryRedundancySet

• OperatingVoltage HP_MemoryModule

• MinimumVoltage

• Ranks

• Technology

Added following CIM experimental properties to HP Profile until they are finalized by DMTF

• IsSpeedInMhz • MaxMemorySpeed

• ConfiguredMemoryClockSpeed

2.1.0 37

Bibliography



Date: 10/08/2009

Version: 1.4.0

HP Base Server Physical Asset Profile




2 Version 1.4.0

Contents



3 Terms and Definitions ........................................................................................................................... 5 4 Symbols and Abbreviated Terms .......................................................................................................... 6 5 Synopsis ................................................................................................................................................ 7 6 Description ............................................................................................................................................ 7 7 Implementation Requirements .............................................................................................................. 8

7.1 HP_ComputerSystemChassis .................................................................................................... 8 8 Methods ............................................................................................................................................... 11

8.1 Profile Conventions for Operations ........................................................................................... 11 8.2 HP_ComputerSystemChassis .................................................................................................. 11 8.3 HP_ComputerSystemPackage ................................................................................................. 11

9 Use Cases ........................................................................................................................................... 11 9.1 Determine if HP Base Server Physical Asset profile has been implemented........................... 12

10 CIM Elements ...................................................................................................................................... 12 10.1 HP_ComputerSystemChassis .................................................................................................. 12 10.2 HP_ComputerSystemPackage ................................................................................................. 13 10.3 HP_RegisteredProfile ............................................................................................................... 13


Figures

Figure 1 – HP Base Server Physical Asset profile: Class Diagram .............................................................. 7

Tables

Table 1 – Related Profiles ............................................................................................................................. 7 Table 2 – Operations: HP_ComputerSystemPackage .............................................................................. 11 Table 3 – CIM Elements – HP Profile Registration Profile .......................................................................... 12 Table 4 – Class: HP_ComputerSystemChassis ......................................................................................... 13 Table 5 – Class: HP_ComputerSystemPackage ........................................................................................ 13 Table 6 – Class: HP_RegisteredProfile ...................................................................................................... 13 Table 7 – Durable Names generated by this Profile ................................................................................... 14 Table 8 – Correlatable IDs generated by this Profile .................................................................................. 14

Version 1.4.0 3

Foreword

The HP Base Server Physical Asset profile (P00114) was prepared by the HP WBEM TC.

4 Version 1.4.0

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 Base Server Physical elements. 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.

Version 1.4.0 5

1 Scope The HP Base Server Physical Asset profile extends the management capability of referencing profiles by adding the capability to represent base servers physical asset elements.








DMTF DSP1025, Physical Asset profile


HP WBEM TC P00100 – HP Profile Registration profile









6 Version 1.4.0












None.

Version 1.4.0 7

5 Synopsis Profile Name: HP Base Server Physical Asset Profile

Version: 1.4.0



Extends: DMTF DSP1011, Physical Asset profile 1.0

The HP Base Server Physical Asset profile extends DMTF DSP1011 to add the capability of modeling the physical aspects of HP systems.



DSP1011 – Physical Asset profile

DMTF 1.0 Extends

6 Description HP_ComputerSystem

(see HP Base Server profile)


ProductID


CIM_Chassis

(see DMTF Physical Asset profile)


CIM_ComputerSystemPackage

Figure 1 – HP Base Server Physical Asset profile: Class Diagram

HP systems are represented in the implementation namespace as instances of HP_ComputerSystem. The physical side of HP_ComputerSystem is represented with an instance of HP_ComputerSystemChassis via the HP_ComputerSystemPackage association. Both HP_ComputerSystemChassis and HP_ComputerSystemPackage are described in this profile. Figure 1 shows the class diagram for HP Base Server Physical Asset profile.

Implementers of this profile can also optionally model physical slots contained in the computer system chassis shown here by the HP_Slot and HP_SystemSlot classes.

8 Version 1.4.0


7.1 HP_ComputerSystemChassis

7.1.1 HP_ComputerSystemChassis.SerialNumber

This property shall contain the serial number for the system.

7.1.2 HP_ComputerSystemChassis.Model

This property shall contain the model name for the system.

7.1.3 HP_ComputerSystemChassis.ProductID

ProductID is conditionally supported on systems when SerialNumbers are not unique. When this property is a non-null, non-empty string clients shall assume that the SerialNumber is not unique and should be concatenated with the value in this property to obtain a unique value. If the SerialNumber property is unique, this property shall be set to null or a zero length string.

7.1.4 HP_ComputerSystemChassis.UserTracking (optional)

If implemented, this property should be supported as a writeable property used to store the asset-tracking information entered by the system administrator. This property value shall be persisted across reboots. Clients determine that this property is supported by querying a non-null, non-empty string contained in the property. If implemented, providers shall initialize the property to the string value “not set” if a client has not yet initialized or set a value for the property for the first time.

7.1.5 HP_ComputerSystemChassis.VirtualSerialNumber (conditional)

If the Virtual Connect functionality is enabled and the virtual serial number support is active; the virtual serial number information SHALL be populated here.

7.1.6 HP_ComputerSystemChassis.VirtualUUID (conditional)

If the Virtual Connect functionality is enabled and the virtual serial number support is active; the virtual UUID information corresponding to the virtual serial number SHALL be populated here.

7.1.7 HP_ComputerSystemChassis.TPMModule (conditional)

If the computer system has the capability to support a TPM module, this property SHALL be populated.

7.1.8 HP_ComputerSystemChassis.ChassisPackageType (optional)

This property shall contain a value deemed appropriate to the platform.

7.1.9 HP_ComputerSystemChassis.ChassisTypeDescription (optional)

This property shall contain one of the following strings: • “Unknown” • “Other” • “Single blade” • “Conjoined blades” • “Cell blade”

Version 1.4.0 9

• “Cellular” • “Single-node” • “Multi-node” • “Virtual system” • “Virtual partition”

The following table lists possible system configurations along with the expected string for HP_ComputerSystemChassis.ChassisTypeDescription as well as HP_ComputerSystemChassis. VendorEquipmentType properties.

System HP_ComputerSystemChassis. ChassisTypeDescription or HP_ComputerSystemChassis. VendorEquipmentType

Single blade

Examples: - BL860c - BL870c - Kauai COP1

“Single blade”

Conjoined blades – Partitionable or Non-partitionable Examples: - Kauai COP2 non-npar - Kauai COP4 non-npar - nPar with 1 blade in a Kauai COP2 or COP4 - nPar with multi blades in a Kauai COP2 or COP4

“Conjoined blades”

Cell blades – Partitionable or Non-partitionable

- nPar with 1 cell blade in a Superdome2 - nPar with multi cell blades in a Superdome2

“Cell blade”

Cellular partition (single-cell or multi-cell) Examples: - nPar with 1 cell board in a Superdome - nPar with multi cell boards in a Superdome

“Cellular”

Single-node

(Non-cellular servers)

“Single-node”

Multi-node “Multi-node”

10 Version 1.4.0

(Single chassis with multiple servers) e.g T2 Spartan

Virtual partition Example: - vPar

“Virtual partition”

Virtual system Examples: - HPVM guest - Xen guest

“Virtual system”

7.1.10 HP_ComputerSystemChassis.PackageType (optional)

This property shall contain value 16 (Blade) for Blade servers,.and 3 (Chassis/Frame) for other servers.

7.1.11 HP_ComputerSystemChassis.OtherPackageType (optional)

This property does not need to be populated.

7.1.12 HP_ComputerSystemChassis.MultipleSystemSupport (optional)

This property shall indicate TRUE for conjoined blades, multi-node and multi-cell partitions, and FALSE for other server configurations.

Note: when this property is set to TRUE, there should be one CIM_PhysicalPackage instance per blade / per cell in the partition (see Modular System profile).

7.1.13 HP_ComputerSystemChassis.RackMountable (optional)

This property shall indicate TRUE for rack-mountable servers. Stand-alone servers and servers which reside in enclosures (such as blades or cellular partitions) shall have this property set to FALSE.

7.1.14 HP_ComputerSystemChassis.VendorEquipmentType (optional)

This property shall contain one of the following strings: • “Unknown” • “Other” • “Single blade” • “Conjoined blades” • “Cell blade” • “Cellular” • “Single-node” • “Multi-node” • “Virtual system” • “Virtual partition”

For details on the expected string in different system configurations, see the table in section 7.1.9.

Version 1.4.0 11

8 Methods None.




• GetInstance

• Associators

• AssociatorNames

• References

• ReferenceNames






8.3 HP_ComputerSystemPackage


Table 2 – Operations: HP_ComputerSystemPackage


GetIntance Mandatory None





EnumerateInstances Mandatory None


9 Use Cases

12 Version 1.4.0

9.1 Determine if HP Base Server Physical Asset profile has been implemented

The following algorithm can be followed to determine if the HP Base Server Physical Asset profile has been implemented:

• For any given autonomous profile, query for its CIM_RegisteredProfile instance in the interop namespace. For HP server system, this will typically be the DMTF Base Server profile (DSP1004).

• Query for instances of CIM_RegistedProfile associated with this instance of CIM_RegisteredProfile (found in first step) via the association CIM_ReferencedProfile that have the following property values:

• RegisteredOrganization – 2 (DMTF)

• RegisteredName – “Physical Asset”

• Query for instances of HP_RegisteredProfile associated with the instance of CIM_RegisteredProfile (found in previous step) via the association HP_ExtendsProfile that have the following property values:

• RegisteredOrganization – 1 (other)

• OtherRegisteredOrganization – “HP WBEM TC”

• RegisteredName – “HP Base Server Physical Asset”

• If an instance of HP_RegisteredProfile is found in the previous step, the client knows that the implementation namespace’s Physical Asset information has been extended with the HP specific elements defined in this profile. The client would then follow the methods defined in the DMTF Profile Registration (DSP 1033) and HP Profile Registration (P00100) profiles to find the central class of the instances of CIM_RegisteredProfile and HP_RegisteredProfile found in the first steps.




Classes HP_ComputerSystemChassis Mandatory see Section 7.1

HP_ComputerSystemPackage Mandatory see Section 7.2

HP_RegisteredProfile Mandatory see section 10.1 Indications

None defined.


HP_ComputerSystemChassis is used to model the chassis of HP computer systems.

Version 1.4.0 13

Table 4 – Class: HP_ComputerSystemChassis


SerialNumber M (see section 7.1.1)

Model M (see section 7.1.2)

ProductID C (see section 7.1.3)

UserTracking O (see section 7.1.4)

VirtualSerialNumber[] C (see section 7.1.5)

VirtualUUID[] C (see section 7.1.6)

TPMModule C (see section 7.1.7)

ChassisPackageType O (see section 7.1.8)

ChassisTypeDescription O (see section 7.1.9)

PackageType O (see section 7.1.10)

OtherPackageType O (see section 7.1.11)

MultipleSystemSupport O (see section 7.1.12)

RackMountable O (see section 7.1.13)

VendorEquipmentType O (see section 7.1.14)

10.2 HP_ComputerSystemPackage

HP_ComputerSystemPackage is used to associate an HP_ComputerSystem with its chassis instance of HP_ComputerSystemChassis.

Table 5 – Class: HP_ComputerSystemPackage


Antecedent M ref:HP_ComputerSystemChassis

Dependent M ref:HP_ComputerSystem


Implementation shall implement an instance of HP_RegisteredProfile in the interop namespace with the values specified.



RegisteredOrganization M Other (1)

OtherRegisteredOrganization M “HP WBEM TC”

RegisteredName M “HP Base Server Physical Asset”

RegisteredVersion M 1.4.0

14 Version 1.4.0





UUID UUID from SMBIOS Chassis replacement


SerialNumber Serial Number from SMBIOS

Chassis replacement


VirtualSerialNumber Virtual Serial Number as provided by Virtual Connect

Logical server deletion / addition


VirtualUUID Virtual UUID as provided by Virtual Connect

Logical server deletion / addition





ProductID Product ID from SMBIOS

Correlatable when used in conjunction with SerialNumber (see section 7.1.3)

Version 1.4.0 15

ANNEX A (normative)

Change Log


1.0 4/27/06 Initial Draft 1.1.0 1/22/08 Added HP Virtual Connect support (VirtualSerialNumber and VirtualUUID). 1.2.0 6/10/2008 Added the TPMModule property

1.3.0 7/30/2009 Added sections 7.1.8 - 7.1.14 to clarify data populated for various chassis type properties

16 Version 1.4.0


Acknowledgments

Version 1.4.0 17




CR00103 6/14/06 Create HP Profile for the logical and physical base server model. CR00129 1/22/08 Added virtual connect related properties.

Minor update 6/10/2008 Added the TPMModule property

CR00152 7/30/2009 Added sections 7.1.8 - 7.1.14 to clarify data populated for various chassis type properties

18 Version 1.4.0

Bibliography



Date: 09/11/08

Version: 1.1.0

HP Fan Physical Asset Profile




2 Version 1.1.0

Contents

1 Scope ..................................................................................................................................... 5 2 Normative References ........................................................................................................... 5

2.1 Approved References ............................................................................................................ 5 2.2 References Under Development ........................................................................................... 5 2.3 Other References .................................................................................................................. 5

3 Terms and Definitions ............................................................................................................ 5 4 Symbols and Abbreviated Terms .......................................................................................... 6 5 Synopsis ................................................................................................................................ 6 6 Description ............................................................................................................................. 7 7 Implementation Requirements ............................................................................................... 8

7.1 HP_FanModule ...................................................................................................................... 8 7.1.1 HP_FanModule.RemovalConditions.............................................................................. 8 7.1.2 HP_FanModule.Description ........................................................................................... 8

7.2 HP_RealizesFan .................................................................................................................... 8 7.3 HP_SystemPhysicalFan ........................................................................................................ 9 7.4 HP_FanInSlot ........................................................................................................................ 9 7.5 CIM_Slot.ElementName ........................................................................................................ 9

8 Methods ................................................................................................................................. 9 9 Use Cases ............................................................................................................................. 9

9.1 Object Diagram ...................................................................................................................... 9 9.2 Retrieve the Fan Status for a Fan Module .......................................................................... 11

10 CIM Elements ...................................................................................................................... 11 10.1 HP_FanModule .................................................................................................................... 11 10.2 HP_RegisteredProfile .......................................................................................................... 11 10.3 HP_RealizesFan .................................................................................................................. 12 10.4 HP_SystemPhysicalFan ...................................................................................................... 12 10.5 HP_FanInSlot ...................................................................................................................... 12

11 Durable Names and Correlatable IDs .................................................................................. 12

Figures

Figure 1 – HP Fan Physical Asset Profile: Class Diagram ........................................................................... 7 Figure 2 – HP Fan Physical Asset Profile: Inheritance Hierarchy Diagram .................................................. 8 Figure 3 – HP Fan Physical Asset Profile: Object Diagram ........................................................................ 10

Tables

Table 1 – Related Profiles ............................................................................................................................. 7 Table 2 – CIM Elements – HP Fan Profile .................................................................................................. 11 Table 3 – Class: HP_FanModule ................................................................................................................ 11 Table 4 – Class: HP_RegisteredProfile ..................................................................................................... 11 Table 5 – Class: HP_RealizesFan .............................................................................................................. 12 Table 6 – Class: HP_SystemPhysicalFan .................................................................................................. 12 Table 7 – Class: HP_FanInSlot ................................................................................................................... 12 Table 8 – Durable Names generated by this Profile ................................................................................... 12 Table 9 – Correlatable IDs generated by this Profile .................................................................................. 12

Version 1.1.0 3

Foreword

The HP Fan Physical Asset Profile P00115 was prepared by the HP WBEM TC.

4 Version 1.1.0

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 fans in HP systems. 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.

Version 1.1.0 5

1 Scope The HP Fan Physical Asset Profile extends the management capability of referencing profiles by adding the capability to represent the physical fans in HP specific ways.








HP WBEM TC P00102, HP Fan Profile










6 Version 1.1.0











None.

5 Synopsis Profile Name: HP Fan Physical Asset Profile

Version: 1.1.0



Central Class: HP_FanModule

Version 1.1.0 7



The HP Fan Physical Asset profile extends DMTF DSP1011 to add physical fan characteristics that are specific to HP systems.


Profile Name Organization Version Relationship Behavior DSP1011 – Physical Asset Profile

DMTF 1.0.0 Mandatory



P00102 – HP Fan Profile HP WBEM TC 1.0.0 Mandatory

6 Description HP fans are represented in the implementation namespace as instances of HP_Fan. An implementation can optionally implement the physical asset elements of the fan by associating the appropriate instances of HP_Fan to an instance of HP_FanModule via the HP_RealizesFan association class. Both HP_FanModule and HP_RealizesFan are described in this profile.

Instances of HP_FanModule are associated to the HP base server via HP_SystemPhysicalFan and HP_FanInSlot associations, which are also described in this profile.

Figure 1 represents the class schema for the HP Fan Physical Asset Profile. Figure 2 represents additional inheritance hierarchies for classes described in this profile.

HP_Fan

(see HP Fan Profile)

HP_RealizesFan

CIM_PhysicalPackage

(see DMTF Physical Asset Profile)

HP_FanModule




profile)

1

1*

1

CIM_PhysicalPackage

(see referencing profile) HP_SystemPhysicalFan

CIM_Slot

(see referencing profile)HP_FanInSlot

1

0..1

1

*

Figure 1 – HP Fan Physical Asset Profile: Class Diagram

8 Version 1.1.0

CIM_Realizes


HP_RealizesFan HP_SystemPhysicalFan

CIM_Container


HP_FanInSlot

CIM_PackageInSlot


Figure 2 – HP Fan Physical Asset Profile: Inheritance Hierarchy Diagram


7.1 HP_FanModule

There shall be one instance of HP_FanModule instantiated for each instance of HP_Fan.

7.1.1 HP_FanModule.RemovalConditions

HP_FanModule.RemovalConditions property must be implemented. This property contains enumerations that describe the fan module’s removal conditions, including its hot swap capability. Please see DSP1011 Physical Asset Profile.

7.1.2 HP_FanModule.Description

HP_FanModule.Description property may optionally be implemented. This property shall contain a detailed description of the fan module, including Caption, Name or ElementName, FanType and the corresponding string value of OperationalStatus[0] or StatusDescriptions[0].

7.2 HP_RealizesFan

There shall be one instance of HP_RealizesFan instantiated for each instance of HP_Fan. This class associates instances of HP_Fan with a corresponding instance of HP_FanModule.

Version 1.1.0 9

7.3 HP_SystemPhysicalFan

There shall be one instance of HP_SystemPhysicalFan instantiated for each instance of HP_FanModule. This class associates instances of HP_FanModule with CIM_PhysicalPackage.

7.4 HP_FanInSlot

If an instance of CIM_Slot representing the fan slot exists, there shall be one instance of HP_FanInSlot instantiated for each instance of HP_FanModule. This class associates an instance of HP_FanModule with a corresponding instance of CIM_Slot.

7.5 CIM_Slot.ElementName

If an instance of CIM_Slot representing the fan slot exists, CIM_Slot.ElementName shall be implemented and shall contain a descriptive name of the fan slot and Number, in a user displayable format.

8 Methods None.

9 Use Cases

9.1 Object Diagram

Figure 3 represents a possible instantiation of the HP Fan Physical Asset Profile. In this case, system1 has two fans, fan1 and fan2. Fan1 and fan2 are associated to fan modules fm1 and fm2 via HP_RealizesFan. These fan modules are respectively associated to slots fanslot1 and fanslot2 via HP_FanInSlot. The fan modules are all also associated to chassis1 via HP_SystemPhysicalFan. This diagram also shows an example of the HP_Fan.Description property for fm1 and fm2, constructed from property values for ElementName, FanType and value map string of OperationalStatus[0].

For simplicity most properties have been removed from the classes.

10 Version 1.1.0


fan2:HP_Fan


fan1:HP_Fan


HP_SystemFan

HP_SystemFan






HP_RealizesFanHP_RealizesFan

chassis1:CIM_PhysicalPackage

fanslot1:CIM_Slot

HP_FanInSlot

HP_SystemPhysicalFan

HP_SystemSlot

fanslot2:CIM_Slot

fanslot3:CIM_Slot

fanslot4:CIM_Slot

HP_FanInSlot

Fm1:HP_FanModule


Fm2:HP_FanModule


Figure 3 – HP Fan Physical Asset Profile: Object Diagram

Version 1.1.0 11

9.2 Retrieve the Fan Status for a Fan Module

For the given instance of HP_FanModule, retrieve associated instances of HP_Fan through the HP_RealizesFan association. Observe the HP_Fan.OperationalStatus property for this instance.


Table 2 – CIM Elements – HP Fan Profile


HP_FanModule Mandatory See Sections 7.1 and 10.1 HP_RegisteredProfile Mandatory See Section 10.2 HP_RealizesFan Mandatory See Sections 7.2 and 10.3 HP_SystemPhysicalFan Mandatory See Sections 7.3 and 10.4 HP_FanInSlot Conditional See Sections 7.4 and 10.5 CIM_Slot Optional See Section 7.5


10.1 HP_FanModule

HP_FanModule is used to represent a fan module in a managed system.

Table 3 – Class: HP_FanModule

Properties Requirement Notes RemovalConditions Mandatory See Section 7.1.1 Description Optional See Section 7.1.2




Properties Requirement Description RegisteredName Mandatory "HP Fan Physical Asset" RegisteredVersion Mandatory “1.1.0” RegisteredOrganization Mandatory Other (1)

12 Version 1.1.0


10.3 HP_RealizesFan

HP_RealizesFan is used to represent the association between HP_Fan and HP_FanModule.

Table 5 – Class: HP_RealizesFan

Properties Requirement Notes Antecedent Mandatory Key: References HP_FanModule

Dependent Mandatory Key: References HP_Fan

10.4 HP_SystemPhysicalFan

HP_SystemPhysicalFan is used to represent the association between CIM_PhysicalPackage and HP_FanModule.

Table 6 – Class: HP_SystemPhysicalFan

Properties Requirement Notes GroupComponent Mandatory Key: References HP_ComputerSystemChassis PartComponent Mandatory Key: References HP_FanModule

10.5 HP_FanInSlot

HP_FanInSlot is used to represent the association between HP_FanModule and CIM_Slot.

Table 7 – Class: HP_FanInSlot

Properties Requirement Notes Antecedent Mandatory Key: References HP_Slot

Dependent Mandatory Key: References HP_FanModule




None Defined




None Defined

Version 1.1.0 13

ANNEX A (normative)

Change Log

Version Date Description 0.1 5/30/06 Initial draft 1.0 5/31/06 Updated properties and fixed cross reference errors

1.0 11/29/06

Updated the following: • Slot modeling is now optional (FanInSlot is conditional) • Removed slot use cases • Removed sections in 8 because there are no methods defined • Durable Names and Correlatable IDs removed because there are really no


1.0.1 5/16/08 Corrected transposition of Antecedent and Dependent properties in HP_RealizesFan class.

1.1.0 9/11/08

Updated the following: Section 7, added more detail for FanModule.Description and

Slot.ElementName and an example in Section 9 Section 10, added CIM_Slot in class list as optional and

FanModule.Description property as optional.

14 Version 1.1.0


Acknowledgments

Version 1.1.0 15



CR

Number Date Title CR00106 5/31/06 Create HP profile for the environmental model CR00143 9/11/08 Detailed string properties

16 Version 1.1.0

Bibliography



Date: 11/29/06

Version: 1.0.2

HP Power Supply Physical Asset Profile




2 Version 1.0.2

Contents

1 Scope ..................................................................................................................................... 5 2 Normative References ........................................................................................................... 5

2.1 Approved References ............................................................................................................ 5 2.2 References Under Development ........................................................................................... 5 2.3 Other References .................................................................................................................. 5

3 Terms and Definitions ............................................................................................................ 5 4 Symbols and Abbreviated Terms .......................................................................................... 6 5 Synopsis ................................................................................................................................ 6 6 Description ............................................................................................................................. 7 7 Implementation Requirements ............................................................................................... 8

7.1 HP_PowerSupplyModule ....................................................................................................... 8 7.1.1 HP_PowerSupplyModule.RemovalConditions .............................................................. 8

7.2 HP_RealizesPowerSupply ..................................................................................................... 8 7.3 HP_SystemPhysicalPowerSupply ......................................................................................... 8 7.4 HP_PowerSupplyInSlot ......................................................................................................... 8

8 Methods ................................................................................................................................. 8 9 Use Cases ............................................................................................................................. 9

9.1 Object Diagram ...................................................................................................................... 9 9.2 Retrieve the Power Supply Status for a Power Supply Module .......................................... 10

10 CIM Elements ...................................................................................................................... 11 10.1 HP_PowerSupplyModule ..................................................................................................... 11 10.2 HP_RegisteredProfile .......................................................................................................... 11 10.3 HP_RealizesPowerSupply ................................................................................................... 11 10.4 HP_SystemPhysicalPowerSupply ....................................................................................... 12 10.5 HP_PowerSupplyInSlot ....................................................................................................... 12

11 Durable Names and Correlatable IDs .................................................................................. 12

Figures

Figure 1 – HP Power Supply Physical Asset Profile: Class Diagram ........................................................... 8 Figure 2 – HP Power Supply Physical Asset Profile: Inheritance Hierarchy Diagram .................................. 8 Figure 3 – HP Power Supply Physical Asset Profile: Object Diagram ........................................................ 10

Tables

Table 1 – Related Profiles ............................................................................................................................. 7 Table 2 – CIM Elements – HP Power Supply Profile .................................................................................. 11 Table 3 – Class: HP_PowerSupplyModule ................................................................................................. 11 Table 4 – Class: HP_RegisteredProfile ..................................................................................................... 11 Table 5 – Class: HP_RealizesPowerSupply ............................................................................................... 11 Table 6 – Class: HP_SystemPhysicalPowerSupply ................................................................................... 12 Table 7 – Class: HP_PowerSupplyInSlot .................................................................................................... 12 Table 8 – Durable Names generated by this Profile ................................................................................... 12 Table 9 – Correlatable IDs generated by this Profile .................................................................................. 12

Version 1.0.2 3

Foreword

The HP Power Supply Physical Asset Profile P00116 was prepared by the HP WBEM TC.

4 Version 1.0.2

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 power supplies in HP systems. 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.

Version 1.0.2 5

1 Scope The HP Power Supply Physical Asset Profile extends the management capability of referencing profiles by adding the capability to represent the physical power supplies in HP specific ways.








HP WBEM TC P00103, HP Power Supply Profile










6 Version 1.0.2











None.

5 Synopsis Profile Name: HP Power Supply Physical Asset Profile

Version: 1.0.2



Central Class: HP_PowerSupplyModule

Version 1.0.2 7



The HP Power Supply Physical Asset profile extends DMTF DSP1011 to add physical power supply characteristics that are specific to HP systems.


Profile Name Organization Version Relationship Behavior DSP1011 – Physical Asset Profile




P00103 – HP Power Supply Profile


6 Description HP power supplies are represented in the implementation namespace as instances of HP_PowerSupply. An implementation can optionally implement the physical asset elements of the power supply by associating the appropriate instances of HP_PowerSupply to an instance of HP_PowerSupplyModule via the HP_RealizesPowerSupply association class. Both HP_PowerSupplyModule and HP_RealizesPowerSupply are described in this profile.

Instances of HP_PowerSupplyModule are associated to the HP base server via HP_SystemPhysicalPowerSupply and HP_PowerSupplyInSlot associations, which are also described in this profile.

Figure 1 represents the class schema for the HP Power Supply Physical Asset Profile. Figure 2 represents additional inheritance hierarchies for classes described in this profile.

HP_PowerSupply

(see HP Power Supply profile)

HP_RealizesPowerSupply

CIM_PhysicalPackage

(see DMTF Physical Asset Profile)

HP_PowerSupplyModule




profile)

1

1*

1

CIM_PhysicalPackage

(see referencing profile)

HP_SystemPhysicalPowerSupply

CIM_Slot

(see referencing profile)HP_PowerSupplyInSlot

1

0..1

1

*

8 Version 1.0.2

Figure 1 – HP Power Supply Physical Asset Profile: Class Diagram

CIM_Realizes


HP_RealizesPowerSupply HP_SystemPhyiscalPowerSupply

CIM_Container


HP_PowerSupplyInSlot

CIM_PackageInSlot


Figure 2 – HP Power Supply Physical Asset Profile: Inheritance Hierarchy Diagram


7.1 HP_PowerSupplyModule

There shall be one instance of HP_PowerSupplyModule instantiated for each instance of HP_PowerSupply.

7.1.1 HP_PowerSupplyModule.RemovalConditions

HP_PowerSupplyModule.RemovalConditions property must be implemented. This property contains enumerations that describe the power supply module’s removal conditions, including its hot swap capability. Please see DSP1011 Physical Asset Profile.

7.2 HP_RealizesPowerSupply

There shall be one instance of HP_RealizesPowerSupply instantiated for each instance of HP_PowerSupply. This class associates instances of HP_PowerSupply with a corresponding instance of HP_PowerSupplyModule.

7.3 HP_SystemPhysicalPowerSupply

There shall be one instance of HP_SystemPhysicalPowerSupply instantiated for each instance of HP_PowerSupplyModule. This class associates instances of HP_PowerSupplyModule with CIM_PhysicalPackage.

7.4 HP_PowerSupplyInSlot

If an instance of CIM_Slot representing the power supply slot exists, there shall be one instance of HP_PowerSupplyInSlot instantiated for each instance of HP_PowerSupplyModule. This class associates an instance of HP_PowerSupplyModule with a corresponding instance of CIM_Slot.

8 Methods None.

Version 1.0.2 9

9 Use Cases

9.1 Object Diagram

Figure 3 represents a possible instantiation of the HP Power Supply Physical Asset Profile. In this case, system1 has two power supplies, ps1 and ps2. Ps1 and ps2 are associated to power supply modules ps1 and ps2 via HP_RealizesPowerSupply. These power supply modules are respectively associated to slots psslot1 and psslot2 via HP_PowerSupplyInSlot. The power supply modules are all also associated to chassis1 via HP_SystemPhysicalPowerSupply.

For simplicity most properties have been removed from the classes.

10 Version 1.0.2


ps1:HP_PowerSupplyModule ps2:HP_PowerSupplyModule


chassis1:CIM_PhysicalPackage

psslot1:CIM_Slot


HP_SystemPhysicalPowerSupply

psslot2:CIM_Slot

psslot3:CIM_Slot

psslot4:CIM_Slot



ps2:HP_PowerSupply


ps1:HP_PowerSupply



powercollection1:HP_PowerCollection




CIM_Container

Figure 3 – HP Power Supply Physical Asset Profile: Object Diagram

9.2 Retrieve the Power Supply Status for a Power Supply Module

For the given instance of HP_PowerSupplyModule, retrieve associated instances of HP_PowerSupply through the HP_RealizesPowerSupply association. Observe the HP_PowerSupply.OperationalStatus property for this instance.

Version 1.0.2 11


Table 2 – CIM Elements – HP Power Supply Profile


HP_PowerSupplyModule Mandatory See Sections 7.1 and 10.1 HP_RegisteredProfile Mandatory See Section 10.2 HP_RealizesPowerSupply Mandatory See Sections 7.2 and 10.3 HP_SystemPhysicalPowerSupply Mandatory See Sections 7.3 and 10.4 HP_PowerSupplyInSlot Conditional See Sections 7.4 and 10.5


10.1 HP_PowerSupplyModule

HP_PowerSupplyModule is used to represent a power supply module in a managed system.

Table 3 – Class: HP_PowerSupplyModule

Properties Requirement Notes RemovalConditions Mandatory See Section 7.1.1




Properties Requirement Description RegisteredName Mandatory "HP Power Supply Physical Asset" RegisteredVersion Mandatory “1.0.2” RegisteredOrganization Mandatory Other (1) OtherRegisteredOrganization Mandatory “HP WBEM TC”

10.3 HP_RealizesPowerSupply

HP_RealizesPowerSupply is used to represent the association between HP_PowerSupply and HP_PowerSupplyModule.

Table 5 – Class: HP_RealizesPowerSupply

Properties Requirement Notes Antecedent Mandatory Key: References HP_PowerSupplyModule

Dependent Mandatory Key: References HP_PowerSupply

12 Version 1.0.2

10.4 HP_SystemPhysicalPowerSupply

HP_SystemPhysicalPowerSupply is used to represent the association between CIM_PhysicalPackage and HP_PowerSupplyModule.

Table 6 – Class: HP_SystemPhysicalPowerSupply

Properties Requirement Notes GroupComponent Mandatory Key: References HP_ComputerSystemChassis

PartComponent Mandatory Key: References HP_PowerSupplyModule

10.5 HP_PowerSupplyInSlot

HP_PowerSupplyInSlot is used to represent the association between HP_PowerSupplyModule and CIM_Slot.

Table 7 – Class: HP_PowerSupplyInSlot

Properties Requirement Notes Antecedent Mandatory Key: References CIM_Slot

Dependent Mandatory Key: References HP_PowerSupplyModule




None Defined




None Defined

Version 1.0.2 13

ANNEX A (normative)

Change Log

Version Date Description 0.1 5/30/06 Initial draft 1.0 5/31/06 Updated properties and fixed cross reference errors

1.0 11/29/06

Updated the following: • Slot modeling now optional (PowerSupplyInSlot is conditional) • Removed slot use cases • Removed sections in 8 because there are no methods defined • Durable Names and Correlatable IDs removed because there are really no


1.0.1 5/16/08 Corrected transposition of Antecedent and Dependent properties in HP_RealizesPowerSupply class.

1.0.2 7/17/08 Fixed diagrams for associations that subclass off CIM_Container to be aggregations and changed references from HP_Slot, HP_SystemSlot to CIM_Slot, CIM_Container respectively.

14 Version 1.0.2


Acknowledgments

Version 1.0.2 15



CR

Number Date Title CR00106 5/31/06 Create HP profile for the environmental model

16 Version 1.0.2

Bibliography



Date: 06/04/2012

Version: 1.1.0

HP Ethernet Teaming




2 Version 1.1.0

Contents


2.1 Approved References ................................................................................................................. 8 2.2 References under Development ................................................................................................. 8 2.3 Other References ........................................................................................................................ 8

3 Terms and Definitions ........................................................................................................................... 8 4 Symbols and Abbreviated Terms ........................................................................................................ 10 5 Synopsis .............................................................................................................................................. 10 6 Description .......................................................................................................................................... 10 7 Implementation Requirements ............................................................................................................ 14

7.1 HP_EthernetPort ....................................................................................................................... 14 7.2 HP_EthernetDevice .................................................................................................................. 14 7.3 HP_EthernetTeam .................................................................................................................... 15 7.4 HP_EthernetTeamMember ....................................................................................................... 16 7.5 HP_HostedEthernetTeam ......................................................................................................... 17 7.6 HP_EthernetLANEndpoint ........................................................................................................ 17 7.7 HP_EthernetPortToLANEndpoint ............................................................................................. 17 7.8 HP_EthernetTeamToLANEndpoint ........................................................................................... 18 7.9 HP_EthernetLANHostedAccessPoint ....................................................................................... 18 7.10 HP_IPBindsToEthernetLANEndpoint ....................................................................................... 18 7.11 HP_EthernetStatistics ............................................................................................................... 18 7.12 HP_EthernetPortStatisticalData ................................................................................................ 18 7.13 HP_EthernetLANEndpointStatisticalData ................................................................................. 18 7.14 HP_EthernetCollection.............................................................................................................. 18 7.15 HP_EthernetMemberOfCollection ............................................................................................ 19 7.16 HP_EthernetGroupHostedCollection ........................................................................................ 19 7.17 HP_EthernetPortControllerPCIDevice (Optional) ..................................................................... 19 7.18 HP_EthernetPortController ......................................................... Error! Bookmark not defined.

8 Methods ............................................................................................................................................... 20 8.1 Profile Conventions for Operations ........................................................................................... 20 8.2 HP_EthernetPort ....................................................................................................................... 20 8.3 HP_EthernetDevice .................................................................................................................. 20 8.4 HP_EthernetTeam .................................................................................................................... 20 8.5 HP_EthernetTeamMember ....................................................................................................... 20 8.6 HP_HostedEthernetTeam ......................................................................................................... 21 8.7 HP_EthernetLANEndpoint ........................................................................................................ 21 8.8 HP_EthernetPortToLANEndpoint ............................................................................................. 21 8.9 HP_EthernetTeamToLANEndpoint ........................................................................................... 21 8.10 HP_EthernetLANHostedAccessPoint ....................................................................................... 22 8.11 HP_IPBindsToEthernetLANEndpoint ....................................................................................... 22 8.12 HP_EthernetStatistics ............................................................................................................... 22 8.13 HP_EthernetPortStatisticallData ............................................................................................... 22 8.14 HP_EthernetLANEndpointStatisticallData ................................................................................ 23 8.15 HP_EthernetCollection.............................................................................................................. 23 8.16 HP_EthernetMemberOfCollection ............................................................................................ 23 8.17 HP_EthernetGroupHostedCollection ........................................................................................ 24 8.18 HP_EthernetControllerPCIDevice ............................................................................................. 24 8.19 HP_EthernetPortController ....................................................................................................... 24


Version 1.1.0 3

9.2 Retrieve the Operational Status of an Ethernet Port ................................................................ 31 9.3 Retrieve the Operational Status of an Ethernet LAN Endpoint ................................................ 31 9.4 Retrieve the Operational Status of an Ethernet Team .............................................................. 31 9.5 Retrieve the Redundancy Status of an Ethernet Team ............................................................ 31 9.6 Retrieve the Members of an Ethernet Team ............................................................................ 31 9.7 Retrieve the Failed or Degraded Members of an Ethernet Team ............................................ 31 9.8 Retrieve the VLANs on an Ethernet Port .................................................................................. 31 9.9 Retrieve the VLANs on an Ethernet Team ............................................................................... 31 9.10 Retrieve the IP Addresses associated with an Ethernet Port ................................................... 31 9.11 Retrieve the IP Addresses associated with an Ethernet Team. ............................................... 32 9.12 Retrieve the Ethernet Collection Operational Status ................................................................ 32 9.13 Retrieve the Failed Members of an Ethernet Collection ........................................................... 32 9.14 Retrieve the PCI Device IDs for an Ethernet PortController ..................................................... 32 9.15 Retrieve the Controller Version for an Ethernet PortController ................................................ 32

10 CIM Elements ...................................................................................................................................... 32 10.1 HP_EthernetPort ....................................................................................................................... 33 10.2 HP_EthernetDevice .................................................................................................................. 33 10.3 HP_EthernetTeam .................................................................................................................... 34 10.4 HP_EthernetTeamMember ....................................................................................................... 34 10.5 HP_HostedEthernetTeam ......................................................................................................... 34 10.6 HP_EthernetLANEndpoint ........................................................................................................ 34 10.7 HP_EthernetPortToLANEndpoint ............................................................................................. 35 10.8 HP_EthernetTeamToLANEndpoint ........................................................................................... 35 10.9 HP_EthernetLANHostedAccessPoint ....................................................................................... 35 10.10 HP_IPBindsToEthernetLANEndpoint ....................................................................................... 35 10.11 HP_EthernetStatistics ............................................................................................................... 35 10.12 HP_EthernetPortStatisticalData ................................................................................................ 36 10.13 HP_EthernetLANEndpointStatisticalData ................................................................................. 36 10.14 HP_EthernetCollection.............................................................................................................. 36 10.15 HP_EthernetMemberOfCollection ............................................................................................ 37 10.16 HP_EthernetGroupHostedCollection ........................................................................................ 37 10.17 HP_RegisteredProfile ............................................................................................................... 37 10.18 HP_EthernetPortControllerPCIDevice ...................................................................................... 37 10.19 HP_EthernetPortController ....................................................................................................... 37


4 Version 1.1.0

Figures

Figure 1 – HP Ethernet Teaming: Class Diagram....................................................................................... 11 Figure 2 -- HP Ethernet Teaming: Hierarchy Diagram 1 ............................................................................. 12 Figure 3 -- HP Ethernet Teaming: Hierarchy Diagram 2 ............................................................................. 13 Figure 4 – One Ethernet Port, One non-VLAN Ethernet Interface Object Diagram ................................... 25 Figure 5 – One Ethernet Port, One VLAN Ethernet Interface Object Diagram ........................................... 26 Figure 6 – One Ethernet Port, Two Ethernet Interfaces Object Diagram ................................................... 27 Figure 7 – One Ethernet Team of Two Ethernet Ports, One non-VLAN Ethernet Interface Object Diagram28 Figure 8 – One Ethernet Team of Two Ethernet Ports, One VLAN Ethernet Interface Object Diagram .... 29 Figure 9 – One Ethernet Team of Two Ethernet Ports, Two VLAN Ethernet Interfaces Object Diagram .. 30

Version 1.1.0 5

Tables

Table 1 – Related Profiles ........................................................................................................................... 10 Table 2 – Team Redundancy Status to Team Group Operational Status .................................................. 15 Table 3 – Member Operational Status to Team Redundancy Status ........................................................ 16 Table 4 – Operations: HP_EthernetDevice ................................................................................................ 20 Table 5 – Operations: HP_EthernetTeamMember .................................................................................... 21 Table 6 – Operations: HP_HostedEthernetTeam ...................................................................................... 21 Table 7 – Operations: HP_EthernetPortToLANEndpoint ........................................................................... 21 Table 8 – Operations: HP_EthernetTeamToLANEndpoint ........................................................................ 22 Table 9 – Operations: HP_EthernetLANHostedAccessPoint .................................................................... 22 Table 10 – Operations: HP_IPBindsToEthernetLANEndpoint ................................................................... 22 Table 11 – Operations: HP_EthernetPortStatisticalData ........................................................................... 23 Table 12– Operations: HP_EthernetLANEndpointStatisticalData ............................................................. 23 Table 13– Operations: HP_EthernetMemberOfCollection ......................................................................... 24 Table 14 – Operations: HP_EthernetGroupHostedCollection ................................................................... 24 Table 15 – Operations: HP_EthernetControllerPCIDevice ........................................................................ 24 Table 15 – CIM Elements – HP Ethernet Teaming Profile ......................................................................... 33 Table 16 – Class: HP_EthernetPort ............................................................................................................ 33 Table 17 – Class: HP_EthernetDevice ....................................................................................................... 33 Table 18 – Class: HP_EthernetTeam ......................................................................................................... 34 Table 19 – Class: HP_EthernetTeamMember ............................................................................................ 34 Table 20– Class: HP_EthernetTeam .......................................................................................................... 34 Table 21 – Class: HP_EthernetLANEndpoint ............................................................................................. 34 Table 22 – Class: HP_EthernetPortToLANEndpoint .................................................................................. 35 Table 23 – Class: HP_EthernetTeamToLANEndpoint ................................................................................ 35 Table 24 – Class: HP_EthernetLANHostedAccessPoint ............................................................................ 35 Table 25 – Class: HP_IPBindsToEthernetLANEndpoint ............................................................................ 35 Table 26 – Class: HP_EthernetStatistics .................................................................................................... 36 Table 27 – Class: HP_EthernetStatisticalData ........................................................................................... 36 Table 28 – Class: HP_EthernetStatisticalData ........................................................................................... 36 Table 29 – Class: HP_EthernetCollection ................................................................................................... 36 Table 30 – Class: HP_EthernetMemberOfCollection ................................................................................. 37 Table 31 – Class: HP_EthernetGroupHostedCollection ............................................................................. 37 Table 32 – Class: HP_RegisteredProfile ................................................................................................... 37 Table 31 – Class: HP_EthernetPortControllerPCIDevice ........................................................................... 37 Table 33 – Durable Names generated by this Profile ................................................................................. 38 Table 34 – Correlatable IDs generated by this Profile ................................................................................ 38

6 Version 1.1.0

Foreword

The HP Ethernet Teaming Profile P00117 was prepared by the HP WBEM TC.

Version 1.1.0 7

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 Ethernet Ports and Teams of Ethernet Ports in HP systems. 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.

8 Version 1.1.0

1 Scope The HP Ethernet Teaming Profile extends the management capability of referencing profiles by adding the capability to represent Ethernet Ports, Ethernet Teams of Ethernet Ports, Ethernet VLANs (Virtual LANs), and consolidated status. Currently this profile is targeted to Windows Server 2003 and Linux running on Proliant and Integrity Servers.






DMTF DSP1014, Ethernet Port Profile 1.0.0

DMTF DSP1035, Network Port Profile 1.0.0

DMTF DSP1036, IP Interface Profile 1.0.0

DMTF DSP1023, Software Inventory Profile 1.0.0

DMTF DSP1075, PCI Device Profile 1.0.0

HP WBEM TC P00100, HP Profile Registration Profile 1.0.0

HP WBEM TC P00107, HP Consolidated Status Profile 1.0.0

2.2 References under Development



Proliant Networking on Windows Operating Systems white papers – Downloadable from http://h18004.www1.hp.com/products/servers/networking/whitepapers.html




http://h18004.www1.hp.com/products/servers/networking/whitepapers.html

Version 1.1.0 9

can used for statements of possibility and capability, whether material, physical or causal cannot used for statements of possibility and capability, whether material, physical or causal conditional used to indicate requirements strictly to be followed in order to conform to the document when the specified conditions are met mandatory used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted may used to indicate a course of action permissible within the limits of the document need not used to indicate a course of action permissible within the limits of the document optional used to indicate a course of action permissible within the limits of the document referencing profile Indicates a profile which owns the definition of this class and can include a reference to this profile in its “Related Profiles” section. shall used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted shall not used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted should used to indicate that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others, or that a certain course of action is preferred but not necessarily required should not used to indicate that a certain possibility or course of action is deprecated but not prohibited team refers to the concept of multiple Ethernet Ports on the same server, working together as a single Ethernet Port, providing fault tolerance and load balancing.

10 Version 1.1.0


None.

5 Synopsis Profile Name: HP Ethernet Teaming

Version: 1.1.0



Central Classes: HP_EthernetPort

Scoping Classes: Same as defined in DSP1014, Ethernet Port Profile 1.0.0

Extends: DMTF DSP1014, Ethernet Port Profile 1.0.0

Specializes: HP WBEM TC P00107, HP Consolidated Status Profile 1.0.0



DSP1014 – Ethernet Port Profile DMTF 1.0.0 Extends

DSP1036 – IP Profile DMTF 1.0.0 Mandatory

DSP1075 – PCI Device Profile DMTF 1.0.0 Optional





6 Description The HP Ethernet Teaming Profile describes the properties of HP Ethernet Ports, HP Ethernet Port Teams, HP Ethernet Port VLANs, and HP Ethernet Collections in a managed system. Also included are definitions of associations that describe the relationships among HP Ethernet Ports, HP Ethernet Teams, HP Ethernet VLANs, and HP Ethernet Collections. Figure 1 represents the class diagram for the HP Ethernet Teaming Profile. Figure 2 and Figure 3 represent the inheritance hierarchies for classes described in this profile.

Version 1.1.0 11

HP_EthernetPort-Defined in this profile

HP_EthernetLANEndpoint-Defined in this profile

1

0..*

HP_EthernetPortToLANEndpoint

HP_ComputerSystem-See HP Base Server Profile

1

*

HP_EthernetLANHostedAccessPoint

CIM_IPProtocolEndpoint-See DMTF1036 IP Interface Profile

1

* HP_IPBindsToEthernetLANEndpoint

HP_EthernetStatistics-Defined in this profile

1

1

HP_EthernetLANEndpointStatisticalData

HP_EthernetCollection-Defined in this profile 1

*

HP_EthernetMemberOfCollection

HP_EthernetTeam-Defined in this profile

*

1

HP_EthernetTeamToLANEndpoint

1

1

HP_EthernetPortStatisticalData

1

*


HP_RegisteredProfile-See HP Profile Registration Profile

CIM_SoftwareIdentity-See DMTF DSP 1023 Firmware Inventory Profile

11

CIM_ElementSoftwareIdentity

1

1


1

*HP_EthernetDevice

1

1

HP_EthernetGroupHostedCollection

HP_GroupSystemSpecificCollectin-See HP Consolidated Status Profile

1

*

HP_EthernetTeamMember

HP_HostedEthernetTeam

HP_EthernetPortController-defined in this profile

-(see DMTF 1075 PCI Device Profile)CIM_PCIDevice

*

*

CIM_ControlledBy

*

*

HP_EthernetPortControllerPCIDevice

Figure 1 – HP Ethernet Teaming: Class Diagram

12 Version 1.1.0

CIM_EthernetPort-See DMTF Ethernet Port Profile

HP_EthernetPort

CIM_EthernetPortStatistics

HP_EthernetStatistics

HP_GroupRedundancySet-See HP Consolidated Status Profile

CIM_RedundancySet-

HP_GroupSystemSpecificCollection-See HP Consolidated Status Profile

HP_EthernetCollection

CIM_SystemDevice-See DMTF Ethernet Port Profile

HP_EthernetDevice

CIM_SystemSpecificCollection CIM_MemberOfCollection

HP_EthernetMemberOfCollection-See HP Consolidated Status Profile

CIM_ElementStatisticalData


HP_EthernetTeam-Capabilities-CapabilitiesDescriptions-EnalbedCapabilites-EnabledDefault-OtherEnabledCapabilites-Speed-Active MaximumTransmissionUnit CIM_ElementStatisticalData


Figure 2 -- HP Ethernet Teaming: Hierarchy Diagram 1

Version 1.1.0 13

-See HP Consolidated Status ProfileCIM_MemberOfCollection

-Role-MemberOperationalStatus-MemberStatusDescriptions

HP_EthernetTeamMember

-See DMTF Ethernet Port ProfileCIM_DeviceSAPImplementation


-See DMTF Ethernet Port ProfileCIM_BindsToLANEndpoint

HP_IPBindsToEthernetLANEndpoint

-See HP Consolidated Status ProfileHP_GroupHostedCollection


CIM_HostedCollection-See DMTF Ethernet Port Profile

CIM_HostedAccessPoint


-See DMTF Ethernet Port ProfileCIM_LANEndpoint

-VLANId-VLANName

HP_EthernetLANEndpoint

CIM_Dependecy




Figure 3 -- HP Ethernet Teaming: Hierarchy Diagram 2

HP_EthernetPort instances represent physical Ethernet Ports in the system. HP_EthernetPort can be configured into HP Ethernet Teams that are represented by instances of HP_EthernetTeam. HP_EthernetPort instances that are members of the Ethernet Team are associated with the HP_EthernetTeam, via the association, HP_EthernetTeamMember. These Ethernet Teams add fault tolerance and load balancing to Ethernet Ports. Each HP_EthernetPort instance is associated with its scoping system via the association, HP_EthernetDevice. An instance of HP_EthernetCollection is used to consolidate the status of instances of HP_EthernetTeam and instances of HP_EthernetPort. Members of the Ethernet Collection are associated with the Collection via instances of HP_EthernetMemberOfCollection. An instance of HP_EthernetPort will not be both a member of an HP_EthernetTeam and HP_EthernetCollection. Only HP_EthernetPort instances that are not configured into a team will be directly associated with HP_EthernetCollection.

Ethernet Interfaces exposed to the Operating System are represented by instances of HP_EthernetLANEndpoint. An instance of HP_EthernetLANEndpoint, representing an Ethernet Interface

14 Version 1.1.0

for an Ethernet Port is associated to the HP_EthernetPort via the HP_EthernetPortToLANEndpoint association. An instance of HP_EthernetLANEndpoint representing an Ethernet Interface for an Ethernet Team is associated to the HP_EthernetTeam via the HP_EthernetTeamToLANEndpoint association. Each HP_EthernetLANEndpoint instance is associated with its scoping system via the association HP_EthernetLANHostedAccessPoint. Instances of HP_EthernetLANEndpoint are associated to instances of CIM_IPProtocolEndpoint via the HP_IPBindsToEthernetLANEndpoint association.

Ethernet Statistics are represented by instances of HP_EthernetStatistics. Ethernet Statistics are reported for Ethernet Ports and Ethernet Interfaces (LAN Endpoints). Instances of HP_EthernetStatistics are associated to instances of HP_EthernetPort and instances of HP_EthernetLANEndpoint via the HP_EthernetStatisticalData association.


7.1 HP_EthernetPort

HP Ethernet Port modeling is mandatory. There shall be one instance of HP_EthernetPort for each enabled HP Ethernet Port.

Instances of HP_EthernetPort shall be associated to the single instance of the Computer System, HP_ComputerSystem, through the HP_EthernetDevice association.

When configured into a team, instances of HP_EthernetPort shall be associated to an instance of HP_EthernetTeam through the HP_EthernetTeamMember association. An instance of HP_EthernetPort shall not be associated to multiple instances of HP_EthernetTeam because an Ethernet Port cannot be configured into multiple teams.

When not configured into a team instances of HP_EthernetPort shall be associated to the single instance of the Ethernet Collection, HP_EthernetCollection, through the HP_EthernetMemberOfCollection association. Instances of HP_EthernetPort that are associated to instances of HP_EthernetTeam shall not be associated to the instance of HP_EthernetCollection.

7.1.1 IdentifyingDescriptions[]

HP_EthernetPort.IdentifyingDescriptions[] property is optional. If implemented, this property shall conform to standard tags defined by the DMTF and the HP WBEM TC.

7.1.2 OperationalStatus[]

HP_EthernetPort.OperationalStatus[] property is mandatory. The first element of this property shall contain the current operational status of the HP_EthernetPort.

7.1.3 OtherIdentifyInfo[]

HP_EthernetPort.OtherIdentifyInfo[] property is optional. . If implemented, this property shall conform to standard tags defined by the DMTF and the HP WBEM TC.

7.2 HP_EthernetDevice

Instances of HP_EthernetPort shall be associated to the single instance of the Computer System, HP_ComputerSystem, which contains them through the HP_EthernetDevice association.

Version 1.1.0 15

7.3 HP_EthernetTeam

HP Ethernet Port Team modeling is conditional upon configuration of one or more Ethernet Teams. There shall be one instance of HP_EthernetTeam for each configured team of HP Ethernet Ports.

Instances of HP_EthernetTeam shall be associated to the single instance of the Ethernet Collection, HP_EthernetCollection, through the HP_EthernetMemberOfCollection.

Instances of HP_EthernetTeam shall be associated to the Computer System, HP_ComputerSystem, through the HP_HostedEthernetTeam association.

7.3.1 HP_EthernetTeam.ActiveMaximumTransmissionUnit

HP_EthernetTeam.ActiveMaximumTransmissionUnit is mandatory. This property shall describe the active or negotiated maximum transmission unit (MTU) that can be supported.

7.3.2 HP_EthernetTeam.TeamCapabilities[]

HP_EthernetTeam.TeamCapabilities[] property is optional. If implemented, this property shall contain information about the capabilities of the HP_EthernetTeam.

7.3.3 HP_EthernetTeam.TeamEnabledCapabilities[]

HP_EthernetTeam.TeamEnabledCapabilities[] property is optional. If implemented, this property shall specify which capabilities in HP_EthernetTeam.TeamCapabilities[] are enabled.

7.3.4 HP_EthernetTeam.GroupOperationalStatus[]

HP_EthernetTeam.GroupOperationalStatus[] is mandatory. The first element of this property contains the current Operational Status of the HP_EthernetTeam. Values shall be limited to “OK”, “Degraded” and “Error”. HP_EthernetTeam.GroupOperationalStatus is dependent upon HP_EthernetTeam.RedundancyStatus and the values shall be translated according to Table 2.

Table 2 – Team Redundancy Status to Team Group Operational Status

RedundancyStatus GroupOperationalStatus[0]

Fully Redundant OK

Degraded Redundancy Degraded

Redundancy Lost Degraded

Overall Failure Error

7.3.5 HP_EthernetTeam.LoadBalanceAlgorithm

HP_EthernetTeam.LoadBalanceAlgorithm is mandatory. This property contains the current load balancing algorithm for the HP_EthernetTeam.

7.3.6 HP_EthernetTeam.OtherLoadBalanceAlgorithm

HP_EthernetTeam.OtherLoadBalanceAlgorithm property is conditional if HP_EthernetTeam.LoadBalanceAlgorithm is set to “Other”. This property contains the current load balancing algorithm..

16 Version 1.1.0

7.3.7 HP_EthernetTeam.TeamOperatingMode

HP_EthernetTeam.TeamOperatingMode is mandatory. This property contains the configured Operating Mode, also known as the Team Type.

HP_EthernetTeam.TeamCurrentOperatingMode

HP_EthernetTeam.TeamCurrentOperatingMode is mandatory. This property contains the current Operating Mode. The current Operating Mode may be different from the configured Operating Mode.

7.3.8 HP_EthernetTeam.RedundancyStatus

HP_EthernetTeam.RedundancyStatus is mandatory. This property contains the current Redundancy Status of the HP_EthernetTeam. Values shall be limited to “Fully Redundant”, “Degraded Redundancy”, “Redundancy Lost” and “Overall Failure”. HP_EthernetTeam.RedundancyStatus is an aggregation of each team member’s HP_EthernetTeamMember.MemberOperationalStatus[0] and translated according to Table 3.

Table 3 – Member Operational Status to Team Redundancy Status

HP_EthernetTeamMember.MemberOperationalStatus[0] HP_EthernetTeam.RedundancyStatus

All “OK” Fully Redundant

Only one “OK” or “Degraded” Redundancy Lost

None “OK” or “Degraded” Overall Failure

All other cases Degraded Redundancy

7.3.9 HP_EthernetTeam.Speed

HP_EthernetTeam.Speed property is mandatory. This property shall contain the bandwidth of the HP_EthernetTeam in bits per Second

7.4 HP_EthernetTeamMember

Instances of HP_EthernetPort shall be associated to an instance of HP_EthernetTeam through the HP_EthernetTeamMember association, when the Ethernet Port is configured as a member of an Ethernet Team.

7.4.1 HP_EthernetTeamMember.MemberOperationalStatus[]

HP_EthernetTeamMember.MemberOperationalStatus[] is mandatory. The first element of this property shall contain the HP_EthernetPort member status in the HP_EthernetTeam. A value of “Degraded” indicates that the HP_EthernetPort member is currently participating in the team but it is not operating as configured.

Note that HP_EthernetPort.OperationalStatus[0] may be “OK” for an instance of HP_EthernetPort which is a member of an HP_EthernetTeam, while the associated HP_EthernetTeam.MemberOperationalStatus[0] may be “Degraded” as a result of the Team Member not operating as configured.

7.4.2 HP_EthernetTeamMember.MemberStatusDescriptions[]

HP_EthernetTeamMember.MemberStatusDescriptions[] is conditional. If the HP_EthernetMember.OperationalStatus[0] is not “OK”, the first element of this property shall contain the probable cause.

Version 1.1.0 17

7.4.3 HP_EthernetTeamMember.Role

HP_EthernetTeamMember.Role is mandatory. This property contains the HP_EthernetPort member role in the HP_EthernetTeam.

7.5 HP_HostedEthernetTeam

Instances of HP_EthernetTeam shall be associated to the single instance of the Computer System, HP_ComputerSystem, which contains them through the HP_EthernetTeam association.

7.6 HP_EthernetLANEndpoint

HP Ethernet LAN Endpoint modeling is mandatory. There shall be one instance of HP_EthernetLANEndpoint for each Ethernet Interface exposed to the Operating System.

An Ethernet Port that is not a member of a team and does not have any VLANs configured, exposes a single Ethernet Interface.

An Ethernet Port that is not a member of a team and has VLANs configured, exposes an Ethernet Interface for each VLAN.

A Team of Ethernet Ports that does not have VLANs configured exposes a single Ethernet Interface. Note that the Ethernet Ports that are members of a Team do not expose Ethernet Interfaces directly.

A Team of Ethernet Ports that has VLANs configured exposes an Ethernet Interface for each VLAN.

Instances of HP_EthernetPort shall be associated to instances of HP_EthernetLANEndpoint through the HP_EthernetPortToLANEndpoint association.

Instances of HP_EthernetTeam shall be associated to instances of HP_EthernetLANEndpoint through the HP_EthernetTeamToLANEndpoint association.

Instances of HP_EthernetLANEndpoint shall be associated to the single instance of the Computer System, HP_ComputerSystem, through the HP_EthernetLANHostedAccessPoint association.

7.6.1 HP_EthernetLANEndpoint.OperationalStatus[]

HP_EthernetLANEndpoint.OperationalStatus[] is mandatory. HP_EthernetLANEndpoint.OperationalStatus[0] is the same as the associated HP_EthernetPort.OperationalStatus[0] (when associated directly via HP_EthernetPortToLANEndpoint) or the associated HP_EthernetTeam.GroupOperationalStatus[0] (when associated directly via HP_EthernetTeamToLANEndpoint).

7.6.2 HP_EthernetLANEndpoint.VLANId

HP_EthernetLANEndpoint.VLANId property is conditional, upon configuration of one or more VLANs. When the instance of HP_EthernetLANEndpoint represents a VLAN, this property shall be set to the VLAN identifier.

7.6.3 HP_EthernetLANEndpoint.VLANName

HP_EthernetLANEndpoint.VLANName property is conditional, upon configuration of one or more VLANs. When the HP_EthernetLANEndpoint.VLANId property is provided, this property shall be set to the name of the configured VLAN.

7.7 HP_EthernetPortToLANEndpoint

Instances of HP_EthernetPort shall be associated to instances of HP_EthernetLANEndpoint through the HP_EthernetPortToLANEndpoint association.

18 Version 1.1.0

If the HP_EthernetPort is not a member of a team and no VLANs are configured, there is a single instance of HP_EthernetPortToLANEndpoint.

If the HP_EthernetPort is not a member of a team and VLANs are configured, there shall be an instance of HP_EthernetPortToLANEndpoint for each VLAN.

If the HP_EthernetPort is a member of a team there shall not be an instance of HP_EthernetPortToLANEndpoint. The Ethernet LAN Endpoint is associated with the Ethernet Team.

7.8 HP_EthernetTeamToLANEndpoint

Instances of HP_EthernetTeam shall be associated to instances of HP_EthernetLANEndpoint through the HP_EthernetTeamToLANEndpoint association.

If the HP_EthernetTeam does not have VLANs configured, there is a single instance of HP_EthernetTeamToLANEndpoint.

If the HP_EthernetTeam has VLANs configured, there shall be an instance of HP_EthernetTeamToLANEndpoint for each VLAN.

7.9 HP_EthernetLANHostedAccessPoint

Instances of HP_EthernetLANEndpoint shall be associated to the single instance of the Computer System, HP_ComputerSystem, through the HP_EthernetLANHostedAccessPoint association.

7.10 HP_IPBindsToEthernetLANEndpoint

Instances of CIM_IPProtocolEndpoint shall be associated to instances of HP_EthernetLANEndpoint, through the HP_IPBindsToEthernetLANEndpoint association.

7.11 HP_EthernetStatistics

HP Ethernet Statistics modeling is conditional, upon support by the underlying Ethernet drivers. Ethernet Statistics are reported for Ethernet Ports and Ethernet Interfaces. There shall be one instance of HP_EthernetStatistics for each instance of HP_EthernetPort. There shall be one instance of HP_EthernetStatistics for each instance of HP_EthernetLANEndpoint.

Instances of HP_EthernetStatistics shall be associated to instances of HP_EthernetPort through the HP_EthernetStatisticalData association.

Instances of HP_EthernetStatistics shall be associated to the instances of HP_EthernetLANEndpoint through the HP_EthernetStatisticalData association.

7.12 HP_EthernetPortStatisticalData

Instances of HP_EthernetStatistics shall be associated to instances of HP_EthernetPort through the HP_EthernetPortStatisticalData association.

7.13 HP_EthernetLANEndpointStatisticalData

Instances of HP_EthernetStatistics shall be associated to instances of HP_EthernetLANEndpoint through the HP_EthernetLANEndpointStatisticalData association.

7.14 HP_EthernetCollection

HP Ethernet Collection modeling is mandatory. There shall be a single instance of HP_EthernetCollection which is a collection of all HP_EthernetPort instances that expose an Ethernet

Version 1.1.0 19

Interface, (i.e., have an association to one or more instances of HP_EthernetLANEndpoint) and all instances of HP_EthernetTeam.

Instances of HP_EthernetPort (not configured in an Ethernet Team) shall be associated to the single instance of the Ethernet Adapter collection, HP_EthernetCollection, through the HP_EthernetMemberOfCollection association.

Instances of HP_EthernetTeam shall be associated to the single instance of Ethernet Adapter collection, HP_EthernetCollection, through the HP_EthernetMemberOfCollection association.

The single instance of HP_EthernetCollection shall be associated to the single instance of the Computer System, HP_ComputerSystem through the HP_EthernetGroupHostedCollection association.

7.14.1 GroupOperationalStatus[]

HP_EthernetColllection.GroupOperationalStatus[] is mandatory. This property contains the Operational Status of the HP_EthernetCollection. The first element of this property value shall be set to the “worst-of” Operational Status of the Collection members. The Operational Status of an HP Ethernet Port Collection member is HP_EthernetPort.OperationalStatus[0] and the Operational Status of an HP Ethernet Team is HP_EthernetTeam.GroupOperationalStatus[0].

7.15 HP_EthernetMemberOfCollection

Instances of HP_EthernetPort shall be associated to the single instance of the HP Ethernet Collection, HP_EthernetCollection, through the HP_EthernetMemberOfCollection association.

Instances of HP_EthernetTeam shall be associated to the single instance of HP Ethernet Collection, HP_EthernetCollection, through the HP_EthernetMemberOfCollection.

7.16 HP_EthernetGroupHostedCollection

The single instance of HP_EthernetCollection is associated to the single instance of the Computer System, HP_ComputerSystem through the HP_EthernetGroupHostedCollection association.

7.17 HP_EthernetPortControllerPCIDevice (Optional)

This association is optional. Instances of HP_EthernetPortController can be associated to one or more instances of CIM_PCIDevice through the HP_EthernetPortControllerPCIDevice association.

7.18 HP_EthernetPortController (Conditional)

HP Ethernet PortController modeling is Conditional .

If the provider implementation does not support the optional CIM_PortController.ControllerVersion property, the HP_EthernetPortController class need not be implemented. If the provider implementation supports the optional CIM_PortController.ControllerVersion property and all the supported controllers report their version as an Integer, the HP_EthernetPortController class need not be implemented . If the provider implementation supports the optional CIM_PortController.ControllerVersion property and any supported controllers report their version as a String, the HP_EthernetPortController class shall be implemented.

7.18.1 HP_EthernetPortController.ExtendedControllerVersion

8 HP_EthernetPortController. ExtendedControllerVersion is a conditional Property and shall be set when the controller version is of String type. The ExtendedControllerVersion can be set in

20 Version 1.1.0

addition to the optional ControllerVersion property, when the controller version is of integer type.Methods

None.




• GetInstance

• Associators

• AssociatorNames

• References

• ReferenceNames




8.2 HP_EthernetPort



Table 4 lists operations that either have special requirements beyond those from DSP0200 v1.2 or shall not be supported. All other operations may be supported as defined in DSP0200 v1.2.

Table 4 – Operations: HP_EthernetDevice






8.4 HP_EthernetTeam




Version 1.1.0 21

Table 5 – Operations: HP_EthernetTeamMember








Table 6 – Operations: HP_HostedEthernetTeam










Table 7 – Operations: HP_EthernetPortToLANEndpoint








22 Version 1.1.0

Table 8 – Operations: HP_EthernetTeamToLANEndpoint








Table 9 – Operations: HP_EthernetLANHostedAccessPoint








Table 10 – Operations: HP_IPBindsToEthernetLANEndpoint








8.13 HP_EthernetPortStatisticallData


Version 1.1.0 23

Table 11 – Operations: HP_EthernetPortStatisticalData






8.14 HP_EthernetLANEndpointStatisticallData


Table 12– Operations: HP_EthernetLANEndpointStatisticalData










24 Version 1.1.0

Table 13– Operations: HP_EthernetMemberOfCollection








Table 14 – Operations: HP_EthernetGroupHostedCollection






8.18 HP_EthernetControllerPCIDevice


Table 15 – Operations: HP_EthernetControllerPCIDevice






8.19 HP_EthernetPortController


9 Use Cases

9.1 Object Diagrams

9.1.1 One Ethernet Port, one non-VLAN Ethernet Interface.

Figure 4 represents a single Ethernet Port exposing a single non-VLAN Ethernet Interface. Note that there is a single instance of HP_EthernetStatistics.

Version 1.1.0 25

port1:HP_EthernetPort

endpoint1:HP_EthernetLANEndpoint



HP_EthernetDevice


CIM_IPProtocolEndpointHP_IPBindsToEthernetLANEndpoint

stats1:HP_EthernetStatistics


collection1:HP_EthernetCollection


HP_EthernetGroupHostedCollectionHP_EthernetPortStatisticalData


fw1:CIM_SoftwareIdentity

HP_ElementConformstToProfile


Figure 4 – One Ethernet Port, One non-VLAN Ethernet Interface Object Diagram

9.1.2 One Ethernet Port, One VLAN Ethernet Interface

Figure 5 represents a single Ethernet Port exposing a single VLAN Ethernet Interface. Note that there are two instances of HP_EthernetStatistics.

26 Version 1.1.0


-VLANId: 1-VLANName: One




HP_EthernetDevice


CIM_IPProtocolEndpointHP_IPBindsToEthernetLANEndpoint






HP_ElementConformstToProfile




HP_EthernetortStatisticalData


Figure 5 – One Ethernet Port, One VLAN Ethernet Interface Object Diagram

9.1.3 One Ethernet Port, Two VLAN Ethernet Interfaces

Figure 6 represents a single Ethernet Port exposing two VLAN Ethernet Interfaces.

Version 1.1.0 27




HP_EthenetPortToLANEndpoint


HP_EthernetDevice


CIM_IPProtocolEndpoint







-VLANId: 2-VLANName: Two






HP_IPBindsToHPEthernetLANEndpoint




Figure 6 – One Ethernet Port, Two Ethernet Interfaces Object Diagram

28 Version 1.1.0

9.1.4 One Ethernet Team of Two Ethernet Ports, One non-VLAN Ethernet Interface

Figure 7 represents a single Ethernet Team of two Ethernet Ports exposing a single non-VLAN Ethernet Interface.




HP_EthernetDevice


HP_EthernetPortStatitisticalData


HP_EthernetLANEndpointStatitisticalData






HP_IPBindsToEThernetLANEndpoint


HP_EthernetDevice

team1:HP_EthernetTeam



HP_EthernetTeamMember HP_EthernetTeamMember



Figure 7 – One Ethernet Team of Two Ethernet Ports, One non-VLAN Ethernet Interface Object Diagram

Version 1.1.0 29

9.1.5 One Ethernet Team of Two Ethernet Ports, One VLAN Ethernet Interface

Figure 8 represents a single Ethernet Team of two Ethernet Ports exposing a single VLAN Ethernet Interface.





HP_EthernetDevice


HP_EthernetPortStatitisticalData


HP_EthernetLANEndpointStatitisticalData






HP_IPBindsToEThernetLANEndpoint


HP_EthernetDevice







Figure 8 – One Ethernet Team of Two Ethernet Ports, One VLAN Ethernet Interface Object Diagram

30 Version 1.1.0

9.1.6 One Ethernet Team of Two Ethernet Ports, Two VLAN Ethernet Interfaces

Figure 9 represents a single Ethernet Team of two Ethernet Ports exposing two VLAN Ethernet Interfaces.

-VLANId: 4-VLANName: Four

endpoint2:HP_EthenetLANEndpoint


system1:HP_ComputerSystemHP_EthernetDevice












HP_EthernetDevice




-VLANId: 3-VLANName: Three


stats3:HP_EhernetStatistics









Figure 9 – One Ethernet Team of Two Ethernet Ports, Two VLAN Ethernet Interfaces Object Diagram

Version 1.1.0 31

9.2 Retrieve the Operational Status of an Ethernet Port

For a given instance of HP_EthernetPort, the HP_EthernetPort.OperationalStatus[0] contains the Ethernet Port Operational Status.

9.3 Retrieve the Operational Status of an Ethernet LAN Endpoint

For a given instance of HP_EthernetLANEndpoint, the HP_EthernetLANEndpoint.OperationalStatus[0] contains the Ethernet LAN Endpoint Operational Status.

9.4 Retrieve the Operational Status of an Ethernet Team

For a given instance of HP_EthernetTeam, the HP_EthernetTeam.GroupOperationalStatus[0] contains the Ethernet Team Operational Status.

9.5 Retrieve the Redundancy Status of an Ethernet Team

For a given instance of HP_EthernetTeam, the HP_EthernetTeam.RedundancyStatus contains the Ethernet Team Redundancy Set Status.

9.6 Retrieve the Members of an Ethernet Team

For a given instance of HP_EthernetTeam, each associated instance of HP_EthernetTeamMember provides an instance of an HP_EthernetPort team member.

9.7 Retrieve the Failed or Degraded Members of an Ethernet Team

For a given instance of HP_EthernetTeam, the property HP_EthernetTeamMember.MemberOperationalStatus[0] for each associated instance of HP_EthernetTeamMember contains the Operational Status for the HP_EthernetPort Team Member. A status of “OK” indicates that the HP_EthernetPort member is participating in the team as configured. A status of “Degraded” indicates that the HP_EthernetPort member is participating in the team, but is not operating as configured. Any other indicates that the HP_EthernetPort member is no longer participating in the team. The HP_EthernetTeamMember association can then be used to identify the HP_EthernetPort.

9.8 Retrieve the VLANs on an Ethernet Port

For a given instance of HP_EthernetPort, each associated instance of HP_EthernetPortToLANEndpoint provides an instance of an HP_EthernetLANEndpoint. If the HP_EthernetLANEndpoint.VLANId is populated, and not 0 or 4095, then the Ethernet LAN Endpoint is a VLAN.

9.9 Retrieve the VLANs on an Ethernet Team

For a given instance of HP_EthernetTeam, each associated instance of HP_EthernetTeamToLANEndpoint provides an instance of an HP_EthernetLANEndpoint. If the HP_EthernetLANEndpoint.VLANId is populated, and not 0 or 4095, then the Ethernet LAN Endpoint is a VLAN.

9.10 Retrieve the IP Addresses associated with an Ethernet Port

For a given instance of HP_EthernetPort, each associated instance of HP_EthernetPortToLANEndpoint provides an instance of HP_EthernetLANEndpoint. For each instance of HP_EthernetLANEndpoint, each associated instance of CIM_BindsToLANEndpoint provides an instance of CIM_IPProtocolEndpoint. The CIM_IPProtocolEndpoint.IPv4Address is an IPv4 address associated to the Ethernet Port.

32 Version 1.1.0

9.11 Retrieve the IP Addresses associated with an Ethernet Team.

For a given instance of HP_EthernetTeam, each associated instance of HP_EthernetTeamToLANEndpoint provides an instance of HP_EthernetLANEndpoint. For each instance of HP_EthernetLANEndpoint, each associated instance of CIM_BindsToLANEndpoint provides an instance of CIM_IPProtocolEndpoint. The CIM_IPProtococlEndpoint.IPv4Address is an IPv4 address associated to the Ethernet Team.

9.12 Retrieve the Ethernet Collection Operational Status

For the given instance of HP_EthernetCollection, HP_EthernetColllection.GroupOperationalStatus[0] contains the Operational Status for the Ethernet Collection.

9.13 Retrieve the Failed Members of an Ethernet Collection

For the given instance of HP_EthernetCollection, each instance of HP_EthernetMemberOfCollection identifies either an HP_EthernetPort or and HP_EthernetTeam that is a member of the Ethernet Collection.

For an HP_EthernetPort member of the Collection, an HP_EthernetPort.OperationalStatus[0] of not “OK” for the associated HP_EthernetPort, indicates a failed HP_EthernetPort member of the Ethernet Collection.

For an HP_EthernetTeam member of the Collection, an HP_EthernetTeam.GroupOperationalStatus[0] of not “OK” indicates a degraded or failed HP_EthernetTeam member of the Ethernet Collection. See Section 9.7, “Retrieve the Failed or Degraded Members of an Ethernet Team” to further identify the HP_EthernetPort member of the HP_EthernetTeam.

9.14 Retrieve the PCI Device IDs for an Ethernet PortController

For the given instance of CIM_EthernetPortController or HP_EthernetPortController, each instance of CIM_PCIDevice associated via the CIM_ConcreteIdentity association identifies either a CIM_PCIDevice that contains the PCI Device information for the EthernetPortController.

9.15 Retrieve the Controller Version for Ethernet Port Controller

For the given instance of HP_EthernetPortController, if theExtendedControllerVersion property is set, it contains the controller version as a string. If the ExtendedControllerVersion property does not exist (provider implementation used CIM_EthernetPortController class) or is set to an empty or NULL string, if the ControllerVersion property is set, it contains the controller version as an integer. If the ControllerVersion property is not set, the provider does not support reporting controller version.


Version 1.1.0 33

Table 15 – CIM Elements – HP Ethernet Teaming Profile


Classes HP_EthernetPort Mandatory See Section 7.1 and 10.1

HP_EthernetDevice Mandatory See Section 7.2 and 10.2

HP_EthernetTeam Conditional See Section 7.3 and 10.3

HP_EthernetTeamMember Conditional See Section 7.4 and 10.4

HP_HostedEthernetTeam Conditional See Section 7.5 and 10.5

HP_EthernetLANEndpoint Mandatory See Section 7.6 and 10.6

HP_EthernetPortToLANEndpoint Conditional See Section 7.7 and 10.7

HP_EthernetTeamToLANEndpoint Conditional See Section 7.8 and 10.8

HP_EthernetLANHostedAccessPoint Mandatory See Section 7.9 and 10.9

HP_IPBindsToEthernetLANEndpoint Mandatory See Section 7.10 and 10.10

HP_EthernetPortStatistics Conditional See Section 7.11 and 10.11

HP_EthernetLANEndpointStatisticalData Conditional See Section 7.13 and 10.13

HP_EthernetPortStatisticalData Conditional See Section 7.12 and 10.12

HP_EthernetCollection Mandatory See Section 7.14 and 10.14

HP_EthernetMemberOfCollection Mandatory See Section 7.15 and 10.15

HP_EthernetGroupHostedCollection Mandatory See Section 7.16 and 10.16


HP_EthernetPortControllerPCIDevice Optional See section 7.17 and 10.18

HP_EthernetPortController Conditional See section 7.18 and 10.19 Indications


10.1 HP_EthernetPort

HP_EthernetPort is used to represent an Ethernet Port in a managed system.

Table 16 – Class: HP_EthernetPort


IdentifyingDescriptions[] Optional See Section 7.1.1

OperationalStatus[] Mandatory See Section 7.1.2

OtherIdentifyingInfo[] Optional See Section 7.1.3


HP_EthernetDevice is used to associate an Ethernet Port to the Computer System in a managed system.

Table 17 – Class: HP_EthernetDevice


GroupComponent Mandatory Key: References HP_ComputerSystem

PartComponent Mandatory Key: References HP_EthernetPort

34 Version 1.1.0

10.3 HP_EthernetTeam

HP_EthernetTeam is used to represent a Team of Ethernet Ports in a managed system.

Table 18 – Class: HP_EthernetTeam


ActiveMaximumTransmissionUnit Mandatory See Section 7.3.1

TeamCapabilities Optional See Section 7.3.2

TeamEnabledCapabilities Optional See Section 7.3.3

GroupOperationalStatus[] Mandatory See Section 7.3.4

LoadBalanceAlgorithm Mandatory See Section 7.3.5

OtherLoadBalanceAlgorithm Conditional See Section 7.3.6

OperatingMode Mandatory See Section 7.3.7

CurrentOperatingMode Mandatory See Section 0

RedundancyStatus Mandatory See Section 7.3.8

Speed Mandatory See Section 7.3.9


HP_EthernetTeamMember is used to represent an Ethernet Port member of an Ethernet Team in a managed system.

Table 19 – Class: HP_EthernetTeamMember


Collection Mandatory Key: References HP_EthernetTeam

Member Mandatory Key: References HP_EthernetPort

MemberOperationalStatus[] Mandatory See Section 7.4.1

MemberStatusDescriptions[] Conditional See Section 7.4.2

Role Mandatory See Section 7.4.3


HP_EthernetDevice is used to associate an Ethernet Port to the Computer System in a managed system.

Table 20– Class: HP_EthernetTeam


OwningElement Mandatory Key: References HP_ComputerSystem

OwnedElement Mandatory Key: References HP_EthernetTeam


HP_EthernetLANEndpoint is used to represent an Ethernet LAN Endpoint in a managed system.

Table 21 – Class: HP_EthernetLANEndpoint


OperationalStatus[] Mandatory See Section 7.6.1

Version 1.1.0 35


VLANId Conditional See Section 7.6.2

VLANName Conditional See Section 7.6.3


HP_EthernetPortToLANEndpoint is used to associate an Ethernet LAN Endpoint to an Ethernet Port in a managed system.

Table 22 – Class: HP_EthernetPortToLANEndpoint


Antecedent Mandatory Key: References HP_EthernetPort

Dependent Mandatory Key: References HP_EthernetLANEndpoint


HP_EthernetTeamToLANEndpoint is used to associate an Ethernet LAN Endpoint to an Ethernet Team in a managed system.

Table 23 – Class: HP_EthernetTeamToLANEndpoint


Antecedent Mandatory Key: References HP_EthernetTeam



HP_EthernetLANHostedAccessPoint is used to associate and Ethernet LAN Endpoint to the Computer System in a managed system.

Table 24 – Class: HP_EthernetLANHostedAccessPoint





HP_IPBindsToEthernetLANEndpoint is used to associate an IP Interface to an Ethernet LAN Endpoint in a managed system.

Table 25 – Class: HP_IPBindsToEthernetLANEndpoint


Antecedent Mandatory Key: References HP_EthernetLANEndpoint

Dependent Mandatory Key: References CIM_IPProtocolEndpoint


HP_EthernetStatistics is used to represent Ethernet Statistics in a managed system.

36 Version 1.1.0

Table 26 – Class: HP_EthernetStatistics


AlignmentErrors Conditional See CIM_EthernetPortStatistics mof

BytesReceived Conditional See CIM_EthernetPortStatistics mof

BytesTransmitted Conditional See CIM_EthernetPortStatistics mof

DeferredTransmission Conditional See CIM_EthernetPortStatistics mof

ExcessiveCollisions Conditional See CIM_EthernetPortStatistics mof

FCSErrors Conditional See CIM_EthernetPortStatistics mof

InternalMACRecieveErrors Conditional See CIM_EthernetPortStatistics mof

InternalMACTransmitErrrors Conditional See CIM_EthernetPortStatistics mof

LateCollistions Conditional See CIM_EthernetPortStatistics mof

MultipleCollisionFrames Conditional See CIM_EthernetPortStatistics mof

PacketsReceived Conditional See CIM_EthernetPortStatistics mof

PacketsTransmitted Conditional See CIM_EthernetPortStatistics mof

SampleInterval Conditional See CIM_EthernetPortStatistics mof

SingleCollisionFrames Conditional See CIM_EthernetPortStatistics mof

StatisticTime Conditional See CIM_EthernetPortStatistics mof

10.12 HP_EthernetPortStatisticalData

HP_EthernetPortStatisticalData is used to associate Ethernet Ports Ethernet Statistics in a managed system.

Table 27 – Class: HP_EthernetStatisticalData


ManagedElement Mandatory Key: References HP_EthernetPort

Stats Mandatory Key: References HP_EthernetStatistics

10.13 HP_EthernetLANEndpointStatisticalData

HP_EthernetLANEndpointStatisticalData is used to associate Ethernet LAN Endpoints to Ethernet Statistics in a managed system.

Table 28 – Class: HP_EthernetStatisticalData


ManagedElement Mandatory Key: References HP_EthernetLANEndpoint

Stats Mandatory Key: References HP_EthernetStatistics


HP_EthernetCollection is used represent the collection of Ethernet Ports and Ethernet Teams in a managed system.

Table 29 – Class: HP_EthernetCollection


GroupOperationalStatus[] Mandatory See Section 7.14.1

Version 1.1.0 37


HP_EthernetMemberOfCollection is used to associate Ethernet Ports and Ethernet Teams to the Ethernet Collection in a managed system.

Table 30 – Class: HP_EthernetMemberOfCollection


Collection Mandatory Key: References HP_EthernetCollection

Member Mandatory

Key: References HP_EthernetPort or HP_EthernetTeam


HP_EthernetGroupHostedCollection is used to associate the Ethernet Collection to the Computer System in a managed system.

Table 31 – Class: HP_EthernetGroupHostedCollection



Dependent Mandatory Key: References HP_EthernetCollection





RegisteredName Mandatory "HP Ethernet Teaming"




10.18 HP_EthernetPortControllerPCIDevice

HP_EthernetPortControllerPCIDevice is used to associate the Ethernet Port Controller to the PCI Device instances.

Table 33 – Class: HP_EthernetPortControllerPCIDevice


SystemComponent Mandatory Key: References CIM_PCIDevice

SameComponent Mandatory Key: References HP_EthernetPortController

10.19 HP_EthernetPortController

The HP_EthernetPortController class is use to represent Ethernet Port Controller in managed system

38 Version 1.1.0



ExtendedControllerVersion Conditional See Section 7.17.1




HP_EthernetPort PermanentAddress Permanent MAC Address

None


Class Correlatable ID(s)



Version 1.1.0 39

ANNEX A (normative)

Change Log


0.1 06/30/2006 Initial draft 0.2 07/06/2006 Incorporated initial review comments. 0.3 7/10/2006 Incorporated additional review comments.

0.4 07/17/2006

Incorporated additional review comments. Reworked Ethernet Team and Ethernet Team Member class properties. Added Single Ethernet Port with Single VLAN instance diagram. Added Ethernet Team of Two Ethernet Ports with Single VLAN instance diagram. Added Hosted Ethernet Team class. Added Ethernet Statistics Class Properties.

1.0 8/1/2006 Incorporate WBEM TC suggestions. Added additional use cases. Minor corrections. Approved by WBEM TC. Added Operating Mode properties to Ethernet Team

1.0.1 9/14/2006 Removed Windows implementation specific references. 1.1.0 01/02/2011 Added new Property to read String type Controller Version

40 Version 1.1.0


Acknowledgments

Version 1.1.0 41




00109 Ethernet Teaming on Proliant and Integrity Systems 00117 1/9/2012 Added HP_EthernetPortController class and ExtendedControllerVersion property.

42 Version 1.1.0

Bibliography



Date: 04/22/2011

Version: 1.0.5

HP FC HBA Profile




2 HP FC HBA Profile Version 1.0.5

Contents




7.1 HPFCHBA_ComputerSystem ................................................................................................... 12 7.2 HPFCHBA_FCPort ................................................................................................................... 12 7.3 HPFCHBA_PortController ........................................................................................................ 12 7.4 HPFCHBA_FCPortStatistics ..................................................................................................... 13 7.5 HPFCHBA_LogicalPortGroup ................................................................................................... 13 7.6 HPFCHBA_PhysicalPackage ................................................................................................... 13 7.7 HPFCHBA_Product .................................................................................................................. 14 7.8 HPFCHBA_SoftwareIdentityDrv ............................................................................................... 14 7.9 HPFCHBA_FirmwareIdentityFW .............................................................................................. 14 7.10 HPFCHBA_FirmwareIdentityBIOS ........................................................................................... 14 7.11 HPFCHBA_SCSIProtocolController ......................................................................................... 15 7.12 HPFCHBA_SCSIProtocolEndpoint ........................................................................................... 15 7.13 HPFCHBA_GroupSystemSpecificCollection ............................................................................ 15

8 Methods ............................................................................................................................................... 16 8.1 Profile Conventions for Operations ........................................................................................... 16 8.2 Supported Operations ............................................................................................................... 16

9 Use Cases ........................................................................................................................................... 17 9.1 Object Diagrams ....................................................................................................................... 17 9.2 Retrieve the FC HBA Group Operational Status ...................................................................... 19 9.3 Retrieve the FC Port Status ...................................................................................................... 19

10 CIM Elements ...................................................................................................................................... 19 10.1 HPFCHBA_ComputerSystem ................................................................................................... 20 10.2 HPFCHBA_FCPort ................................................................................................................... 20 10.3 HPFCHBA_PortController ........................................................................................................ 21 10.4 HPFCHBA_FcPortStatistics ...................................................................................................... 21 10.5 HPFCHBA_LogicalPortGroup ................................................................................................... 21 10.6 HPFCHBA_PhysicalPackage ................................................................................................... 21 10.7 HPFCHBA_Product .................................................................................................................. 22 10.8 HPFCHBA_SoftwareIdentityDrv ............................................................................................... 22 10.9 HPFCHBA_FirmwareIdentityFW .............................................................................................. 22 10.10 HPFCHBA_FirmwareIdentityBIOS ........................................................................................... 22 10.11 HPFCHBA_SCSIProtocolController ......................................................................................... 23 10.12 HPFCHBA_SCSIProtocolEndpoint ........................................................................................... 23 10.13 HPFCHBA_GroupSystemSpecificCollection ............................................................................ 24 10.14 HPFCHBA_ComputerSystemFCPort ....................................................................................... 24 10.15 HPFCHBA_ComputerSystemPortController ............................................................................ 24 10.16 HPFCHBA_ComputerSystemSCSIProtocolController ............................................................. 24 10.17 HPFCHBA_ComputerSystemLogicalPortGroup ....................................................................... 25 10.18 HPFCHBA_ComputerSystemSoftwareIdentityDrv ................................................................... 25 10.19 HPFCHBA_SystemServiceAccessPoint ................................................................................... 25

Version 1.0.5 HP FC HBA Profile 3

10.20 HPFCHBA_FCPortFCPortStatistics ......................................................................................... 25 10.21 HPFCHBA_FCPortLogicalPortGroup ....................................................................................... 26 10.22 HPFCHBA_FCPortSCSIProtocolEndpoint ............................................................................... 26 10.23 HPFCHBA_SCSIProtocolControllerFCPort .............................................................................. 26 10.24 HPFCHBA_PortControllerFCPort ............................................................................................. 26 10.25 HPFCHBA_PhysicalPackagePortController ............................................................................. 27 10.26 HPFCHBA_SoftwareIdentityDrvPortController ......................................................................... 27 10.27 HPFCHBA_PortControllerFirmwareIdentityFW ........................................................................ 27 10.28 HPFCHBA_PortControllerFirmwareIdentityBIOS ..................................................................... 27 10.29 HPFCHBA_ProductPhysicalComponent .................................................................................. 28 10.30 HPFCHBA_SystemPackaging .................................................................................................. 28 10.31 HPFCHBA_ConcreteIdentity .................................................................................................... 28 10.32 HPFCHBA_GroupHostedCollection ......................................................................................... 28 10.33 HPFCHBA_FCPortGroupSystemSpecific................................................................................. 29 10.34 HP_RegisteredProfile ............................................................................................................... 29 10.35 HPFCHBA_PortControllerPCIDevice ....................................................................................... 29


Figures

Figure 1 – HP FC HBA Profile: Class Diagram ........................................................................................... 10 Figure 2 – HP FC HBA Profile: Object Diagram ......................................................................................... 18

Tables

Table 1 – Related Profiles ............................................................................................................................. 9 Table 2 – Supported Operations ................................................................................................................. 16 Table 3 – CIM Elements – HP FC HBA Profile ........................................................................................... 19 Table 4 – Class: HPFCHBA_ComputerSystem .......................................................................................... 20 Table 5 – Class: HPFCHBA_FCPort .......................................................................................................... 20 Table 6 – Class: HPFCHBA_PortController ................................................................................................ 21 Table 7 – Class: HPFCHBA_FcPortStatistics ............................................................................................. 21 Table 8 – Class: HPFCHBA_LogicalPortGroup .......................................................................................... 21 Table 9 – Class: HPFCHBA_PhysicalPackage .......................................................................................... 21 Table 10 – Class: HPFCHBA_Product ....................................................................................................... 22 Table 11 – Class: HPFCHBA_SoftwareIdentityDrv .................................................................................... 22 Table 12 – Class: HPFCHBA_FirmwareIdentityFW.................................................................................... 22 Table 13 – Class: HPFCHBA_FirmwareIdentityBIOS ................................................................................ 23 Table 14 – Class: HPFCHBA_SCSIProtocolController .............................................................................. 23 Table 15 – Class: HPFCHBA_SCSIProtocolEndpoint ................................................................................ 23 Table 16 – Class: HPFCHBA_GroupSystemSpecificCollection ................................................................. 24 Table 17 – Class: HPFCHBA_ComputerSystemFCPort ............................................................................ 24 Table 18 – Class: HPFCHBA_ComputerSystemPortController .................................................................. 24


Table 19 – Class: HPFCHBA_ComputerSystemSCSIProtocolController .................................................. 24 Table 20 – Class: HPFCHBA_ComputerSystemLogicalPortGroup ............................................................ 25 Table 21 – Class: HPFCHBA_ComputerSystemSoftwareIdentityDrv ........................................................ 25 Table 22 – Class: HPFCHBA_SystemServiceAccessPoint ........................................................................ 25 Table 23 – Class: HPFCHBA_FCPortFCPortStatistics .............................................................................. 25 Table 24 – Class: HPFCHBA_FCPortLogicalPortGroup ............................................................................ 26 Table 25 – Class: HPFCHBA_FCPortSCSIProtocolEndpoint .................................................................... 26 Table 26 – Class: HPFCHBA_SCSIProtocolControllerFCPort ................................................................... 26 Table 27 – Class: HPFCHBA_PortControllerFCPort .................................................................................. 26 Table 28 – Class: HPFCHBA_PhysicalPackagePortController .................................................................. 27 Table 29 – Class: HPFCHBA_SoftwareIdentityDrvPortController .............................................................. 27 Table 30 – Class: HPFCHBA_PortControllerFirmwareIdentityFW ............................................................. 27 Table 31 – Class: HPFCHBA_PortControllerFirmwareIdentityBIOS .......................................................... 27 Table 32 – Class: HPFCHBA_ProductPhysicalComponent ....................................................................... 28 Table 33 – Class: HPFCHBA_SystemPackaging ....................................................................................... 28 Table 34 – Class: HPFCHBA_ConcreteIdentity.......................................................................................... 28 Table 35 – Class: HPFCHBA_GroupHostedCollection .............................................................................. 28 Table 36 – Class: HPFCHBA_FCPortGroupSystemSpecific ...................................................................... 29 Table 37 – Class: HP_RegisteredProfile .................................................................................................... 29 Table 36 – Class: HPFCHBA_PortControllerPCIDevice ............................................................................ 29 Table 38 – Durable Names generated by this Profile ................................................................................. 30


Foreword

The HP FC HBA Profile P00119 was prepared by the HP WBEM TC.


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 Fibre Channel Host Bus Adapter system. 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.


1 Scope The HP FC HBA Profile extends the management capability of the referencing profiles by adding the capability to represent the FC HBAs and the consolidated status in HP specific ways.







DMTF DSP1075, PCI Device Profile



HP WBEM TC P00113, HP Location Profile

2.2 References Under Development SNIA SMI-S 1.2.0 rev. 1

2.3 Other References None






4.1 FC Fibre Channel

4.2 HBA Host Bus Adapter

5 Synopsis Profile Name: HP FC HBA Profile

Version: 1.0.5



Central Class: HPFCHBA_ComputerSystem

Scoping Class: CIM_ComputerSystem

Extends: SMI-S 1.2.0, FC HBA Profile


The HP FC HBA profile extends SMI-S 1.2.0 FC HBA Profile and specializes HP WBEM TC P00107 to add FC HBA and consolidated status characteristics that are specific to HP systems.



SMI-S FC HBA Profile SNIA 1.2.0 Mandatory

DSP1075 PCI Device Profile DMTF 1.0.0 Optional




HP WBEM TC 1.0 Specializes

6 Description The HB FC HBA profile describes behavior of Fibre Channel host adapters supporting the SCSI (FCP) command set. A Fibre Channel adapter used in a host system is called a Host Bus Adapter. An HBA is a physical device that contains one or more Fibre Channel ports. A single system contains one or more HBAs.

Figure 1 represents the class schema for the HP FC HBA Profile.


Figure 1 – HP FC HBA Profile: Class Diagram


The HP FC HBA Profile represents the collection of HBAs in CIM using HPFCHBA_FCPort and associating it to HPFCHBA_ComputerSystem through the HPFCHBA_ComputerSystemFCPort association. The HPFCHBA_ComputerSystem contains a consolidated status built using the status of all associated HBAs. The individual port status is contained in HPFCHBA_FCPort. The HPFCHBA_PortController represents the logical behavior of the HBA card. It is associated to the HPFCHBA_ComputerSystem through the HPFCHBA_ComputerSystemPortController association and associated to the FC ports through the HPFCHBA_PortControllerFCPort association. HPFCHBA_PortController’s HPFCHBA_PhysicalPackage is associated with HPFCHBA_Product; which holds information about the HBA (including vendor and model names). To understand the containment to the HBAs physical implementation the HPFCHBA_PortControllers are associated to HPFCHBA_PhysicalPackage through the HPFCHBA_PhysicalPackagePortController association.

HPFCHBA_ComputerSystem is the central class. There is only one instance of HPFCHBA_ComputerSystem no matter how many ports or port controllers. A single FC HBA can have more than one port controller. Each port controller has one or more FC ports.

The overall status of all HPFCHBA_FCPort(s) can be found in HPFCHBA_GroupSystemSpecificCollection.

Figure 2 – HP FC HBA Profile: Additional Associations



7.1 HPFCHBA_ComputerSystem

There shall be one instance of HPFCHBA_ComputerSystem instantiated.

7.1.1 Name

HPFCHBA_ComputerSystem.Name property shall be implemented. This property is a key property.

7.1.2 OtherIdentifyingInfo[]

HPFCHBA_ComputerSystem.OtherIdentifyingInfo[] property shall be implemented. This property can be used to describe additional information about the element.

7.1.3 IdentifyingDescriptions[]

HPFCHBA_ComputerSystem.IdentifyingDescriptions[] property shall be implemented. This property describes the additional information for the corresponding OtherIndentifyingInfo element.

7.1.4 OperationalStatus

HPFCHBA_ComputerSystem.OperationalStatus property shall be implemented. This property describes a combined status of all associated FC HBAs via a mapped value. The mapped values used by this profile are “Other”, “OK”, “Degraded”, and “Error”. If any FC port status is “Error”, then this value will be “Error”. Otherwise, if any FC port status is “Degraded”; this value is “Degraded”. Otherwise if any port status is “OK”, this status is “OK”. Lastly, if all port statuses are “Unknown”, this status will be “Other”.

7.2 HPFCHBA_FCPort

There shall be at least one instance of HPFCHBA_FCPort instantiated for every FC port device.


OperationalStatus property shall be implemented. This property describes a combined status of FC Port via a mapped value. The status value used in this property is generated directly by the FC port.

7.2.2 PermanentAddress

PermanentAddress property shall be implemented. This property contains the port’s node address.

7.2.3 DeviceID

DeviceID property shall be implemented. This property is contains the node’s worldwide name and port’s worldwide name formatted as NODEWWN:PORTWWN.

7.3 HPFCHBA_PortController

The HPFCHBA_PortController is a logical device corresponding to a hardware FC port controller. There shall be at least one instance of HPFCHBA_PortController instantiated for every FC port device.


7.3.1 ControllerType

ControllerType property shall be implemented. This property must be set to 4 (FC).

7.3.2 DeviceID

DeviceID property shall be implemented. This property is contains the port’s worldwide name and HBA’s serial number formatted as PORTWWN:SERIALNUMBER.

7.3.3 Name

Name property shall be implemented. This property contains the port’s worldwide name

7.4 HPFCHBA_FCPortStatistics

There shall be one instance of HPFCHBA_FCPortStatistics for every instance for HPFCHBA_FCPort. The associated HPFCHBA_FCPortStatistics contains the statistics for that FC port.

7.4.1 InstanceID

InstanceID property shall be implemented.

7.5 HPFCHBA_LogicalPortGroup

A collection of one or more ports logically grouped for administrative and discovery/topology purposes. HPFCHBA_LogicalPortGroup define port collection for access control, or for use in routing policy or other management tasks.

7.5.1 Name

Name property shall be implemented. This property contains the port’s worldwide name.

7.5.2 NameFormat

Name property shall be implemented. This property contains WWN.

7.6 HPFCHBA_PhysicalPackage

HPFCHBA_PhysicalPackage class represents physical element that hosts the FC port controller.

7.6.1 Name


7.6.2 ElementName

ElementName property shall be implemented. This property contains a user friendly name for the HBA.


OperationalStatus property shall be implemented. This property describes a combined status of FC ports that are associated with this physical package via a mapped value. The mapped values used by this profile are “Other”, “OK”, “Degraded”, and “Error”. If any FC port status is “Error”, then this value will be “Error”. Otherwise, if any FC port status is “Degraded”; this value is “Degraded”. Otherwise if any port status is “OK”, this status is “OK”. Lastly, if all port statuses are “Unknown”, this status will be “Other”.


7.7 HPFCHBA_Product

HPFCHBA_Product aggregates physical element classes HPFCHBA_PhysicalPackage.

7.7.1 Name

Name property shall be implemented. This property contains the GUID and port’s worldwide name formatted as HP:GUID:85408DBD-6A39-41CD-9E5A-357AEA130BBF:NODEWWN:nodewwn.

7.7.2 ElementName


7.7.3 IdentifyingNumber

IdentifyingNumber property shall be implemented. This property contains the HBA’s board ID.

7.7.4 VersionString

VersionString property shall be implemented. This property contains the HBA’s firmware version.

7.8 HPFCHBA_SoftwareIdentityDrv

HPFCHBA_SoftwareIdentityDrv represents software driver associated with the FC port controller.

7.8.1 Classifications

Classifications property shall be implemented. This property contains 2 (Driver).

7.8.2 Name


7.8.3 Version

Version property shall be implemented. This property contains the driver version.

7.9 HPFCHBA_FirmwareIdentityFW

HPFCHBA_FirmwareIdentityFW represents adapter firmware associated with the FC port controller.


Classifications property shall be implemented. This property contains 10 (Firmware).

7.9.2 Name


7.9.3 VersionString

VersionString property shall be implemented. This property contains the firmware version.

7.10 HPFCHBA_FirmwareIdentityBIOS

HPFCHBA_FirmwareIdentityBIOS represents adapter BIOS associated with the FC port controller.



Classifications property shall be implemented. This property contains 11 (BIOS).

7.10.2 Name


7.10.3 VersionString

VersionString property shall be implemented. This property contains the BIOS version.

7.11 HPFCHBA_SCSIProtocolController

HPFCHBA_SCSIProtocolController represents a protocol controller that manages a SCSI interface. This class is used for backward compatibility with SMI-S 1.0.

7.11.1 DeviceID

DeviceID property shall be implemented. This property contains the port’s worldwide name

7.11.2 ElementName



OperationalStatus property shall be implemented. This property describes a combined status of FC ports that are associated with this protocol controller via a mapped value. The mapped values used by this profile are “Other”, “OK”, “Degraded”, and “Error”. If any associated FC port status is “Error”, then this value will be “Error”. Otherwise, if any FC port status is “Degraded”; this value is “Degraded”. Otherwise if any port status is “OK”, this status is “OK”. Lastly, all port statuses are “Unknown”, this status will be “Other”.

7.12 HPFCHBA_SCSIProtocolEndpoint

HPFCHBA_SCSIProtocolEndpoint represents the protocol aspects of a logical SCSI port, independent of the connection/transport.

7.12.1 Name


7.12.2 ConnectionType

ConnectionType property shall be implemented. This property must be set to 2 (FC).

7.12.3 Role

Role property shall be implemented. This property must be set to 2 (Initiator).

7.12.4 ProtocolIFType

ProtocolIFType property shall be implemented. This property must be set to 57 (HIPPI Interface).

7.13 HPFCHBA_GroupSystemSpecificCollection

HPFCHBA_GroupSystemSpecificCollection is a collection of the status conditions of all the FC ports.


7.13.1 GroupOperationalStatus

GroupOperationalStatus property shall be implemented. This property describes a combined status of all FC ports via a mapped value. The mapped values used by this profile are “Other”, “OK”, “Degraded”, and “Error”. If any FC port status is “Error”, then this value will be “Error”. Otherwise, if any FC port status is “Degraded”; this value is “Degraded”. Otherwise, if port status is “OK”, this status is “OK”. Lastly, if all port statuses are “Unknown”, this status will be “Other”.

8 Methods None.




• GetInstance

• Associators

• AssociatorNames

• References

• ReferenceNames




8.2 Supported Operations


Table 2 – Supported Operations










9 Use Cases

9.1 Object Diagrams

The following figures represent a possible instantiation of the HP FC HBA Profile. In this case, cs1 has a single FC Ports fc1. Fc1 belongs is associated to its port controller via HPFCHBA_PortControllerFCPort, pc1. Pc1 is associated to HPFCHBA_ComputerSystem, cs1, via HPFCHBA_ComputerSystemPortController.


Figure 2 – HP FC HBA Profile: Object Diagram


9.2 Retrieve the FC HBA Group Operational Status

For the given instance of HPFCHBA_ComputerSystem, select the associated instance of HPFCHBA_GroupSystemSpecificCollection through the HBFCHBA_GroupHostedCollection association. Retrieve the value of HPFCHBA_GroupSystemSpecificCollection.GroupOperationalStatus property.

9.3 Retrieve the FC Port Status

For the given instance of HPFCHBA_FCPort, retrieve the value of HPFCHBA_FCPort.OperationalStatus property. Additional status information can be found in HPFCHBA_FCPort.StatusDesciptions.


Table 3 – CIM Elements – HP FC HBA Profile


Classes HPFCHBA_ComputerSystem Mandatory See Sections 7.1 and 10.1

HPFCHBA_FCPort Mandatory See Sections 7.2 and 10.2

HPFCHBA_PortController Mandatory See Sections 7.3 and 10.3

HPFCHBA_FcPortStatistics Mandatory See Sections 7.4 and 10.4

HPFCHBA_LogicalPortGroup Optional See Sections 7.5 and 10.5

HPFCHBA_PhysicalPackage Mandatory See Sections 7.6 and 10.6

HPFCHBA_Product Mandatory See Sections 7.7 and 10.7

HPFCHBA_SoftwareIdentityDrv Mandatory See Sections 7.8 and 10.8

HPFCHBA_FirmwareIdentityFW Mandatory See Sections 7.9 and 10.9

HPFCHBA_FirmwareIdentityBIOS Mandatory See Sections 7.10 and 10.10

HPFCHBA_SCSIProtocolController Mandatory See Sections 7.11 and 10.11

HPFCHBA_SCSIProtocolEndpoint Mandatory See Sections 7.12 and 10.12

HPFCHBA_GroupSystemSpecificCollection Mandatory See Sections 7.13 and 10.13

HPFCHBA_ComputerSystemFCPort Mandatory See Section 10.14

HPFCHBA_ComputerSystemPortController Mandatory See Section 10.15

HPFCHBA_ComputerSystemSCSIProtocolController Mandatory See Section 10.16

HPFCHBA_ComputerSystemLogicalPortGroup Mandatory See Section 10.17

HPFCHBA_ComputerSystemSoftwareIdentityDrv Optional See Section 10.18

HPFCHBA_SystemServiceAccessPoint Mandatory See Section 10.19

HPFCHBA_FCPortFCPortStatistics Mandatory See Section 10.20

HPFCHBA_FCPortLogicalPortGroup Optional See Section 10.21

HPFCHBA_FCPortSCSIProtocolEndpoint Mandatory See Section 10.22

HPFCHBA_SCSIProtocolControllerFCPort Mandatory See Section 10.23

HPFCHBA_PortControllerFCPort Mandatory See Section 10.24

HPFCHBA_PhysicalPackagePortController Mandatory See Section 10.25



HPFCHBA_SoftwareIdentityDrvPortController Mandatory See Section 10.26

HPFCHBA_PortControllerFirmwareIdentityFW Mandatory See Section 10.27

HPFCHBA_PortControllerFirmwareIdentityBIOS Mandatory See Section 10.28

HPFCHBA_ProductPhysicalComponent Mandatory See Section 10.29

HPFCHBA_SystemPackaging Mandatory See Section 10.30

HPFCHBA_ConcreteIdentity Mandatory See Section 10.31

HBFCHBA_GroupHostedCollection Mandatory See Section 10.32

HPFCHBA_FCPortGroupSystemSpecific Mandatory See Section 10.33


HPFCHBA_PortControllerPCIDevice Optional See section 10.35

Indications


10.1 HPFCHBA_ComputerSystem

HPFCHBA_ComputerSystem is used identify classes that represent the FC HBA.

Table 4 – Class: HPFCHBA_ComputerSystem


HPFCHBA_ComputerSystem

CIM_ComputerSystem

Name Mandatory See Section 7.1.1

OtherIdentifyingInfo[] Mandatory See Section 7.1.2

IdentifyingDescriptions[] Mandatory See Section 7.1.3


10.2 HPFCHBA_FCPort

HPFCHBA_FCPort is used to represent a FC port device.

Table 5 – Class: HPFCHBA_FCPort


HPFCHBA_FCPort

CIM_FCPort


PermanentAddress Mandatory See Section 7.2.2

DeviceID Mandatory See Section 7.2.3


10.3 HPFCHBA_PortController

HPFCHBA_PortController is is a logical device corresponding to a hardware network port controller.

Table 6 – Class: HPFCHBA_PortController


HPFCHBA_PortController

CIM_PortController

ControllerType Mandatory See Section 7.3.1



10.4 HPFCHBA_FcPortStatistics

HPFCHBA_FcPortStatistics is the set of statistics for the FC port.

Table 7 – Class: HPFCHBA_FcPortStatistics


HPFCHBA_FcPortStatistics

CIM_FCPortStatistics

10.5 HPFCHBA_LogicalPortGroup

HPFCHBA_LogicalPortGroup is a collection of one or more ports logically grouped for administrative and discovery/topology purposes.

Table 8 – Class: HPFCHBA_LogicalPortGroup


HPFCHBA_LogicalPortGroup

CIM_LogicalPortGroup


NameFormat Mandatory See Section 7.5.2

10.6 HPFCHBA_PhysicalPackage

HPFCHBA_PhysicalPackage class represents physical element that hosts the FC port controller.

Table 9 – Class: HPFCHBA_PhysicalPackage


HPFCHBA_PhysicalPackage

CIM_PhysicalPackage


ElementName Mandatory See Section 7.6.2



10.7 HPFCHBA_Product

HPFCHBA_Product is used to aggregate physical element of the FC HBA.

Table 10 – Class: HPFCHBA_Product


HPFCHBA_Product

CIM_Product


IdentifyingNumber Mandatory See Section 7.7.3

VersionString Mandatory See Section 7.7.4

10.8 HPFCHBA_SoftwareIdentityDrv

HPFCHBA_SoftwareIdentityDrv represents software driver associated with the FC port controller.

Table 11 – Class: HPFCHBA_SoftwareIdentityDrv


HPFCHBA_SoftwareIdentityDrv


Classifications Mandatory See Section 7.8.1



10.9 HPFCHBA_FirmwareIdentityFW

HPFCHBA_FirmwareIdentityFW represents adapter firmware associated with the FC port controller.

Table 12 – Class: HPFCHBA_FirmwareIdentityFW


HPFCHBA_FirmwareIdentityFW





10.10 HPFCHBA_FirmwareIdentityBIOS

HPFCHBA_FirmwareIdentityBIOS represents adapter BIOS associated with the FC port controller.


Table 13 – Class: HPFCHBA_FirmwareIdentityBIOS


HPFCHBA_FirmwareIdentityBIOS





10.11 HPFCHBA_SCSIProtocolController

HPFCHBA_SCSIProtocolController represents a protocol controller that manages a SCSI interface. This class is used for backward compatibility with SMI-S 1.0.

Table 14 – Class: HPFCHBA_SCSIProtocolController


HPFCHBA_SCSIProtocolController

CIM_SCSIProtocolController




10.12 HPFCHBA_SCSIProtocolEndpoint

HPFCHBA_SCSIProtocolEndpoint represents the protocol aspects of a logical SCSI port, independent of the connection/transport.

Table 15 – Class: HPFCHBA_SCSIProtocolEndpoint


HPFCHBA_SCSIProtocolEndpoint

CIM_DeviceSAPImplementation


ConnectionType Mandatory See Section 7.12.2

Role Mandatory See Section 7.12.3

ProtocolIFType Mandatory See Section 7.12.4


10.13 HPFCHBA_GroupSystemSpecificCollection

HPFCHBA_GroupSystemSpecificCollection is used to represent the group status of all FC HBAs.

Table 16 – Class: HPFCHBA_GroupSystemSpecificCollection


HPFCHBA_GroupSystemSpecificCollection


GroupOperationalStatus Mandatory See Section 7.13.1

CIM_SystemSpecificCollection

10.14 HPFCHBA_ComputerSystemFCPort

HPFCHBA_ComputerSystemFCPort is used to represent an association between HPFCHBA_ComputerSystem and HPFCHBA_FCPort.

Table 17 – Class: HPFCHBA_ComputerSystemFCPort


GroupComponent Mandatory Key: References HPFCHBA_ComputerSystem

PartComponent Mandatory Key: References HPFCHBA_FCPort

10.15 HPFCHBA_ComputerSystemPortController

HPFCHBA_ComputerSystemPortController is used to represent an association between HPFCHBA_ComputerSystem and HPFCHBA_PortController.

Table 18 – Class: HPFCHBA_ComputerSystemPortController



PartComponent Mandatory Key: References HPFCHBA_PortController

10.16 HPFCHBA_ComputerSystemSCSIProtocolController

HPFCHBA_ComputerSystemSCSIProtocolController is used to represent an association between HPFCHBA_ComputerSystem and HPFCHBA_SCSIProtocolController.

Table 19 – Class: HPFCHBA_ComputerSystemSCSIProtocolController



PartComponent Mandatory Key: References HPFCHBA_ SCSIProtocolController


10.17 HPFCHBA_ComputerSystemLogicalPortGroup

HPFCHBA_ComputerSystemLogicalPortGroup is used to represent an association between HPFCHBA_ComputerSystem and HPFCHBA_LogicalPortGroup.

Table 20 – Class: HPFCHBA_ComputerSystemLogicalPortGroup


Antecedent Mandatory Key: References HPFCHBA_ComputerSystem

Dependent Mandatory Key: References HPFCHBA_ LogicalPortGroup

10.18 HPFCHBA_ComputerSystemSoftwareIdentityDrv

HPFCHBA_ComputerSystemSoftwareIdentityDrv is used to represent an association between HPFCHBA_ComputerSystem and HPFCHBA_SoftwareIdentityDrv.

Table 21 – Class: HPFCHBA_ComputerSystemSoftwareIdentityDrv


System Mandatory Key: References HPFCHBA_ComputerSystem

InstalledSoftware Mandatory Key: References HPFCHBA_ SoftwareIdentityDrv

10.19 HPFCHBA_SystemServiceAccessPoint

HPFCHBA_SystemServiceAccessPoint is used to represent an association between HPFCHBA_ComputerSystem and HPFCHBA_SCSIProtocolEndpoint.

Table 22 – Class: HPFCHBA_SystemServiceAccessPoint


Antecedent Mandatory Key: References HPFCHBA_ComputerSystem

Dependent Mandatory Key: References HPFCHBA_SCSIProtocolEndpoint

10.20 HPFCHBA_FCPortFCPortStatistics

HPFCHBA_FCPortFCPortStatistics is used to represent an association between HPFCHBA_FCPort and HPFCHBA_FCPortStatistics.

Table 23 – Class: HPFCHBA_FCPortFCPortStatistics


ManagedElement Mandatory Key: References HPFCHBA_FCPort Stats Mandatory Key: References HPFCHBA_FCPortStatistics


10.21 HPFCHBA_FCPortLogicalPortGroup

HPFCHBA_FCPortLogicalPortGroup is used to represent an association between HPFCHBA_FCPort and HPFCHBA_LogicalPortGroup.

Table 24 – Class: HPFCHBA_FCPortLogicalPortGroup


Member Mandatory Key: References HPFCHBA_FCPort Collection Mandatory Key: References HPFCHBA_LogicalPortGroup

10.22 HPFCHBA_FCPortSCSIProtocolEndpoint

HPFCHBA_FCPortSCSIProtocolEndpoint is used to represent an association between HPFCHBA_FCPort and HPFCHBA_SCSIProtocolEndpoint.

Table 25 – Class: HPFCHBA_FCPortSCSIProtocolEndpoint


Antecedent Mandatory Key: References HPFCHBA_FCPort Dependent Mandatory Key: References HPFCHBA_SCSIProtocolEndpoint

10.23 HPFCHBA_SCSIProtocolControllerFCPort

HPFCHBA_SCSIProtocolControllerFCPort is used to represent an association between HPFCHBA_FCPort and HPFCHBA_SCSIProtocolController.

Table 26 – Class: HPFCHBA_SCSIProtocolControllerFCPort


Dependent Mandatory Key: References HPFCHBA_FCPort Antecedent Mandatory Key: References HPFCHBA_SCSIProtocolController

10.24 HPFCHBA_PortControllerFCPort

HPFCHBA_PortControllerFCPort is used to represent an association between HPFCHBA_PortController and HPFCHBA_FCPort.

Table 27 – Class: HPFCHBA_PortControllerFCPort


Antecedent Mandatory Key: References HPFCHBA_PortController Dependent Mandatory Key: References HPFCHBA_FCPort


10.25 HPFCHBA_PhysicalPackagePortController

HPFCHBA_PhysicalPackagePortController is used to represent an association between HPFCHBA_PortController and HPFCHBA_PhysicalPackage.

Table 28 – Class: HPFCHBA_PhysicalPackagePortController


Antecedent Mandatory Key: References HPFCHBA_PhysicalPackage

Dependent Mandatory Key: References HPFCHBA_ PortController

10.26 HPFCHBA_SoftwareIdentityDrvPortController

HPFCHBA_SoftwareIdentityDrvPortController is used to represent an association between HPFCHBA_PortController and HPFCHBA_SoftwareIdentityDrv.

Table 29 – Class: HPFCHBA_SoftwareIdentityDrvPortController


Antecedent Mandatory Key: References HPFCHBA_SoftwareIdentityDrv


10.27 HPFCHBA_PortControllerFirmwareIdentityFW

HPFCHBA_PortControllerFirmwareIdentityFW is used to represent an association between HPFCHBA_PortController and HPFCHBA_FirmwareIdentityFW.

Table 30 – Class: HPFCHBA_PortControllerFirmwareIdentityFW


Antecedent Mandatory Key: References HPFCHBA_FirmwareIdentityFW


10.28 HPFCHBA_PortControllerFirmwareIdentityBIOS

HPFCHBA_PortControllerFirmwareIdentityBIOS is used to represent an association between HPFCHBA_PortController and HPFCHBA_FirmwareIdentityBIOS.

Table 31 – Class: HPFCHBA_PortControllerFirmwareIdentityBIOS


Antecedent Mandatory Key: References HPFCHBA_FirmwareIdentityBIOS



10.29 HPFCHBA_ProductPhysicalComponent

HPFCHBA_ProductPhysicalComponent is used to represent an association between HPFCHBA_Product and HPFCHBA_PhysicalPackage.

Table 32 – Class: HPFCHBA_ProductPhysicalComponent


GroupComponent Mandatory Key: References HPFCHBA_Product PartComponent Mandatory Key: References HPFCHBA_PhysicalPackage

10.30 HPFCHBA_SystemPackaging

HPFCHBA_SystemPackaging is used to represent an association between HPFCHBA_PhysicalPackage and HPFCHBA_ComputerSystem.

Table 33 – Class: HPFCHBA_SystemPackaging


Antecedent Mandatory Key: References HPFCHBA_PhysicalPackage

Dependent Mandatory Key: References HPFCHBA_ComputerSystem

10.31 HPFCHBA_ConcreteIdentity

HPFCHBA_ConcreteIdentity used to represent an association between CIM_ComputerSystem and HPFCHBA_ComputerSystem.

Table 34 – Class: HPFCHBA_ConcreteIdentity


SystemElement Mandatory Key: References CIM_ComputerSystem

SameElement Mandatory Key: References HPFCHBA_ComputerSystem

10.32 HPFCHBA_GroupHostedCollection

HPFCHBA_GroupHostedCollection used to represent an association between CIM_ComputerSystem and HPFCHBA_GroupSystemSpecificCollection.

Table 35 – Class: HPFCHBA_GroupHostedCollection


Antecedent Mandatory Key: References CIM_ComputerSystem

Dependent Mandatory Key: References HPFCHBA_GroupSystemSpecificCollection


10.33 HPFCHBA_FCPortGroupSystemSpecific

HPFCHBA_FCPortGroupSystemSpecific used to represent an association between CIM_FCPort and HPFCHBA_GroupSystemSpecificCollection.

Table 36 – Class: HPFCHBA_FCPortGroupSystemSpecific


Member Mandatory Key: References CIM_FCPort Collection Mandatory Key: References

HPFCHBA_GroupSystemSpecificCollection





RegisteredName Mandatory "HP FC HBA"




10.35 HPFCHBA_PortControllerPCIDevice

HPFCHBA_PortControllerPCIDevice used to represent an association between HPFCHBA_PortController and CIM_PCIDevice.

Table 38 – Class: HPFCHBA_PortControllerPCIDevice


SystemElement Mandatory Key: References CIM_PCIDevice

SameElement Mandatory Key: References HPFCHBA_PortController





HPFCHBA_FCPort PermanentAddress Port WWN

HPFCHBA_PortController Name Node WWN

HPFCHBA_LogicalPortGroup Name Node WWN

HPFCHBA_PhysicalPackage Name Node WWN

HPFCHBA_Product Name HP:GUID:NODE WWN

HPFCHBA_SoftwareIdentityDrv Name Node WWN

HPFCHBA_FirmwareIdentityFW Name Node WWN

HPFCHBA_FirmwareIdentityBIOS Name Node WWN

HPFCHBA_SCSIProtocolController DeviceID Node WWN

HPFCHBA_SCSIProtocolEndpoint Name Node WWN


ANNEX A (normative)

Change Log


1.0 8/31/2006 Initial draft 1.0.1 9/6/2006 Corrections 1.0.2 9/16/2006 Corrections 1.0.3 9/26/06 Corrections 1.0.4 11/15/06 RQM fixes 1.0.5 04/22/2011 Add PCIDevice



Acknowledgments




CR

Number Date Title

CR0111 8/31/2006 Add HP FC HBA Profile and MOF


Bibliography



Date: 03/01/10

Version: 1.0.1

HP Storage Enclosure Profile




2 Version 1.0.1

Contents



3 Terms and Definitions ........................................................................................................................... 7 4 Symbols and Abbreviated Terms .......................................................................................................... 8 5 Synopsis ................................................................................................................................................ 9 6 Description .......................................................................................................................................... 10

6.1 Location information.................................................................................................................. 11 6.2 Software Inventory .................................................................................................................... 11

7 Implementation Requirements ............................................................................................................ 12 7.1 HP_StorageEnclosureProcessor (Mandatory) ......................................................................... 12 7.2 HP_StorageEnclosure (Mandatory) .......................................................................................... 13 7.3 HP_DriveCage .......................................................................................................................... 13

8 Methods ............................................................................................................................................... 14 8.1 Profile Conventions for Operations ........................................................................................... 14


10 CIM Elements ...................................................................................................................................... 20 10.1 HP_StorageEnclosureProcessor .............................................................................................. 20 10.2 HP_StorageEnclosure .............................................................................................................. 21 10.3 HP_DriveCage .......................................................................................................................... 21 10.4 CIM_SystemComponent ........................................................................................................... 22 10.5 CIM_SystemPackaging............................................................................................................. 22 10.6 CIM_Containner ........................................................................................................................ 22 10.7 HP_RegisteredProfile ............................................................................................................... 23


Version 1.0.1 3

Figures

Figure 1 – HP Storage Enclosure profile: Class Diagram ........................................................................... 10 Figure 2 – HP Storage Enclosure profile: Location specification ................................................................ 11 Figure 3 – HP Storage Enclosure Profile: HHRC controller with External enclosure ................................. 15 Figure 4 – HP Storage Enclosure Profile: External Storage Subsystem with controllers ........................... 17 Figure 5 – HP Storage Enclosure Profile: Host System with HBA (HHRC) and internal enclosure ........... 18 Figure 6 – HP Storage Enclosure profile: Internal and External Enclosures .............................................. 19

4 Version 1.0.1

Tables

Table 1 – Related Profiles ............................................................................................................................. 9 Table 2 – OperationalStatus extended values. ........................................................................................... 12 Table 3 – HP_StorageEnclosure.Location values ...................................................................................... 13 Table 4 – CIM Elements – HP Storage Enclosure Profile .......................................................................... 20 Table 5 – Class: HP_StorageEnclosureProcessor ..................................................................................... 21 Table 6 – Class: HP_StorageEnclosure ..................................................................................................... 21 Table 7 – Class: HP_DriveCage ................................................................................................................. 22 Table 8 – Class: CIM_SystemComponent .................................................................................................. 22 Table 9 – Class: CIM_SystemPackaging .................................................................................................... 22 Table 10 – Class: CIM_SystemContainer ................................................................................................... 23 Table 11 – Class: HP_RegisteredProfile .................................................................................................... 23 Table 12 – Durable Names generated by this Profile ................................................................................. 23 Table 13 – Correlatable IDs generated by this Profile ................................................................................ 23

Version 1.0.1 5

Foreword

The HP Storage Enclosure Profile (P00120) was prepared by the HP WBEM TC.

6 Version 1.0.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 Storage Enclosures. 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.

Version 1.0.1 7

1 Scope

The HP Storage Enclosure profile is a component profile to describe management aspects of HP Storage Enclosures. This should be used with other autonomous profiles that adhere to the SMI-S 1.2 specification.











2.2 References Under Development SNIA SMI-S 1.4 (Draft)








8 Version 1.0.1












None.

Version 1.0.1 9

5 Synopsis Profile Name: HP Storage Enclosure Profile

Version: 1.0.1


CIM Schema Version: 2.18.1


The HP Storage Enclosure Profile extends the DMTF physical asset profile to add the ability to model and represent HP Storage Enclosures.

Central Class: HP_StorageEnclosure

Scoping Class: CIM_ComputerSystem



P00100 HP Profile Registration Profile


P00124 HP Location Profile HP WBEM TC 1.0.0 Mandatory

DSP1011- Physical Asset Profile DMTF 1.0.2 Mandatory

Disk Drive Lite SNIA 1.3.0 Mandatory

DSP1023 - Software Inventory Profile


10 Version 1.0.1

6 Description

CIM_ComputerSystem

HP_StorageEnclosureProcessorHP_StorageEnclosure

Container

HP_DriveCage

CIM_ComputerSystem

see Referencing Profile (Array, HHRC)

SystemComponentSystemPackaging

CIM_Chassis

CIM_PhysicalPackage



SoftwareIdentity

Enclosure Firmware

ElementSoftwareIdentity

See DMTF Software Identity Profile

See HP Profile Registration Profile

CIM_PhysicalPackage (Disk) HP_DiskDriveCIM_Realizes

See SNIA Disk Drive Lite Subprofile

CIM_Container

Figure 1 – HP Storage Enclosure profile: Class Diagram

Instances of the physical enclosure (HP_StorageEnclosure) are associated to the logical representation of the enclosure in the system via the association CIM_SystemPackaging to an instance of HP_StorageEnclosureProcessor. The instance of HP_StorageEnclosureProcessor is associated to the scoping CIM_ComputerSystem class of the referencing profile (e.g. Host Hardware RAID Controller) using the CIM_SystemComponent association. HP_StorageEnclosureProcessor extends OperationalStatus to reflect the status of Fans, Power Supplies and Sensors contained within the storage enclosure (see section 7.1.1)

Version 1.0.1 11

The HP_StorageEnclosure can contain multiple drive cages represented by instances of HP_DriveCage. Each instance of HP_DriveCage is associated with the enclosure it is contained within (HP_StorageEnclosure) via the association CIM_Container.

6.1 Location information

Container

SystemPackaging

HP_StorageEnclosureProcessor

HP_StorageEnclosure

HP_DriveCage HP_Location

ElemInfoTagDesc = Port

HP_Location

ElemInfoTagDesc = ChassisName, Box

PhysicalElementLocation


CIM_PhysicalPackage (Disk)

Disk Drive Lite Subprofile

Container

HP_Location

ElemInfoTagDesc = Bay, SCSI IDPhysicalElementLocation

Figure 2 – HP Storage Enclosure profile: Location specification

Location information can be determined through containment relationship within the overall storage enclosure chassis represented by an instance of HP_StorageEnclosure. Implementations shall include an instance of HP_Location associated to each physical package by CIM_PhysicalElementLocation.

6.2 Software Inventory

The Firmware version of the enclosure will be reported using the DMTF Software Inventory Profile (DSP1023).

An instance of CIM_SoftwareIdentity shall be associated with each HP_StorageEnclosureProfile instance via CIM_ElementSoftwareIdentity association. (See Figure 1).

12 Version 1.0.1

7 Implementation Requirements This section details the requirements for implementations of this profile.

7.1 HP_StorageEnclosureProcessor (Mandatory)

There shall be an instance of HP_StorageEnclosureProcessor for each instance of a Storage Enclosure. These instances should be associated to the scoping CIM_ComputerSystem class by an instance of CIM_SystemComponent association.

7.1.1 HP_StorageEnclosureProcessor.OperationalStatus

The OperationalStatus values have been extended to allow reporting the enclosure status related to Fans, Power Supplies and Temperature Sensors. The status values of the enclosure shall be reflected in the OperationalStatus Array as defined in Table 2.

The values for each element in the array shall be populated as follows: OperationalStatus[0] – Overall Status will be the “worst of” value according to Table 2 OperationalStatus[1] – Fan Status OperationalStatus[2] – Power Supply Status OperationalStatus[3] – Temperature Status It is expected that the overall status would contribute to the consolidated status for the referencing profile according to its collection algorithm.

Table 2 – OperationalStatus extended values.

OperationalStatus[n] OperationalStatus[0] Description

Fan not Detected (0x8000) OK

Fan OK (0x8001) OK

Fan Degraded (0x8002) Degraded

Fan Failed (0x8003) Error

Power Supply Not Detected (0x8004) OK

Non Redundant Power Supply (0x8005) OK

Redundant Power Supply (0x8006) OK

Redundant Power Supply Degraded (0x8007) Degraded

Temperature Sensor Not Detected (0x8008) OK

Temperature OK (0x8009) OK

Temperature Warning (0x800A) Degraded

Temperature Critical (0x800B) Error

Version 1.0.1 13

7.1.2 HP_ StorageEnclosureProcessor.Dedicated

This property shall be set to a value of 2 to indicate “Other”. See section 7.1.3 for more details

7.1.3 HP_ StorageEnclosureProcessor.OtherDedicatedDescriptions

This property is used to define how the computer system class is being used. In this case the value shall be set to “SDE” to represent Storage Device Enclosure.

7.2 HP_StorageEnclosure (Mandatory)

There shall be one HP_StorageEnclosure instance associated to HP_StorageEnclosureProcessor by association CIM_SystemPackaging to represent the physical enclosure chassis.

7.2.1 HP_StorageEnclosure.Location

Table 3 – HP_StorageEnclosure.Location values

This property shall be used to determine the physical location of the attached enclosure with respect to the scoping class instance. This property shall be set to one of the values listed in Table 3.

7.2.2 HP_StorageEnclosure.Model

This property should contain the model name for the enclosure.

7.2.3 HP_StorageEnclosure.SerialNumber

This property should contain the serial number for the enclosure.

7.2.4 HP_StorageEnclosure.PartNumber

This property should contain the part number for the enclosure, if known. If the part number is unknown then it should contain “N/A”.

7.2.5 HP_StorageEnclosure.Manufacturer

This property should contain the manufacturer name for the enclosure.

7.3 HP_DriveCage

There shall be one instance for each Drive Cage contained within the enclosure associated by CIM_Container to HP_StorageEnclosure.

7.3.1 HP_DriveCage.DriveBays

This property shall indicate the total number of drive bays (hot plug drives) supported by this instance of the Drive Cage.

Location Description

Unknown (0) Undetermined

Internal (1) Contained within the system package associated to the Scoping class instance.

External (2) Located external to the system package associated to the Scoping class instance.

14 Version 1.0.1

7.3.2 HP_DriveCage.DuplexLocation

This property shall indicate the location of the Drive Cage in cases where the enclosure supports splitting of the drive cages. In the case where there is not duplex option (or is not configured) then the value shall be set to “None”.

7.3.3 HP_DriveCage.BackplaneSpeed

This property shall indicate the maximum speed of the backplane incorporated within the drive cage.

8 Methods None.




• GetInstance

• Associators

• AssociatorNames

• References

• ReferenceNames




Version 1.0.1 15

9 Use Cases

9.1 Object Diagrams

HPSA_StorageEnclosureProcessor:SE1HPSA_StorageEnclosure:SE1

Location=”1" (External)

Container

HPSA_DriveCage:SE1:DC0

HPSA_ArraySystem:abcd

OperationalStatus[]=”2" SystemComponent

SystemPackaging

HPSA_StorageEnclosureLocation:SE1

ElemInfoTagDesc = BoxElemInfoTag = “1”


HPSA_DriveCageLocation:SE1:DC0

Port = “1E”PhysicalElementLocation

HPSA_DiskPhysicalPackage:abcd:D0

Container

HPSA_DiskDriveLocation:abcd:D0

ElemInfoTagDesc = Bay ElemInfoTag = “5”


HPSA_DiskDrive:abcd:D0

OperationalStatus[]=”2" (OK)Realizes


HPSA_PhysicalPackage:abcd

SystemPackaging

HPSA_ArraySystemLocation:abcd

ElemInfoTagDesc = PCI Slot ElemInfoTag = “3”


HHRCExternal Storage Enclosure

HPSA_EnclosureFirmware:SE1


Figure 3 – HP Storage Enclosure Profile: HHRC controller with External enclosure

Figure 3 shows an instance of Host Hardware RAID Controller (HHRC) HBA installed in PCI Slot 3 of the Host system. The Storage Enclosure is attached via cable (e.g. SCSI, SAS) to an external port on the HBA. The central class instance (HPSA_StorageEnclosureProcessor) is associated to the Scoping Class instance of HHRC (HPSA_ArraySystem) via a SystemComponent association.

The physical chassis (HPSA_StorageEnclosure) is associated to the central class instance via CIM_SystemPackaging association. Once the chassis instance has been discovered, then Drive Cages instances can be found using CIM_Container association.

Disk Drive physical package (as defined in Disk Drive Lite sub-profile (SNIA)) is associated to the drive cage via the association CIM_Container

Location of a given physical package can be determined by traversing the association CIM_PhysicalElementLocation to an instance of HP_Location. By using the tags defined in this profile, and walking the containment shown above, the location can be determined.

In the case of Figure 4, the location of the disk drive could be generated as follows. Starting with the instance of HPSA_DiskDrive:abcd:D0 (HP_DiskDrive)

16 Version 1.0.1

1. Use CIM_Realizes association to find HPSA_DiskPhysicalPackage.

2. Use PhysicalElementLocation association to find HPSA_DiskDriveLocation instance

3. Tag/values yields – Bay 5

4. Use CIM_Container association to find parent instance of CIM_PhysicalPackage (HPSA_DriveCage)

5. Use PhysicalElementLocation association to find HPSA_DriveCageLocation instance

6. Tag/values yields – Port 1E

7. Use CIM_Container association to find parent instance of CIM_PhysicalPackage (HPSA_StorageEnclosure)

8. Use PhysicalElementLocation association to find HPSA_StorageEnclsoureLocation instance

9. Tag/values yields – Box 1

10. Complete location string would look like – “Box 1, Port 1E, Bay 5”

Note attachment to the HBA is via cable and is represented at the Drive Cage level since this could be duplexed and have more than one drive cage.

The Firmware version for the enclosure can be determined by using association CIM_ElementSoftwareIdentity from the instance of HPSA_StorageEnclosureProcessor. (This is defined in DMTF profile DSP1023)

Version 1.0.1 17


Location=”2" (Internal)

Container



OperationalStatus[]=”2"

SystemComponent

SystemPackaging


ElemInfoTagDesc = Box ElemtInfoTag = “1”



ElemInfoTagDesc = PortElemInfoTag = “2I”


PhysicalElementLocationHPSA_DiskPhysicalPackage:abcd:D0

Container


ElemInfoTagDesc = BayElemInfoTag = “5”






Storage SubsystemSystemPackaging


ChassisName = “CHASS1”


Array Profile

External Storage Subsystem (MSA)

Container





HPSA_SPIPort:abcd

Front End Port = SCSI

SystemDevice

CIM_ComputerSystem

see Referencing Profile (HHRC)

ComponentCS

BaseServer

Figure 4 – HP Storage Enclosure Profile: External Storage Subsystem with controllers

18 Version 1.0.1

Figure 4 shows an example of an external SCSI/SAS attached storage subsystem that contains one or more array controllers plus an internal storage enclosure in the same chassis. This should be modeled with the SNIA array profile as opposed to HHRC which deals with HBA raid controllers.



Container



OperationalStatus[]=”2" SystemComponent

SystemPackaging





ElemInfoTagDesc = Port ElemtInfoTag = “1I”



Container


ElemInfoTagDesc = Bay ElemtInfoTag = “2”






SystemPackaging


ElemInfoTagDesc = PCISlot ElemtInfoTag = “0”


HHRC

Internal Storage Enclosure

HP_Chassis:CS1

No Location info

Container

Base ServerHP_ComputerSystem:CS1

SystemComponent


HPSA_PortController:abcd

LogicalIdentity

Figure 5 – HP Storage Enclosure Profile: Host System with HBA (HHRC) and internal enclosure

Figure 5 shows a typical server with Embedded Smart Array controller attached to an internal enclosure. In this case the enclosure central class (HPSA_StorageEnclosure) is discovered as previously, associated to HPSA_ArraySystem via CIM_SystemComponent. The physical package is associated to HPSA_StorageEnclosureProcessor via CIM_SystemPackaging. This instance shows the location as “Internal” with respect to the host. This instance is also associated to the HP_Chassis instance (Base Server) via CIM_Container.

In this implementation the enclosure will not monitor the Fans, Power Supplies and temperature since this is done in the Base Server profile. In this case the OperationalStatus for the HPSA_StorageEnclosureProcessor should contain values to indicate, “Fan not detected” etc.

Version 1.0.1 19



Container



OperationalStatus[]=”2"

SystemComponent

SystemPackaging





ElemInfoTagDesc = Port ElemtInfoTag = “2I”



Container








SystemPackaging


ElemInfoTagDesc = PCISlotElemtInfoTag = “0”


HHRC

Internal Storage Enclosure

HP_Chassis:CS1

No Location info

Container

Server Chassis


Location=”2" (External)

Container


SystemPackaging





ElemInfoTagDesc = Port ElemtInfoTag = “1E”



Container







External Storage Enclosure

SystemComponent

SystemDevice

SystemDevice

HP_ComputerSystem:CS1SystemComponent

HPSA_PortController:abcd

Logicalidentity


Figure 6 – HP Storage Enclosure profile: Internal and External Enclosures

20 Version 1.0.1

Figure 6 shows an embedded Smart Array controller connected to internal and external storage enclosures. By using CIM_SystemComponent association from the HPSA_ArraySystem instance should yield two instances of HPSA_StorageEnclosureProcessor. Location of each enclosure can be determined by traversing the CIM_SystemPackaging association to the HPSA_StorageEnclosure instance and inspecting the Location property.

By using same process as detailed for Figure 4, the location strings for both disk drives should look like

Internal Drive – “Box 1, Port 2I, Bay 5”

External Drive – “Box 2, Port 1E, Bay 1”


Table 4 – CIM Elements – HP Storage Enclosure Profile


Classes HP_StorageEnclosureProcessor Mandatory See Section 7

HP_StorageEnclosure Mandatory See Section 7

HP_DriveCage Mandatory See Section 7

CIM_SystemPackaging Mandatory

CIM_SystemComponent Mandatory

CIM_Container Mandatory

HP_Location Mandatory

HP_RegisteredProfile Mandatory See Section 10.7 Indications

None defined.

10.1 HP_StorageEnclosureProcessor The HP_StorageEnclosureProcessor is used to model an HP storage enclosure. Error! Reference source not found. shows the properties that shall be implemented for the HP_StorageEnclosureProcessor class and its subclasses.

Version 1.0.1 21

Table 5 – Class: HP_StorageEnclosureProcessor


CreationClassName M Key

Name M Key

NameFormat M Shall be set to “Other”

OperationalStatus M (see section 7.1.1)

ElementName M

Dedicated M (see section 7.1.2)

OtherDedicatedDescriptions M (see section 7.1.3)

10.2 HP_StorageEnclosure

HP_StorageEnclosure is a subclass of CIM_Chassis and is used to model the physical chassis for an HP Storage Enclosure. Error! Reference source not found. shows the properties that shall be implemented for the HP_StorageEnclosureProcessor class and its subclasses.

Table 6 – Class: HP_StorageEnclosure



Tag M Key

ElementName M User friendly Name

Location M (see section 7.2.1)

Model M (see section 7.2.2)

SerialNumber M (see section 7.2.3)

PartNumber M (see section 7.2.4)

Manufacturer M (see section 7.2.5)

Name M (see section 7.2.6)

Version M (see section 7.2.7)

10.3 HP_DriveCage

HP_DriveCage is a subclass of CIM_PhysicalPackage and is used to model the physical cage for an HP Drive Cage. Table Error! Reference source not found. shows the properties that shall be implemented for the HP_StorageEnclosureProcessor class and its subclasses.

22 Version 1.0.1

Table 7 – Class: HP_DriveCage



Tag M Key

ElementName M User friendly Name

DriveBays O (see section 7.3.1)

DuplexLocation O (see section 7.3.2)

BackplaneSpeed O (see section 7.3.3)

Model M

SerialNumber M

PartNumber M

Manufacturer M

Name M

Version M

10.4 CIM_SystemComponent

CIM_SystemComponent is used to model the association between HP_StorageEnclosureProcessor and the Scoping CIM_ComputerSystem instance. Table 8 shows the properties that shall be implemented for the CIM_SystemComponent class and its subclasses.

Table 8 – Class: CIM_SystemComponent


GroupComponent M Key, Scoping CIM_ComputerSystem Instance

PartComponent M Key

10.5 CIM_SystemPackaging

CIM_SystemPackaging is used to model the association between HP_StorageEnclosureProcessor and the physical HP_StorageEnclosure instance. Table 9 shows the properties that shall be implemented for the CIM_SystemPackaging class and its subclasses.

Table 9 – Class: CIM_SystemPackaging


Antecedent M Key, CIM_PhysicalElement

Dependent M Key, CIM_System

10.6 CIM_Containner

CIM_Container is used to model the association between HP_StorageEnclosure and the physical HP_DriveCage instance. Table 10 shows the properties that shall be implemented for the CIM_Container class and its subclasses.

Version 1.0.1 23

Table 10 – Class: CIM_SystemContainer


GroupComponent M Key, Containing physical package

PartComponent M Key, CIM_PhysicalElement







RegisteredName Mandatory “HP Storage Enclosure”





None Defined




None Defined

24 Version 1.0.1

ANNEX A (normative)

Change Log


.001 8/22/06 Initial Draft

.002 9/14/06 Update per WBEM TC review - 9/14/06

.003 9/15/06 Removed reference to HP_Location Profile, updated table of contents

.004 9/19/06 Corrected instance diagram for internal enclosure.

.005 9/21/06 Corrections to fig 4 and fig 5 to show correct association for Base Server

.006 11/30/06 Updated per rQms/Feedback

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 Changed the version of the profile shown in the footers Added 2010 to copyright string

Version 1.0.1 25


Acknowledgments

26 Version 1.0.1



CR

Number Date Title

CR00113 8/23/06 Create HP Storage related profiles

Version 1.0.1 27

Bibliography



Date: 04/04/2011

Version: 2.0.0

HP Smart Array Profile




2 Version 1.3.0015.0

Contents

1 SCOPE .................................................................................................................................................. 9

2 NORMATIVE REFERENCES ................................................................................................................ 9

2.1 APPROVED REFERENCES .................................................................................................................. 9 2.2 SNIA SMI-S 1.2 REVISION 6 REFERENCES UNDER DEVELOPMENT ..................................................... 9 2.3 OTHER REFERENCES ........................................................................................................................ 9

3 TERMS AND DEFINITIONS .................................................................................................................. 9

4 SYMBOLS AND ABBREVIATED TERMS.......................................................................................... 10

5 SYNOPSIS ........................................................................................................................................... 11

6 DESCRIPTION .................................................................................................................................... 11

6.1 HOST HARDWARE RAID CONTROLLER............................................................................................. 13 6.2 ARRAY ........................................................................................................................................... 18 6.3 BLOCK SERVICES ............................................................................................................................ 19 6.4 DISK DRIVE LITE ............................................................................................................................. 21 6.5 EXTENT MAPPING ........................................................................................................................... 23 6.6 DISK SPARING ................................................................................................................................ 24 6.7 PROFILE REGISTRATION .................................................................................................................. 25 6.8 CONSOLIDATED STATUS .................................................................................................................. 26 6.9 MONITORING AND PERFORMANCE (MNP) DATA ............................................................................... 27 6.10 LOCATION INFORMATION .............................................................................................................. 27 6.11 SOFTWARE INVENTORY ............................................................................................................... 27 6.12 SAS TARGET PORT SUPPORT ...................................................................................................... 28 6.13 SAS INITIATOR PORT SUPPORT .................................................................................................... 29 6.14 SAS ENCLOSURE PORT SUPPORT ................................................................................................ 31

7 IMPLEMENTATION REQUIREMENTS .............................................................................................. 33

7.1 HPSA_ARRAYCONTROLLER ........................................................................................................... 33 7.2 HPSA_ARRAYSYSTEM ................................................................................................................... 37

7.2.1 HPSA_ArraySystem.Identify(uint32 Duration) ...................................................................... 37 7.2.2 HPSA_ArraySystem.Dedicated ............................................................................................. 37

7.3 HPSA_DISKDRIVE ......................................................................................................................... 37 7.3.1 HPSA_DiskDrive.TotalPowerOnHours ................................................................................. 37 7.3.2 HPSA_DiskDrive.DriveInterface ............................................................................................ 38 7.3.3 HPSA_DiskDrive.MediaType ................................................................................................ 38 7.3.4 HPSA_DiskDrive.NegotiatedSpeed ...................................................................................... 38 7.3.5 HPSA_DiskDrive.NegotiatedDataWidth ................................................................................ 38 7.3.6 HPSA_DiskDrive.Identify(uint32 Duration) ............................................................................ 39 7.3.7 HPSA_DiskDrive.DriveConfiguration .................................................................................... 39 7.3.8 HPSA_ DiskDrive.DriveRotationalSpeed .............................................................................. 39 7.3.9 HPSA_DiskDrive.DriveHasMNPData .................................................................................... 39 7.3.10 HPSA_DiskDrive.DrivePlacement ......................................................................................... 39 7.3.11 HPSA_DiskDrive.ControllerLocation ..................................................................................... 39 7.3.12 HPSA_DiskDrive.OperationalStatus. .................................................................................... 40 OperationalStatus[1]: 0x8007 (Not Authenticated) ........................................................................... 41 7.3.13 HPSA_DiskDrive.SSDTotalPowerOnHours .......................................................................... 41 7.3.14 HPSA_DiskDrive.SSDPercentageEnduranceUsed .............................................................. 41 7.3.15 HPSA_DiskDrive.SSDLifeRemaining .................................................................................... 41 7.3.16 HPSA_DiskDrive. SSDWearStatus ....................................................................................... 41 7.3.17 HPSA_DiskDrive.SmartDriveCarrierAuthStatus ................................................................... 41

Version 2.0.0 3

7.3.18 HPSA_DiskDrive.OtherSmartDriveCarrierAuthStatus .......................................................... 41 7.4 HPSA_STORAGEVOLUME ............................................................................................................... 41

7.4.1 HPSA_StorageVolume.Deleteable........................................................................................ 42 7.4.2 HPSA_StorageVolume.Accelerator ...................................................................................... 42 7.4.3 HPSA_StorageVolume.StripeSize ........................................................................................ 42 7.4.4 HPSA_StorageVolume.PercentComplete ............................................................................. 42 7.4.5 HPSA_StorageVolume.FaultTolerance ................................................................................. 42 7.4.6 HPSA_StorageVolume.OperationalStatus ............................................................................ 42 7.4.7 HPSA_StorageVolume. PhysicalDrvMultipathAccess .......................................................... 43 7.4.8 HPSA_StorageVolume.OSName .......................................................................................... 44 7.4.9 HPSA_StorageVolume.Identify(uint32 Duration) .................................................................. 44

7.5 HPSA_STORAGEPOOL ................................................................................................................... 44 7.5.1 HPSA_StoragePool.Identify(uint32 Duration) ....................................................................... 44

7.6 HPSA_MEDIAACCESSSTATDATA .................................................................................................... 44 7.6.1 HPSA_MediaAccessStatData.AbortedCommands ............................................................... 44 7.6.2 HPSA_MediaAccessStatData.BadTargetErrors ................................................................... 44 7.6.3 HPSA_MediaAccessStatData.ECCRecoveredReadErrors .................................................. 45 7.6.4 HPSA_MediaAccessStatData.FormatErrors ......................................................................... 45 7.6.5 HPSA_MediaAccessStatData.HardReadErrors .................................................................... 45 7.6.6 HPSA_MediaAccessStatData.HardWriteErrors .................................................................... 45 7.6.7 HPSA_MediaAccessStatData.HardwareErrors ..................................................................... 45 7.6.8 HPSA_MediaAccessStatData.HotPlugCount ........................................................................ 45 7.6.9 HPSA_MediaAccessStatData.MediaFailures ....................................................................... 45 7.6.10 HPSA_MediaAccessStatData.NotReadyErrors .................................................................... 45 7.6.11 HPSA_MediaAccessStatData.OtherTimeOuts ..................................................................... 45 7.6.12 HPSA_MediaAccessStatData.SCSIBusFaults ...................................................................... 45 7.6.13 HPSA_MediaAccessStatData.SectorsRead ......................................................................... 45 7.6.14 HPSA_MediaAccessStatData.SectorsWritten ...................................................................... 45 7.6.15 HPSA_MediaAccessStatData.SeekCount ............................................................................ 45 7.6.16 HPSA_MediaAccessStatData.SeekErrors ............................................................................ 45 7.6.17 HPSA_MediaAccessStatData.SpinUpErrors ........................................................................ 46 7.6.18 HPSA_MediaAccessStatData.DRQTimeOuts ...................................................................... 46 7.6.19 HPSA_MediaAccessStatData.RetryRecoveredReadErrors ................................................. 46 7.6.20 HPSA_MediaAccessStatData.RetryRecoveredWriteErrors .................................................. 46 7.6.21 HPSA_MediaAccessStatData.FailedReadRecovers ............................................................ 46 7.6.22 HPSA_MediaAccessStatData.FailedWriteRecovers ............................................................. 46 7.6.23 HPSA_MediaAccessStatData.ServiceHours ........................................................................ 46

7.7 HPSA_TSASSCSIPROTOCOLENDPOINT ........................................................................................ 46 7.7.1 HPSA_TSASSCSIProtocolEndpoint.ProtocolIFType ............................................................ 46 7.7.2 HPSA_TSASSCSIProtocolEndpoint.OtherTypeDescription ................................................. 46 7.7.3 HPSA_TSASSCSIProtocolEndpoint.Role ............................................................................. 46 7.7.4 HPSA_TSASSCSIProtocolEndpoint.Path ............................................................................. 46

7.8 HPSA_TSASPORT ........................................................................................................................ 47 7.8.1 HPSA_TSASPort. OperationalStatus .................................................................................... 47 7.8.2 HPSA_TSASPort.PortType ................................................................................................... 47 7.8.3 HPSA_TSASPort.UsageRestriction ...................................................................................... 47

7.9 HPSA_ISASSCSIPROTOCOLENDPOINT ......................................................................................... 47 7.9.1 HPSA_ISASSCSIProtocolEndpoint.ProtocolIFType ............................................................. 47 7.9.2 HPSA_ISASSCSIProtocolEndpoint.OtherTypeDescription .................................................. 47 7.9.3 HPSA_ISASSCSIProtocolEndpoint.Role .............................................................................. 47

7.10 HPSA_ ISASPORT ..................................................................................................................... 47 7.10.1 HPSA_ISASPort.OperationalStatus ...................................................................................... 47 7.10.2 HPSA_ISASPort.PortType .................................................................................................... 47 7.10.3 HPSA_ISASPort.UsageRestriction ....................................................................................... 48

7.11 HPSA_ SCSIINITIATORTARGETLOGICALUNITPATH ...................................................................... 48 7.11.1 HPSA_ SCSIInitiatorTargetLogicalUnitPath.Initiator ............................................................. 48 7.11.2 HPSA_ SCSIInitiatorTargetLogicalUnitPath.Target .............................................................. 48

4 Version 2.0.0

7.11.3 HPSA_ SCSIInitiatorTargetLogicalUnitPath.LogicalUnit ....................................................... 48 7.11.4 HPSA_ SCSIInitiatorTargetLogicalUnitPath.State ................................................................ 48

7.12 HPSA_ENCPROTOCOLENDPOINT ................................................................................................ 48 7.12.1 HPSA_ EncProtocolEndpoint.ProtocolIFType ...................................................................... 48 7.12.2 HPSA_ EncProtocolEndpoint.OtherTypeDescription ............................................................ 49 7.12.3 HPSA_ EncProtocolEndpoint.Role........................................................................................ 49 7.12.4 HPSA_ EncProtocolEndpoint.Path........................................................................................ 49

7.13 HPSA_ENCSASPORT ................................................................................................................ 49 7.13.1 HPSA_EncSASPort. OperationalStatus ................................................................................ 49 7.13.2 HPSA_EncSASPort.PortType ............................................................................................... 49 7.13.3 HPSA_EncSASPort.UsageRestriction .................................................................................. 49

7.14 HPSA_CONNECTIVITYCOLLECTION ............................................................................................. 49 7.14.1 HPSA_ ConnectivityCollection. ConnectivityStatus .............................................................. 49

7.15 HPSA_ARRAYSYSTEMEXTERNALARRAYSYSTEM ......................................................................... 50 8 METHODS ........................................................................................................................................... 50

8.1 PROFILE CONVENTIONS FOR OPERATIONS ....................................................................................... 50 9 USE CASES ........................................................................................................................................ 51

9.1 HOST HARDWARE RAID CONTROLLER............................................................................................. 51 9.1.1 Host Hardware RAID Controller Physical model ................................................................... 53

9.2 EXTERNAL MSA500 STORAGE SUBSYSTEM ..................................................................................... 54 9.2.1 External MSA500 Storage Subsystem physical model ......................................................... 56

9.3 EXTERNAL MSA20 STORAGE SYSTEM .............................................................................................. 57 9.4 EXTERNAL INTELLIGENT STORAGE SYSTEM CONNECTED USING A HBA IN PCI BUS.............................. 58 9.5 SINGLE POOL – MULTIPLE STORAGE VOLUME .................................................................................. 59 9.6 MULTIPLE POOL EXAMPLE ............................................................................................................... 60 9.7 DISK SPARING – MULTIPLE SPARES ................................................................................................. 61 9.8 DISK SPARING - DRIVE FAILURE EXAMPLE ......................................................................................... 61

9.8.1 Before drive failure ................................................................................................................ 62 9.8.2 Drive Failed – Data Rebuilding .............................................................................................. 63 9.8.3 Drive Failed – Rebuild Complete........................................................................................... 64 9.8.4 Drive replaced – Data Rebuild .............................................................................................. 65 9.8.5 Drive replaced – Rebuild Complete....................................................................................... 66

9.9 HOST BASED HBA CONTROLLER MODEL ........................................................................................... 66 9.10 EXTERNAL ARRAY WITH REDUNDANT CONTROLLER MODEL ............................................................ 67 9.11 CONSOLIDATED STATUS EXAMPLE ................................................................................................ 68 9.12 MULTI-PATH SUPPORT EXAMPLE ................................................................................................... 69

9.12.1 Multi-path support – Dual Port Drive ..................................................................................... 69 9.12.2 Multi-path support – Single Port Drive .................................................................................. 69 9.12.3 Multi-path support – Logical Volume Changes ..................................................................... 70

9.13 DETERMINE SMART DRIVE CARRIER FIRMWARE VERSION ............................................................. 71 10 CIM ELEMENTS .............................................................................................................................. 72

10.1 HPSA_ARRAYSYSTEM ................................................................................................................ 72 10.2 HPSA_ARRAYCONTROLLER ........................................................................................................ 72 10.3 HPSA_DISKDRIVE ...................................................................................................................... 73 10.4 HPSA_STORAGEVOLUME ........................................................................................................... 74 10.5 HPSA_STORAGEPOOL ............................................................................................................... 74 10.6 HPSA_MEDIAACCESSSTATDATA ................................................................................................ 75 10.7 CIM_ELEMENTSTATISTICALDATA ................................................................................................ 75 10.8 HP_REGISTEREDPROFILE ........................................................................................................... 76 10.9 HPSA_ SCSIINITIATORTARGETLOGICALUNITPATH ...................................................................... 76 10.10 HPSA_ARRAYSYSTEMEXTERNALARRAYSYSTEM ......................................................................... 76 10.11 CIM_SOFTWAREIDENTITY ........................................................................................................... 77

11 DURABLE NAMES AND CORRELATABLE IDS ........................................................................... 77

Figures

Figure 1 – HP Smart Array profile: HHRC Class Diagram 13 Figure 2 – HP Smart Array profile: HHRC SA specific Class Diagram 16 Figure 3 – HP Smart Array profile: HHR Ports Class Diagram 17 Figure 4 – HP Smart Array profile: Array Controller Class Diagram 18 Figure 5 – HP Smart Array profile: Block Services Class Diagram 19 Figure 6 – HP Smart Array profile: Disk Drive Lite class diagram 21 Figure 7 – HP Smart Array profile: Extent Mapping Class Diagram 23 Figure 8 – HP Smart Array profile: Disk Sparing Class Diagram 24 Figure 9 – HP Smart Array profile: Profile Registration 25 Figure 10 – HP Smart Array profile: Consolidated Status 26 Figure 11 – HP Smart Array profile: MNP Data 27 Figure 12 – HP Smart Array profile: Software 28 Figure 13 – HP Smart Array profile: Target Port Class Diagram 29 Figure 14 – HP Smart Array profile: Initiator Port Class Diagram Multi-path support 30 Figure 15 – HP Smart Array profile: Multi-path support Diagram 31 Figure 26 - HP Smart Array profile: Disk sparing – Multiple Spares 61

Tables

Table 1 – Related Profiles 11 Table 2 – Consolidated Status Algorithm 26 Table 3 - HP Smart Array profile: HPSA_ArrayController.OperationalStatus[0] 33 Table 4 - HP Smart Array profile: HPSA_ArrayController.ADGSupported 33 Table 5 - HP Smart Array profile: HPSA_ArrayController.RebuildPriority 34 Table 6 - HP Smart Array profile: HPSA_ArrayController.ExpandPriority 34 Table 7 – HP Smart Array profile: HPSA_ArrayController. AcceleratorBackupPowerSource 34 Table 8 – HP Smart Array profile: HPSA_ArrayController.BatteryStatus 35 Table 9 – HP Smart Array profile: HPSA_ArrayController.CacheStatus 35 Table 10 – HP Smart Array profile: HPSA_ArrayController.CacheState 36 Table 11 – HP Smart Array profile: HPSA_ArrayController.ControllerStatus 36 Table 12 - HP Smart Array profile: HPSA_ArraySystem.Identify() Method: Return values 37 Table 13 - HP Smart Array profile: HPSA_ArraySystem.Identify() Method: Parameters 37 Table 14 - HP Smart Array profile: HPSA_ArraySystem.Dedicated 37 Table 155 - HP Smart Array profile: HPSA_DiskDrive.DriveInterface 38 Table 166 - HP Smart Array profile: HPSA_DiskDrive.MediaType 38 Table 177 - HP Smart Array profile: HPSA_DiskDrive.NegotiatedSpeed Parallel 38 Table 23- HP Smart Array profile: HPSA_DiskDrive.DrivePlacement 41 Table 24 - HP Smart Array profile: HPSA_DiskDrive.SmartDriveCarrierAuthStatus 41 Table 30- HP Smart Array profile: HPSA_TSASSCSIProtocolEndpoint.Path 46 Table 32 - HP Smart Array profile: HPSA_ EncProtocolEndpoint.Path 49 Table 33 - HP Smart Array profile: HPSA_ ConnectivityCollection.ConnectivityStatus 49 Table 45 - Class Properties: CIM_SoftwareIdentity 77

Version 2.0.0 7

Foreword

The HP Smart Array Profile (P00121) was prepared by the HP WBEM TC.

8 Version 2.0.0

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 Smart Array controllers. 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.

Version 2.0.0 9

1 Scope The HP Smart Array profile is an autonomous profile to describe management aspects of HP Smart Array controller and their attached storage devices. This profile extends certain profiles and sub-profiles defined in SNIA SMI-S version 1.2.











SNIA SMI-S 1.4.4

2.2 SNIA SMI-S 1.2 Revision 6 References under Development

SNIA SMI-S 1.4 (Revision 1 and 4)







10 Version 2.0.0












4 Symbols and Abbreviated Terms None.

Version 2.0.0 11

5 Synopsis Profile Name: HP Smart Array Profile

Version: 2.0.0



Extends: SNIA SMI-S Array, Host Hardware RAID Controller profiles.

The HP Smart Array Profile extends the SNIA Array and HHRC profiles to add the ability to model and represent HP Smart Array controllers.

Central Class: HPSA_ArraySystem for SNIA SMI-S Array profile, HPSA_PortController for Host Hardware RAID Controller profile


Profile Name Organization Version Relationship Behavior P00100 HP Profile Registration Profile


P00113 HP Consolidated Status Profile



P00120 HP Storage Enclosure Profile


Array profile SNIA 1.3.0 Mandatory

Host Hardware RAID Controller SNIA 1.3.0 Mandatory


Extent Mapping SNIA 1.3.0 Mandatory

Physical Package SNIA 1.3.0 Mandatory

Location SNIA 1.3.0 Mandatory

Disk Sparing SNIA 1.3.0 Mandatory

Generic Initiator Ports SNIA 1.3.0 Optional



SAS Target Ports profile SNIA 1.4.4 Optional Implemented clause 10 of SMI-S 1.4.4 for multi-path supported smart array controllers

SAS Initiator Ports profile SNIA 1.4.4 Optional Implemented clause 18 of SMI-S 1.4.4 for multi-path supported smart array controllers

SAS Enclosure Ports profile SNIA 1.4.4 Optional Modelled Enclosure ports using connectivity collection model in SMI-S 1.4.4 clause 14.

6 Description This profile models 2 management domains related to Smart Array controllers. The first is a Smart Array Controller installed directly in a base server. In this case, it is referred to as a Host Based Smart Array

12 Version 2.0.0

and is modeled using the SMI-S Host Hardware Raid Controller profile and HP extensions defined in this profile (see Section 6.1)

The second case is an external Smart Array controller installed in an external storage chassis (such as an MSA 500 or MSA 20). In this case, it is modeled using the SMI-S Array profile and HP extensions defined in this profile (see Section 6.2)

Version 2.0.0 13

6.1 Host Hardware RAID Controller

ComputerSystem

Array

HP_ComputerSystem

HP Base Server

SystemDevicePortController

CentralClass

LogicalIdentityPhysicalPackageSystemPackaging

Product

ProductPhysicalComponent

DAPort

HostedAccessPoint

ProtocolEndpoint

Role: Initiator

StorageVolume

ProtocolControllerForUnit

SystemDevice

ComputerSystem

ArrayControllerComponentCS

See DA Port

See HP Array Controller

See DMTF Physical Asset Profile Realizes

See Block Services

See Initiator Ports

ProtocolEndpoint

Role: Target

ProtocolControllerSAPAvailableForElement

See Target Ports

CIM_SCSIInitiatorTargetLogicalUnitPath

StorageExtent

Primoridal Extent

See Extent Mapping

LogicalPort

UsageRestriction:Backend Only

LogicalPort

UsageRestriction:Front-end Only

DeviceSAPImplementation

ControlledBy

SystemComponent


LogicalPortStatistics

ElementStatisticalData

ProtocolEndpoint

See HHRC and DA Port

BasedOn


DiskDrive

MediaPresent

SAPAvailableForElement


ProtocolEndPoint

Role: Target

LogicalPort

StorageEnclosure

CIM_Chassis


SAPAvailableforElement

ConnectivityCollection

MemberofCollection

MemberofCollection

HostedCollection

Figure 1 – HP Smart Array profile: HHRC Class Diagram

14 Version 2.0.0

The Host Hardware RAID Controller profile is used to model PCI based Smart Array HBAs.

ComputerSystem

Array

HP_ComputerSystem

HP Base Server

SystemDevicePortController

CentralClass

LogicalIdentityPhysicalPackageSystemPackaging

Product


DAPort

HostedAccessPoint

ProtocolEndpoint

Role: Initiator

StorageVolume


SystemDevice

ComputerSystem

ArrayControllerComponentCS

See DA Port


See DMTF Physical Asset Profile Realizes

See Block Services

See Initiator Ports

ProtocolEndpoint

Role: Target

ProtocolControllerSAPAvailableForElement

See Target Ports


StorageExtent

Primoridal Extent

See Extent Mapping

LogicalPort


LogicalPort



ControlledBy

SystemComponent


LogicalPortStatistics


ProtocolEndpoint


BasedOn


DiskDrive

MediaPresent



ProtocolEndPoint

Role: Target

LogicalPort

StorageEnclosure

CIM_Chassis


SAPAvailableforElement


MemberofCollection

MemberofCollection

HostedCollection

Figure 1 shows the class derivation from the SNIA defined required classes and their related SNIA profiles. The central class for HBAs will be HPSA_PortController and is associated to the Host system via CIM_SystemComponent. HPSA_ArraySystem represents the top level system for the host based Smart Array. This instance of HPSA_ArraySystem will be associated to the central class (HPSA_PortController)

Version 2.0.0 15

via CIM_LogicalIdentity. Most Smart Array HBA managed objects will be scoped (or associated) to this top level system instance. See section 6.2, Array Profile.

The use of PhysicalPackage will serve to model the physical aspects of the HBA and also the use of HPSA_Product to hold Marketing names for supported HBAs. HPSA_PhysicalPackage is associated to the Top Level System (HPSA_ArraySystem) via CIM_SystemPackaging association. HPSA_Product is associated to HPSA_PhysicalPackage via CIM_ProductPhysicalPackage.

Initiator ports and Target ports will serve to model the management of SAS Initiator ports and SAS Target ports respectively in case of multi-path supported smart array controllers.

The SAS Target Port Profile models the behavior of SAS target ports of disk drives in storage systems such as MSAs.

The Connectivity Collection model is used to model target ports of MSAs.

The SAS Initiator Port Profile models the behavior of initiator ports in a smart array controller. It uses the same primary classes as the Target Port Profile.

Sections 6.12 and 6.13 illustrate the target port support and initiator port support in smart array controllers.

16 Version 2.0.0

HPSA_ArraySystem

HP_ComputerSystem

HP Base Server

SystemDevice

HPSA_PortController

CentralClassLogicalIdentity

ComputerSystem

PortController

HPSA_PhysicalPackageSystemPackaging

PhysicalPackage

HPSA_Product

Product


HPSA_DAPort

HostedAccessPoint

DAPort

HPSA_SCSIProtocolEndpoint

Role: Initiator

SCSIProtocolEndPoint

HPSA_StorageVolume

StorageVolume


SystemDevice

HPSA_ArrayController

ComponentCS

ComputerSystem

See DA Port


See DMTF Physical Asset ProfileRealizes

See Block Services

See Initiator Ports


Role: Target

HPSA_SCSIProtocolController

SCSIProtocolController


See Target Ports

HPSA_SCSIInitiatorTargetLogicalUnitPath

HPSA_StorageExtent

Primoridal Extent

StorageExtent

See Extent Mapping and Disk Drive Lite

HPSA_ISASPort


SASPort

HPSA_TSASPort



ControlledBy

SystemComponent

HPSA_ATAProtocolEndpoint

Role: Initiator


BasedOn




DiskDrive

HPSA_DiskDrive


MediaPresent

BindsTo


HPSA_EncProtocolEndPoint

Role: Target

HPSA_EncSASPort

DeviceSAPImplementation ConnectivityCollection

HPSA_StorageEnclosure

CIM_Chassis

SAPAvailableforElementMemberofCollection

HostedCollection

F

Version 2.0.0 17

igure 2 – HP Smart Array profile: HHRC SA specific Class Diagram

BindsToHPSA_SCSIProtocolEndpoint

Role: Initiator

See SAS Initiator Ports


Role: Target

See SAS Target Ports


HPSA_ISASPort


HPSA_TSASPort



HPSA_ATAProtocolEndpointRole: Initiator


HPSA_StorageExtent

Primoridal Extent

HPSA_LogicalPortStatisticsElementStatisticalData

HPSA_ATAProtocolEndpoint

Role: Target

See ATA Target Ports

HPSA_ATAPort

PortType: “SATA”


HPSA_StorageExtent

Primoridal Extent

HPSA_ATAInitiatorTargetLogicalUnitPath

HPSA_SASPhy

HPSA_SASPhyStatistics


ConcreteComponent

HPSA_SASPhy

HPSA_SASPhyStatistics


ConcreteComponent

Figure 3 – HP Smart Array profile: HHR Ports Class Diagram

18 Version 2.0.0

HPSA_ArraySystem

Central ClassSystemComponent

HPSA_ArrayControllerComponentCS

ComputerSystem

HPSA_RedundancySet

RedundancySet

HostedCollection

MemberOfCollection

HPSA_PhysicalPackage

SystemPackaging

HPSA_ArrayControllerPhysicalPackage

HPSA_ArrayControllerLocation

Container


PhysicalPackage

HP_Location

See HP Location

SystemPackaging

HPSA_ArraySystemLocation


HP_Location

See HP Location

See Multiple Computer System

Figure 4 – HP Smart Array profile: Array Controller Class Diagram

To allow for consistency between implementation that have redundant controllers and single controller implementations, the actual controller is modeled as HPSA_ArrayController class. Figure 2 shows the class derivation and their related profiles. This is a subclass of CIM_ComputerSystem and is associated to the Top Level System using CIM_ComponentCS. This class has been extended to add properties that address Smart Array specifics (e.g. Accelerator, Expand/Rebuild priorities etc.). (See Section 7.1)

The HP Location profile is used to model the location of the array system and the array controller.

Front end ports are modeled as CIM_DAPorts which implies direct attached to the host bus (e.g. PCI, PCI-X, etc.).

6.2 Array

The SNIA Array profile is used to model external storage subsystems (e.g. MSA500) attached to the host via SCSI through a Smart Array HBA. See Figure 1 in section 6.1. Note that the central class in this case is HPSA_ArraySystem which also serves as the Top Level System from the array point of view. This

Version 2.0.0 19

storage implementation can accommodate redundant controllers. See Figure 2 in section 6.1. This is modeled using SNIA Multiple Computer Systems profile and uses HPSA_RedundancySet to show a collection of controllers in a redundant configuration. The controllers are associated to the Top Level System via CIM_ComponentCS. In the case of externally connected controllers, the front end port is modeled on the connection type to the host (e.g. CIM_SPIPort).

PhysicalPackage package is used to model the chassis (containing the array controller(s) and optionally a storage enclosure) that is external to the host. The top level system, HPSA_arraySystem of the external storage is associated to the top level system of the PCI based smart array HBA via instance of HPSA_arraySystemExternalArraySystem. See Section 9.4 for specific use cases

6.3 Block Services

HPSA_ArraySystem

SystemDevice

HPSA_PrimordialPool

Promordial = “True”

StoragePool

AllocatedFromStoragePool

HostedStoragePool

HPSA_StoragePool

Promordial = “False” (Concrete)


HPSA_StorageVolume

StorageVolume

HPSA_StorageCapabilities

StorageCapabiliites

HPSA_StorageCapabilities

ElementCapabilities

ElementCapabilities

HPSA_StorageSetting

ElementSettingDataStorageSetting

HostedStoragePool

Figure 5 – HP Smart Array profile: Block Services Class Diagram

20 Version 2.0.0

The Block services profile is used to model the logical storage that is presented by the Array system.

In this implementation, there will be one Primordial Pool to represent all the raw storage managed by the Array system (HPSA_PrimordialPool). The Primordial Pool instance shall be associated to the Top Level System via CIM_HostedStoragePool. All concrete pools will be allocated from this primordial pool. All concrete pools shall be associated to the primordial via a CIM_AllocatedFromStoragePool. An HPSA_StorageCapabilities instance shall be associated to each pool to indicate current capabilities for the pool.

The instances HPSA_PrimordialPool represent raw storage managed by the array system. This instance of HPSA_PrimordialPool is associated to the top level system (HPSA_ArraySystem) using CIM_HostedStoragePool. Concrete pools are allocated from primordial pools (HPSA_PrimordialPool). This is represented by instances of HPSA_StoragePool associated to the primordial pool (HPSA_PrimordialPool) it is allocated from via instances of CIM_AllocatedFromStoragePool.

Storage Volumes (HPSA_StorageVolume) will be allocated from concrete pools (HPSA_StoragePool) and associated them via CIM_AllocatedFromStoragePool. The current storage settings for a storage volume are specified in the associated Storage Setting class (HPSA_StorageSetting). HPSA_StorageSetting will be associated to the storage volume via CIM_ElementSettingData.

Version 2.0.0 21

6.4 Disk Drive Lite

HPSA_DiskDrive

DiskDrive

HPSA_SoftwareIdentity

Drive F/WSmart Carrier Application FWSmart Carrier Bootloader FW

MediaPresent

SoftwareIdentity

HPSA_StorageExtent

Primoridal Extent

StorageExtent


HPSA_DiskPhysicalPackage

Realizes

PhysicalPackage

HPSA_DiskLocation

HP_Location

HPSA_ArraySystem

SystemDevice


HP_DriveCage

HP_StorageEnclosure

Container

Container

HP_StorageEnclosureProcessorSystemPackaging

SystemComponent

See HP_StorageEnclosure Profile

Figure 6 – HP Smart Array profile: Disk Drive Lite class diagram

The Disk Drive Lite profile is used to model logical and physical aspects of disks. In this profile the HPSA_DiskDrive class has been extended from CIM_DiskDrive to add HP specific properties.

Drive firmware will be supported within the HPSA_DiskDriveFirmware class associated to the HPSA_DiskDrive class via CIM_ElementSoftwareIdentity in accordance with SNIA Disk Drive Lite Profile.

Smart Drive Carrier Application firmware will be supported within the CIM_SoftwareIdentity class associated to the HPSA_DiskDrive class via CIM_ElementSoftwareIdentity in accordance with SNIA Disk Drive Lite Profile.

22 Version 2.0.0

Smart Drive Carrier Bootloader firmware will be supported within the CIM_SoftwareIdentity class associated to the HPSA_DiskDrive class via CIM_ElementSoftwareIdentity in accordance with SNIA Disk Drive Lite Profile.

Figure 6 shows how the disk drives may be contained within a storage enclosure. (See HP Storage Enclosure Profile, P00120).

Version 2.0.0 23

6.5 Extent Mapping

HPSA_DiskDrive

DiskDrive

MediaPresent

HPSA_StorageExtent

Primoridal Extent

StorageExtent

Realizes

HPSA_ArraySystem

SystemDeviceHPSA_StorageVolume

HPSA_StoragePool

Concrete Pool

StorageVolume

StoragePool


BasedOn

ConcreteComponent

HostedStoragePool

SystemDevice1 1

Figure 7 – HP Smart Array 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. These extents are associated one to one with disk drive instances using the CIM_MediaPresent association.

24 Version 2.0.0

6.6 Disk Sparing

HPSA_StorageExtent

HPSA_StorageExtent

HPSA_StorageExtent

HPSA_StoragePool

Concrete Pool

ConcreteComponent HPSA_StorageRedundancySetMemberOfCollection

HPSA_StorageExtent

SpareIsSpare

StorageExtent

StorageRedundancySetStoragePool

Figure 8 – HP Smart Array profile: Disk Sparing Class Diagram

The Disk Sparing profile is used to model spare drives for raid sets. All the drives (HPSA_StorageExtent instances) in a raid shall be associated to an instance of HPSA_StorageRedundancySet via CIM_MemberOfCollection. Any spare drives (HPSA_StorageExtent) shall be associated to the same Storage Redundancy Set via the CIM_IsSpare association.

For Smart Array, any raid set may have more than one spare drive and any drive configured as a spare can be a spare to more than one Storage Redundancy Collection.

When a spare drive is “in use”, the HPSA_StorageExtent will be associated to the failed drive(s) via CIM_Spared association.

See Section 9.7 for specific use cases.

Version 2.0.0 25

6.7 Profile Registration

HPSA_ArraySystem

HPSA_PortController


ElementConformsToProfile

HPSA_ArraySystem

Central Class

ComputerSystem


HHRC

Array


SNIA “HHRC”

Interop Namespace


HP WBEM TC “Smart Array”

HP_ExtendsProfile


SNIA “Array”

Interop Namespace


HP WBEM TC “Smart Array”

HP_ExtendsProfile

HP_ComputerSystem

ScopingClass

SystemDevice


HP WBEM TC “HP Base Server”


ReferencesProfile

HP_ComputerSystem

ScopingClass


HP WBEM TC “HP Base Server”

ReferencesProfile

SystemComponent


SystemComponent

Figure 9 – HP Smart Array profile: Profile Registration

The CIM_Registered profile instances will be populated in the root\Interop namespace. If central class profile registration methodology is used, there shall be a CIM_ElementConformsToProfile association to locate the central class for each profile. If scoping profile registration methodology is used, there shall be a References association from the HP Base Server profile to the HP Smart Array profile and a CIM_ElementConformsToProfile association between the HP Base Server profile and the scoping class, HP_ComputerSystem. Supported profiles are SNIA:Array and SNIA:HHRC.

26 Version 2.0.0

6.8 Consolidated Status

HPSA_ArraySystem

OperationalStatus = OK

HPSA_ArraySystem


HPSA_ArraySystem

OperationalStatus = Degraded

HPSA_StorageSpecificCollection

GroupOperationalStatus = Degraded

MemberOfCollectionMemberOfCollection

MemberOfCollection


HP_ComputerSystem


HPSA_ArraySystem


HPSA_ArraySystem





MemberOfCollection


HP_ComputerSystem



HPSA_StorageGroupHostedCollection

Figure 10 – HP Smart Array profile: Consolidated Status

This provider will calculate operational status values for each Top Level System. These status values will be in accordance with the HP WBEM TC P00113, HP Consolidated Status Profile. This will allow the condition of the Storage System to participate in the Consolidated Status mechanism. The “worst off” status of these instances will be aggregated and populated in a single instance of HPSA_StorageSpecificCollection which then gets collected by the Base Server provider to participate in the overall consolidated status algorithm. The instances of HPSA_ArraySystem will be associated to HPSA_StorageSpecificCollection via CIM_MemberOfCollection. The instances of HPSA_StorageSpecificCollection will be associated to the singleton instance of HP_ComputerSystem (see. HP Base Server Profile) via a subclass of HP_GroupHostedCollection (HPSA_StorageGroupHostedCollection).

The consolidated status will be defined with three possible states. These three states are defined in Table 2 along with the algorithms to calculate each possible status.

Table 2 – Consolidated Status Algorithm

Reason for Status Error If there is a logical drive failure or

If there is a Storage Enclosure in Critical condition or If there is a SA controller cache failure or If the active SA controller is failed

Degraded If none Failed conditions are met and If a physical drive status is not OK or If a logical drive status is not OK or If a SA controller cache battery status is not OK If a SA controller cache status is not OK If a Storage Enclosure status is not OK

Version 2.0.0 27

Reason for Status OK If none of the Failed and none of the Degraded

conditions are met

6.9 Monitoring and Performance (MNP) Data

HPSA_DiskDrive

DiskDrive


HPSA_ArraySystem

SystemDevice

HPSA_MediaAccessStatData

CIM_MediaAccessStatData

Figure 11 – HP Smart Array profile: MNP Data

The SNIA Disk Drive Lite profile has been extended to include an instance of HPSA_MediaAccessStatData. This is associated to the HPSA_DiskDrive instance via CIM_ElementStatisticalData. The HPSA_MediaAccessStatData class has been extended form CIM_MediaAccessStatData to add properties to report the Monitoring and Performance counters for Hard Drives.

These classes are conditional and shall be present when the HPSA_DiskDrive.DriveHasMNPData property is set to true (See section 7.3.8).


An instance of HP_Location sub class will be associated to applicable physical packages by CIM_PhysicalElementLocation.


Firmware version is supported for Array Controllers. Firmware version will be reported in an instance of CIM_SoftwareIdentity as defined in DMTF Software Inventory profile DSP1023.

28 Version 2.0.0

HPSA_ArraySystem HPSA_Firmware

CentralClass

ComputerSystem SoftwareIdentity

InstalledSoftwareIdentity


Figure 12 – HP Smart Array profile: Software

Disk Drive firmware will be reported as part of the SNIA Disk Drive Lite implementation (See section 6.4).

6.12 SAS Target Port support

The Target port subprofile is used to model the Serial Attached SCSI (SAS) Target Port. This support is implemented only for multi-path supported controllers.

In this implementation, for each port on a SAS drive an instance of HPSA_TSASSCSIProtocolEndpoint and HPSA_TSASPort will be created. The instances will be associated with an instance of HPSA_TSASPortTSASSCSIPE which derives from CIM_DeviceSAPImplementation.

The instances of HPSA_TSASPort will be associated to HPSA_ArraySystem, representing the containing smart array controller, via instances of HPSA_ArraySystemTSASPort (derives from CIM_SystemDevice).

Each instance of HPSA_TSASSCSIProtocolEndpoint will be associated with both HPSA_ArraySystem (via HPSA_ArraySystemTSASSCSIPE) and HPSA_DiskDrive (via HPSA_DiskDriveTSASSCSIPE) which represents the disk drive the port is contained on.

Version 2.0.0 29

HPSA_ArraySystem

HPSA_DiskDrive

HPSA_StorageExtent

MediaP

resentH

PS

A_D

iskDriveS

torageExtent

DiskDrive Lite

CIM

_System

Device

HP

SA

_ArrayS

ystemD

iskDrive

CIM

_System

Device

HP

SA

_ArrayS

ystemS

torageExtent

HPSA_TSASSCSIProtocolEndpoint

HPSA_TSASPort

CIM_SystemDeviceHPSA_ArraySystemTSASPort C

IM_H

ostedAccessP

ointH

PS

A_A

rraySystem

TSA

SS

CS

IPE

Target Port / SAS Target Port

CIM

_SA

PA

vailableForElem

entH

PS

A_D

iskDriveTS

AS

SC

SIP

E


HPSA_TSASPort

CIM_DeviceSAPImplementationHPSA_TSASPortTSASSCSIPE

Figure 13 – HP Smart Array profile: Target Port Class Diagram

6.13 SAS Initiator Port support

The Initiator port subprofile is used to model the SMI-S 1.4 SAS Initiator Port profile. This support is implemented only for multi-path supported controllers.

In this implementation, for all ports on the smart array controller that are supported an instance of both HPSA_ISASPort and HPSA_ISASSCSIProtocolEndpoint is created.

Each instance of HPSA_ISASPort is associated to HPSA_ArraySystem (via HPSA_ArraySystemISASPort) that represents the array controller system that the port is contained on. It is also associated to the instance of HPSA_PortController (via HPSA_PortControllerISASPort) that represents the port controller of the array system.

Each instance of HPSA_ISASSCSIProtocolEndpoint is associated to the instance of HPSA_ISASPort (via HPSA_ISAPortSASISASSCSIPE) that implements it. Each instance is also associated to the instance of HPSA_ArraySystem (via HPSA_ArraySystemISASSCSIPE) that contains the port that implements the protocol endpoint.

30 Version 2.0.0

HPSA_ArraySystem

HPSA_PortController LogicalIdentityHPSA_ArraySystemPortController

HHRC

HPSA_ISASSCSIProtocolEndpoint

HPSA_ISASPort

Initiator Port / SAS Initiator


HPSA_ISASPort

CIM_SystemDeviceHPSA_ArraySystemISASPort

CIM_DeviceSAPImplementationHPSA_ISASPortISASSCSIPE

CIM_ControlledByHPSA_PortControllerISASPort

CIM_HostedAccessPointHPSA_ArraySystemISASSCSIPE

Figure 14 – HP Smart Array profile: Initiator Port Class Diagram Multi-path support

The following figure shows the low level implementation details for multi-path support.

For each path between a SAS initiator port and a SAS target port (contained on a SAS drive), an instance of HPSA_SCSIInitiatorTargetLogicalUnitPath will be created. This instance represents the path from the controller port and the drives port. The association is a 3-way and associates the initiator port, target port, and the storage extent of the physical disk.

Version 2.0.0 31

HPSA_ArraySystem

ElementName: “Smart Array xxx in slot n”

HPSA_DiskDrive

ElementName: “Port:1I Box: 1 Bay: 1”

HPSA_StorageExtent

MediaPresentHPSA_DiskDriveStorageExtent

DiskDrive Lite


HPSA_ISASPort

ElementName:Port: 1E



CIM

_HostedA

ccessPoint

HP

SA

_ArrayS

ystemIS

AS

SC

SIP

E


ElementName: Protocol Endpoint for Port 2

HPSA_TSASPort

ElementName: Port 1

CIM

_System

Device

HP

SA

_ArrayS

ystemTS

AS

Port

CIM

_HostedA

ccessPoint

HP

SA

_ArrayS

ystemTS

AS

SC

SIP

E


HPSA_ISASPort

ElementName:Port: 2E


ElementName: Protocol Endpoint for Port 1


HPSA_TSASPort

ElementName:Port 2


Consolidated Status


MemberOfCollectionHPSA_StorageSpecificCollection

HP_ComputerSystem

System

CIM

_Com

ponentCS

HP

SA

_Com

puterSystem

ArrayS

ystem

HPSA_PortController

ElementName: “Smart Array xxx in slot n”

SystemDevice(not currently populated by

WMI)



HPSA_StorageVolume

CIM_SystemDeviceHPSA_ArraySystemStorageVolume

CIM

_BasedO

nH

PS

A_S

torageExtentS

torageVolum

e



LogicalIdentityHPSA_ArraySystemPortController

CIM

_SA

PA

vailableForElem

entH

PS

A_D

iskDriveTS

AS

SC

SIP

E

HP

SA

_ArrayS

ystemS

torageEnclosureP

rocessor

Figure 15 – HP Smart Array profile: Multi-path support Diagram

6.14 SAS Enclosure Port support

Enclosure port support is modeled using the SMI-S connectivitycollection model. This support is implemented only for multi-path supported controllers.

In this implementation, for each port on Enclosure an instance of HPSA_EncProtocolEndpoint and HPSA_EncSASPort will be created. The instances will be associated with an instance of HPSA_EncSASPortEncPE derived from CIM_DeviceSAPImplementation.

HPSA_ISASSCSIProtocolEndpoint instance of the Initiator port profile and HPSA_EncProtocolEndpoint are grouped in one collection using HPSA_ConnectivityCollection instance to represent the connection between array controller initiator port to the Enclosure port.

32 Version 2.0.0

Each instance of HPSA_EncProtocolEndpoint will be associated with both HPSA_ArraySystem (via HPSA_ArraySystemEncPE) and HPSA_StorageEnclosure (via HPSA_ StorageEnclosureEncPE) which represents the StorageEnclosure the port is contained on

HPSA_PortController

CentralClass

PortController

HPSA_StorageEnclosure

CIM_Chassis

HPSA_ArraySystemLogicalIdentity

HPSA_ISASPort

HPSA_ISASSCSIProtocolEndPoint

Role: Initiator

DeviceSAPImplementa

tion

ControlledBy

SystemDevice

HostedAccessPoint

HPSA_EncProtocolEndPoint

Role: Target

HPSA_EncSASPort

DeviceSAPImplementationHPSA_EncSASPortEncPE

SAPAvailableforElementHPSA_StorageEnclosureEncPE

HostedAccessPointHPSA_ArraySystemEncPE

HPSA_ConnectivityCollection

HP_ComputerSystem

HP Base Server

HostedCollectionMemberofCollection

SystemDevice


Figure 16 – HP Smart Array profile: Enclosure Port support Diagram

Version 2.0.0 33

7 Implementation Requirements This section details the requirements for the HP extensions of this profile. All requirements for the related profiles defined in Table 1 in Section 5 apply.

7.1 HPSA_ArrayController

There shall be an instance of HPSA_ArrayController for each array controller present. These instances should be associated to the Top Level System (HPSA_ArraySystem) class by an instance of CIM_ComponentCS association. Note that some external storage subsystems may have multiple controllers configured in a redundant configuration. The HPSA_ArrayController class has been extended from CIM_ComputerSystem as defined in SNIA Multiple Computer Systems profile.

HPSA_ArrayController.OperationalStatus

OperationalStatus[0] will be used to indicates the overall health of the controller. Values for index [0] will be calculated as follows.

Table 3 - HP Smart Array profile: HPSA_ArrayController.OperationalStatus[0]

OperationalStatus[0] Reason for Status Error If the controller status is ERROR or

If the Cache Status is Permanently Disabled or If the Battery is failed

Degraded If none Failed conditions are met and If the Cache Status is Temporarily Disabled or If the Battery is not fully charged or If the Capacitor charge is low or If the capacitor is not attached or If the capacitor-based cache module backup operation failed or If the capacitor-based cache module restore operation failed or If the capacitor-based cache module hardware failed or If the Capacitor failed to charge or If the cache is not configured

OK If none of the Failed and none of the Degraded conditions are met

HPSA_ArrayController.ADGSupported

Value indicates whether this controller supports Advanced Data Guard Raid level.

Table 4 - HP Smart Array profile: HPSA_ArrayController.ADGSupported

Value ValueMap 0 Unknown 1 Yes 2 No 3 N/A

34 Version 2.0.0

HPSA_ArrayController.RebuildPriority

Value indicates the current controller rebuild priority.

Table 5 - HP Smart Array profile: HPSA_ArrayController.RebuildPriority

Value ValueMap 0 Unknown 1 Low 2 Medium 3 High 4 N/A

HPSA_ArrayController.ExpandPriority

Value indicates the current controller expand priority.

Table 6 - HP Smart Array profile: HPSA_ArrayController.ExpandPriority

Value ValueMap 0 Unknown 1 Low 2 Medium 3 High 4 N/A

HPSA_ArrayController.NumberOfPorts

Value indicates the total number of ports currently available on this controller.

HPSA_ArrayController.NumberOfInternalPorts

Value indicates the count of internal ports currently available on this controller.

HPSA_ArrayController.NumberOfExternalPorts

Value indicates the count of external ports currently available on this controller.HPSA_ArrayController.CacheBoardPresent

Value indicates whether there is a cache board attached to this controller.

HPSA_ArrayController.CacheHasBattery

Value indicates whether the cache memory has battery backup. The backup source can be a battery or a capacitor. The property AcceleratorBackupPowerSource would indicate if the backup power source is a battery or capacitor.

HPSA_ArrayController.AcceleratorBackupPowerSource

Value indicates if the cache module is battery backed or capacitor backed. Table 7 – HP Smart Array profile: HPSA_ArrayController. AcceleratorBackupPowerSource

Version 2.0.0 35

Value ValueMap 0 Unknown 1 ACCEL_BATTERY 2 ACCEL_CAPACITOR 3 N/A

HPSA_ArrayController.BatteryStatus

Value indicates the current status of the backup source. The backup source can be a battery or a capacitor.

Table 8 – HP Smart Array profile: HPSA_ArrayController.BatteryStatus

Value ValueMap 0 Unknown 1 OK 2 Failed 3 Not Fully charged 4 Not Present

HPSA_ArrayController.CacheSizeTotal

Total size of cache memory installed on the controller in bytes.

HPSA_ArrayController.CacheReadPercent

Indicates the amount of cache memory assigned to read operations as a percentage of total cache memory.

HPSA_ArrayController.CacheWritePercent

Indicates the amount of cache memory assigned to write operations as a percentage of total cache memory.

HPSA_ArrayController.CacheParityReadErrors

Indicates the number of Cache parity read errors.

HPSA_ArrayController.CacheParityWriteErrors

Indicates the number of Cache parity write errors.

HPSA_ArrayController.CacheSerialNumber

String containing the serial number of the cache board if available.

HPSA_ArrayController.CacheStatus

Overall status of cache memory module. (E.g. Cache may be temporarily disabled while some rebuild operations are in progress.)

Table 9 – HP Smart Array profile: HPSA_ArrayController.CacheStatus

36 Version 2.0.0

Value ValueMap 0 Unknown 1 OK 2 Temporarily disabled 3 Permanently disabled 4 Not Configured

HPSA_ArrayController.CacheState

CacheState carries the detailed error code for cache status. This property indicates the various cache disable conditions resulted due to failure in cache backup power source.

Table 10 – HP Smart Array profile: HPSA_ArrayController.CacheState

Value ValueMap 0 None 1 OK 2 Redundant Controller Cache Size Mismatch 3 Cache Disabled Expand In Progress 4 Cache Disabled Low Batteries 5 Cache Disabled Low Resources 6 Error Reading Cache Board 7 Requires Reboot To Enable Cache 8 Cache Disabled Run ADU 9 Cache Disabled Snapshot In Progress 10 Error Writing Cache Board 11 Wrong Cache Board Attached 12 Possible Data Loss From Low Battery 13 Error Detected Run ADU 14 Valid Data In Cache Board Found

15 Cache Disabled capacitor charge is low 16 Cache Disabled capacitor is not attached 17 capacitor-based cache module backup operation

failed 18 capacitor-based cache module restore operation

failed 19 capacitor-based cache module hardware failure 20 capacitor-based cache module capacitor failed to

charge

HPSA_ArrayController.ControllerStatus

This enumeration will be used to indicate the status returned by the controller. Table 11 – HP Smart Array profile: HPSA_ArrayController.ControllerStatus

Value ValueMap 0 Unknown 1 Other 2 OK 3 ERROR

Version 2.0.0 37

7.2 HPSA_ArraySystem

The HPSA_ArraySystem class has been extended form the CIM_ComputerSystem class as defined in SNIA Array/HHRC profiles and shall be instantiated to represent the top level system.

7.2.1 HPSA_ArraySystem.Identify(uint32 Duration)

This method will cause all hard drives connected to this controller to set some indicator (e.g. set or blink drive LEDs) for the given duration (default duration is 30 seconds). After the duration has expired the drive indicator(s) will return to normal use.

Return values for Identify() method shall be as specified in Table 12 where the method execution behavior matches the return code description.

Table 12 - HP Smart Array profile: HPSA_ArraySystem.Identify() Method: Return values

Value ValueMap 0 Request was successfully executed 1 Method not supported 2 Error occurred

Identify() parameters are specified in Table 13.

Table 13 - HP Smart Array profile: HPSA_ArraySystem.Identify() Method: Parameters

Qualifiers Name Type Description IN Duration uint32 n - Number of seconds to set identifier.

NULL – default of 30 secs. After the duration has expired the drive indicator(s) will return to normal use.

7.2.2 HPSA_ArraySystem.Dedicated

Enumeration indicating the purpose(s) to which the ComputerSystem is dedicated, if any, and what functionality is provided.

Table 14 - HP Smart Array profile: HPSA_ArraySystem.Dedicated

Value ValueMap 30,15 Host Hardware Raid Controller, Block Server 3 ,15 Storage (External) , Block Server

7.3 HPSA_DiskDrive

The HPSA_DiskDrive class has been extended from CIM_DiskDrive as defined in SNIA Disk Drive Lite profile.

7.3.1 HPSA_DiskDrive.TotalPowerOnHours

Value indicates the total number of hours that the drive has logged with power on.

38 Version 2.0.0

7.3.2 HPSA_DiskDrive.DriveInterface

Value indicates the type of interface for the disk. (E.g. Parallel, SATA, SAS)

Table 155 - HP Smart Array profile: HPSA_DiskDrive.DriveInterface

Value ValueMap 0 Unknown 1 Parallel 2 SATA 3 SAS 4 SATALogical 5 SASLogical

7.3.3 HPSA_DiskDrive.MediaType

Value indicates the media type of the disk.

Table 166 - HP Smart Array profile: HPSA_DiskDrive.MediaType

Value ValueMap 0 Unknown 1 Rotational Platters 2 Solid State

7.3.4 HPSA_DiskDrive.NegotiatedSpeed

Indicates the current speed of the drive in Bits per second.

Possible Parallel Values are

Table 177 - HP Smart Array profile: HPSA_DiskDrive.NegotiatedSpeed Parallel

Value Notes 0 Unknown 41943040 5 MBytes/sec 83886080 10 MBytes/sec 167772160 20 MBytes/sec 335544320 40 MBytes/sec 671088640 80 MBytes/sec 1342177280 160 MBytes/sec 2684354560 320 MBytes/sec

Possible Serial Values are

Table 18 - HP Smart Array profile: HPSA_DiskDrive.NegotiatedSpeed Serial

Value Notes 0 Unknown 1500000000 1.5 GBits/sec 3000000000 3 GBits/sec 6000000000 6 GBits/sec

7.3.5 HPSA_DiskDrive.NegotiatedDataWidth

Indicates the current width of the bus. Supported values are

Table 19 - HP Smart Array profile: HPSA_DiskDrive.NegotiatedDataWidth

Version 2.0.0 39

Value ValueMap 0 Unknown 1 SAS/SATA serial 8 Narrow 16 Wide

7.3.6 HPSA_DiskDrive.Identify(uint32 Duration)

This method will cause the hard drive to set some indicator (e.g. set or blink drive LEDs) for the given duration (default duration is 30 seconds). After the duration has expired the drive indicator will return to normal use.

Return values for Identify() method shall be the same as specified in Table 12 where the method execution behavior matches the return code description.

Identify() parameters shall be the same as those specified in Table 13.

7.3.7 HPSA_DiskDrive.DriveConfiguration

Indicates the how the drive has been configured by the controller. Supported values are:

Table 20 - HP Smart Array profile: HPSA_DiskDrive.DriveConfiguration

Value ValueMap 0 Unknown 1 Unconfigured 2 Data 3 Spare 4 Non RAID

7.3.8 HPSA_ DiskDrive.DriveRotationalSpeed

Value indicates the rotational speed of the drive in revolutions per minute.

7.3.9 HPSA_DiskDrive.DriveHasMNPData

Boolean value indicates that the drive supports reporting of Monitoring and Performance data counters.

7.3.10 HPSA_DiskDrive.DrivePlacement

Value indicates where the drive is located with respect to the controller.

Table 21 - HP Smart Array profile: HPSA_DiskDrive.DrivePlacement

Value ValueMap 0 Unknown 1 Internal 2 External

7.3.11 HPSA_DiskDrive.ControllerLocation

This value indicates the location of the controller with which the disk drive is attached to.

40 Version 2.0.0

7.3.12 HPSA_DiskDrive.OperationalStatus.

This value indicates the Operational Status of the disk drive. Operationalstatus[0] depicts the Primary operational status of the disk drive .

OperationalStatus[1] values shows the secondary(or extended) operational status of the disk drive.

The below values shows the possible OperationalStatus[1] values to account for the failure of a path from controller to disk.

• If any path to the disk making up this volume is currently set to 5 (Path Error) and there still exists at least one path that is active and the disk is currently ok then:

o OperationalStatus [0]: 3 (degraded) o OperationalStatus[1]: 32771 (0x8003) (Physical Path In Error)

• If all paths on all disks are set to 5 (Path Error) then: o OperationalStatus[0]: 6 (error) o OperationalStatus[1]: 32771(0x8003) (Physical Path In Error)

The below values shows the possible OperationalStatus[1] values related to secure erase operations.

Table 22 - HP Smart Array profile: HPSA_DiskDrive.OperationalStatus

Value ValueMap 0x8000 Queued for Secure Erase 0x8001 Erase in Progress 0x8002 Erase Completed

The below values shows the possible OperationalStatus[1] values to account for transient data drive and rebuilding of a physical drive.

• If the disk is in transient data drive status:

o OperationalStatus [0]: 2 (OK) o OperationalStatus[1]: 0x8004 (Transient Data Drive)

• If the disk is in the process of rebuilding it data due to becoming an active spare or recovering

from a previous failure: o OperationalStatus [0]: 2 (OK) o OperationalStatus[1]: 0x8005 (Rebuild)

The below values shows the possible OperationalStatus [1] values to account for Solid State drive wear out.

• If the Solid state drive reports a Smart Trip due to wear out then: o OperationalStatus [0]: 5 (Predictive Failure) o OperationalStatus[1]: 32774 (Solid State drive wear out)

NOTE: The properties from section 7.3.13 till 7.3.16 are conditionally populated only if the controller firmware and disk drive firmware support reporting drive life parameters for Solid State Disk Drives. Otherwise, these property values will be empty.

If the firmware supports reporting these parameters can be verified using SSDWearStatus property. If this property value is set to “Unknown”, it implies that the provider is unable to determine the physical drive’ s solid state disk drive life parameters. The below values shows the possible OperationalStatus [1] values to account for Physical Drive Authentication.

• If the physical drive reports an authentication failure then: o OperationalStatus [0]: 3 (Degraded)

Version 2.0.0 41

7.3.13 OperationalStatus[1]: 0x8007 (Not Authenticated)HPSA_DiskDrive.SSDTotalPowerOnHours

This value indicates the total number of hours that the Solid State Disk has been powered on. This property will only be available if the controller firmware supports reporting of solid state drive life information.

7.3.14 HPSA_DiskDrive.SSDPercentageEnduranceUsed

This value indicates the Physical Drive Solid State Percent Endurance Used. This property will only be available if the controller firmware supports reporting of solid state drive life information.

7.3.15 HPSA_DiskDrive.SSDLifeRemaining

This value indicates the Solid State drive life remaining days until wear out. This property will only be available if the controller firmware supports reporting of solid state drive life information.

7.3.16 HPSA_DiskDrive. SSDWearStatus

This value indicates the wearout status of the Solid State drive.

Table 18- HP Smart Array profile: HPSA_DiskDrive.DrivePlacement

Value ValueMap 0 Unknown 1 OK 2 56 day threshold passed 3 5 percent threshold passed 4 2 percent threshold passed 5 SSD Wear Out

7.3.17 HPSA_DiskDrive.SmartDriveCarrierAuthStatus

This value indicates the status of the Smart Drive Carrier Authentication if the controller supports hard drive and Smart Drive Carrier Authentication.

Table 19 - HP Smart Array profile: HPSA_DiskDrive.SmartDriveCarrierAuthStatus

Value ValueMap 0 Not Supported 1 Not Authenticated 2 Authenticated 3 Other

7.3.18 HPSA_DiskDrive.OtherSmartDriveCarrierAuthStatus

A string that describes the authentication status of the element when the HPSA_DiskDrive.SmartDriveCarrierAuthStatus property is set to 3 ("Other"). This property must be set to null when HPSA_DiskDrive.SmartDriveCarrierAuthStatus is any value other than 3.

7.4 HPSA_StorageVolume

The HPSA_StorageVolume class has been extended from CIM_StorageVolume class as defined in SNIA Block Services profile.

42 Version 2.0.0

7.4.1 HPSA_StorageVolume.Deleteable

Boolean value indicates whether this logical volume can be deleted. In most configurations, only the volume that is physically located at the end of the raid set can be deleted.

7.4.2 HPSA_StorageVolume.Accelerator

Value that indicates the status of the accelerator for this logical volume.

Supported values are as follows

Table 25 - HP Smart Array profile: HPSA_StorageVolume.Accelerator

Value ValueMap 0 Unknown 1 Enabled 2 Disabled

7.4.3 HPSA_StorageVolume.StripeSize

Value indicates the current stripe size in Bytes for the Logical Volume. Note that this may not have a value for some configurations (e.g. RAID 0 with a single drive, RAID 1 with only two drives).

7.4.4 HPSA_StorageVolume.PercentComplete

During a rebuild or expand operation, this will indicate progress as a percentage value. Note this value shall only be populated when a rebuild or expand operation is being performed on this logical volume.

7.4.5 HPSA_StorageVolume.FaultTolerance

Enumeration to indicate which type of raid is currently configured for a logical volume. Supported values are:

Table 26 - HP Smart Array profile: HPSA_StorageVolume.FaultTolerance

Value ValueMap 0 Unknown 1 RAID 0 2 RAID 1 3 RAID 1+0 4 RAID 4 5 RAID 5 6 RAID 51 7 RAID 6 8 RAID 50 9 RAID 60

7.4.6 HPSA_StorageVolume.OperationalStatus

OperationalStatus values have been extended to add Smart Array specific values for Logical Volume status.

The extended values shall be populated in OperationalStatus[1] and the equivalent DMTF defined status will be populated in OperationalStatus[0] as specified in Table . Note these extended values will more accurately define the storage volume’s status when in a degraded state.

Table 27 - HP Smart Array profile: HPSA_StorageVolume.OperationalStatus – Extended values

Version 2.0.0 43

Value ValueMap OperationalStatus[0] 0x8000 Physical Drive improperly connected Degraded (3) 0x8001 Expanding Degraded (3) 0x8002 Overheated Degraded (3) 0x8003 Overheating Degraded (3) 0x8004 Interim Recovery Degraded (3) 0x8005 Not Configured Degraded (3) 0x8006 Not Yet Available Degraded (3) 0x8007 Queued For Expansion Degraded (3) 0x8008 Ready For Recovery Degraded (3) 0x8009 Recovering Degraded (3) 0x800A Wrong Drive Replaced Degraded (3)

Table 28 - HP Smart Array profile: HPSA_StorageVolume.OperationalStatus[1]

The below OperationalStatus[1] reflects the Secondary (OR) Extended status of the logical volume which participate in the Secure Erase Operation.

Value ValueMap OperationalStatus[0]

0x800B Erase in Progress Degraded (3) 0x800C Erase Completed Degraded (3)

The below OperationalStatus[1] includes the statuses of all paths from an initiator port to a target port on a disk. Current HPSA_StorageVolume provider will change to determine status of all paths associated with storage extents that the volume is based on.

• If any path on any disk making up this volume is currently set to 5 (Path Error) and there still exists at least one path that is active and the volume is currently ok then:

o OperationalStatus [0]: 3 (degraded) o OperationalStatus[1]: 32781 (0x800D) (Physical Path In Error)

• If all paths on all disks are set to 5 (Path Error) then: o OperationalStatus[0]: 6 (error) o OperationalStatus[1]: 32781 (0x800D) (Physical Path In Error)

7.4.7 HPSA_StorageVolume. PhysicalDrvMultipathAccess

This is a new property that will be added to the definition of HPSA_StorageVolume. Definition will be: Uint16 PhysicalDrvMultipathAccess.

Table 29 - HP Smart Array profile: HPSA_StorageVolume.PhysicalDrvMultipathAccess

Value ValueMap Description 1 not supported Not supported by Array

Firmware 2 not configured Supported by Array

Firmware but not configured

3 configured redundant Volume is configured with redundant physical paths on all physical drives that make up the volume

44 Version 2.0.0

Value ValueMap Description 4 configured non-redundant Volume is configured with

redundant paths but is currently not redundant possibly due to failure of 1 or more paths or a configuration error

7.4.8 HPSA_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.4.9 HPSA_StorageVolume.Identify(uint32 Duration)

This method will cause hard drives that make up this logical volume to set some indicator (e.g. set or blink drive LEDs) for the given duration (default duration is 30 seconds). After the duration has expired the drive indicator(s) will return to normal use



7.5 HPSA_StoragePool

The HPSA_StoragePool class has been extended from CIM_StoragePool class as defined in SNIA Block Services profile.

7.5.1 HPSA_StoragePool.Identify(uint32 Duration)

This method will cause hard drives that make up this Storage Pool to set some indicator (e.g. set or blink drive LEDs) for the given duration (default duration is 30 seconds). After the duration has expired the drive indicator(s) will return to normal use



7.6 HPSA_MediaAccessStatData

The SNIA Disk Drive Lite profile has been extended to add the class HPSA_MediaAccessStatData. The following properties have been added to model the Monitoring and Performance counter for Hard Drives connected to Smart Array controllers.

7.6.1 HPSA_MediaAccessStatData.AbortedCommands

Value indicates the number of Aborted Commands as reported by MNP counters.

7.6.2 HPSA_MediaAccessStatData.BadTargetErrors

Value indicates the number of Bad Target Errors as reported by MNP counters.

Version 2.0.0 45

7.6.3 HPSA_MediaAccessStatData.ECCRecoveredReadErrors

Value indicates the number of ECC Recovered Read Errors as reported by MNP counters.

7.6.4 HPSA_MediaAccessStatData.FormatErrors

Value indicates the number of Format Errors as reported by MNP counters.

7.6.5 HPSA_MediaAccessStatData.HardReadErrors

Value indicates the number of Hard Read Errors as reported by MNP counters.

7.6.6 HPSA_MediaAccessStatData.HardWriteErrors

Value indicates the number of Hard Write Errors as reported by MNP counters.

7.6.7 HPSA_MediaAccessStatData.HardwareErrors

Value indicates the number of Hardware Errors as reported by MNP counters.

7.6.8 HPSA_MediaAccessStatData.HotPlugCount

Value indicates the Hot Plug Count as reported by MNP counters.

7.6.9 HPSA_MediaAccessStatData.MediaFailures

Value indicates the number of Media Failures as reported by MNP counters.

7.6.10 HPSA_MediaAccessStatData.NotReadyErrors

Value indicates the number of Not Ready Errors as reported by MNP counters.

7.6.11 HPSA_MediaAccessStatData.OtherTimeOuts

Value indicates the number of Other Time Outs as reported by MNP counters.

7.6.12 HPSA_MediaAccessStatData.SCSIBusFaults

Value indicates the number of SCSI Bus Faults as reported by MNP counters.

7.6.13 HPSA_MediaAccessStatData.SectorsRead

Value indicates the number of Sectors Read as reported by MNP counters.

7.6.14 HPSA_MediaAccessStatData.SectorsWritten

Value indicates the number of Sectors Written as reported by MNP counters.

7.6.15 HPSA_MediaAccessStatData.SeekCount

Value indicates the Seek Count as reported by MNP counters.

7.6.16 HPSA_MediaAccessStatData.SeekErrors

Value indicates the number of Seek Errors as reported by MNP counters.

46 Version 2.0.0

7.6.17 HPSA_MediaAccessStatData.SpinUpErrors

Value indicates the number of Spin Up Errors as reported by MNP counters.

7.6.18 HPSA_MediaAccessStatData.DRQTimeOuts

Value indicates the number of DRQ Time Outs as reported by MNP counters.

7.6.19 HPSA_MediaAccessStatData.RetryRecoveredReadErrors

Value indicates the number of Retry Recovered Read Errors as reported by MNP counters.

7.6.20 HPSA_MediaAccessStatData.RetryRecoveredWriteErrors

Value indicates the number of Retry Recovered Write Errors as reported by MNP counters.

7.6.21 HPSA_MediaAccessStatData.FailedReadRecovers

Value indicates the number of Failed Read Recovers as reported by MNP counters.

7.6.22 HPSA_MediaAccessStatData.FailedWriteRecovers

Value indicates the number of Failed Write Recovers as reported by MNP counters.

7.6.23 HPSA_MediaAccessStatData.ServiceHours

Value indicates the number of Service Hours as reported by MNP counters.

7.7 HPSA_TSASSCSIProtocolEndpoint

The HPSA_TSASSCSIProtocolEndpoint class has been extended from CIM_SCSIProtocolEndpoint as defined in SNIA SAS Target ports profile. The following properties have been added to represent the protocol (command set) associated to a target port.

7.7.1 HPSA_TSASSCSIProtocolEndpoint.ProtocolIFType

ProtocolIFType is an enumeration that is synchronized with the IANA ifType MIB. Note that if the ProtocolIFType is set to 1 (Other), then the type information should be provided in the OtherTypeDescription string property.

7.7.2 HPSA_TSASSCSIProtocolEndpoint.OtherTypeDescription

The type of protocol endpoint when the Type property of this class (or any of its subclasses) is set to 1 (Other).Value is set to the string ‘SCSI’.

7.7.3 HPSA_TSASSCSIProtocolEndpoint.Role

Value is set to 3 for Target port.

7.7.4 HPSA_TSASSCSIProtocolEndpoint.Path

Value indicates whether the diskdrive port path is active or not.

Table 20- HP Smart Array profile: HPSA_TSASSCSIProtocolEndpoint.Path

Value ValueMap 0 Unknown 2 Active

Version 2.0.0 47

Value ValueMap 3 Passive 5 Path Error

7.8 HPSA_TSASPort

The HPSA_TSASPort class has been extended from CIM_LogicalPort as defined in SNIA SAS Target ports profile. The following properties have been added to represent a target port.

7.8.1 HPSA_TSASPort. OperationalStatus

This value indicates the Operational Status of the port. Value is set to 2 (OK) .

7.8.2 HPSA_TSASPort.PortType

PortType defines the type of port. Value is set to 94 for SAS port.

7.8.3 HPSA_TSASPort.UsageRestriction

A LogicalPort might be identifiable as a front end or back end port. If there is no restriction on the use of the port, then the value should be set to 'not restricted'. Value is set to 4 (Not restricted) for Target port.

7.9 HPSA_ISASSCSIProtocolEndpoint

The HPSA_ISASSCSIProtocolEndpoint class has been extended from CIM_SCSIProtocolEndpoint as defined in SNIA SAS Initiator ports profile. The following properties have been added to represent the protocol (command set) associated to an initiator port.

7.9.1 HPSA_ISASSCSIProtocolEndpoint.ProtocolIFType


7.9.2 HPSA_ISASSCSIProtocolEndpoint.OtherTypeDescription


7.9.3 HPSA_ISASSCSIProtocolEndpoint.Role

Value is set to 2 for Initiator port.

7.10 HPSA_ ISASPort

The HPSA_ISASPort class has been extended from CIM_ LogicalPort as defined in SNIA SAS Initiator ports profile. The following properties have been added to represent an initiator port.

7.10.1 HPSA_ISASPort.OperationalStatus


7.10.2 HPSA_ISASPort.PortType


48 Version 2.0.0

7.10.3 HPSA_ISASPort.UsageRestriction

A LogicalPort might be identifiable as a front end or back end port. If there is no restriction on the use of the port, then the value should be set to 'not restricted'. Value is set to 4 (Not restricted) for initiator port.

7.11 HPSA_ SCSIInitiatorTargetLogicalUnitPath

The HPSA_SCSIInitiatorTargetLogicalUnitPath class has been extended from CIM_SCSIInitiatorTargetLogicalUnitPath to represent a path between a SCSI initiator, target, and logical unit..

7.11.1 HPSA_ SCSIInitiatorTargetLogicalUnitPath.Initiator

This value is a reference to an instance of HPSA_ISASSCSIProtocolEndpoint.

7.11.2 HPSA_ SCSIInitiatorTargetLogicalUnitPath.Target

This value is a reference to an instance of HPSA_TSASSCSIProtocolEndpoint.

7.11.3 HPSA_ SCSIInitiatorTargetLogicalUnitPath.LogicalUnit

This value is a reference to an instance of HPSA_StorageExtent.

7.11.4 HPSA_ SCSIInitiatorTargetLogicalUnitPath.State

The state of this path. Values are defined as follows.

Table 31 - HP Smart Array profile: HPSA_SCSIInitiatorTargetLogicalUnitPath.State

Value ValueMap Description 0 Unknown The path status cannot be

ascertained 2 Active The path is active and

healthy 3 Passive Path is healthy but is not

active or is the standby path

5 Path Error path has an error condition

7.12 HPSA_EncProtocolEndpoint

The HPSA_EncProtocolEndpoint class has been extended from CIM_SCSIProtocolEndpoint and represents the protocolendpoint of an enclosure port. The following properties have been added to represent the protocol (command set) associated to a target port.

7.12.1 HPSA_ EncProtocolEndpoint.ProtocolIFType


Version 2.0.0 49

7.12.2 HPSA_ EncProtocolEndpoint.OtherTypeDescription


7.12.3 HPSA_ EncProtocolEndpoint.Role

Value is set to 3 for Target port.

7.12.4 HPSA_ EncProtocolEndpoint.Path

Value indicates whether the enclosure port path is active or not.

Table 21 - HP Smart Array profile: HPSA_ EncProtocolEndpoint.Path

Value ValueMap 0 Unknown 2 Active 3 Passive 5 Path Error

7.13 HPSA_EncSASPort

The HPSA_EncSASPort class has been extended from CIM_LogicalPort to define an enclosure target port.

7.13.1 HPSA_EncSASPort. OperationalStatus


7.13.2 HPSA_EncSASPort.PortType


7.13.3 HPSA_EncSASPort.UsageRestriction

A LogicalPort might be identifiable as a front end or back end port. If there is no restriction on the use of the port, then the value should be set to 'not restricted'. Value is set to 4 (Not restricted) for Target port.

7.14 HPSA_ConnectivityCollection

HPSA_ConnectivityCollection class derives from CIM_ConnectivityCollection to group initiator and target ports. HPSA_ISASSCSIProtocolEndpoint instance of the Initiator port profile and HPSA_EncProtocolEndpoint are grouped in one collection using HPSA_ConnectivityCollection instance to represent the connection between array controller initiator ports to the Enclosure port.

7.14.1 HPSA_ ConnectivityCollection. ConnectivityStatus

An enumeration describing the current or potential connectivity between endpoints in this collection.

Table 22 - HP Smart Array profile: HPSA_ ConnectivityCollection.ConnectivityStatus

Value ValueMap 0 Unknown 2 Connectivity/Up 3 No Connectivity/Down

50 Version 2.0.0

Value ValueMap 4 Partitioned 32768 Connectivity/Passive

7.15 HPSA_ArraySystemExternalArraySystem

HPSA_ArraySystemExternalArraySystem class derived from CIM_ComponentCS to associate the ArraySystem to the HBA and the ArraySystem for an external storage controller.

8 Methods None.




• GetInstance

• Associators

• AssociatorNames

• References

• ReferenceNames




Version 2.0.0 51

9 Use Cases


HPSA_ArraySystem:01

Dedicated:30,15

HP_ComputerSystem:88

HP Base Server

SystemDevice

HPSA_PortController:01


HPSA_PhysicalPackage:01

SystemPackaging

HPSA_Product:01

Name = “Smart Array 6i”ProductPhysicalComponent

HPSA_DAPort:01

HostedAccessPoint

HPSA_SCSIProtocolEndpoint:01

HPSA_SCSIProtocolController:01

SystemDevice

HPSA_StorageVolume:002

Name = VPD pg83(RAID 1 logical volume)



SystemDevice

HPSA_ArrayController:123ComponentCS

HPSA_PrimordialPool:00


HPSA_StoragePool:01


HPSA_Location:01

ElemInfoTagDesc = PCISlotElemInfoTag = “0”

HPSA_DiskDrive:004

HPSA_DiskDrive:005

SystemDevice

HPSA_StorageExtent:004


BasedOn

MediaPresent

MediaPresent



HostedStoragePool



HPSA_StorageSetting:002

DataRedundandy = 2PackageRedundancy = 1

ElementSettingDataConcreteComponent


RegisteredProfile

RegisteredOrg = “SNIA”RegisteredName = “HHRC”

RegisteredProfile

RegisteredOrg = “Other”OtherRegOrg = “HP WBEM TC”RegisteredName = “HP Smart Array”

HP_ExtendsProfile

52 Version 2.0.0

Figure 17 - HP Smart Array profile: Host Hardware RAID Controller

The example in Figure shows a PCI based Smart Array HBA in slot 3. If Central class method is used, the HPSA_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. If Scoping method is used, the HPSA_PortController central class instance can be identified by following the CIM_ElementConformsToProfile association from the CIM_RegisteredProfile instance in root/interop to the HP Computer System scoped class, and then following the SystemDevice association.

The Top Level System (used to scope devices managed by the array) is identified by following CIM_LogicalIdentity association to HPSA_ArraySystem class. Specifics about the controller itself can be obtained from the HPSA_ArrayController instance associated with the Top Level System via CIM_ComponentCS.

This example shows a RAID 1 volume based on two disk drives. All disk drives can be found using SystemDevice associations from the Top Level System. To find disk drives that belong to any StorageVolume, use the BasedOn association from the StorageVolume to the StorageExtents. The StorageExtents represent the primordial extent and map to DiskDrive instances one to one using MediaPresent associations.

The raid characteristics of the Storage Volume can be determined by inspecting the FaultTolerance property of the HPSA_StorageVolume class. Alternatively, the HPSA_StorageSetting class associated to the Storage Volume via CIM_ElementSettingData, contains DataRedundancy and PackageRedundancy properties that define the Quality of Service. Raid types and corresponding values in StorageSetting class are covered in the SMI-S specification.

The marketing name for the controller can be found by first traversing the SystemPackaging association from the Top Level System instance to the PhysicalPackage that represent the Array system, then the HPSA_Product class can be found using CIM_ProductPhysicalPackage association. The Marketing name is stored in the HPSA_Product.Name property.

Version 2.0.0 53

9.1.1 Host Hardware RAID Controller Physical model

HPSA_ArraySystem:01

Dedicated: 30,15


CentralClass

LogicalIdentity


SystemPackaging

HPSA_Product:01

Name = “Smart Array 6i”ProductPhysicalComponent

SystemDevice

HPSA_ArrayController:123

ComponentCS

HPSA_Location:01


HPSA_DiskDrive:004

HPSA_DiskDrive:005


HPSA_StorageExtent:005MediaPresent

MediaPresent


HPSA_ArrayCopntrollerPhysicalPackage:01

HPSA_ArrayControllerLocation:01


Realizes


HPSA_DiskPhysicalPackage:004


Realizes

Realizes

HPSA_StorageEnclosureProcessor:SE1

HPSA_StorageEnclosure:SE1



SystemPackaging



Container




ContainerHPSA_DiskLocation:004


HPSA_DiskLocation:005




Container


SystemComponent

Container

See HP_StorageEnclosure

Figure 18 - HP Smart Array profile: Host Hardware RAID Controller Physical

Figure 18 shows the physical instances for the same PCI Based Smart Array HBA. This shows the use of HP Storage Enclosure Profile to show containment of the disk drives connected to the HBA, These drives are located in an internal enclosure within the Host Chassis. Instances of HP_Location classes are used to define location strings for each physical package.

54 Version 2.0.0

9.2 External MSA500 Storage Subsystem

HPSA_ArraySystem:01

Central classDedicated[30,15]

HPSA_SPIPort:01

HPSA_ArraySystem:02


SystemDevice


HPSA_ArraySystemExternalArraySystem

LogicalIdentityHPSA_ArraySystem

PortController

ComponentCS

Figure 19 - HP Smart Array profile: External intelligent MSA(MSA 500/20) and HBA computer system to which it is associated

Figure 19 shows the instance diagram for an MSA500/MSA20 type storage system connected to the PCI Host Bus Raid controller.

Figure 20 shows the instance diagram for an MSA500 type storage system (HPSA_ARrraySystem:02 computer system stack) with two controllers in a redundant configuration. The redundancy of the controllers is identified via the HPSA_RedundancySet collection.

For instance diagram of HBA storage system (HPSA_ARrraySystem:01 computer system stack) , refer figure 17.

Figure shows the instances for the physical components of an MSA500(HPSA_ArraySystem:02) in a chassis named “BladeStor01”. The MSA500 has 2 drives installed in the internal drive cage. (Note only one controller is shown for the sake of clarity)

The location value for the HPSA_StorageEnclosure is relative to the top level system location. This enclosure is internal with respect to HPSA_ArraySystem but the whole storage subsystem is external to the host.

Version 2.0.0 55

HPSA_ArraySystem:02

Dedicated:3,15

SystemComponent


SystemPackaging

HPSA_Product:02

Name = “MSA500”ProductPhysicalComponent

HPSA_SPIPort:01

HostedAccessPointHPSA_SCSIProtocolEndpoint:02


SystemDevice





SystemDevice


ComponentCS



HPSA_StoragePool:02


HPSA_Location:02

ElemInfoTagDesc = ChassisNameElemInfoTag = “BladeStor01”

HPSA_DiskDrive:004

HPSA_DiskDrive:005



BasedOn

MediaPresent

MediaPresent

AllocatedFromStoragePool AllocatedFromStoragePool

HostedStoragePool


RegisteredProfile

SNIA “Array”




ElementSettingData ConcreteComponent

SystemDevice


HPSA_RedundancySet:02

MemberOfCollection


HP Base Server

Figure 20 - HP Smart Array profile: External MSA500

56 Version 2.0.0

9.2.1 External MSA500 Storage Subsystem physical model

HPSA_ArraySystem:02

Dedicated:3,15


SystemPackaging

HPSA_Product:02


SystemDevice


ComponentCS

HPSA_Location:02

ElemInfoTagDesc = ChassisNameElemInfoTag = “BladeStor01”

HPSA_DiskDrive:004

HPSA_DiskDrive:005


HPSA_StorageExtent:005MediaPresent

MediaPresent


HPSA_ArrayControllerPhysicalPackage:02

HPSA_ArrayControllerLocation:02

ElemInfoTagDesc = SlotElemInfoTag = “0”

Realizes




Realizes

Realizes

HPSA_StorageEnclosureProcessor:SE1

HPSA_StorageEnclosure:SE1



SystemPackaging



Container




ContainerHPSA_DiskLocation:004


HPSA_DiskLocation:005




Container


SystemComponent

Container

See HP_StorageEnclosure

Container

Figure 21 - HP Smart Array profile: External MSA500 physical model

Version 2.0.0 57

9.3 External MSA20 storage system

HPSA_ArraySystem:02

Dedicated:3,15SystemComponent


SystemPackaging

HPSA_Product:02


HPSA_SPIPort:01

HostedAccessPointHPSA_SCSIProtocolEndpoint:02


SystemDevice





SystemDevice




HPSA_StoragePool:02


HPSA_Location:02

ElemInfoTagDesc = ChassisNameElemInfoTag = “88”

HPSA_DiskDrive:004

DriveType = SATA

HPSA_DiskDrive:006

DriveType = SATA



BasedOn

MediaPresent

MediaPresent

AllocatedFromStoragePool AllocatedFromStoragePool

HostedStoragePool


RegisteredProfile

SNIA “Array”




ElementSettingData ConcreteComponent

SystemDevice

HPSA_DiskDrive:005

DriveType = SATA


MediaPresent


HP Base Server


58 Version 2.0.0

Figure 22 shows an MSA20 external storage system(HPSA_ArraySystem:02) with three SATA drives configured in a RAID 5 configuration. Note in this case the MSA20 does not support controller redundancy so the HPSA_RedundancySet instance is not modeled.

Figure 19 shows the instance diagram for an MSA20 type storage system connected to the PCI Host Bus Raid controller. Refer figure 17 for computer system stack of the host bus adapter(HPSA_arraySystem:01)

9.4 External intelligent storage system connected using a HBA in PCI bus

Figure 23,This instance diagram depicts the instances of HPSA_arraySystem for External array system and the HBA it is connected to. The association instance HPSA_ArraySystemExternalArraySystem is used to associate two array system, HBA array system and the external storage system array system.. HPSA_ArraySystem with dedicated value of 30 is HBA array system and HPSA_ArraySystem:02 with dedicated value of 3 indicates external storage.

HPSA_ArraySystem:01


SystemComponent

HPSA_SPIPort:01

SystemDevice


ComponentCS

RegisteredProfile

SNIA “Array”ElementConformsToProfile


MemberOfCollection


HP Base Server

HPSA_ArraySystem:02


SystemDevice

SystemComponent




MemberOfCollection

ComponentCS


HPSA_ArraySystemExternalArraySystem

LogicalIdentityHPSA_ArraySystem

PortController


ComponentCS

Hosted collectionHosted collection


Version 2.0.0 59

9.5 Single Pool – Multiple Storage Volume

HPSA_ArraySystem:01

SystemDevice






HPSA_StoragePool:01


HPSA_DiskDrive:004

HPSA_DiskDrive:005

SystemDevice



BasedOn

MediaPresent

MediaPresent



HostedStoragePool








BasedOn

ElementSettingData


HostedStoragePool

Figure 24 - HP Smart Array profile: Multiple Storage Volumes

Figure shows a typical Smart Array configuration that has one storage pool configured with two disk drives. This pool can have multiple Storage Volumes configured. In this example we have both a RAID 0 and a RAID 1 volumes allocated from the same pool. Note that the capabilities of the pool will dictate which RAID levels are currently supported. (E.g. in the above example, RAID 5 or RAID 6 cannot be supported with only two drives).

60 Version 2.0.0

9.6 Multiple Pool example

HPSA_ArraySystem:01

SystemDevice






HPSA_StoragePool:01


HPSA_DiskDrive:004

HPSA_DiskDrive:005

SystemDevice



BasedOn

MediaPresent

MediaPresent



HostedStoragePool








ElementSettingData

HPSA_StoragePool:02




HPSA_DiskDrive:008


MediaPresent

BasedOn

ConcreteComponent

HostedStoragePool

HostedStoragePool

Figure 25 - HP Smart Array profile: Multiple Storage Pools

Figure 5 shows a Smart Array controller with two concrete Storage Pools each with one logical Drive configured. Both concrete storage pools are allocated from the single primordial pool.

In this case the pool with only one disk can only support RAID 0 logical volumes. The pool with two drives can support both RAID 0 and RAID 1 logical volumes.

Version 2.0.0 61

9.7 Disk Sparing – Multiple Spares




HPSA_StoragePool:1

Concrete Pool

ConcreteComponent

HPSA_StorageRedundancySet:A

MemberOfCollection


Spare

HPSA_StoragePool:1

Concrete Pool




ConcreteComponent

HPSA_StorageRedundancySet:B

MemberOfCollection

IsSpare


Spare

IsSpare

Figure 166 - HP Smart Array profile: Disk sparing – Multiple Spares

Redundancy sets can have multiple spares and also a disk drive can be a spare to more than one redundancy set. In Figure 166, we see that HPSA_StorageRedundancySet:A has two CIM_IsSpare associations to two HPSA_StorageExtent instances. Also, HPSA_StorageExtent:005 has CIM_IsSpare associations to both HPSA_StorageRedundancySet:A and HPSA_StorageRedundancySet:B.

9.8 Disk Sparing - Drive failure example

The following sections describe the implementation of Disk Sparing for Smart Array controllers.

62 Version 2.0.0

9.8.1 Before drive failure


OPStatus = “OK”


OPStatus = “OK”


OPStatus = “OK”

HPSA_StoragePool:1

Concrete Pool

ConcreteComponent


MemberOfCollection


SpareOPStatus = “OK”

IsSpare


OpStatus = “OK”


Figure 27 - HP Smart Array profile: Disk sparing – Pre failure

Figure 7 shows a three drive raid set with one spare drive. OperationalStatus for all the drives and the storage volumes are “OK”. The data drives can be identified by their MemberOfCollection association to the StorageRedundancySet instance. The spare drive can be identified by its IsSpare association to the StorageRedundancySet.

Version 2.0.0 63

9.8.2 Drive Failed – Data Rebuilding


OPStatus = “OK”


OPStatus = “OK”


OPStatus = “ERROR”

HPSA_StoragePool:1

Concrete Pool

ConcreteComponent


MemberOfCollection


SpareOPStatus = “OK,Rebuld”ExtentStatus = “Rebuild”

IsSpare


OpStatus = “Degraded, Recovering”

PercentComplete = “33”


Spared

Figure 28 - HP Smart Array profile: Disk sparing – Drive failed - rebuilding

Figure 8 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 OpStat[0]:“Degraded”, OpStat[1]:”Recovering”. The OperationalStatus for the Spare drive will show OpStat[0]:“OK” and the ExtentStatus will show OpStat[1]:“Rebuild”. This signifies that data is being rebuilt to the spare drive. The progress for the rebuild will be shown in HPSA_StorageVolume.PercentComplete.

The CIM_Spared association is used to associate the spare to the failed drive that it has replaced.

64 Version 2.0.0

9.8.3 Drive Failed – Rebuild Complete


OPStatus = “OK”


OPStatus = “OK”



HPSA_StoragePool:1

Concrete Pool

ConcreteComponent


MemberOfCollection



IsSpare


OpStatus = “OK”


Spared

Figure 29 - HP Smart Array profile: Drive Failed – Rebuild complete

Figure 9 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.

Note the StorageVolume still shown as a member of the StorageRedundancySet and has an “ERROR” status value. For Smart Array, it will remain in this state until the data drive is replaced. The CIM_Spared association is still maintained during this time.

Version 2.0.0 65

9.8.4 Drive replaced – Data Rebuild


OPStatus = “OK”


OPStatus = “OK”


OPStatus = “OK,Rebuild”ExtentStatus = “Rebuild”

HPSA_StoragePool:1

Concrete Pool

ConcreteComponent


MemberOfCollection



IsSpare


OpStatus = “Degraded, Recovering”

PercentComplete = “88”


Spared

Figure 30 - HP Smart Array profile: Drive Replaced – data rebuilding

Figure 30 shows the instance diagram for the case where the failed drive has been replaced with a functional drive and the array controller has started to rebuild the data back to the original drive. This resembles Figure . Note that the ExtentStatus (OpStat[1]) for the Spare Drive is “None” and the original Data Drive shows ExtentStatus (OpStat[1]) of “Rebuild” indicating that the data is being rebuilt to the original drive.

StorageVolume OperationalStatus shows “OpStat[0]:Degraded, OpStat[1]:Recovering” and the progress is available in property PercentComplete.

66 Version 2.0.0

9.8.5 Drive replaced – Rebuild Complete


OPStatus = “OK”


OPStatus = “OK”


OPStatus = “OK”

HPSA_StoragePool:1

Concrete Pool

ConcreteComponent


MemberOfCollection



IsSpare


OpStatus = “OK”


Figure 31 - HP Smart Array profile: Drive Replaced – Data rebuild complete

Figure 31 shows that the Array has recovered back to the state before the drive failed. Full redundancy is restored and the Spare Drive is once again available to act as a hot spare.

9.9 Host based HBA controller model

HPSA_ArraySystem:01

OpStatus = “Degraded”


OpStatus = “OK”

ComponentCSHPSA_StorageVolume:002


SystemDevice

Figure 32 - HP Smart Array profile: Host HBA Controller

Figure shows the instance diagram for a host based (HBA) Smart Array controller. The HPSA_ArraySystem represents the overall array and the OperationalStatus value will contain the consolidated status for the array. The controller instance (HPSA_ArrayController) is associated via CIM_ComponentCS. In the above example we see that the “degraded” status of a logical drive has been consolidated into HPSA_ArraySystem.OperationalStatus[0].

Version 2.0.0 67

9.10 External Array with redundant controller model

HPSA_ArraySystem:01



OpStatus = “OK”

ComponentCSHPSA_StorageVolume:002



OpStatus = “OK”

ComponentCS


TypeOfSet = “Sparing”RedundancyStatus = “OK”

ConcreteIdentity


SystemDevice

Figure 33 - HP Smart Array profile: External Array – redundant controllers

Figure 3 shows a typical external Storage Subsystem with two redundant controllers. The HPSA_RedundancySet and CIM_MemberOfCollection show the two controllers in a redundant pair. HPSA_RedundancySet.TypeOfSet is set to “Sparing” to indicate active/standby configuration. The RedundancyStatus is “OK” for the above example. In the above example we see that the “degraded” status of a logical drive has been consolidated into HPSA_ArraySystem.OperationalStatus[0].

68 Version 2.0.0

9.11 Consolidated status example

HPSA_ArraySystem:11


HPSA_ArraySystem


HPSA_StorageSpecificCollection:01


MemberOfCollection MemberOfCollection

HP_ComputerSystem







SystemDeviceSystemDevice





BasedOn




OperationalStatus = ERROR

BasedOn

Figure 34 - HP Smart Array profile: Consolidated Status

Figure 4 shows a typical instance diagram where a single drive failure in a Raid configuration will cause elements to have “Degraded” OperationalStatus values. This will be propagated up to HPSA_ArraySystem.OperationalStatus and on to the GroupOperationalStatus in the HPSA_StorateSpecificCollection to participate in the overall system OperationalStatus for the Host per the HP Consolidated Status profile.

Note: some instances have not been included in the diagram for the sake of clarity.

Version 2.0.0 69

9.12 Multi-path support example

9.12.1 Multi-path support – Dual Port Drive

The following figure shows an array controller with 2 ports that are connected with 2 redundant paths to a dual port SAS drive.

For each path between a SAS initiator port and a SAS target port (contained on a SAS drive), an instance of HPSA_SCSIInitiatorTargetLogicalUnitPath will be created. This instance represents the path from the controller port and the drives port. The association is a 3-way and associates the initiator port, target port, and the storage extent of the physical disk.



HPSA_ArraySystem

HPSA_DiskDrive

HPSA_StorageExtent


DiskDrive Lite


HPSA_ISASPort



CIM

_HostedA

ccessPoint

HP

SA

_ArrayS

ystemIS

AS

SC

SIP

E


HPSA_TSASPort

CIM

_System

Device

HP

SA

_ArrayS

ystemTS

AS

Port

CIM

_HostedA

ccessPoint

HP

SA

_ArrayS

ystemTS

AS

SC

SIP

E


CIM

_SA

PA

vailableForElem

entH

PS

A_D

iskDriveTS

AS

SC

SIP

E

HPSA_ISASPort



HPSA_TSASPort


Figure 35 - HP Smart Array profile: Multi-path Instance Dual Port Drive

9.12.2 Multi-path support – Single Port Drive

The following figure shows a similar configuration as above. In this instance, a Smart Array controller with 2 ports is configured with dual paths to a single port SAS drive. Note that only one instance of HPSA_TSASSCSIProtocolEndpoint and HPSA_TSASPort is created to represent the single port on the SAS drive. Also, note that the Target property in each instance of HPSA_SCSIInitiatorTargetLogicalUnitPath points to the instance of HPSA_TSASSCSIProtocolEndpoint representing the single SCSI protocol endpoint of the single ported SAS disk

70 Version 2.0.0

HPSA_ArraySystem

HPSA_DiskDrive

HPSA_StorageExtent


DiskDrive Lite


HPSA_ISASPort



CIM

_HostedA

ccessPoint

HP

SA

_ArrayS

ystemIS

AS

SC

SIP

E


HPSA_TSASPort

CIM

_System

Device

HP

SA

_ArrayS

ystemTS

AS

Port

CIM

_HostedA

ccessPoint

HP

SA

_ArrayS

ystemTS

AS

SC

SIP

E


CIM

_SA

PA

vailableForElem

entH

PS

A_D

iskDriveTS

AS

SC

SIP

E

HPSA_ISASPort





Figure 36 - HP Smart Array profile: Multi-path Instance Single Port Drive

9.12.3 Multi-path support – Logical Volume Changes The statuses of all paths from an initiator port to a target port on a disk are rolled up into the status of the HPSA_StorageVolume.OperationalStatus. The following instance diagrams serves to illustrate this. This instance diagram shows a smart array controller with 2 ports connected to a dual port SAS drive. The paths are redundant (as shown with 2 instances of HPSA_SCSIInitiatorTargetLogicalUnitPath).

Version 2.0.0 71

HPSA_ArraySystem

HPSA_DiskDrive

OperationalStatus:[0] 3 (degraded)[1] 32771 (Path In Error)

HPSA_StorageExtent

MediaP

resentH

PS

A_D

iskDriveS

torageExtent

DiskDrive Lite


HPSA_ISASPort



CIM

_HostedA

ccessPoint

HP

SA

_ArrayS

ystemIS

AS

SC

SIP

E


HPSA_TSASPort

CIM

_System

Device

HP

SA

_ArrayS

ystemTS

AS

Port

CIM

_HostedA

ccessPoint

HP

SA

_ArrayS

ystemTS

AS

SC

SIP

E


CIM

_SA

PA

vailableForElem

entH

PS

A_D

iskDriveTS

AS

SC

SIP

EHPSA_ISASPort



HPSA_TSASPort


Consolidated Status


MemberOfCollectionHPSA_StorageSpecificCollection

HP_ComputerSystem

System

CIM

_Com

ponentCS

HP

SA

_Com

puterSystem

ArrayS

ystem

HPSA_PortController

SystemDevice(not currently populated by

WMI)



CIM_SystemDeviceHPSA_ArraySystemStorageVolume

CIM_BasedOnHPSA_StorageExtentStorageVolume


State: 2 (Active)


State: 5 (Path Error)

LogicalIdentityHPSA_ArraySystemPortController

HPSA_StorageVolume

OperationalStatus: [0] 3 (degraded) [1] 32781 (Path In Error)PhysicalDrvMultipathAccess: 4 (configured non-redundant)

Figure 37 - HP Smart Array profile: Multi-path Logical Volume changes

As shown, one path is active and another path is in error (5 – path error). This status is reflected into the HPSA_StorageVolume.OperationalStatus. The OperationalStatus primary status is 2 (degraded) and the secondary status is 32781 (Path In Error). The status is also reflected into HPSA_DiskDrive.OpStat[0]:3 (degraded) and HPSA_DiskDrive.OpStat[1]: 32771 (Path In Error). PhysicalDrvMultipathAccess is set to 4 – ‘Configured non-redundant’..

9.13 Determine Smart Drive Carrier Firmware Version

If the array controller is capable of reporting the Smart Drive carrier application firmware version, for a given instance of HPSA_DiskDrive, select an associated instance of CIM_SoftwareIdentity through CIM_ElementSoftwareIdentity. Retrieve the version from the CIM_SoftwareIdentity.VersionString property.

If the array controller is capable of reporting the Smart Drive carrier bootloader firmware version, for a given instance of HPSA_DiskDrive, select an associated instance of CIM_SoftwareIdentity through CIM_ElementSoftwareIdentity. Retrieve the version from the CIM_SoftwareIdentity.VersionString property

72 Version 2.0.0


Table 34 – CIM Elements – HP Smart Array Profile


HPSA_ArrayController Mandatory See Section 10.2 HPSA_ArraySystem Mandatory See Section 10.1 HPSA_DiskDrive Mandatory See Section 10.3 HPSA_StorageVolume Mandatory See Section 10.4 HPSA_StoragePool Mandatory See Section 10.5 HPSA_MediaAccessStatData Conditional See Section 10.6 CIM_ElementStatisticalData Conditional See Section 10.7 HPSA_TSASSCSIProtocolEndpoint Conditional See Section 10.7 HPSA_TSASPort Conditional See Section 7.8 HPSA_ISASSCSIProtocolEndpoint Conditional See Section 7.9 HPSA_ISASPort Conditional See Section 7.10 HPSA_ SCSIInitiatorTargetLogicalUnitPath

Conditional See Section 7.11

HPSA_ EncProtocolEndpoint Conditional See Section 7.12 HPSA_EncSASPort Conditional See Section 7.13 HPSA_ConnectivityCollection Conditional See Section 7.14 HPSA_ArraySystemExternalArraySystem Conditional See Section 7.15 CIM_SoftwareIdentity Conditional See Section 10.11

Indications None defined.

10.1 HPSA_ArraySystem

The HPSA_ArraySystem class has been extended form CIM_ComputerSystem to add the following items.

Table 35 – Class: HPSA_ArraySystem

Properties Requirement Notes Identify() M (see section 7.2.1)

10.2 HPSA_ArrayController

HPSA_ArrayController has been extended from CIM_ComputerSystem to add properties to model Smart Array features.

Version 2.0.0 73

Table 36 – Class: HPSA_ArrayController

Properties Requirement Notes ADGSupported M See Section 0

RebuildPriority M See Section 0

ExpandPriority M See Section 0

NumberOfPorts M See Section 0

CacheBoardPresent M See Section 0

CacheHasBattery M See Section 0

BatteryStatus M See Section 0

CacheSizeTotal M See Section 0

CacheReadPercent M See Section 0

CacheWritePercent M See Section 0

CacheParityReadErrors M See Section 0

CacheParityWriteErrors M See Section 0

CacheSerialNumber M See Section 0

CacheStatus M See Section 0

CacheState M See Section 0

ControllerStatus M See Section 0

10.3 HPSA_DiskDrive

HPSA_DiskDrive class has been extended from CIM_DiskDrive to add Smart Array specific features.

74 Version 2.0.0

Table 37 – Class: HPSA_DiskDrive


Notes

TotalPowerOnHours O See Section 7.3.1

DriveInterface M See Section 7.3.2

MediaType O See Section 7.3.3

NegotiatedSpeed O See Section 7.3.4

NegotiatedDataWidth O See Section 7.3.5

Identify() M See Section 7.3.6

DriveConfguration M See Section 7.3.7

DriveRotationalSpeed O See Section 7.3.8

DriveHasMNPData M See Section 7.3.9

DrivePlacement M See Section 7.3.10

ControllerLocation M See Section 7.3.11

OperationalStatus M See Section 7.3.12

SSDTotalPowerOnHours C See Section 7.3.13

SSDPercentageEnduranceUsed C See Section 7.3.14

SSDLifeRemaining C See Section 7.3.15

SSDWearStatus C See Section 7.3.16

SmartDriveCarrierAuthStatus O See Section 7.3.17

OtherSmartDriveCarrierAuthStatus C See Section 7.3.18

10.4 HPSA_StorageVolume

HPSA_StorageVolume has been extended from CIM_StorageVolume as defined in SNIA Block Services profile.

Table 38 – Class: HPSA_StorageVolume

Properties Requirement Notes Deleteable M See Section 7.4.1

Accelerator M See Section 7.4.2

FaultTolerance M See Section 7.4.5

Identify() M See Section 7.4.9


StripeSize O See Section 7.4.3

PercentComplete O See Section 7.4.4

OSName O See Section 7.4.6 PhysicalDrvMultipathAccess M See Section 7.4.7

10.5 HPSA_StoragePool

HPSA_StoragePool has been extended from CIM_StoragePool as defined in SNIA Block Services profile.

Version 2.0.0 75

Table 39 – Class: HPSA_StorageVolume

Properties Requirement Notes Identify() M See Section 7.5.1

10.6 HPSA_MediaAccessStatData

The SNIA Disk Drive Lite profile has been extended to add HPSA_MediaAccessStatData class to model Monitoring and Performance counters reported by Disk Drives. The following properties have been added to the CIM_MediaAccessStatData class.

Table 40 – Class: HPSA_MediaAccessStatData

Properties Requirement Notes InstanceID M Key

AbortedCommands O See Section 7.6.1

BadTargetErrors O See Section 7.6.2

ECCRecoveredReadErrors O See Section 7.6.3

FormatErrors O See Section 7.6.4

HardReadErrors O See Section 7.6.5

HardWriteErrors O See Section 7.6.6

HardwareErrors O See Section 7.6.7

HotPlugCount O See Section 7.6.8

MediaFailures O See Section 7.6.9

NotReadyErrors O See Section 7.6.10

OtherTimeOuts O See Section 7.6.11

SCSIBusFaults O See Section 7.6.12

SectorsRead O See Section 7.6.13

SectorsWritten O See Section 7.6.14

SeekCount O See Section 7.6.15

SeekErrors O See Section 7.6.16

SpinUpErrors O See Section 7.6.17

DRQTimeOuts O See Section 7.6.18

RetryRecoveredReadErrors O See Section 7.6.19

RetryRecoveredWriteErrors O See Section 7.6.20

FailedReadRecovers O See Section 7.6.21

FailedWriteRecovers O See Section 7.6.22

ServiceHours O See Section 7.6.23

10.7 CIM_ElementStatisticalData

This class is used to associate HPSA_MediaAccessStatData to HPSA_DiskDrive.

Table 41 – Class: CIM_ElementStatisticalData

76 Version 2.0.0

Properties Requirement Notes ManagedElement M Key, Ref CIM_ManagedElement

Stats M Key, Ref CIM_StatisticalData






RegisteredName Mandatory “HP Smart Array”


10.9 HPSA_ SCSIInitiatorTargetLogicalUnitPath

HPSA_ SCSIInitiatorTargetLogicalUnitPath class has been extended from CIM_ SCSIInitiatorTargetLogicalUnitPath to add Smart Array specific features.

Table 43 – Class: HPSA_SCSIInitiatorTargetLogicalUnitPath

Property Requirement Notes

Initiator Mandatory Reference to an instance of HPSA_ISASSCSIProtocolEndpoint

Target Mandatory Reference to an instance of HPSA_TSASSCSIProtocolEndpoint

LogicalUnit Mandatory Reference to an instance of HPSA_StorageExtent

State Optional

Set to:

0 (unknown) if the path status cannot be ascertained

2 (active) if the path is active and healthy

5 (Path Error) path has an error condition

3 (passive) path is healthy but is not active or is the standby path

10.10 HPSA_ArraySystemExternalArraySystem

This class is used to associate HPSA_ArraySystem representing the HBA to HPSA_ArraySystem representing the external storage controller.

Table 44 – Class: HPSA_ArraySystemExternalArraySystem

Version 2.0.0 77

Properties Requirement Notes GroupComponent M Key, Ref CIM_ComputerSystem

PartComponent M Key, Ref CIM_ComputerSystem

10.11 CIM_SoftwareIdentity

The CIM_SoftwareIdentity class is defined by document DMTF DSP1023, Software Inventory Profile and is used to describe the array controller firmware, drive firmware, Smart Drive Carrier Application firmware and Smart Drive Carrier Bootloader firmware.

Table 23 - Class Properties: CIM_SoftwareIdentity

Properties Requirement Notes BuildNumber Conditional The build number of the firmware (if one exists) Classifications[] Mandatory This property shall have the value of

10=’Firmware’ in the [0] element. Manufacturer Mandatory Indicates the manufacturer of the firmware, e.g.

“HP”. MajorVersion Mandatory The major version value of the firmware MinorVersion Mandatory The minor version value of the firmware RevisionNumber Conditional The revision number of firmware (if one exists) VersionString Mandatory A string representing the complete firmware

version information.




None Defined




None Defined

78 Version 2.0.0

ANNEX A (normative)

Change Log

Version Date Description .001 09/08/06 Initial Draft .002 09/19/06 Update per review (B. Evans) .003 09/29/06 Update per review (WBEM TC 09/28/06) .004 11/30/06 Update per rQms, Review and SMH enhancements .005 12/15/06 Minor update .006 02/14/07 Minor update to change consolidated status algorithm

1.2.0 01/05/09 Update diagrams and text to correct class names. Add Scoping method to Profile registration. Add note that Target Port SNIA profile is not implemented, even though mandatory.

1.3.0 04/16/09

Merge the multi-path implementation classes into the profile. Updated with implementation of SNIA Target ports profile, Initiator ports profile, Multi-path support. Update to change battery and cache status for capacitor based cache module support. Added 2 new properties NumberOfInternalPorts and NumberOfExternalPorts to HPSA_ArrayController class to represent the count of external and internal ports.

1.4.0 06/29/09 Added Enclosure ports model. 1.4.1 7/30/09 Add support for external storage controller to HBA identification 1.4.2 9/9/09 Add new MediaType property to differentiate solid state storage. 1.4.3 10/1/09 Add new Connectivity/Passive status to ConnectivityCollection.

1.4.4 1/3/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.4.5 04/19/10 Added Rebuild to list of possible OperationalStatus[1] values for DiskDrive and StorageExtent.

1.4.6 09/24/10 Added Transient Data Drive status to list of possible OperationalStatus[1] values for DiskDrive

1.4.7 11/22/2010 Add new properties and operational status for Solid State Drive life information. 1.4.8 03/11/2010 Added new SSD wear status for Solid State Drives 2.0.0 04/06/2011 Version 2.0.0 created from CR00173

Version 2.0.0 79

ANNEX B (Informative)

Acknowledgments

80 Version 2.0.0

ANNEX C (Informative)


CR

Number Date Title CR00112 9/08/06 Create HP Profile for HP Smart Array CR00153 7/30/09 Add support for external storage controller and HBA array system Identification

CR00173 4/06/2011

Added new properties and operational status for Smart Drive Carrier Authentication. Added new classes to represent HPSA_SmartCarrierAppFirmware and HPSA_SmartCarrierBootldrFirmware for reporting Smart Drive Carrier FW information. Updated datatypes for HPSA_DiskDrive SSD properties Updated the primary OperationalStatus for SSD Wearout

Version 2.0.0 81

Bibliography



Date: 06/04/2012

Version: 2.1.0

HP SAS HBA Profile




2 Version 2.1.0

Contents



3 Terms and Definitions ........................................................................................................................... 7 4 Symbols and Abbreviated Terms .......................................................................................................... 9 5 Synopsis ................................................................................................................................................ 9 6 Description ............................................................................................................................................ 9

6.1 Host Hardware RAID Controller ................................................................................................ 10 6.2 Block Services .......................................................................................................................... 12 6.3 Disk Drive Lite ........................................................................................................................... 14 6.4 Extent Mapping ......................................................................................................................... 15 6.5 Disk Sparing .............................................................................................................................. 16 6.6 Profile Registration .................................................................................................................... 16 6.7 Consolidated Status .................................................................................................................. 18 6.8 Location information.................................................................................................................. 19 6.9 Software Inventory .................................................................................................................... 19

7 Implementation Requirements ............................................................................................................ 19 7.1 HPSAS_DiskDrive .................................................................................................................... 19 7.2 HPSAS_StorageVolume ........................................................................................................... 22 7.3 HPSAS_StorageExtent ............................................................................................................. 23

8 Methods ............................................................................................................................................... 23 8.1 Profile Conventions for Operations ........................................................................................... 23

9 Use Cases ........................................................................................................................................... 23 9.1 Host Hardware RAID Controller ................................................................................................ 24 9.2 Single Pool – Single Storage Volume ....................................................................................... 28 9.3 Mixed Pool Example ................................................................................................................. 29 9.4 Single NonRaid Pool Example .................................................................................................. 30 9.5 Disk Sparing - Drive failure example ........................................................................................ 31 9.6 Host based HBA controller model ............................................................................................. 34 9.7 Consolidated status example .................................................................................................... 35

10 CIM Elements ...................................................................................................................................... 36 10.1 HPSAS_DiskDrive .................................................................................................................... 36 10.2 HPSAS_StorageVolume ........................................................................................................... 36 10.3 HPSAS_StorageExtent ............................................................................................................. 37 10.4 HP_RegisteredProfile ............................................................................................................... 37 10.5 CIM_SoftwareIdentity................................................................................................................ 37

11 Durable Names and Correlatable IDs ................................................................................................. 38 ANNEX A (normative) Change Log ........................................................................................................... 39 ANNEX B (Informative) Acknowledgments ................................................................................................ 40 ANNEX C (Informative) Included WBEM TC CR Numbers ....................................................................... 41 Bibliography ................................................................................................................................................ 42

Version 2.1.0 3

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 ............................................................... 15 Figure 5 - HP SAS HBA profile: Disk Sparing Class Diagram .................................................................... 16 Figure 6 - HP SAS HBA profile: Profile Registration ................................................................................... 17 Figure 7 - HP SAS HBA profile: Consolidated Status ................................................................................. 18 Figure 8 - HP SAS HBA profile: Software Inventory ................................................................................... 19 Figure 9 - HP SAS HBA profile: Host Hardware RAID Controller ............................................................... 25 Figure 10 - HP SAS HBA profile: Host Hardware RAID Controller Physical .............................................. 26 Figure 11 - HP SAS HBA profile: Single Storage Volume .......................................................................... 28 Figure 12 - HP SAS HBA profile: Mixed Pool Example .............................................................................. 29 Figure 13 - HP SAS HBA profile: Single NonRaid Pool Example ............................................................... 30

4 Version 2.1.0

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 ...................................................... 20 Table 5 - HP SAS HBA profile: HPSAS_DrivePlacement ........................................................................... 20 Table 7 - HP SAS HBA profile: HPSAS_StorageVolume.FaultTolerance .................................................. 23 Table 8 – CIM Elements – HP SAS HBA Profile ........................................................................................ 36 Table 9 – Class: HPSAS_DiskDrive ........................................................................................................... 36 Table 10 – Class: HPSAS_StorageVolume ................................................................................................ 37 Table 11 – Class: HPSAS_StorageExtent .................................................................................................. 37 Table 12 – Class: HP_RegisteredProfile .................................................................................................... 37 Table 45 - Class Properties: CIM_SoftwareIdentity .................................................................................... 38 Table 13 – Durable Names generated by this Profile ................................................................................. 38 Table 14 – Correlatable IDs generated by this Profile ................................................................................ 38

Version 2.1.0 5

Foreword

The HP SAS HBA Profile (P00122) was prepared by the HP WBEM TC.

6 Version 2.1.0

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.

Version 2.1.0 7

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.











SNIA SMI-S 1.0.2


SNIA SMI-S 1.4 (Draft 4)







8 Version 2.1.0












Version 2.1.0 9


None.

5 Synopsis Profile Name: HP SAS HBA Profile

Version: 2.0.0


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



P00100 HP Profile Registration Profile


P00113 HP Consolidated Status Profile



P00120 HP Storage Enclosure Profile


Host Hardware RAID Controller SNIA 1.3.0 Mandatory

Multiple Computer Systems SNIA 1.1.0 Mandatory


Extent Mapping SNIA 1.3.0 Mandatory

Physical Package SNIA 1.3.0 Mandatory

Location SNIA 1.3.0 Mandatory

Disk Sparing SNIA 1.3.0 Mandatory

Generic Initiator Ports SNIA 1.3.0 Optional



6 Description This profile models the HP SAS HBA installed in a base server using Host Hardware RAID Controller profile and HP extensions defined in this profile. (See section 6.1)

10 Version 2.1.0


HPSAS_ArraySystem

HP_ComputerSystem

HP Base Server

SystemComponent

HPSAS_PortController


ComputerSystem PortController

HPSAS_PhysicalPackageSystemPackaging

PhysicalPackage

HPSAS_Product

Product


HPSAS_DAPort

HostedAccessPoint

DAPort

HPSAS_SCSIProtocolEndpoint

SCSIProtocolEndPoint

HPSAS_SCSIProtocolController

SCSIProtocolController

HPSAS_StorageVolume

StorageVolume



SystemDevice

SystemDevice

See Direct Attached Port Profile

See DMTF Physical Asset Profile

HPSAS_ArrayControllerComponentCS

ComputerSystem

SystemDevice

DeviceSAPImplermentation

Figure 1 – HP SAS HBA profile: HHRC Class Diagram

The Host Hardware Raid Controller profile is used to model PCI based SAS HBA’s. Figure 1 shows the class derivation from the SNIA defined required classes. The central class for HBAs will be HPSAS_PortController and is associated to the Host system via CIM_SystemComponent.

Version 2.1.0 11

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. HPSAS_PhysicalPackage is associated to the Top Level System (HPSAS_ArraySystem) via CIM_SystemPackaging association. HPSAS_Product is associated to HPSAS_PhysicalPackage via CIM_ProductPhysicalPackage.

The managed aspects of the actual controller are modeled in the HPSAS_ArrayController class. This is a subclass of CIM_ComputerSystem and is associated to the Top Level System using CIM_ComponentCS. This class will hold the Operational Status for the controller itself. The HPSAS_ArraySystem class will hold the consolidated Operational Status for the array as a whole.

Front end ports are modeled as CIM_DAPorts which implies direct attached to the host bus (e.g. PCI, PCI-X, etc.).

12 Version 2.1.0

6.2 Block Services

HPSAS_ArraySystem

SystemDevice

HPSAS_PrimordialPool

Promordial = “True” (RAID)

StoragePool


HostedStoragePool

HPSAS_StoragePool



HPSAS_StorageVolume

StorageVolume

HPSAS_StorageCapabilities

DataRedundancyMax = 2PackageRedundancyMax = 1

StorageCapabiliites


ElementCapabilities

ElementCapabilities

HPSAS_StorageSetting

ElementSettingData StorageSetting

HPSAS_PrimordialPoolNonRaid

Promordial = “True” (Non RAID)

HostedStoragePool

HPSAS_StorageExtent

ConcreteComponent


DataRedundancyMax = 1PackageRedundancyMax = 0

ElementCapabilities

HostedStoragePool

SystemDevice

Figure 2 - HP SAS HBA profile: Block Services Class Diagram

Block services profile is used to model the logical storage that is presented by the Array system. Note that this implementation only supports a “read only” capability; there is no support for methods that allow configuration of pools and volumes.

Version 2.1.0 13

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. All concrete pools will be allocated from the primordial pool for RAID drives. All the concrete pools shall be associated to this primordial pool via a CIM_AllocatedFromStoragePool. An HPSAS_StorageCapabilities instance shall be associated to each pool to indicate current capabilities for the pool.

Instances of HPSAS_PrimordialPool represent raw storage managed by the array system. Instances of HPSAS_Primordialpool are associated to the top level system (HPSAS_ArraySystem) using CIM_HostedStoragePool. Concrete pools are allocated from primordial pools (HPSAS_PrimordialPool). This is represented by instances of HPSAS_StoragePool associated to the primordial pool (HPSAS_PrimordialPool) it is allocated from via instances of CIM_AllocatedFromStoragePool

Storage Volumes (HPSAS_StorageVolume) will be allocated from concrete pools (HPSAS_StoragePool) and associated to them via CIM_AllocatedFromStoragePool. The current storage settings for a storage volume are specified in the associated Storage Setting class (HPSAS_StorageSetting). HPSAS_StorageSetting will be associated to the storage volume via CIM_ElementSettingData.

Disks that are not in any RAID configurations will be modeled as HPSAS_StorageExtent and associated to an HPSAS_PrimordialPoolNonRaid instance via CIM_ConcreteComponent. The HPSAS_StorageCapabilities for this Pool show DataRedundancyMax is one and PackageRedundancyMax is zero, indicating no redundancy available.

Note that if all the disks connected to a HBA are configured to be part of RAID sets, HPSAS_PrimordialPoolNonRaid instance shall not be created. Vice versa, if none of the disks are in any RAID configurations, HPSAS_PrimordialPool instance shall not be created.

14 Version 2.1.0

6.3 Disk Drive Lite

HPSAS_DiskDrive

DiskDrive

HPSAS_SoftwareIdentity

Drive F/WMediaPresent

SoftwareIdentity

HPSAS_StorageExtent

Primoridal Extent

StorageExtent


HPSAS_DiskPhysicalPackage

Realizes

PhysicalPackage

HPSAS_DiskLocation

HP_Location

HPSAS_ArraySystem

SystemDevice


HP_DriveCage

HP_StorageEnclosure

Container

Container

HP_StorageEnclosureProcessorSystemPackaging

SystemComponent

See HP_StorageEnclosure Profile

Figure 3 - HP SAS HBA profile: Disk Drive Lite class diagram

Disk Drive Lite profile is used to model logical and physical aspects of disks. In this profile the HPSAS_DiskDrive class has been extended from CIM_DiskDrive to add HP specific properties.

Drive firmware will be supported within the HPSAS_DiskDriveFirmware class associated to the HPSAS_DiskDrive class via CIM_ElementSoftwareIdentity in accordance with DMTF Software Inventory Profile.

Version 2.1.0 15

Smart Carrier Application firmware will be supported associated to the HPSAS_DiskDrive class via CIM_ElementSoftwareIdentity in accordance with SNIA Disk Drive Lite Profile.

Smart Carrier Bootloader firmware will be supported associated to the HPSAS_DiskDrive class via CIM_ElementSoftwareIdentity in accordance with SNIA Disk Drive Lite Profile.

Figure 3 shows how the disk drives may be contained within a storage enclosure. (See HP Storage Enclosure Profile, P00120).

6.4 Extent Mapping

HPSAS_DiskDrive

DiskDrive

MediaPresent

HPSAS_StorageExtent

Primoridal Extent

StorageExtent

HPSAS_ArraySystem

SystemDeviceHPSAS_StorageVolume

HPSAS_StoragePool

Concrete Pool

StorageVolume

StoragePool


BasedOn

ConcreteComponent

HostedStoragePool

SystemDevice

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. These extents are associated one per disk drive using the CIM_MediaPresent association.

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

SpareIsSpare

StorageExtent

StorageRedundancySetStoragePool

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

Version 2.1.0 17

HPSAS_ArraySystem HPSAS_PortController


ComputerSystem PortController


SNIA “HHRC”


HHRC

Interop Namespace


HP WBEM TC “SAS HBA”

HP_ExtendsProfile

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.

18 Version 2.1.0

6.7 Consolidated Status

HPSAS_ArraySystem


HPSAS_ArraySystem


HPSAS_ArraySystem


HPSAS_StorageSpecificCollection



MemberOfCollection


HP_ComputerSystem



HPSAS_StorageGroupHostedCollection

Figure 7 - HP SAS HBA profile: Consolidated Status

This provider will calculate operational status values for each Top Level System. These status values will be in accordance with the HP WBEM TC P00113, HP Consolidated Status Profile. This will allow the condition of the Storage System to participate in the Consolidated Status mechanism. The “worst off” status of these instances will be aggregated and populated in a single instance of HPSAS_StorageSpecificCollection which then gets collected by the Base Server provider to participate in the overall consolidated status algorithm. The instances of HPSAS_ArraySystem will be associated to HPSAS_StorageSpecificCollection via HPSAS_StorageSpecificCollectionArraySystem (CIM_MemberOfCollection). The instances of HPSAS_StorageSpecificCollection will be associated to the singleton instance of HP_WinComputerSystem (BaseServer Profile) via a subclass of HP_GroupHostedCollection (HPSAS_StorageGroupHostedCollection).

The consolidated status will be defined with three possible states. These three states are defined in Table 2 along with the algorithms to calculate each possible status.

Table 2 – Consolidated Status Algorithm

Status Reason for Status Error If there is a controller failure or

If there is a logical drive failure or If there is a Storage Enclosure in Critical condition

Degraded If none Failed conditions are met and If a physical drive status is not OK or If a logical drive status is not OK or If a Storage Enclosure status is not OK

OK If none of the Failed and none of the Degraded conditions are met

Version 2.1.0 19


An instance of HP_Location sub class will be associated to applicable physical packages by CIM_PhysicalElementLocation.


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.

HPSAS_ArraySystem HPSAS_Firmware

CentralClass

ComputerSystem SoftwareIdentity



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 Implementation Requirements This section details the requirements for implementations of this profile.

7.1 HPSAS_DiskDrive

The HPSAS_DiskDrive class has been extended from CIM_DiskDrive as defined in SNIA Disk Drive Lite profile.

7.1.1 HPSAS_DiskDrive.DriveInterface

Value indicates the type of interface for the disk. (E.g. Parallel, SATA, SAS). Note that SAS HBA provider only supports SATA and SAS drives.

Table 3 - HP SAS HBA profile: HPSAS_DiskDrive.DriveInterface

Value ValueMap 0 Unknown 1 Parallel 2 SATA 3 SAS 4 SATALogical 5 SASLogical

20 Version 2.1.0

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 ValueMap 0 Unknown 1 Unconfigured 2 Data 3 Spare 4 Non RAID

7.1.3 HPSAS_DiskDrive.DriveRotationalSpeed

Value indicates the rotational speed of the drive in Revolutions per minute.

7.1.4 HPSAS_DiskDrive.DriveHasMNPData

Boolean value indicates that the drive supports reporting of Monitoring and Performance data counters. Note that this value will always be false for SAS HBA provider.

7.1.5 HPSAS_DiskDrive.DrivePlacement

Value indicates where the drive is located with respect to the controller.

Table 5 - HP SAS HBA profile: HPSAS_DrivePlacement

Value ValueMap 0 Unknown 1 Internal 2 External

7.1.6 HPSAS_DiskDrive.OperationalStatus.

HPSAS_DiskDrive.OperationalStatus[0] property shall be implemented. This property indicates the Operational Status of the disk drive. Operationalstatus[0] depicts the Primary operational status of the disk drive .

OperationalStatus[1] values shows the secondary(or extended) operational status of the disk drive.

The below values shows the possible OperationalStatus[1] values related to secure erase operations.

Table 6 HP SAS HBA profile: HPSAS_DiskDrive.OperationalStatus

Value ValueMap 0x8000 Queued for Secure Erase 0x8001 Erase in Progress 0x8002 Erase Completed

The below values shows the possible OperationalStatus[1] values to account for the failure of a path from controller to disk.

• If any path to the disk making up this volume is currently set to 5 (Path Error) and there still exists at least one path that is active and the disk is currently ok then:

o OperationalStatus [0]: 3 (degraded) o OperationalStatus[1]: 32771 (0x8003) (Physical Path In Error)

Version 2.1.0 21

• If all paths on all disks are set to 5 (Path Error) then: o OperationalStatus[0]: 6 (error) o OperationalStatus[1]: 32771(0x8003) (Physical Path In Error)

The below values shows the possible OperationalStatus[1] values to account for transient data drive and rebuilding of a physical drive.

• If the disk is in transient data drive status:

o OperationalStatus [0]: 2 (OK) o OperationalStatus[1]: 0x8004 (Transient Data Drive)

• If the disk is in the process of rebuilding it data due to becoming an active spare or recovering from a previous failure:

o OperationalStatus [0]: 2 (OK) o OperationalStatus[1]: 0x8005 (Rebuild)

The below values shows the possible OperationalStatus [1] values to account for Solid State drive wear out.

• If the Solid state drive reports a Smart Trip due to wear out then: o OperationalStatus[0]: 5 (Predictive Failure) o OperationalStatus[1]: 0x8006 (Solid State drive wear out)

The below values shows the possible OperationalStatus [1] values to account for Physical Drive Authentication.

• If the physical drive reports a authentication failure then: o OperationalStatus [0]: 3 (Degraded) o OperationalStatus[1]: 0x8007(Not Authenticated)

NOTE: The properties from section 7.1.6 till 7.1.9 are conditionally populated only if the controller firmware and disk drive firmware support reporting drive life parameters for Solid State Disk Drives. Otherwise, these property values will be empty.

If the firmware supports reporting these parameters can be verified using SSDWearStatus property. If this property value is set to “Unknown”, it implies that the provider is unable to determine the physical drive’s solid state disk drive life parameters.

7.1.7 HPSAS_DiskDrive.SSDTotalPowerOnHours

This value indicates the total number of hours that the Solid State Disk has been powered on. This property will only be available if the controller firmware supports reporting of solid state drive life information.

7.1.8 HPSAS_DiskDrive.SSDPercentageEnduranceUsed

This value reports the Physical Drive Solid State Percent Endurance Used as integer. This property will only be available if the controller firmware supports reporting of solid state drive life information.

7.1.9 HPSAS_DiskDrive.SSDLifeRemaining

This value indicates the Solid State drive life remaining days until wear out. This property will only be available if the controller firmware supports reporting of solid state drive life information.

22 Version 2.1.0

7.1.10 HPSAS_DiskDrive. SSDWearStatus

This value indicates the wearout status of the Solid State drive.

Table 21 - HP SAS HBA profile: HPSAS_DiskDrive.DrivePlacement

Value ValueMap 0 Unknown 1 OK 2 56 day threshold passed 3 5 percent threshold passed 4 2 percent threshold passed 5 SSD Wear Out

7.1.11 HPSAS_DiskDrive.SmartCarrierAuthStatus

This value indicates the status of the Smart Carrier Authentication if the controller supports hard drive and SmartCarrier Authentication.

Table 22 - HP Smart Array profile: HPSAS_DiskDrive.SmartCarrierAuthStatus

Value ValueMap 0 Not Supported 1 Not Authenticated 2 Authenticated 3 Other

7.1.12 HPSAS_DiskDrive.OtherSmartCarrierAuthStatus

A string that describes the authentication status of the element when the HPSAS_DiskDrive.SmartCarrierAuthStatus property is set to 3 ("Other"). This property must be set to null when HPSAS_DiskDrive.SmartCarrierAuthStatus is any value other than 3.

7.1.13 HPSAS_DiskDrive.SSDPercentEnduranceUsed

This value reports the Physical Drive Solid State Percent Endurance Used as Real. This property will only be available if the controller firmware supports reporting of solid state drive life information.

7.2 HPSAS_StorageVolume

The HPSAS_StorageVolume class has been extended from CIM_StorageVolume class as defined in SNIA Block Services profile.

7.2.1 HPSAS_StorageVolume.PercentComplete

During a rebuild operation, this will indicate progress as a percentage value. Note this value shall only be populated when a rebuild operation is being performed on this logical volume.

7.2.2 HPSAS_StorageVolume.FaultTolerance

Enumeration to indicate which type of raid is currently configured for a logical volume. Supported values are:

Version 2.1.0 23

Table 7 - HP SAS HBA profile: HPSAS_StorageVolume.FaultTolerance

Value ValueMap 0 Unknown 1 RAID 0 2 RAID 1 3 RAID 1+0 4 RAID 4 5 RAID 5 6 RAID 51 7 RAID 6

7.2.3 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.OSName

For drives that have not been configured as part of a raid set, this should display the volume name as it is known to the operating system, otherwise it shall not be assigned a value.

8 Methods None.




• GetInstance

• Associators

• AssociatorNames

• References

• ReferenceNames




9 Use Cases

24 Version 2.1.0


HPSAS_ArraySystem:01


HP Base Server

SystemComponent

HPSAS_PortController:01


HPSAS_PhysicalPackage:01

SystemPackaging

HPSAS_Product:01

Name = “HP 4 Port SATA/SAS”ProductPhysicalComponent

HPSAS_DAPort:01

HostedAccessPoint

HPSAS_SCSIProtocolEndpoint:01

HPSAS_SCSIProtocolController:01

SystemDevice

HPSAS_StorageVolume:002




SystemDevice

HPSAS_PrimordialPool:00


HPSAS_StoragePool:01


HPSAS_Location:01


HPSAS_DiskDrive:004

HPSAS_DiskDrive:005

SystemDevice

HPSAS_StorageExtent:004


BasedOn

MediaPresent

MediaPresent



HostedStoragePool


RegisteredProfile

RegisteredOrg = “SNIA”RegisteredName = “HHRC”


HPSAS_StorageSetting:002




HPSAS_ArrayController:123ComponentCS

RegisteredProfile

RegisteredOrg = “Other”OtherRegOrg = “HP WBEM TC”RegisteredName = “HP SAS HBA”

HP_ExtendsProfile

Version 2.1.0 25

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.

The Top Level System (used to scope devices managed by the array) is identified by following CIM_LogicalIdentity association to HPSAS_ArraySystem class.

This example shows a RAID 1 volume based on two disk drives. All disk drives can be found using SystemDevice association from the Top Level System. Disk drives that belong to any StorageVolume can be found by using the BasedOn association from the StorageVolume to the StorageExtents. The StorageExtents represent the primordial extent and map to DiskDrive instances one to one using MediaPresent association.

The raid characteristics of the Storage Volume can be determined by inspecting the FaultTolerance property of the HPSAS_StorageVolume class. Alternatively the HPSAS_StorageSetting class, associated to the Storage Volume via CIM_ElementSettingData contains DataRedundancy and PackageRedundancy properties that define the Quality of Service. Raid types and corresponding values in StorageSetting class are covered in the SMI-S specification.

The marketing name for the controller can be found by first traversing the SystemPackaging association from the Top Level System instance to the PhysicalPackage that represent the Array system, then the HPSAS_Product class can be found using CIM_ProductPhysicalPackage association. The Marketing name an IS stored in the HPSAS_Product.Name property.

26 Version 2.1.0

9.1.1 Host Hardware RAID Controller Physical model


HPSAS_PortController:01

CentralClass

LogicalIdentity

HPSAS_PhysicalPackage:01

SystemPackaging

HPSAS_Product:01

Name = “HP 4 Port SATA/SAS”ProductPhysicalComponent

SystemDevice

HPSAS_ArrayController:123

ComponentCS

HPSAS_Location:01


HPSAS_DiskDrive:004

HPSAS_DiskDrive:005


HPSAS_StorageExtent:005MediaPresent

MediaPresent


HPSAS_DiskPhysicalPackage:004

HPSAS_DiskPhysicalPackage:005

Realizes

Realizes

HPSAS_DiskLocation:004


HPSAS_DiskLocation:005




SystemDevice

Figure 10 - HP SAS HBA profile: Host Hardware RAID Controller Physical

Version 2.1.0 27

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.

28 Version 2.1.0

9.2 Single Pool – Single Storage Volume


SystemDevice







HPSAS_DiskDrive:004

HPSAS_DiskDrive:005

SystemDevice



BasedOn

MediaPresent

MediaPresent



HostedStoragePool





Figure 11 - HP SAS HBA profile: Single Storage Volume

Version 2.1.0 29

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.3 Mixed Pool Example


SystemDevice



HPSAS_ArrayController:123ComponentCS





HPSAS_DiskDrive:004

HPSAS_DiskDrive:005

SystemDevice



BasedOn

MediaPresent

MediaPresent



HostedStoragePool




HPSAS_DiskDrive:008


MediaPresent

ConcreteComponent

HPSAS_PrimordialPoolNonRaid:00


HostedStoragePool

SystemDevice

Figure 12 - HP SAS HBA profile: Mixed Pool Example

Figure 12 shows a SAS controller with two Primordial Pools. The RAID capable pool has one concrete Storage Pool with one Storage Volume configured.

30 Version 2.1.0

The Non RAID pool shows one Storage Extent that is not part of any RAID configuration.

9.4 Single NonRaid Pool Example


SystemDevice

MediaPresent

ConcreteComponent

HPSAS_PrimordialPoolNonRaid:00


HostedStoragePool

SystemDevice


HPSAS_DiskDrive:008

MediaPresent

ConcreteComponent

HPSAS_DiskDrive:005


Figure 133 - HP SAS HBA profile: Single NonRaid Pool Example

Figure 123 shows a SAS controller with a Non RAID Primordial Pool. The Non RAID pool shows two Storage Extents that are not part of any RAID configuration.

Version 2.1.0 31

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


OPStatus = “OK”


OPStatus = “OK”

HPSAS_StoragePool:1

Concrete Pool

ConcreteComponent

ConcreteComponent

HPSAS_StorageRedundancySet:AMemberOfCollection

MemberOfCollection



IsSpare


OpStatus = “OK”


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. The spare drive can be identified by its IsSpare association to the StorageRedundancySet.

32 Version 2.1.0

9.5.2 Drive Failed – data rebuilding


OPStatus = “OK”



HPSAS_StoragePool:1

Concrete Pool

ConcreteComponent

ConcreteComponent

HPSAS_StorageRedundancySet:A

MemberOfCollection

MemberOfCollection



ExtentStatus = “Rebuild”

IsSpare


OpStatus = “Degraded”PercentComplete = “33”


Spared

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. The progress for the rebuild will be shown in HPSAS_StorageVolume.PercentComplete.

The CIM_Spared association is used to associate the spare to the failed drive that it has replaced.

Version 2.1.0 33

9.5.3 Drive Failed – Rebuild complete


OPStatus = “OK”


SpareOPStatus = “ERROR”

HPSAS_StoragePool:1

Concrete Pool

ConcreteComponent

ConcreteComponent


MemberOfCollection

MemberOfCollection


OPStatus = “OK”

IsSpare


OpStatus = “OK”


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.

34 Version 2.1.0

9.5.4 Drive replaced


OPStatus = “OK”



HPSAS_StoragePool:1

Concrete Pool

ConcreteComponent

ConcreteComponent


MemberOfCollection

MemberOfCollection


OPStatus = “OK”

IsSpare


OpStatus = “OK”


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



HPSAS_ArrayController:123

OpStatus = “OK”

ComponentCSHPSAS_StorageVolume:002


SystemDevice

Figure 18 - HP SAS HBA profile: Host HBA Controller

Figure shows the instance diagram for a SAS HBA controller. The HPSAS_ArraySystem represents the overall array and the OperationalStatus value will contain the consolidated status for the array. The controller instance (HPSAS_ArrayController) is associated via CIM_ComponentCS. In the above example

Version 2.1.0 35

we see that the “degraded” status of a logical drive has been consolidated into HPSAS_ArraySystem.OperationalStatus[0].

9.7 Consolidated status example



HPSAS_ArraySystem


HPSAS_StorageSpecificCollection:01



HP_ComputerSystem







SystemDeviceSystemDevice





BasedOn




OperationalStatus = ERROR

BasedOn

Figure 19 - HP SAS HBA profile: Consolidated Status

Figure shows a typical instance diagram where a single drive failure in a Raid configuration will cause elements to have “Degraded” OperationalStatus. This will be propagated up to HPSAS_ArraySystem.OperationalStatus and so to the GroupOperationalStatus in the HPSAS_StorageSpecificCollection to participate in the overall system OperationalStatus for the Host per the HP Consolidated Status profile.

Note: some instances have not been included in the diagram for the sake of clarity.

36 Version 2.1.0


Table 8 – CIM Elements – HP SAS HBA Profile


Classes HPSAS_DiskDrive Mandatory See Section 7.1

HPSAS_StorageVolume Mandatory See Section 7.1.6

HPSAS_StorageExtent Mandatory See Section 7.3

CIM_SoftwareIdentity Conditional See Section 10.5 Indications

None defined.

10.1 HPSAS_DiskDrive

HPSAS_DiskDrive class has been extended from CIM_DiskDrive to add SAS HBA specific features.

Table 9 – Class: HPSAS_DiskDrive


Notes

DriveConfguration M See Section 7.1.2

DriveInterface M See Section 7.1.1

DriveRotationalSpeed M See Section 7.1.3

DriveHasMNPData M See Section 7.1.4

DrivePlacement M See Section 7.1.5


SSDTotalPowerOnHours C See Section 7.1.7

SSDPercentageEnduranceUsed C See Section 7.1.8

SSDLifeRemaining C See Section 7.1.9

SSDWearStatus C See Section 7.1.10

SmartDriveCarrierAuthStatus O See Section 7.1.11

OtherSmartDriveCarrierAuthStatus C See Section 7.1.12

SSDPercentEnduranceUsed C See Section 7.1.13

10.2 HPSAS_StorageVolume

HPSAS_StorageVolume has been extended from CIM_StorageVolume as defined in SNIA Block Services profile.

Version 2.1.0 37

Table 10 – Class: HPSAS_StorageVolume


FaultTolerance M See Section 7.2.2

PercentComplete O See Section 7.2.1

OSName O See Section 7.2.3

10.3 HPSAS_StorageExtent

HPSAS_StorageExtent has been extended from CIM_StorageExtent as defined in SNIA Block Services profile.

Table 11 – Class: HPSAS_StorageExtent


OSName O See Section 7.3.1







RegisteredName Mandatory “HP SAS HBA


10.5 CIM_SoftwareIdentity

The CIM_SoftwareIdentity class is defined by document DMTF DSP1023, Software Inventory Profile and is used to describe the array controller firmware, drive firmware, Smart Drive Carrier Application firmware and Smart Drive Carrier Bootloader firmware.

38 Version 2.1.0

Table 6 - Class Properties: CIM_SoftwareIdentity

Properties Requirement Notes BuildNumber Conditional The build number of the firmware (if one exists) Classifications[] Mandatory This property shall have the value of


“HP”. MajorVersion Mandatory The major version value of the firmware MinorVersion Mandatory The minor version value of the firmware RevisionNumber Conditional The revision number of firmware (if one exists) VersionString Mandatory A string representing the complete firmware





None Defined




None Defined

Version 2.1.0 39

ANNEX A (normative)

Change Log



.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.1.0 27/10/10 Updated mandatory clauses for PrimordialPool instance creation 2.0.0 23/05/2011 Version 2.0.0 created from CR00172 2.1.0 12/09/2011 Version 2.1.0 created from CR00176

40 Version 2.1.0

ANNEX B (Informative)

Acknowledgments

Version 2.1.0 41

ANNEX C (Informative)


CR

Number Date Title

CR00112 9/08/06 Create HP Profile for HP SAS HBA CR00165 10/27/10 Clarification of SAS Profile

CR00172 05/23/2011

Added Rebuild to list of possible OperationalStatus[1] values for DiskDrive. Added Transient Data Drive status to list of possible OperationalStatus[1] values for DiskDrive Add new properties and operational status for Solid State Drive life information. Added new properties and operational status for Smart Carrier Authentication. Added new classes SmartCarrierAppFirmware and SmartCarrierBootldrFirmware for SmartCarrier FW information.

CR00176 07/12/2011 Added new property SSDPrecentEnduranceUsed of real datatype in HPSAS_DiskDrive class

42 Version 2.1.0

Bibliography



Date: 03/25/09

Version: 1.2.0

HP Location Profile




2 Version 1.2.0

Contents




7.1 HP_Location ............................................................................................................................. 10 8 Methods ............................................................................................................................................... 14 9 Use Cases ........................................................................................................................................... 15

9.1 Identifying the Location of a Managed Element ....................................................................... 15 9.2 Object Diagrams ....................................................................................................................... 16

10 CIM Elements ...................................................................................................................................... 19 10.1 HP_Location ............................................................................................................................. 19 10.2 HP_ElementLocation ................................................................................................................ 20


Version 1.2.0 3

Figures

Figure 1 – Location Class Diagram ............................................................................................................... 9Figure 2 – Location Full Containment Implemented ................................................................................... 17Figure 3 – Location without physical side of model .................................................................................... 18Figure 4 – Typical Location Implementation ............................................................................................... 19

4 Version 1.2.0

Tables

Table 1 – Related Profiles ............................................................................................................................. 9Table 2 – ElementLocationTagDesc Values ............................................................................................... 12Table 3 – LocationInfoDesc defined tags .................................................................................................... 13Table 4 – CIM Elements – HP Profile Registration Profile .......................................................................... 19Table 5 – Class: HP_Location .................................................................................................................... 20Table 6 – Class: HP_ElementLocation ....................................................................................................... 20Table 7 – Durable Names generated by this Profile ................................................................................... 20Table 8 – Correlatable IDs generated by this Profile .................................................................................. 20

Version 1.2.0 5

Foreword

The HP Location Profile (P00124) was prepared by the HP WBEM TC.

6 Version 1.2.0

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 the location of a managed element within its containment hierarchy. 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.

Version 1.2.0 7

1 Scope The HP Location profile extends the management capability of referencing profiles by adding the capability to represent the Location of a managed element.















http://isotc.iso.org/livelink/livelink.exe?func=ll&objId=4230456&objAction=browse&sort=subtype�

http://www.omg.org/technology/documents/modeling_spec_catalog.htm#UML�

8 Version 1.2.0











None.

5 Synopsis Profile Name: HP Location Profile

Version: 1.1.0



Version 1.2.0 9

Extends: N/A



None

6 Description

CIM_Location

HP_Location

ElementLocationTagDescElementLocationTagLocationInformationLocationInfoDesc

CIM_ManagedElement

HP_ElementLocation

CIM_ElementLocation

Figure 1 – Location Class Diagram

Figure 1 shows the class diagram for the Location Profile. Providers associate an instance of HP_Location to any managed element that they want to report location information for using the HP_ElementLocation association.

HP_Location provides a mechanism for providers to supply 2 separate but related bits of information about the location of a managed element. The first is the ability to supply a well defined element tag that is used to identify the location of the instance of the element inside its containment. This is supported by the ElementLocationTag/ElementLocationTagDesc property pair. Secondly, HP_Location provides the ability to fully describe the location path of the containment hierarchy of the managed element associated with HP_Location. This is supported by the LocationInformation/LocationInfoDesc property pair.

Note that this profile does not reference any other profiles nor does any other profile reference this profile. Profile elements defined in this profile are intended to be optionally used by any managed element defined within another profile to report location information and/or the location information of its containment. Furthermore, this profile has no requirement to be registered in the interop namespace using profile registration defined in P00100 and DSP1033 (see section 2.1)

10 Version 1.2.0


7.1 HP_Location HP_Location adds 4 properties to more deterministically describe and report the location of the managed elements.

7.1.1 Name (mandatory)

The name property is defined as a key and should be implemented as an opaque value used to differentiate between instances unless another profile places restrictions on its use.

7.1.2 PhysicalPosition (mandatory)

The PhysicalPosition property is defined as a key and should be implemented as an opaque value used to differentiate between instances unless another profile places restrictions on its use.

7.1.3 ElementLocationTagDesc (mandatory)

ElementLocationTagDesc shall contain one of the enumerated values contained in Table 2. These values describe the semantic meaning of the value in the ElementLocationTag property. The combination of ElementLocationTagDesc and ElementLocationTag provide a location tag for the managed element associated to an instance of HP_Location.

ElementLocationTagDesc defined tag values

Description of contents of ElementLocationTag

Example of ElementLocationTag Contents

Hood Tag The Hood tag or silk screen ID that identifies this managed element to the user. Several systems shipped by HP contain a diagram on the physical hood that contains IDs identifying the location of all replaceable items in the system.

“Fan 1”

Slot This tag shall be used to identify the actual slot. This would typically be the case when HP_Location is associated with an instance of CIM_Slot or one of its sub-classes. Typically clients would have to query the slot type from the instance of CIM_Slot (or subclass) to determine what type of slot the tag is referring to.

“4”

Socket This tag is used to identify a socket. “7”

Chassis This tag is used to identify the actual chassis a managed element represents.

“3”

Cell This tag is used to identify a cell. “A”

Cabinet This tag is used to identify a cabinet. “6”

Version 1.2.0 11

Backplane This tag is used to identify a backplane. “5”

Card Cage This tag is used to identify a card cage. “CellCage”

Memory Module This tag is used to identify a memory module.

“1”

Memory Board This tag is used to identify a memory board.

“3”

Fan This tag is used to identify a fan. “12”

Power Supply This tag is used to identify a power supply.

“1”

Sensor This tag is used to identify a sensor. “15”

Processor This tag is used to identify a processor. “4”

Processor Module This tag is used to identify a processor module.

“5”

PCI Bus:Device:Function This is the PCI Bus, Device, and function of concatenated with ‘:’ (ie PCIBus:PCIDevice:PCIFunction)

“1:3:1”

SBA This tag is used to identify the System Bus Adapter (SBA) which provides a bridge between the System Bus (connects processors and memory) and the Local Bus Adapter (LBA).

“1”

LBA This tag is used to identify the Logical Bus Adapter which bridges between the System Bus Adapter (SBA) and the Host Bus Adapter bus, i.e.: PCI.

“1”

Port This tag is used to identify a Port on a managed element.

“1E”

Box This tag is used to identify a Box. “1”

Bay This tag is used to identify a Bay. “7”

SCSI ID This tag is used to identify the SCSI ID of a managed element

“0”

Drive Cage This tag is used to identify a drive cage. “4”

Adapter This tag is used to identify an adapter “1”

Blade This tag is used to identify a blade “2”

Server Node This tag is used to identify a server node in a multi-server chassis

“3”

12 Version 1.2.0

Table 2 – ElementLocationTagDesc Values

7.1.4 ElementLocationTag (mandatory)

ElementLocationTag shall contain a value corresponding semantically to the descriptive enumeration placed into ElementLocationTagDesc.

7.1.5 LocationInfoDesc (optional)

LocationInfoDesc shall contain a value defined in Table 3. LocationInfoDesc is defined to be of type uint16 and includes values/valuemap qualifiers to enumerate the type of information being described in LocationInformation’s corresponding array location. Table 3 defines the enumerations defined for LocationInfoDesc and the intent or contents of the corresponding LocationInformation array location.

The combination of LocationInfoDesc and LocationInformation arrays is intended to give provider writers the ability to report the full location path of the containment hierarchy for a particular managed element in one instance of HP_Location (see use cases - section 9 ).

This property is optional because some provider sets build out instances of the hierarchy and wouldn’t need to report the containment using this property pair.

The order of the values in the array is important because they imply containment. Each value/tag pair in an array index is implied to be contained within the value/tag being described in the next higher index array elements (see section 7.1.6).

LocationInfoDesc defined tag value Description of contents of LocationInformation

Example of LocationInformation Contents

Slot This tag shall be used to describe the Slot number that a managed element is plugged into.

“2”

Mezzanine Slot This tag shall be used to describe the mezzanine slot a managed element is contained in.

“4”

Interconnect Bay This tag shall be used to describe the interconnect bay a managed element is contained in.

“2”

PCI Slot This tag shall be used to describe the PCI/PCI-X/PCIe slot a managed element is contained in.

“1”

Socket This tag is used to identify a managed element plugged into a socket. The value represents the socket the managed element is plugged into.

“2”

Memory Board This tag identifies the memory board that the managed element is contained within. For example, if the managed element is a slot or connector it could use this tag to identify that the slot is contained on a memory board. If the element is a memory module, this tag

“2”

Version 1.2.0 13

would indicate which memory board the module is contained within without regard to slot.

Chassis This tag is used to identify the chassis a managed element is plugged into or contained within.

“5”

Cabinet This tag is used to identify the cabinet a managed element is contained within.

“4”

Card Cage This tag is used to identify the card cage a managed element is contained within.

“CellCage”

Backplane This tag is used to identify the Backplane a managed element is contained within.

“4”

Cell This tag is used to identify the Cell a managed element is contained within.

“A”

SBA This tag is used to identify the System Bus Adapter (SBA) which provides a bridge between the System Bus (connects processors and memory) and the Local Bus Adapter (LBA).

“1”

LBA This tag is used to identify the Logical Bus Adapter which bridges between the System Bus Adapter (SBA) and the Host Bus Adapter bus, i.e.: PCI.

“1”

Port This tag is used to identify the port a managed element is plugged or contained in.

“5”

Blade Bay This tag is used to identify the blade bay number a managed element is plugged or contained in.

“2”

Server Node Bay This tag is used to identify the server node bay number a managed element is plugged or contained in.

“3”

Table 3 – LocationInfoDesc defined tags

7.1.6 LocationInformation (Optional)

LocationInformation is defined as a string array that shall contain the string values for the location of the managed element’s containment hierarchy path. The corresponding array value in LocationInfoDesc contains a tag that describes the semantics of the value contained in a particular LocationInformation array location. When LocationInformation contains multiple values in multiple array locations, a particular array location indexed value implies that is contained within the value in the next higher indexed array element. For example, given an instance of HP_Location that has the following LocationInformation/LocationInfoDesc values:

14 Version 1.2.0

Array Index LocationInfoDesc LocationInformation

0 Slot “1”

1 Chassis “2”

The CIM_ManagedElement that is associated with this instance of HP_Location would be contained in slot 1 because array element 0 always applies to the CIM_ManagedElement associated with HP_Location and described by the ElementLocationTag/ElementLocationTagDesc properties. For example if these properties contained the values “1:3:1”/’PCI Bus:Device:Function’, the client could assume the device a slot are PCI. Furthermore, from array element 1 you can determine that this PCI slot number 1 is contained inside chassis number 2 from the combination of values “Chassis”/”2”. A more complex example follows:

Array Index LocationInfoDesc LocationInformation

0 Slot “1”

1 Chassis “3”

3 Slot “2”

4 Chassis “2”

From this information clients can determine that the CIM_ManagedElement associated directly with HP_Location is contained in slot number 1. This slot number 1 is contained Chassis Number 3. Chassis Number 3 is contained in Slot number 2 (a chassis slot in this case). Chassis slot 2 is contained in Chassis Number 2. This describes a very hypothetical computer that has a chassis that contains chassis slots. One of the slots contains a chassis with PCI slots and one of those slots contains a CIM_ManagedElement.

This property is optional because some provider sets build out instances of the physical hierarchy and wouldn’t need to report the containment using this property pair.

7.1.7 ElementName (mandatory)

The ElementName property is defined as a user displayable name of the object, when Name is used as a key. This property shall contain the name of the object and its location, in a user displayable format, using the information in the Location class. See the examples in section 2.

7.1.8 Description (optional)

The Description property is defined as a detailed description of the object. If this property is implemented, it shall contain the name of the object and its full location, in a user displayable format, using the information in the Location class. See the examples in section 2.

8 Methods None Defined

Version 1.2.0 15

9 Use Cases

9.1 Identifying the Location of a Managed Element

Clients can use the following algorithm to discover the location of a managed element within its contained system.

Pre-conditions:

Client has an instance of CIM_ManagedElement (element1) that they want to identify a location for. The client has determined that element1 is a component of a managed system instance of HP_ComputerSystem (system1) by verifying it is associated to system1 via an instance of CIM_SystemComponent or one of its defined sub-classes. System1 has an associated chassis instance of HP_ComputerSystemChassis (chassis1) that is associated with system1 via an instance of HP_ComputerSystemPackage. Chassis1 is the base or root of the containment hierarchy because every managed element associate with chassis1 is contained within chassis1.

Location Algorithm:

1. If element1 has an instance of HP_Location associated to it via an instance of HP_ElementLocation, and if LocationInformation and LocationInfoDesc arrays have values, save off array element members in order to locinfolist1 and locdesclist1 respectively. Save ElementLocationTagDesc and ElementLocationTag into loctagdesc1 and loctag1 respectively.

2. If element1 is associated with an instance of PhysicalElement via a CIM_Realizes or CIM_SystemPackaging, traverse association and obtain the instance of CIM_PhysicalElement (physicalelement1).

a. For each PhysicalElement (starting with physicalelement1)

i. If PhysicalElement has an instance of HP_Location associated to it via an instance of HP_ElementLocation, and if LocationInformation and LocationInfoDesc arrays have values, append the array element members in order to locinfolist1 and locdesclist1 respectively. Append ElementLocationTagDesc and ElementLocationTag to loctagdesc1 and loctag1 respectively.

ii. If the CIM_PhysicalElement has an associate CIM_PhysicalElement via the associations CIM_Container or CIM_ElementInConnector obtain the associated instance (physicalelement2).

1. If physicalelement2 is the same instance as chassis1 then stop

2. Go to step 2-a using physicalelement2.

iii. Else if there is no associated CIM_PhysicalElement then stop. 3. Else Stop

Result:

The client has obtained a list of LocationInformation (locinfolist1) and associated list of LocationInfoDesc (locdesclist1) describing the containment hierarchy. The client has also collected a set of element tags (loctagdesc1 and loctag1) for elements in the containment hierarchy.

There are 2 general cases to consider. One case is when a set of providers fully model and instantiate the full physical containment hierarchy. In this case, the provider will primarily use the ElementLocationTagDesc and ElementLocationTag to identify each element in the physical containment hierarchy.

16 Version 1.2.0

The second case is when the providers do not fully instantiate or implement the physical containment hierarchy, but still need to report the location of a managed element within it. This requires augmenting the ElementLocationTagDesc/ElementLocationTag properties with the LocationInformationDesc/LocationInformation property arrays.

The following object diagrams show instances of each and how both cases can be supported by a single set of providers in the same implementation namespace.

9.2 Object Diagrams

Figure 2 shows an instance of a system where the main chassis (chassis1) contains another chassis (chassis2) directly, no slot has been modeled between the two. Chassis2 contains 2 slots capable of holding another type of chassis, one of which has a chassis (chassis3) plugged into it. Chassis3 contains 1 fan slot (fanslot1) which contains a single fan module (fm1). Fm1 is associated with its logical side via a CIM_Realizes association to a logical fan (fan3). Fan3 is a system device of the contained computer system (system1).

This instance diagram shows an instance of an implementation that has fully instantiated the containment hierarchy of the system. To this end, the providers utilize ElementLocationTagDesc and ElementLocationTag to identify the location of each element in the hierarchy. All physical components are modeled and supported and the containment of each component is explicitly instantiated. For example, you can see explicitly that fan module fm1 is contained in slot fanslot1 and that chassis chassis3 is contained in chassis slot chslt2. In this case, HP_Location is used to tag each physical component to communicate to clients the label of the physical element and not the location inside its contained component. The red arrow shows the path of traversal and client would follow when following the algorithm defined in section 9.1. At the end of implementing this algorithm the client should have 2 corresponding lists:

Index ElementLocationTag ElementLocationTagDesc

0 “3” Fan

1 “1” Slot

2 “3” Chassis

3 “2” Slot

4 “2” Chassis

Clients can use this information along with the semantics of the tags defined in ElementLocationTag as well as the associations between each CIM_PhysicalElement to report the following string to the user has the location for the instance of HP_Fan:

“Fan 3 is plugged into Slot 1 which is contained in Chassis 3 which is plugged into Slot 2 which is contained in Chassis 2 which is contained in the Main System chassis.”

Version 1.2.0 17


HP_ComputerSystemPackagechassis1 :


fan3:HP_Fan

CIM_SystemDevice

chassis2:CIM_Chassis

CIM_Container

loc1:HP_Location

ElementLocationTagDesc: ChassisElementLocationTag: “2”LocationInformation[0] – (not used)LocationInfoDesc[0] – (not used)

chslt1:HP_Slot

loc3:HP_Location

ElementLocationTagDesc: SlotElementLocationTag: “1”LocationInformation[0]: (not used)LocationInfoDesc[0]: (not used)

chslt2:HP_Slotloc2:HP_Location


chassis3:CIM_Chassis

loc1:HP_Location

ElementLocationTagDesc: ChassisElementLocationTag: “3”LocationInformation[0]: (not used)LocationInfoDesc[0]: (not used)

fanslot1:HP_Slot


fm1:HP_FanModule

loc1:HP_Location


CIM_Container

CIM_Realizes

CIM_Container


HP_ElementLocation

HP_ElementLocation

HP_ElementLocation

HP_ElementLocation

HP_ElementLocation

loc1:HP_Location

ElementLocationTagDesc:FanElementLocationTag:”3"LocationInformation[0] – (not used)LocationInfoDesc[0] – (not used)

HP_ElementLocation

Figure 2 – Location Full Containment Implemented

Figure 3 shows the same system but with an implementation that does not build out the physical side of containment hierarchy. In this case, the provider has associated the instance of HP_Fan with an HP_Location instance that fully describes the containment of the fan using the LocationInformation and LocationInformationDesc property arrays. From this info, the client can determine and provide the same location string as defined for the previous instance:

“Fan 3 is plugged into Slot 1 which is contained in Chassis 3 which is plugged into Slot 2 which is contained in Chassis 2 which is contained in the Main System chassis.”

This example is for illustrative purposes to show this mechanism could be used to describe complex containment. It is recommended that systems with complex containment relationships such as those shown in Figure 2 build out the physical side of the model.

18 Version 1.2.0




fan3:HP_Fan

CIM_SystemDevice

loc1:HP_Location

ElementLocationTagDesc:FanElementLocationTag:”3"LocationInformation[0] – “1"LocationInfoDesc[0] – SlotLocationInformation[1] – “3”LocationInfoDesc[1] – ChassisLocationInformation[2] – “2"LocationInfoDesc[2] – SlotLocationInformation[3] – “2”LocationInfoDesc[3] – Chassis

HP_ElementLocation

Figure 3 – Location without physical side of model

A typical implementation of a set of providers that either does not or only partially builds out the physical model is shown in Figure 4. The system contains 2 memory modules, 1 fan, and 1 PCI controller. From the instances of HP_Location, the client can create the following location strings from the information provided by the model instance (note: for illustrative purpose only):

• Fan 1 has a Hood Tag ID of “Fan 1”

• Memory Module 1 is contained in Socket 1

• Memory Module 2 is contained in Socket 2

• Port1 has PCI Bus:Device:Function of 1:3:1 is contained in Slot 5

Version 1.2.0 19




fan3:HP_Fan

loc1:HP_Location

ElementLocationTagDesc:Hood TagElementLocationTag:”Fan 1"LocationInformation[0] – (not used)LocationInfoDesc[0] – (not used)

mem1:HP_Memory

HP_ElementLocation

mm1:HP_MemoryModule

mm2:HP_MemoryModule

loc1:HP_Location

ElementLocationTagDesc:Memory ModuleElementLocationTag:”1"LocationInformation[0] – “1”LocationInfoDesc[0] – Socket

loc2:HP_Location

ElementLocationTagDesc:Memory ModuleElementLocationTag:”2"LocationInformation[0] – “2”LocationInfoDesc[0] – Socket


HP_ElementLocation

HP_ElementLocation

dev1:CIM_PCIDevice

loc3:HP_Location

ElementLocationTagDesc:PCI Bus:Device:FunctionElementLocationTag:”1:3:1"LocationInformation[0] – “5”LocationInfoDesc[0] – Slot

HP_ElementLocation

port1:CIM_LogicalPort

CIM_SystemDevice

CIM_PortOnDevice

Figure 4 – Typical Location Implementation




Classes HP_Location Mandatory (see section 7.1 and 10.1)

HP_ElementLocation Mandatory (see section 10.2) Indications

None defined.

10.1 HP_Location

The HP_Location is used to model a location for a managed element. Table 4 shows the properties that shall be implemented for the HP_Location class.

20 Version 1.2.0

Table 5 – Class: HP_Location


Name Mandatory Key (see section 7.1.1)

PhysicalPosition Mandatory Key (see section 7.1.2)

ElementLocationTagDesc Mandatory (see section 7.1.3)

ElementLocationTag Mandatory (see section 7.1.4)

LocationInformation Optional (see section 7.1.6)

LocationInfoDesc Optional (see section 7.1.5)

ElementName Mandatory (see section 7.1.7)

Description Optional (see section 7.1.8)

10.2 HP_ElementLocation HP_ElementLocation extends the class CIM_ElementLocation in ways that are specific to HP systems. This class shall associate managed elements to an instances of HP_Location.

Table 6 – Class: HP_ElementLocation


Element Mandatory REF: CIM_ManagedElement

PhysicalLocation Mandatory REF: HP_Location




None Defined




None Defined

Version 1.2.0 21

ANNEX A (normative)

Change Log



.002 8/24/06 Incorporate feedback from 8/23 WBEM TC review.

.003 6/4/07 Added Blade specific enumerations.

1.1.0 9/11/08

Updated the following: Section 7, added detail on the contents of Location ElementName and

Description properties Section 10, added Location ElementName and Description properties to

Location class table. 1.2.0 3/25/09 Added multi-server chassis enumerations

22 Version 1.2.0


Acknowledgments

Version 1.2.0 23



CR

Number Date Title

CR00143 9/11/08 Detailed string properties Minor

update 3/25/09 Added multi-server chassis enumerations

24 Version 1.2.0

Bibliography


Version 2.1.0 1


Date: 4/8/09

Version: 2.1.0

HP Blade System Lite Profile



2 Version 2.1.0


Version 2.1.0 3

Contents



3 Terms and Definitions .................................................................................................................... 7 4 Symbols and Abbreviated Terms .................................................................................................. 8 5 Synopsis ........................................................................................................................................ 9 6 Description ................................................................................................................................... 10 7 Implementation Requirements ..................................................................................................... 11

7.1 HP_ComputerSystem (Blade/Server Node) ................................................................................ 11 7.2 CIM_ComputerSystem (Blade) .................................................................................................... 11 7.3 HP_ComputerSystem (vPartition/nPartition/Virtual System) (Optional) ...................................... 12 7.4 HP_BladeEnclosureCS (Enclosure Manager/Multi-Node Server Chassis Computer

System Instance) .............................................................................................................................. 12 7.4.1 HP_BladeEnclosureCS.Dedicated ...................................................................................... 12 7.4.2 HP_BladeEnclosureCS.OtherDedicatedDescriptions ......................................................... 12 7.4.3 HP_BladeEnclosureCS.Caption .......................................................................................... 12 7.4.4 HP_BladeEnclosureCS.Description ..................................................................................... 12 7.4.5 HP_BladeEnclosureCS.ElementName ................................................................................ 12 7.4.6 HP_BladeEnclosureCS.SerialNumber................................................................................. 12 7.4.7 HP_BladeEnclosureCS.ProductID ....................................................................................... 12 7.4.8 HP_BladeEnclosureCS.OperationalStatus .......................................................................... 13 7.4.9 HP_BladeEnclosureCS.ManagementIPAddress ................................................................. 13 7.4.10 HP_BladeEnclosureCS.ManagementURL ......................................................................... 13 7.4.11 HP_BladeEnclosureCS.ManagementMACAddress (Optional) .......................................... 13 7.4.12 HP_BladeEnclosureCS.RackName .................................................................................... 13 7.4.13 HP_BladeEnclosureCS.RackUID ....................................................................................... 13 7.4.14 HP_BladeEnclosureCS.EnclosureName ............................................................................ 13

7.5 HP_BladeEnclosureCollection ..................................................................................................... 13 7.6 HP_BladeEnclosureGroupHostedCollection ............................................................................... 13 7.7 HP_MemberOfBladeEnclosureCollection.................................................................................... 14 7.8 HP_BladeSystemComponent ...................................................................................................... 14 7.9 HP_BladeCSLocation .................................................................................................................. 14

7.9.1 HP_BladeCSLocation.ElementLocationTagDesc ................................................................ 14 7.9.2 HP_BladeCSLocation.ElementLocationTag ........................................................................ 14 7.9.3 HP_BladeCSLocation.LocationInfoDesc ............................................................................. 14 7.9.4 HP_BladeCSLocation.LocationInformation ......................................................................... 14

7.10 HP_BladeCSElementLocation ..................................................................................................... 14 8 Methods ....................................................................................................................................... 15

8.1 Profile Conventions for Operations .............................................................................................. 15 8.2 HP_ComputerSystem .................................................................................................................. 15 8.3 HP_BladeEnclosureCS ............................................................................................................... 15 8.4 HP_EnabledElementCapabilities ................................................................................................. 15 8.5 HP_BladeEnclosureCollection ..................................................................................................... 15 8.6 HP_BladeEnclosureGroupHostedCollection ............................................................................... 15 8.7 HP_MemberOfBladeEnclosureCollection.................................................................................... 15 8.8 HP_BladeSystemComponent ...................................................................................................... 15 8.9 HP_BladeCSLocation .................................................................................................................. 15 8.10 HP_BladeCSElementLocation ..................................................................................................... 16

9 Use Cases ................................................................................................................................... 16 9.1 Object Diagrams .......................................................................................................................... 16

4 Version 2.1.0

9.2 Determine if Server is a Blade ..................................................................................................... 19 9.3 Determine if Server is a Node ..................................................................................................... 20 9.4 Determine Blade or Node Location ............................................................................................. 20

10 CIM Elements .............................................................................................................................. 20 10.1 HP_ComputerSystem .................................................................................................................. 20 10.2 HP_BladeEnclosureCS ............................................................................................................... 20 10.3 HP_BladeSystemComponent ...................................................................................................... 21 10.4 HP_RegisteredProfile .................................................................................................................. 21 10.5 HP_BladeEnclosureCollection ..................................................................................................... 22 10.6 HP_BladeEnclosureGroupHostedCollection ............................................................................... 22 10.7 HP_MemberOfBladeEnclosureCollection.................................................................................... 22 10.8 HP_BladeCSLocation .................................................................................................................. 22 10.9 HP_BladeCSElementLocation ..................................................................................................... 23 10.10 CIM_HostedDependency ............................................................................................................ 23 10.11 CIM_SoftwareIdentity .................................................................................................................. 23


Figures

Figure 1 – Blade System Lite Profile: Class Diagram ......................................................................................... 10 Figure 2 – Blade System Lite Profile: Class Diagram ......................................................................................... 10 Figure 3 – Blade System Lite Profile: Inheritance Hierarchy .............................................................................. 11 Figure 4 – Blade System Lite Profile: Object Diagram for system with single blade .......................................... 16 Figure 5 - Blade System Lite Profile: Object diagram for system with single blade ........................................... 17 Figure 6 – Blade System Lite Profile Object Diagram for system with multiple enclosures ............................... 18 Figure 7 - Blade System Lite Profile: Object diagram for multi-system chassis with single server node ........... 19

Tables

Table 1 – Related Profiles ..................................................................................................................................... 9 Table 2 – CIM Elements – HP Blade System Lite Profile ................................................................................... 20 Table 3 – Class – HP_BladeEnclosureCS .......................................................................................................... 21 Table 4 – Class – HP_SystemComponent ......................................................................................................... 21 Table 5 – Class – HP_RegisteredProfile ............................................................................................................ 22 Table 6 – Class – HP_BladeEnclosureGroupHostedCollection ......................................................................... 22 Table 7 – Class – HP_MemberOfBladeCollection .............................................................................................. 22 Table 8 – Class – HP_BladeCSLocation ............................................................................................................ 23 Table 9 – Class – HP_BladeCSElementLocation ............................................................................................... 23 Table 10 – Class properties: CIM_HostedDependency ...................................................................................... 23 Table 11 – Class properties: CIM_SoftwareIdentity ........................................................................................... 24 Table 12 – Durable Names generated by this Profile ......................................................................................... 24 Table 13 – Correlatable IDs generated by this Profile ........................................................................................ 24

Version 2.1.0 5

Foreword

The HP Blade System Lite Profile P00125 was prepared by the HP WBEM TC.

6 Version 2.1.0

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 Blade Server systems and their Enclosures. 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.

Version 2.1.0 7

1 Scope The HP Blade System Lite profile extends the management capability of referencing profiles by adding the capability to represent the DMTF Modular System Profile in HP specific ways. While this profile is based on the DMTF Modular System Profile; it will not conform to that profile.

This is intended to be supported only by the blades within an enclosure as a means for tying the blade to an enclosure. This profile is not intended to be implemented by the enclosure (via the Onboard Administrator). The Onboard Administrator shall manage the shared enclosure resources.






DMTF DSP1008, Modular System Profile

DMTF DSP1023, Software Inventory Profile


HP WBEM TC P00124, HP Location Profile









8 Version 2.1.0













None.

Version 2.1.0 9

5 Synopsis Profile Name: HP Blade System Lite Profile

Version: 2.1.0



Central Class: HP_BladeEnclosureCS


Based on: DMTF DSP1008, Modular System Profile 1.0.0

The HP Blade System Lite Profile is based on DMTF DSP1008 to add c-class blade server characteristics that are specific to HP systems. Since the full support of DSP1008 is not planned, we do not claim support of DSP1008.




10 Version 2.1.0

6 Description

HP_BladeEnclosureCS

Dedicated: 2 (Other)OtherDedicatedDescriptions: “Modular” for c-class; “Mult-node” for SL systems




profile)


HP_ComputerSystem (blade or node)

Dedicated:0 (Not Dedicated) (see HP Base Server Profile)

HP_BladeEnclosureCollection

GroupOperationalStatus: (See HP Consolidated Status Profile)

HP_MemberOfBladeEnclosureCollection

HP_BladeEnclosureGroupHostedCollection

11

0..1 1

*

1

1HP_BladeCSLocation

(see HP Location Profile)Reference Blade bay or Server Node

HP_BladeCSElementLocation

1

1


(see DMTF DSP 1023 Software Inventory Profile)

1

*

CIM_ElementSoftwareIdentity1

1CIM_InstalledSoftwareIdentity

0..1

Figure 1 – Blade System Lite Profile: Class Diagram

HP_BladeEnclosureCS

Dedicated: 2 (Other)OtherDedicatedDescriptions: Modular




profile)


CIM_ComputerSystem (blade)

Dedicated: 0 (Not Dedicated)HP_BladeEnclosureCollection

GroupOperationalStatus: (See HP Consolidated Status Profile)


HP_BladeEnclosureGroupHostedCollection 1

0..11

0..* 1

*

1

1HP_BladeCSLocation

(see HP Location Profile)


1

1


(see DMTF DSP 1023 Software Inventory Profile)

1

*

CIM_ElementSoftwareIdentity1

1CIM_InstalledSoftwareIdentity

HP_ComputerSystem (partition)

Dedicated: 32568 (nPartition)(see HP Base Server Profile)

*1


Figure 2 – Blade System Lite Profile: Class Diagram

Version 2.1.0 11






HP_BladeEnclosureGroupHostedCollectionHP_BladeEnclosureCollection



HP_BladeEnclosureCS

CIM_ComputerSystem


CIM_SystemComponent

HP_BladeCSLocation

HP_Location

see HP Location profile


HP_ElementLocation

see HP Location profile

Figure 3 – Blade System Lite Profile: Inheritance Hierarchy

The HP Blade System Lite profile is loosely based on the DMTF Modular System profile defined in DSP1008 to add the HP capabilities tying the blade computer system to the external chassis manager computer system. The intent is to model the view of the blade and enclosure from the top level computer system from the HP Base Server profile, meaning the blades and enclosures that are used by the computer system.

Figures 1 and 2 show the class diagrams for the HP Blade System Lite profile.

Figure 2 shows the inheritance of the blade classes.


7.1 HP_ComputerSystem (Blade/Server Node)

This section shall apply when representing non-partitionable, single bladed computer systems. The blade/server node computer system instance shall follow the HP Base Server profile as defined in the HP Base Server Profile. No additional properties are needed. This represents the top-level computer system instance. This instance shall be instantiated if the HP_ComputerSystem (vPartition/nPartition/Virtual System) is not instantiated. The property “Dedicated” will have a value of zero (not dedicated).

7.2 CIM_ComputerSystem (Blade)

This section shall apply when modeling partitionable, or multi-bladed computer systems. The blade/server node computer system instance shall be instantiated if the HP_ComputerSystem (vPartition/nPartition/VirtualSystem) is instantiated. The property “Dedicated” will have a value of zero (not dedicated).

12 Version 2.1.0

7.3 HP_ComputerSystem (vPartition/nPartition/Virtual System) (Optional)

This section shall apply when modeling partitionable or multi-bladed computer systems.

The partition running on the bladed computer system shall follow the HP_Base Server Profile. No additional properties are required. The property “Dedicated” will use a vendor specific value (32568 to 32570) to indicate a vPartition, nPartition, or Virtual System. This represents the top-level computer system instance. To determine the blades that are used to form this computer system, the CIM_HostedDependency association must be traversed to get the CIM_ComputerSystem instances representing each of the blades.

Use of the HP_ComputerSystem instance to represent the partition instance is optional if the system is not partitionable (or not partitioned) or uses a single bladed computer system. In such cases, a single HP_ComputerSystem (Blade/Server Node) instance shall represent the blade and also be the top level computer system instance.

7.4 HP_BladeEnclosureCS (Enclosure Manager/Multi-Node Server Chassis Computer System Instance)


7.4.1 HP_BladeEnclosureCS.Dedicated

This property shall be supported by providing setting the value to 0 (Other).

7.4.2 HP_BladeEnclosureCS.OtherDedicatedDescriptions

This property shall be supported by providing setting the value to either “Modular” for blade systems or “Multi-node” for multi-node server systems.

7.4.3 HP_BladeEnclosureCS.Caption

This property shall be supported by providing a short string describing the modular system enclosure or multi-node system chassis.

7.4.4 HP_BladeEnclosureCS.Description

This property shall be supported by providing a string describing the modular system enclosure or multi-node system chassis.

7.4.5 HP_BladeEnclosureCS.ElementName

This property shall be supported by providing a human readable string (suitable for a UI) describing the modular system enclosure or multi-node system chassis. This should be the enclosure DNS name if available.

7.4.6 HP_BladeEnclosureCS.SerialNumber

This property shall be supported by providing a string indicating the modular system enclosure or multi-node system chassis serial number.

7.4.7 HP_BladeEnclosureCS.ProductID

This property shall be conditionally supported by providing a string indicating the modular system enclosure or multi-node system chassis product id provided this information is available to the blade system or server node.

Version 2.1.0 13

7.4.8 HP_BladeEnclosureCS.OperationalStatus

This property shall be supported by the operational status of the shared enclosure sub-systems. Multi-node server chassis may populate this value with “unknown” if the multi-node server chassis does not report status for the chassis or shared resources.

7.4.9 HP_BladeEnclosureCS.ManagementIPAddress

This property shall be supported by the populating the string representation of the enclosure’s currently active management IP Address. Multi-node server chassis may populate this value with NULL or an empty string if the multi-node server chassis does not report this information.

7.4.10 HP_BladeEnclosureCS.ManagementURL

This property shall be supported by the populating the string representation of the enclosure’s currently active management home page URL. Multi-node server chassis may populate this value with NULL or an empty string if the multi-node server chassis does not report this information.

7.4.11 HP_BladeEnclosureCS.ManagementMACAddress (Optional)

This property may be supported by providing the string representation of the Onboard Administrator’s (Enclosure Manager) currently active MAC Address. . Multi-node server chassis may populate this value with NULL or an empty string if the multi-node server chassis does not report this information.

7.4.12 HP_BladeEnclosureCS.RackName

This property may be supported by populating the string representation the name of the rack containing the enclosure. . Multi-node server chassis may populate this value with NULL or an empty string if the multi-node server chassis does not report this information.

7.4.13 HP_BladeEnclosureCS.RackUID

This property may be supported by populating the string representation of the Rack UID. . Multi-node server chassis may populate this value with NULL or an empty string if the multi-node server chassis does not report this information.

7.4.14 HP_BladeEnclosureCS.EnclosureName

This property may be supported by populating the name of the Enclosure. . Multi-node server chassis may populate this value with NULL or an empty string if the multi-node server chassis does not report this information.

7.5 HP_BladeEnclosureCollection

The blade enclosure collection instance shall follow the HP Consolidated Status profile as defined in the section describing the HP_GroupSystemSpecificCollection class.

The algorithm used by the collection class is worst case.

Multi-node server chassis that do not report status SHALL NOT populate this class.

7.6 HP_BladeEnclosureGroupHostedCollection

The blade enclosure group hosted collection instance shall follow the HP Consolidated Status profile as defined in the section describing the HP_GroupHostedCollection class.


14 Version 2.1.0

7.7 HP_MemberOfBladeEnclosureCollection

The member of blade enclosure collection instance shall follow the HP Consolidated Status profile as defined in the section describing the HP_MemberOfCollection class.


7.8 HP_BladeSystemComponent

The blade system component aggregation association will aggregate the blade/server node computer system instances with the enclosure/multi-system chassis computer system instance.

7.9 HP_BladeCSLocation

The blade computer system location instance shall follow the HP Location profile as defined in the HP Location Profile. No additional properties are needed.

7.9.1 HP_BladeCSLocation.ElementLocationTagDesc

This property SHALL BE supported for blade systems by providing the description of the element location with the value of Blade(24).

This property SHALL BE supported for multi-node systems by providing the description of the element location with the value of Server Node(25).

7.9.2 HP_BladeCSLocation.ElementLocationTag

This property shall be supported by providing a string indicating the modular system enclosure blade name or multi-node server chassis name.

7.9.3 HP_BladeCSLocation.LocationInfoDesc

This property SHALL BE supported for blade systems by providing an enumerated array with a single element having the enumerated value Blade Bay(14).

This property SHALL BE supported for multi-node systems by providing an enumerated array with a single element having the enumerated value Server Node Bay(15).

7.9.4 HP_BladeCSLocation.LocationInformation

This property shall be supported by providing a string array with a single element having the string representation of the Blade Bay number or Server Node Bay.

7.10 HP_BladeCSElementLocation

The blade computer system / multi-node server system element location instance shall follow the HP Location profile as defined in the HP Location Profile. No additional properties are needed.

Version 2.1.0 15

8 Methods




• GetInstance

• Associators

• AssociatorNames

• References

• ReferenceNames






8.3 HP_BladeEnclosureCS


8.4 HP_EnabledElementCapabilities


8.5 HP_BladeEnclosureCollection


8.6 HP_BladeEnclosureGroupHostedCollection


8.7 HP_MemberOfBladeEnclosureCollection


8.8 HP_BladeSystemComponent


8.9 HP_BladeCSLocation


16 Version 2.1.0

8.10 HP_BladeCSElementLocation


9 Use Cases

9.1 Object Diagrams

encl1: HP_BladeEnclosureCS


RegisteredName: HP Blade System Lite

blade1:CIM_ComputerSystem (blade)

Dedicated:0 (Not Dedicated)



bcoll1:HP_BladeEnclosureCollectionBladeEnclosureGroupHostedCollection

MemberOfBladeEnclosureCollection

loc1: HP_BladeCSLocation

ElementLocationTagDesc: Blade(24)ElementLocationTag: “blade1”LocationInfoDesc: Blade Bay(14)LocationInformation: “2”




CIM_InstalledSoftwareIdentity

system1: HP_ComputerSystem (partition)

Dedicated:32568 (nPartition) CIM_HostedDependency

Figure 4 – Blade System Lite Profile: Object Diagram for system with single blade

The above picture shows an instance of CIM_ComputerSystem for the Blade System Enclosure indicated by “encl1”. The blade system instance of the CIM_ComputerSystem is indicated by “blade1”. The top-level Computer System instance of the HP_ComputerSystem is indicated by “system1”.The enclosure instance is associated to the blade instance via the SystemComponent association. The HP_BladeCSLocation instance indicated by “loc1” contains the location of the server blade within the chassis (Blade Bay 2).

Version 2.1.0 17




system1: HP_ComputerSystem (blade)



bcoll1:HP_BladeEnclosureCollectionBladeEnclosureGroupHostedCollection



ElementLocationTagDesc: Blade(24)ElementLocationTag: “blade1”LocationInfoDesc: Blade Bay(14)LocationInformation: “2”





Figure 5 - Blade System Lite Profile: Object diagram for system with single blade

The above picture shows an alternate way to show the same system as in the previous example, without modeling the partition. A single instance of HP_ComputerSystem represents the top level computer system as well as the blade on which it is running.

18 Version 2.1.0


blade1:CIM_ComputerSystem (blade)



bcoll1:HP_BladeEnclosureCollection

BladeEnclosureGroupHostedCollection


loc1: HP_BladeCSLocationElementLocationTagDesc: Blade(24)ElementLocationTag:"blade1"LocationInfoDesc: BladeBay(14)LocationInformation: "4"


Encl2: HP_BladeEnclosureCS

Loc2: HP_BladeCSLocationElementLocationTagDesc: Blade(24)ElementLocationTag:"blade2"LocationInfoDesc: BladeBay(14)LocationInformation: "3"

loc3: HP_BladeCSLocationElementLocationTagDesc: Blade(24)ElementLocationTag:"blade3"LocationInfoDesc: BladeBay(14)LocationInformation: "1"


Blade3:CIM_ComputerSystem (blade)


Blade2:CIM_ComputerSystem (blade)




system1: HP_ComputerSystem (Partition)

Dedicated:32569 (nPartition)




Figure 6 – Blade System Lite Profile Object Diagram for system with multiple enclosures

Version 2.1.0 19

The above picture shows a bladed system in which a partition spans across blades located in multiple enclosures. The top-level HP_ComputerSystem instance indicated by “system1” comprised of three blade servers. An instance of CIM_ComputerSystem with the property “Dedicated” having a value 0 (“Not Dedicated”) represents each blade that forms the partition. Two of these blades is located in the enclosure indicated by “encl1” and is present in the 3rd and 4th blade bays. Another blade is located in the enclosure indicated by “encl2” and is present in the 1st blade bay. The instances of CIM_SoftwareIdentify and CIM_RegisteredProfile are not shown in the diagram, but there will be these instances associated with each instance of HP_BladeEnclosureCS.




system1: HP_ComputerSystem (node)




ElementLocationTagDesc: Server Node(25)ElementLocationTag: “node1”LocationInfoDesc: Server Node Bay(15)LocationInformation: “2”





Figure 7 - Blade System Lite Profile: Object diagram for multi-system chassis with single server node

The above picture shows an instance of HP_ComputerSystem for the Multi-node system chassis indicated by “encl1”. The server node system instance of the HP_ComputerSystem is indicated by “node1”. The top-level Computer System instance is indicated by “system1”.The enclosure instance is associated to the blade instance via the SystemComponent association. The HP_BladeCSLocation instance indicated by “loc1” contains the location of the server node within the chassis (Server Node Bay 2). BJC – Add OtherDedicatedDescription to class.

9.2 Determine if Server is a Blade

Find the top level ComputerSystem instance as defined in the HP Base Server profile. Follow the CIM_HostedDependency associations and check if an associated ComputerSystem has the Dedicated property set to 0 (Not Dedicated). If the top level ComputerSystem has the Dedicated property set to 32568 (nPartition) or 32569 (vPartition), there will be a multiple levels of CIM_HostedDependency to follow until the ComputerSystem with a Dedicated property set to 0 (Not Dedicated) is discovered. If any such instances are present, follow the SystemComponent associations and check if an associated ComputerSystem instance has the Dedicated property set to 2 (Other) and the OtherDedicatedProperty set to “Modular”. If there are no CIM_HostedDependency associations, follow the SystemComponent associations directly from the top-level computer system and check if an associated ComputerSystem instance has the Dedicated property set to 2 (other) and the OtherDedicatedProperty set to “Modular”

20 Version 2.1.0

9.3 Determine if Server is a Node

Find the blade’s ComputerSystem instance as defined in the HP Base Server profile. Follow the CIM_HostedDependency associations and check if an associated ComputerSystem has the Dedicated property set to 0 (Not Dedicated). If any such instances are present, follow the SystemComponent associations and check if an associated ComputerSystem instance has the Dedicated property set to 2 (Other) and the OtherDedicatedProperty set to “Multi-node”. If there are no CIM_HostedDependency associations, follow the SystemComponent associations directly from the top-level computer system and check if an associated ComputerSystem instance has the Dedicated property set to 2 (other) and the OtherDedicatedProperty set to “Multi-node”

9.4 Determine Blade or Node Location

Determine is the server is a blade as in section 9.2. Follow the CIM_HostedDependency instances to find the blades that form this computer system. For each blade that forms this system, follow the HP_BladeCSElementLocation association to find the instance(s) of the HP_BladeCSLocation class containing the blade location information.

10 CIM Elements Table 2 – CIM Elements – HP Blade System Lite Profile


HP_ComputerSystem Mandatory See section 7.1 and 7.3 and 10.1 HP_BladeEnclosureCS Mandatory See section 7.4 and 10.2 HP_BladeSystemComponent Mandatory See section 10.3 HP_RegisteredProfile Mandatory See section 10.4 HP_BladeEnclosureCollection Conditional See section 10.5

HP_BladeEnclosureGroupHostedCollection Conditional See section 10.6

HP_MemberOfBladeEnclosureCollection Conditional See section 10.7

HP_BladeCSLocation Mandatory See section 7.9 and 10.8

HP_BladeCSElementLocation Mandatory See section 7.10 and 10.9

CIM_SoftwareIdentity Mandatory See section 10.11

Indications None

10.1 HP_ComputerSystem HP_ComputerSystem instance representing the partition on the blade system or the server node shall be treated as an HP Base Server ComputerSystem instance. Each blade forming the partition has associated instances of CIM_ComputerSystem with the Dedicated property set to 0 (Not Dedicated). Refer to the HP Base Server Profile for more information.

10.2 HP_BladeEnclosureCS HP_ComputerSystem instance for the blade enclosure extends the class CIM_ComputerSystem to model the status information of the enclosure and its shared resources and the necessary links to allow HP SIM and the HP Web Management Agent to provide a Web Link to the Web-based Management web page for the enclosure.

Version 2.1.0 21

HP_ComputerSystem instance for the multi-system chassis extends the class CIM_ComputerSystem to model the multi-system chassis.

Table 3 – Class – HP_BladeEnclosureCS

Properties Requirement Notes Dedicated Mandatory See section 7.4.1 OtherDedicatedDescriptions Mandatory See section 7.4.1 Caption Mandatory See section 7.4.3 Description Mandatory See section 7.4.4 ElementName Mandatory See section 7.4.5 SerialNumber Mandatory See section 7.4.6 ProductID Mandatory See section 7.4.7 OperationalStatus Mandatory See section 7.4.6 ManagementIPAddress Mandatory See section 7.4.9 ManagementURL Mandatory See section 7.4.10 ManagementMACAddress Optional See section 7.4.11 RackName Optional See section 7.4.12 RackUID Optional See section 7.4.13

10.3 HP_BladeSystemComponent HP_BladeSystemComponent extends the class CIM_SystemComponent to associate the Enclosure’s ComputerSystem instance to the blade’s ComputerSystem instance.

Table 4 – Class – HP_SystemComponent

Properties Requirement Notes GroupComponent Mandatory REF: HP_BladeEnclosureCS PartComponent Mandatory REF: CIM_ComputerSystem

(Blade/Node)



22 Version 2.1.0

Table 5 – Class – HP_RegisteredProfile



RegisteredName Mandatory “HP Blade System Lite”


10.5 HP_BladeEnclosureCollection HP_BladeEnclosureCollection extends the class HP_GroupSystemSpecificCollection to aggregate the Enclosure’s operational status. See the Consolidated Status Profile for more information.

Not populated for multi-node server chassis that do not report chassis status.

10.6 HP_BladeEnclosureGroupHostedCollection HP_BladeEnclosureGroupHostedCollection extends the class HP_GroupHostedCollection to associate the top level ComputerSystem instance to the blade collection instance.


Table 6 – Class – HP_BladeEnclosureGroupHostedCollection

Properties Requirement Notes Antecedent Mandatory REF: CIM_ComputerSystem Dependent Mandatory REF: HP_BladeEnclosureCollection

10.7 HP_MemberOfBladeEnclosureCollection HP_MemberOfBladeEnclosureCollection extends the class HP_MemberOfCollection to associate the Enclosure’s ComputerSystem instance to the blade enclosure collection instance.


Table 7 – Class – HP_MemberOfBladeCollection

Properties Requirement Notes Collection Mandatory REF: HP_BladeEnclosureCollection Member Mandatory REF: HP_BladeEnclosureCS

10.8 HP_BladeCSLocation HP_BladeCSLocation extends the class HP_Location class to provide blade bay location information. The HP_BladeCSLocation class shall be populated as defined in the HP Location Profile with the blade or node specific location information specified below.

Version 2.1.0 23

Table 8 – Class – HP_BladeCSLocation

Properties Requirement Notes ElementLocationTag Mandatory See section 7.9.2 ElementLocationTagDesc Mandatory See section 7.9.1 LocationInformation Mandatory See section 7.9.4 LocationInfoDesc Mandatory See section 7.9.3

10.9 HP_BladeCSElementLocation HP_BladeCSLocation extends the class HP_Location class to provide the chassis location and blade bay or server node bay location information.

Table 9 – Class – HP_BladeCSElementLocation

Properties Requirement Notes Element Mandatory REF: CIM_ComputerSystem PhysicalLocation Mandatory REF: HP_BladeCSLocation

10.10 CIM_HostedDependency

An instance of this class models the association between the top level computer system and the computer system instances representing the blades that form the system. Modeling of this instance itself is optional if a single blade hosts a single OS instance.

Table 10 – Class properties: CIM_HostedDependency

Properties Requirement Notes Antecedent Mandatory REF: HP_ComputerSystem (top-level) Dependent Mandatory REF: CIM_ComputerSystem (blade)

10.11 CIM_SoftwareIdentity The CIM_SoftwareIdentity class is defined by document DMTF DSP1023, Software Inventory Profile and is used to describe the enclosure firmware.

24 Version 2.1.0

Table 11 – Class properties: CIM_SoftwareIdentity

Properties Requirement Notes BuildNumber Conditional The build number of enclosure firmware (if one

exists) Classifications[] Mandatory This property shall have the value of


“HP”. MajorVersion Mandatory The major version value of the enclosure firmware MinorVersion Mandatory The minor version value of the enclosure firmware RevisionNumber Conditional The revision number of enclosure firmware (if one

exists) VersionString Mandatory A string representing the complete firmware



Class Durable Name(s) Source ID Information Circumstances for Change

HP_BladeEnclosureCS SerialNumber Serial number for the enclosure.

Enclosure system board replacement

HP_BladeEnclosureCS ProductID Product ID for the enclosure.

Enclosure system board replacement




None

Version 2.1.0 25

ANNEX A (normative)

Change Log

Version Date Description 0.7 8/28/06 Initial Draft 0.9 9/1/06 Add consolidated status support 1.0 9/18/06 General cleanup for TC submittal; added document number P00125 and CR number. 1.0 9/28/06 Updates from TC review 1.0 12/5/06 Added MAC Address property 1.0 6/5/07 Added ProductID property and blade location support.

1.0b 10/12/2007 Added Firmware version (Software Identity) support. 2.0 8/20/2008 Added support for multiple enclosures 2.0 10/20/2008 Updates from TC review 2.1 3/26/2009 Added support for multi-node server chassis 2.1 5/8/2009 Modify multiple blades and enclosures update for CIM vs HP Computer System.

26 Version 2.1.0


Acknowledgments

Version 2.1.0 27



CR

Number Date Title CR00114 9/13/2006 Create HP Profiles for the Blade System Lite model. CR00116 11/15/2006 Add OBA Mac Address property to HP_BladeEnclosureCS CR00123 6/5/2007 Add blade location classes; added product id. CR00126 10/12/2007 Add Firmware version (DSP 1023) support. CR00142 8/20/2008 Changes to support multiple enclosures

CR00145 3/26/2009 Changes to support support for multi-node server chassis, fix multiple blade/enclosure addition

28 Version 2.1.0

Bibliography


Version 2.0.0 HP Software Inventory and Update Profile 1


Date: 1/14/2011

Version: 2.0.0

HP Software Inventory and Update Profile


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. HP shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.

2 HP Software Inventory and Update Profile Version 2.0.0

CONTENTS

Introduction.................................................................................................................................................... 3 1 Scope .................................................................................................................................................... 4 2 Normative References ........................................................................................................................... 4

2.1 Approved References ................................................................................................................. 4 2.2 References under Development ................................................................................................. 4 2.3 Other References ........................................................................................................................ 4

3 Profile 1023 - Software Inventory Profile Changes ............................................................................... 5 3.1 Installed Software vs. Available Software ................................................................................... 5 3.2 Versioning ................................................................................................................................... 5 3.3 ElementSoftwareIdentity Associations ........................................................................................ 6 3.4 Collections and Categories ......................................................................................................... 6 3.5 Matching Installed Software to Repository Software .................................................................. 7 3.6 Bundles ....................................................................................................................................... 8 3.7 Additional HP_SoftwareIdentity Properties (optional) ................................................................. 8 3.8 HP 1023 Profile Use Cases ........................................................................................................ 9

4 1025 - Software Update Profile Changes............................................................................................ 13 4.1 Deliverable Type for InstallFromURI() InstallFromByteStream .. Error! Bookmark not defined. 4.2 Determining Package Type in InstallFromURI() and InstallFromByteStream() ........................ 13

5 Software Repository Service ............................................................................................................... 14 5.1 Available Software (1023) ......................................................................................................... 14 5.2 New SoftwareRepositoryService Methods (1025) .................................................................... 14 5.3 Software Repository Service Use Cases .................................................................................. 17

ANNEX 1 (Informative) Change Log ........................................................................................................ 19 ANNEX 1 (informative) Acknowledgments ............................................................................................... 20

Figures

Figure 1 – Bundle with Install State Set to Partial ......................................................................................... 9 Figure 2 – Collection of Bundle and Components ...................................................................................... 10 Figure 3 - Using IdentityInfoType and IdentityInfoValue to Match Different Versions of Same Software .. 11 Figure 4 – Available, Installed and Not Installed SoftwareIdentities ........................................................... 12 Figure 5 – SoftwareRepositoryService Class Diagram ............................................................................... 14 Figure 6 – SoftwareRepositoryService – Hierarchical Collections .............................................................. 17

Tables

Table 1 – New IdentityInfoType – HPQ:SoftwareCategory Values .............................................................. 6 Table 2 – New HP_SoftwareIdentity Properties............................................................................................ 8 Table 13 – New resource type values for InstallOptions .............................. Error! Bookmark not defined. Table 15 – CIM_SoftwareRepositoryService.GetSoftwareIdentityByteStream() Method Return Values ... 15 Table 16 – CIM_SoftwareRepositoryService.GetSoftwareIdentityByteStream() Method Parameters ....... 15 Table 17 – CIM_SoftwareRepositoryService.GetURIForSoftwareIdentity() Method Return Values .......... 15 Table 18 – CIM_SoftwareRepositoryService.GetURIForSoftwareIdentity() Method Parameters .............. 15 Table 19 – CIM_SoftwareRepositoryService.GetDependenciesForSoftwareIdentity () Method Return Values ......................................................................................................................................................... 16 Table 20 – CIM_SoftwareRepositoryService.GetDependenciesForSoftwareIdentity () Method Parameters16


Introduction

The information in this specification extends the functionality detailed in the following DMTF profiles:

Software Inventory Profile (http://www.dmtf.org/standards/published_documents/DSP1023.pdf)

Software Update Profile (http://www.dmtf.org/standards/published_documents/DSP1025.pdf)

While these changes will initially be specific to HP, we would like to include some, if not all of them in the DMTF profiles in order to create a common standard.

Use of this document assumes familiarity with the profiles described above. HP developers implementing 1023 and 1025 should reference both the DMTF spec and this document.

http://www.dmtf.org/standards/published_documents/DSP1023.pdf





HP Software Inventory and Update Profile

1 Scope The HP Extensions to Profiles 1023 and 1025 describes the changes and extensions to the CIM schema elements described in DMTF Profiles 1023 (Software Inventory Profile) and 1025 (Software Update Profile.)






DMTF DSP 1023, Software Inventory Profile

DMTF DSP1025, Software Update Profile

2.2 References under Development DMTF DSP1033, Profile Registration Profile

2.3 Other References ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards

OMG, Unified Modeling Language (UML) from the Open Management Group (OMG)


http://www.dmtf.org/standards/published_documents/DSP0004V2.3_final.pdf







http://www.uml.org/


3 Profile 1023 - Software Inventory Profile Changes

3.1 Installed Software vs. Available Software

The 1023 profile, Section 7.1, says that an implementation will model Installed Software, Available Software or both. HP shall support Installed Software as indicated in the profile to report on software and firmware installed on a managed element.

HP shall model Available Software to report software and firmware available to install as part of an optional software repository provider. See the section Software Repository Service below for more details on how the repository will model Available software.

Optionally, providers may model Available Software if they have access to SW/FW that can be installed on that computer system. This functionality is useful if the provider also supports the 1025 profile and can install SW/FW, since in this case it is not necessary for the client application to be aware of a repository. For more details on this, see the use case model “Installing Available Software – No Client App Repository Requirement.”

3.2 Versioning

Providers should make every attempt to use the Major Version, Minor Version, Revision and Build Number fields rather than (or in addition to) the VersionString. Client applications (e.g. HP Systems Insight Manager) have a much easier time doing version comparisons between components if the versions are indicated numerically.

3.2.1 HP Internal Requirements

Example version sorting algorithm.

if str1 is null or str2 is null

if str1 is null and str2 is not null return 1

else if str1 is not null and str2 is null return -1

else return 0

else split str1 into separate pieces, using ‘.’ as a token split str2 into separate pieces, using ‘.’ as a token for i = 1 to the number of tokens in str1

if (i > the number of tokens in str2) result = 1 break

assign token i in str1 to s1 assign token i in str2 to s2 convert token i in str1 and str2 to upper case call parseint on str1 to get an int n1 call parseint on str2 to get an int n2 if n1 is not a number or n2 is not a number

if n1 is not a number and n2 is not a number if s1 < s2

result = -1 break


if s1 > s2 result = 1 break

else if n1 is not a number result = -1 break

else result = 1 break

else if n1 < n2

result = -1 break

if n1 > n2 result = 1

if result = 0 and str1’s token array length < str2’s token array length

result = -1 return result

Notes: Possible return values: -1 str1 > str2 0 both strings are equal 1 str2 > str12 the parseint function returns the integer version of a string. If a string cannot be parsed into an integer, then it returns a value indicating that the string is not a number.

3.3 ElementSoftwareIdentity Associations

We strongly encourage providers to supply ElementSoftwareIdentity associations for any returned InstalledSoftwareIdentity items. If no ManagedElement is available to make the association to, then make the association back to the ComputerSystem (see Figure 5 in the Software Installation Profile.)

This will allow client applications to determine the ElementSoftwareStatus[].

3.4 Collections and Categories

Collections can be used to categorize installed software (e.g. NIC Collection, System Collection, Storage Collection, etc.) Members of a collection may be individual SoftwareIdentity items, bundles, or additional collections.

We are also defining a new IdentityInfoType, HPQ: SoftwareCategory, that can be used to store values related to the category of software, such as NIC driver, NIC firmware, System Management Software, etc.

The categorization is used by client applications to display SW/FW belonging to the same category together.

The list below is not comprehensive. However, new categories should be added to this list to prevent there being multiple, similar categories developed by different groups.

Table 1 – New IdentityInfoType – HPQ:SoftwareCategory Values Classification Values Notes


Classification Values Notes

Software Bundle Support Pack

BIOS/FCode System ROM

Driver Graphics

Driver Lights-Out Management

Driver Network

Driver Storage Controller

Driver Storage Fiber Channel

Driver System Management

Firmware Blade Infrastructure Onboard Administrator

Firmware Systems Management Baseboard Management Controller

Firmware Lights-Out Management (iLO/Management Processor, Service Processor)

Firmware Storage Controller

Firmware System ROM System firmware, ie: EFI, SMBIOS, etc

Firmware Storage Device

Firmware NIC

Instrumentation Blade Infrastructure Management

Instrumentation Lights-Out Management

Instrumentation Storage Controller

Instrumentation Storage Fiber Channel

Instrumentation System Management

Application Tools

3.5 Matching Installed Software to Repository Software

Client applications often have the need to match installed versions of software to available software in a repository. One main application for this is determining if a software component in the repository is an upgrade to a component installed on a system.

HP shall use SoftwarePath and SoftwareFamily in IdentityInfoType to match installed software to repository software. The SoftwarePath indicates the location that the component is installed or would install by default (even though the user can change the install destination.) The SoftwareFamily contains a name that is language and version independent. This name is normally the name of the primary executable.

The SoftwarePath and the SoftwareFamily must remain unchanged between versions and language releases.

Example: For the Windows Version Control Agent, the SoftwareFamily is ‘vcagent.exe’ and the path might be ‘c:\hp\hpsmh\data\cgi-bin\vcagent’.

Note that the SoftwarePath is used for identification purposes only and should not be used by the client application to determine the actual location of the installed component. Historically, the SoftwarePath was created to work around a problem of multiple component types having the same SoftwareFamily (key filename.)


3.6 Bundles

Bundle SoftwareIdentities will have the Classifications[] = “Software Bundle” as defined in the CIM_SoftwareIdentity MOF.

Bundles will also have a new property, InstallState, that shall be set to one of the following values:

Installed – all of the items in the bundle are installed

Partial – at least one of the items in the bundle are installed, but not all of them

None – none of the items in the bundle are installed

Bundles have the InstalledSoftwareIdentity association, even if the InstalledState is set to Partial. A client application will use the InstallState from the bundle, and the InstalledSoftwareIdentity association from the bundle’s components to determine which SoftwareIdentity objects in the bundle are installed and which are missing.

3.7 Additional HP_SoftwareIdentity Properties (optional)

These properties are optional. If these properties are implemented, it is not necessary to implement all of them.

Table 2 – New HP_SoftwareIdentity Properties Property Type Description

InstallationNotes string Free-form field for entering any specific notes related to the installation procedure.

RevisionHistory string Free-form field for entering release notes for previous versions

Severity uint8 Indicates the severity of issue addressed by the release. Possible values are 0 – No Issue 1– Minor 2– Major 3– Critical

SourceFileName string Complete file name of the installation package excluding path.

Distribution string The name of the distributor of this package

LicenseModel string The license model of this package.")]

Packager string The packager of this package. This can be different from the owner

Copyright string The copyright which applies to this package

FileSize uint32 The size (total number of bytes) of this package

TargetArchType uint16 The hardware architecture in which this package is intended to operate on. The object code is compatible to operate on this platform.


3.8 HP 1023 Profile Use Cases

3.8.1 Bundle with InstallState set to Partial

The following figure shows swbun partially installed on system1. swbun has two components, swid1 and swid2, as shown by the OrderedComponent association back to swbun. The InstallState is set to Partial to indicate a partial install of the bundle. Swid1 is installed, as shown by the InstalledSoftwareIdentity association back to system1. Swid2 is not installed as it does not have an InstalledSofwareIdentity association back to system1.

system1: ComputerSystem

Swbun : SoftwareIdentityMajorVersion : 1MinorVersion : 0RevisionNumber : 10BuildNumber : 20VersionString : “1.0.10.20”Classifications[0] : “Software Bundle”InstallState : Partial


Swid1: SoftwareIdentity Swid2 : SoftwareIdentity

OrderedComponentAssignedSequence:0



Figure 1 – Bundle with Install State Set to Partial

3.8.2 Collection of Bundles and Components

The following figure shows a bundle, swbun which is a bundle for the system firmware recipie, as indicated by the IdentityInfoType of SoftwareCategory and IdentityInfoValue of “System Firmware Recipie”. Swbun has 2 components, swid1 and swid2, both installed, so the bundle is fully installed. The figure also shows a collection, SystemFWCollection, to represent a collection of all system firmware. SystemFWCollection has two members, Swbun and swid3 which is a single Software Identity that is part of the collection, but not in the swbun bundle.



Swbun : SoftwareIdentityClassifications[0] : “Software Bundle”InstallState : InstalledIdentityInfoTypes[] :{ “HPQ:SoftwareCategory”}IdentityInfoValues[] :{“System Firmware Recipie”}


Swid1: SoftwareIdentity Swid2 : SoftwareIdentity





SystemFWCollection : SystemSpecificCollection

HostedCollection

MemberOfCollection

Swid3 : SoftwareIdentity

MemberOfCollection


Figure 2 – Collection of Bundle and Components

3.8.3 SoftwareFamily and SoftwarePath

The following figure shows swid1 installed on system1. System2 hosts a Software Repository Service that contains swid2. A client application retrieving swid1 and swid2 would know that they are different versions of the same software, since both the SoftwarePath and SoftwareFamily match.



swid2: SoftwareIdentityMajorVersion : 1MinorVersion : 3RevisionNumber : 15BuildNumber : 1VersionString : “1.3.15.1”IdentityInfoTypes[] :{ “HPQ:SoftwarePath”, “HPQ:SoftwareFamily”}IdentityInfoValues[] :{“C:\Program Files\hpwbem”, “HPQ:hpwmiver.dll”}

swid1: SoftwareIdentity MajorVersion : 1MinorVersion : 0RevisionNumber : 10BuildNumber : 20VersionString : “1.0.10.20”IdentityInfoTypes[] :{ “HPQ:SoftwarePath”, “HPQ:SoftwareFamily”}IdentityInfoValues[] :{“C:\Program Files\hpwbem”, “HPQ:hpwmiver.dll”}


System2: ComputerSystem

SoftwareRepository:SystemSpecificCollection

MemberOfCollection

HostedCollection

Figure 3 - Using IdentityInfoType and IdentityInfoValue to Match Different Versions of Same Software

3.8.4 Installing Available Software – No Client App Repository Requirement

This use case is slightly different than others in this document or in the 1023/1025 profiles in that it refers to specific tools. The aim, however, is to point out the sizeable benefits of this approach given the current HP environment.


Figure 4 – Available, Installed and Not Installed SoftwareIdentities

A given 1023 provider can determine and report not only what is installed on a system, but what is available to install.

Example: A provider running on a managed system can be configured (this configuration is provider-specific) to point to a file share of all possible installable components. Using internal logic, it would determine what was installed on the system it’s running on, and what from the repository was applicable to install to its system. Both Installed and Available Software are returned via a 1023 provider to the client application.

The client application can display the list of Available Software to the user, who can select what to install. The client application sends the selected items down to a 1025 provider (InstallFromSoftwareIdentity()) on the managed system.


Note that in this example the client application did not need to know about the repository of all available software. In this way, so long as the provider understood how to acquire applicable available software, the client application can install install SW/FW that’s packaged in any format.

4 1025 - Software Update Profile Changes

4.1 Determining Package Type in InstallFromURI() and InstallFromByteStream() The calls to InstallFromSoftwareIdentity() and CheckSoftwareIdentity contain a SoftwareIdentity. ExtendedResourceType in the SoftwareIdentity notifies the method of the packaging type for the component (i.e. Smart Component, RPM, SD, etc.)

The calls to InstallFromURI() and InstallFromByteStream() do not take a SoftwareIdentity, so there is no way for the client application to notify the method of the packaging type. Instead, it is up to the client application to know what types of packages the provider supports (via SupportedExtendedResourceTypes) and to only send packages of the supported types. Additionally, if the provider supports multiple package types, it is up to the provider to intelligently parse packages that it receives to ensure it is the appropriate the type.

NOTE: The value “HP Smart Component” has been added to the enumerations for CIM_SoftwareInstallationServiceCapabilities.SupportedExtendedResourceTypes and CIM_SoftwareIdentity.ExtendedResourceType properties in CIM 2.28 via CIMCoreCR01562.001 and CIMCoreCR01560.002 respectively. The HP MOFs associated with this Profile will contain those values until CIM 2.28 is released by the DMTF.

4.2 Modified CIM_SoftwareInstallationService.InstallFromURI( ) Add a new return code from the InstallFromURI() method to support reporting that the target hardware is not valid for the requested installation. This could be the server where the installation is to be performed or the hardware which is requested to have its firmware updated.

Table 3 – CIM_SoftwareInstallationService.InstallFromURI( ) Method Return Values

Value Description

4106 Not applicable to Target.


5 Software Repository Service A software repository service will use sections of both the 1023 profile and the 1025 profile as indicated in the following sections.

Figure 5 – SoftwareRepositoryService Class Diagram

5.1 Available Software (1023)

Section 6 of the 1023 profile specifies that Available Software pertains to software available to install on managed elements in its scope. This will be ignored for purposes of the software repository service, which will report ALL available software, not just software available in its scope.

The repository will contain SoftwareIdentity items beyond what can be installed on managed elements within the scope of the service. Therefore, there is not an ElementSoftwareIdentity association from the SoftwareIdentity to a ManagedElement.

5.2 New SoftwareRepositoryService Methods (1025)

These new methods should be considered for extensions to the 1025 profile as they are used for retrieving components that occur during the installation and upgrade of software.


5.2.1 HP_SoftwareRepositoryService.GetSoftwareIdentityByteStream()

HP_SoftwareInstallationService.GetSoftwareIdentityByByteStream() will retrieve a bytestream of an available SoftwareIdentity from the repository.

Table 4 – CIM_SoftwareRepositoryService.GetSoftwareIdentityByteStream() Method Return Values

Value Description


Table 5 – CIM_SoftwareRepositoryService.GetSoftwareIdentityByteStream() Method Parameters

Qualifiers Name Type Description/Values

IN Source CIM_SoftwareIdentity REF See below

OUT Image Uint8[] See below

5.2.1.1 Source

The reference to the SoftwareIdentity that represents the software to be retrieved from the repository. The method shall return the value 2(Error Occurred) when this parameter is Null, or cannot be returned from the repository.

5.2.1.2 Image

This parameter is used to return the array of bytes that contain the image representing the SoftwareIdentity. This parameter is Null if the method returns the value 2(Error Occurred.)

5.2.2 HP_SoftwareRepositoryService.GetURIForSoftwareIdentity()

HP_SoftwareRepositoryService.GetURIForSoftwareIdentity() will return the URI for the specified SoftwareIdentity. Then intent of this method is to allow target systems to use the URI to retrieve the component directly from the repository and install it.

Table 6 – CIM_SoftwareRepositoryService.GetURIForSoftwareIdentity() Method Return Values

Value Description


Table 7 – CIM_SoftwareRepositoryService.GetURIForSoftwareIdentity() Method Parameters



OUT URI String See below

5.2.2.1 Source



5.2.2.2 URI

The URI parameter is used to specify the URI information of the software corresponding to the SoftwareIdentity IN parameter. This shall be Null if the method returns value 2(Error Occurred.)

5.2.3 HP_SoftwareRepositoryService.GetDependenciesForSoftwareIdentity()

HP_SoftwareInstallationService.GetDependenciesForSoftwareIdentity() will return an array of dependencies that must be present for the specified SoftwareIdentity to properly install. Note that this is a single level of dependencies. It is the responsibility of the client application to recursively traverse the dependency list to find the complete ‘tree’ of dependencies.

Table 8 – CIM_SoftwareRepositoryService.GetDependenciesForSoftwareIdentity () Method Return Values

Value Description


Table 9 – CIM_SoftwareRepositoryService.GetDependenciesForSoftwareIdentity () Method Parameters



OUT Dependencies String[] An array of Embedded Instances elements that are required before the component specified can install.

5.2.3.1 Source


5.2.3.2 Dependencies

This output parameter is an array of Strings - Embedded Instances of CIM_SoftwareIdentity describing the dependencies that must be present but are missing.


5.3 Software Repository Service Use Cases

5.3.1 Hierarchical Collections

Figure 6 – SoftwareRepositoryService – Hierarchical Collections


5.3.2 Retrieving the Component Bytes from a Software Repository Service

A client application would first get search the repository for the desired SoftwareIdentity from the Software Repository Service. If the desired SoftwareIdentity was discovered, the client application would get the reference to the SoftwareIdentity from the Software Repository Service. Then the application would use SoftwareRepositoryService.GetSoftwareIdentityByteStream(), passing in the desired reference.

5.3.3 Retrieving the URI for a SoftwareIdentity in a Software Repository

A client application would first get search the repository for the desired SoftwareIdentity from the Software Repository Service. If the desired SoftwareIdentity was discovered, the client application would get the reference to the SoftwareIdentity from the Software Repository Service. Then the application would use SoftwareRepositoryService.GetURIForSoftwareIdentity(), passing in the desired reference.

5.3.4 Software Repository Service with Heirarchical Collections

<include hierarchical collection diagram here>

5.3.5 Client Uses GetSoftwareIdentityByteStream() then InstallFromURI()

In this example, the client application has a web server and can make installable components available via URI.

The client application would first retrieve the component from the repository using SoftwareRepositoryService.GetSoftwareIdentityByteStream() as described in section 5.3.1.

The client application would store the byte stream locally and call the target system’s InstallFromURI() with a link to the file, as described in the profile 1025.

5.3.6 Using InstallFromURI() to Install Component From Repository

The client application would first get a URI to a SoftwareIdentity as described in section 5.3.2.

The client then calls the SoftwareInstallationService.InstallFromURI() method on the target system using the URI retrieved from the repository.


ANNEX 1 (Informative)

Change Log

Version Date Author Description

1.0.0a 3/2/2007 Kevin Brusky Barb Criag Peter Mellquist

Initial Document

1.0.0b 3/15/2007 Kevin Brusky

Changes after initial review by Barbara, Peter and Aaraj

1.0.0c 3/19/2007 Kevin Brusky

Minor updates from Barbara:

• Add Missing Dependencies error code to Check/Install methods

• Returned UnspecifiedError if the InstallFromSoftwareIdentity doesn’t support uninstall

• Specified all new values instead of leaving them at XX.

1.0.0d 3/27/2007 Kevin Brusky

Added back support for reporting Available Software and installing using the InstallFromSoftwareIdentity() method.

1.0.0e 4/10/2007 Peter Mellquist

Changed return values on methods to allow for usage of already CIM defined return codes.

1.0.0.f 5/10/2007 Kevin Brusky

Final edits before submitting to WBEM TC.

1.0.0.g 5/24/07 Barb Craig Updates for handling resource types using install options and few typographical fixes.

1.0.0.h 8/16/07 Barb Craig Add example sorting algorithm at request of WBEM TC.

1.0.2 4/24/08 Barb Craig Add firmware specific entries to table 1

2.0.0 1/14/2011/ Barb Craig CR00166 - Remove all the dependency related references from this profile.

Remove HP Smart Component HP specific enumeration additions, as DMTF added them in 2.28.

Remove HP specific InstallOptions to identify package. Provider still has to validate incoming package whether this parameter is set correctly or not.

Add “Not applicable to target” to InstallFromURI() method.


ANNEX 1 (informative)

Acknowledgments

The authors wish to acknowledge the following people.

Editor:

• Kevin Brusky

Contributors:

• Kevin BruskyBarbara Craig

• Peter Mellquist

• John Planow

• Christina Shaw

• Aaraj Thyagaraj