HP Insight Management WBEM Providers for HP integrated VMware vSphere 5.1 October 2012 Profiles

ManualsBrandsHP ManualsSoftwareVMware Virtualcenter Management Server License Software

HP Insight Management WBEM Providers for

HP integrated VMware vSphere 5.1 October

2012 Profiles

Summary of content (656 pages)

PAGE 1
HP Insight Management WBEM Providers for HP integrated VMware vSphere 5.
PAGE 2
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.
PAGE 3
Contents Foreword ....................................................................................................................................................... 5 Introduction.................................................................................................................................................... 6 1 Scope ....................................................................................................................................................
PAGE 4
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) ..............................
PAGE 5
Tables Table 1 – Related Profiles ............................................................................................................................. 9 Table 2 – Operations: HP_ExtendsProfile ................................................................................................. 13 Table 3 – Operations: HP_ReferencedProfile............................................................................................ 13 Table 4 – Operations: HP_ElementConformsToProfile .....................
PAGE 6
Foreword The HP Profile Registration Profile (P00100) was prepared by the HP W BEM TC. Version 2.0.
PAGE 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 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. 6 Version 2.0.
PAGE 8
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.
PAGE 9
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.
PAGE 10
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 DSP1033 – Profile Registration Profile 6 Version DMTF 1.0.
PAGE 11
CIM_ReferencedProfile CIM_Dependency see Profile Registration Profile HP_ReferencedProfile CIM_ElementConformsToProfile see Profile Registration Profile HP_ExtendsProfile HP_ElementConformsToProfile 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.
PAGE 12
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.
PAGE 13
• 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. 8.2 HP_RegisteredProfile All operations are supported as described by DSP200 v1.2. 12 Version 2.0.
PAGE 14
8.3 HP_ExtendsProfile 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 8.
PAGE 15
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.
PAGE 16
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.
PAGE 17
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.
PAGE 18
HP_ComputerSystem: system1 HP_ComputerSystemPackage HP_ComputerSystemChassis: chassis1 HP_SystemPhysicalFan HP_SystemFan mod1: HP_FanModule fan1: HP_Fan HP_RealizesFan HP_SystemPhysicalProcessor CPU2: HP_Processor proc1: HP_ProcessorChip HP_RealizesProcessor HP_SystemProcessor prof3: CIM_RegisteredProfile CIM_ElementConformsToProfile HP_ExtendsProfile CIM_ReferencedProfile RegisteredOrg: DMTF (2) RegisteredName: Base Server CIM_ReferencedProfile CIM_ReferencedProfile prof2: CIM_RegisteredProfile
PAGE 19
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.
PAGE 20
HP_ComputerSystemPackage HP_ComputerSystem: system1 HP_ComputerSystemChassis: chassis1 HP_ProcessorGroupHostedCollection HP_SystemPhysicalProcessor HP_SystemProcessor HP_ProcessorCollection: collection1 HP_PhysicalMemberOfProcessorCollection HP_LogicalMemberOfProcessorCollection HP_Processor: proc1 HP_ProcessorChip: procchip1 HP_RealizesProcessor HP_Processor: proc2 HP_ProcessorChip: procchip2 HP_RealizesProcessor CIM_ElementConformsToProfile prof3: CIM_RegisteredProfile RegisteredOrg: DMTF (2)
PAGE 21
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.
PAGE 22
System1:HP_ComputerSystem: SMX_ComputerSystem HP_SystemFan Fan1:HP_Fan:SMX_Fan CIM_RunningOS Os1:CIM_OperatingSystem: SMX_OperatingSystem CIM_ElementConformsToProfile prof3: CIM_RegisteredProfile HP_ExtendsProfile RegisteredOrg: DMTF (2) RegisteredName: Base Server CIM_ReferencedProfile CIM_ReferencedProfile prof2: CIM_RegisteredProfile prof1: CIM_RegisteredProfile RegisteredOrg: DMTF (2) RegisteredName: OS Status ImplementationCentralClassNames[0]:”SMX _OperatingSystem” ImplementationNameSpaces[0
PAGE 23
• For each association instance found in previous step • • 9.3 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.
PAGE 24
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. 10.1 HP_RegisteredProfile HP_RegisteredProfile represents an HP defined profile registered in the interop namespace.
PAGE 25
10.4 HP_ElementConformsToProfile 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.
PAGE 26
ANNEX A (normative) Change Log Version Date 0.1 3/15/06 Version 2.0.
PAGE 27
ANNEX B (informative) Acknowledgments 26 Version 2.0.
PAGE 28
ANNEX C (informative) Included WBEM TC CR Numbers CR Number Date CR00100 5/3/06 Version 2.0.
PAGE 29
Bibliography This section contains a list of the external references and dependencies for this specification. 28 Version 2.0.
PAGE 30
HP WBEM TC Document Number: P00101 Date: 04/22/2011 Version: 2.1.1 HP Management Processor (MP) Lite Profile © Copyright 2009 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.
PAGE 31
Contents Forward ......................................................................................................................................................... 5 Introduction.................................................................................................................................................... 6 1 Scope ....................................................................................................................................................
PAGE 32
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 ................................................
PAGE 33
Tables Table 1 – Related Profiles ............................................................................................................................. 9 Table 2 – OperationalStatus mapping ........................................................................................................ 13 Table 3 – Operations: HP_ManagementProcessor ................................................................................... 15 Table 4 – Operations: HP_MPCollection ....................................
PAGE 34
Forward The HP Management Processor Lite Profile (P00101) was prepared by the HP WBEM TC. Version 2.1.
PAGE 35
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. 6 Version 2.1.
PAGE 36
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 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.
PAGE 37
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 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.
PAGE 38
4 Symbols and Abbreviated Terms MP 5 Management Processor Synopsis Profile Name: HP Management Processor Lite Profile Version: 2.1.1 Organization: HP WBEM TC CIM Schema Version: 2.12 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.
PAGE 39
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.
PAGE 40
CIM_Dependency CIM_MemberOfCollection CIM_Component CIM_SoftwareIdentity CIM_HostedDependency CIM_MemberOfPolicyCollection CIM_SystemComponent HP_MPFirmware CIM_HostedCollection HP_MPMemberOfCollection CIM_ComponentCS HP_GroupHostedCollection HP_MPComponentCS HP_MPHostedCollection Figure 2 – Management Processor Association Hierarchy: Class Diagram Version 2.1.
PAGE 41
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.
PAGE 42
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.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.
PAGE 43
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.
PAGE 44
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).
PAGE 45
8.4 HP_MPCollection Table 4 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.
PAGE 46
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.
PAGE 47
For simplicity, not all properties are shown.
PAGE 48
System1:HP_ComputerSystem Profile3:CIM_RegisteredProfile CIM_ElementConformsToProfile RegisteredOrg: DMTF RegisteredName: Base Server HP_ExtendsProfile HP_MPHostedCollection Profile2:HP_RegisteredProfile RegisteredOrg: Other OtherRegOrg: HP WBEM TC RegisteredName: HP Base Server MPCollection1:HP_MPCollection HP_MPComponentCS GroupOperationalStatus[0]: OK FW1:HP_MPFirmware HP_ReferencedProfile Profile1:HP_RegisteredProfile RegisteredOrg: Other OtherRegOrg: HP WBEM TC RegisteredName: HP MP Lite HP_M
PAGE 49
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 Element Name Requirement Description Classes 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.
PAGE 50
Table 6 – Class properties: HP_ManagementProcessor Properties Requirement Notes Properties of class HP_ManagementProcessor ControllerType Conditional uint16 (See Note 1) 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 Int
PAGE 51
Properties IPAddress Requirement Deprecated Notes 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.
PAGE 52
Properties SupportedProtocols[] Requirement Notes Conditional uint16 (See Note 1) 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 uint16 (See Note 1) 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.
PAGE 53
Properties OperationalStatus[] Requirement Mandatory Notes 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.
PAGE 54
Table 7 – Class properties: HP_MPCollection Properties Requirement Notes Properties of class HP_MPCollection 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 Key Mandatory 10.
PAGE 55
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.
PAGE 56
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.
PAGE 57
28 Version 2.1.
PAGE 58
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.
PAGE 59
ANNEX B (informative) Acknowledgments 30 Version 2.1.
PAGE 60
ANNEX C (informative) Included WBEM TC CR Numbers 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.
PAGE 61
Bibliography This section contains a list of the external references and dependencies for this specification. 32 Version 2.1.
PAGE 62
HP WBEM TC Document Number: P00102 Date: 09/11/08 Version: 1.3.0 HP Fan 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.
PAGE 63
Contents Foreword ...................................................................................................................................................... 5 Introduction .................................................................................................................................................. 6 1 Scope .........................................................................................................................................................
PAGE 64
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 ..............................
PAGE 65
Foreword The HP Fan Profile P00102 was prepared by the HP WBEM TC. 4 Version 1.3.
PAGE 66
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. Version 1.3.
PAGE 67
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. 2.
PAGE 68
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 permissib
PAGE 69
5 Synopsis Profile Name: HP Fan Profile Version: 1.3.0 Organization: HP WBEM TC CIM Schema Version: 2.13 Central Class: HP_Fan Scoping Class: Same as DSP1013 – Fan Profile Extends: DMTF DSP1013, Fan Profile 1.0.0 Specializes: HP WBEM TC P00113, HP Consolidated Status Profile 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.
PAGE 70
CIM_ComputerSystem HP_HostedCoolingRedundancySet see referencing profile 1 1 CIM_Fan see DMTF Fan Profile HP_GroupSystemSpecificCollection HP_RegisteredProfile see HP Consolidated Status profile see HP profile registration profile HP_SystemFan 1 HP_HostedCoolingCollection 0..* HP_CoolingRedundancySet CIM_ManagedSystemElement HP_CoolingCollection see referencing profile * 0..1 0..* HP_AssociatedCooling HP_MemberOfCoolingCollection 1..* 1..* HP_Fan HP_MemberOfCoolingRedundancy 1..* 1..
PAGE 71
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.
PAGE 72
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.
PAGE 73
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.
PAGE 74
9 9.1 Use Cases 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].
PAGE 75
system1:CIM_ComputerSystem profile1:CIM_RegisteredProfile HP_HostedCoolingRedundancySet RegisteredName: Base System Profile CIM_ElementConformsToProfile HP_HostedCoolingCollection CIM_ReferencedProfile profile1:CIM_RegisteredProfile coolingcollection1:HP_Cooling Collection RegisteredName: Fan Profile GroupOperationalStatus: (Error) HP_ExtendsProfile HP_SystemFan profile1:HP_RegisteredProfile RegisteredName: HP Fan Profile HP_MemberOfCoolingCollection fan1:HP_Fan OperationalStatus: (Failed) fan2:H
PAGE 76
system1:CIM_ComputerSystem HP_SystemFan CIM_SystemDevice cpu1:CIM_Processor fan1:HP_Fan HP_AssociatedCooling OperationalStatus: (OK) Figure 5 – HP Fan Profile: Associated Cooling Object Diagram Version 1.3.
PAGE 77
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.
PAGE 78
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 OtherIdentifyingInfo[] Optional See Section 7.1.3 IdentifyingDescriptions[] Optional See Section 7.1.4 Description Optional See Section 7.1.2 CIM_Fan 10.
PAGE 79
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.
PAGE 80
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.
PAGE 81
ANNEX A (normative) Change Log Version Date 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 1.0 11/29/06 1.1.0 20 4/2/08 1.2.0 7/17/08 1.3.
PAGE 82
ANNEX B (informative) Acknowledgments Version 1.3.
PAGE 83
ANNEX C (informative) Included WBEM TC CR Numbers 22 CR Number Date CR00106 5/31/06 Create HP profile for the environmental model CR00143 9/11/08 Detailed string properties Title Version 1.3.
PAGE 84
Bibliography This section contains a list of the external references and dependencies for this specification. Version 1.3.
PAGE 85
HP WBEM TC Document Number: P00103 Date: 04/28/09 Version: 1.3.0 HP Power Supply Profile © Copyright 2008, 2009 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.
PAGE 86
Contents Foreword ....................................................................................................................................................... 5 Introduction.................................................................................................................................................... 6 1 Scope ....................................................................................................................................................
PAGE 87
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.................................
PAGE 88
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 ................................
PAGE 89
Foreword The HP Power Supply Profile P00103 was prepared by the HP WBEM TC. Version 1.3.
PAGE 90
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. 6 Version 1.3.
PAGE 91
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. 2 Normative References The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies.
PAGE 92
3.3 conditional used to indicate requirements strictly to be followed in order to conform to the document when the specified conditions are met 3.4 mandatory used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted 3.5 may used to indicate a course of action permissible within the limits of the document 3.6 need not used to indicate a course of action permissible within the limits of the document 3.
PAGE 93
5 Synopsis Profile Name: HP Power Supply Profile Version: 1.3.0 Organization: HP WBEM TC 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.
PAGE 94
CIM_ComputerSystem HP_HostedPowerRedundancySet see referencing profile CIM_LogicalDevice 1 1 see referencing profile HP_GroupSystemSpecificCollection * CIM_PowerSupply see HP Consolidated Status profile see DMTF Power Supply profile HP_SystemPowerSupply HP_HostedPowerCollection HP_SuppliesPower 0..* HP_PowerRedundancySet HP_PowerCollection 0..* HP_RegisteredProfile see HP profile registration profile 0..1 1 HP_MemberOfPowerCollection 1..* 1..
PAGE 95
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_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.
PAGE 96
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.
PAGE 97
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.
PAGE 98
profile1:CIM_RegisteredProfile CIM_ElementConformsToProfile RegisteredName: Base System Profile system1:CIM_ComputerSystem HP_HostedPowerCollection CIM_ReferencedProfile profile1:CIM_RegisteredProfile RegisteredName: Power Supply Profile powercollection1:HP_Power Collection GroupOperationalStatus: (OK) HP_ExtendsProfile HP_MemberOfPowerCollectio profile1:HP_RegisteredProfile RegisteredName: HP Power Supply Profile n HP_SystemPowerSupply pm1:HP_PowerMeter ps1:HP_PowerSupply HP_AssociatedPowerMeter
PAGE 99
system1:HP_ComputerSystem profile1:CIM_RegisteredProfile HP_HostedPowerRedundancySet RegisteredName: Base System Profile CIM_ElementConformsToProfile HP_HostedPowerCollection CIM_ReferencedProfile profile1:CIM_RegisteredProfile Powercollection1:HP_Power Collection RegisteredName: Power Supply Profile GroupOperationalStatus: (Error) HP_ExtendsProfile HP_SystemPowerSupply profile1:HP_RegisteredProfile RegisteredName: HP Power Supply Profile HP_MemberOfPowerCollection ps1:HP_PowerSupply ps2:HP_Power
PAGE 100
system1:CIM_ComputerSystem HP_SystemPower CIM_SystemDevice cpu1:CIM_Processor HP_SuppliesPower ps1:HP_PowerSupply OperationalStatus: (OK) Figure 5 – HP Power Supply Profile: Supplies Power Object Diagram 16 Version 1.3.
PAGE 101
system1:HP_ComputerSystem profile1:CIM_RegisteredProfile RegisteredName: Base System Profile HP_HostedPowerRedundancySet CIM_ElementConformsToProfile HP_HostedPowerCollection CIM_ReferencedProfile profile1:CIM_RegisteredProfile Powercollection1:HP_Power Collection GroupOperationalStatus: RegisteredName: Power Supply Profile (Error) HP_ExtendsProfile HP_SystemPowerSupply profile1:HP_RegisteredProfile RegisteredName: HP Power Supply Profile HP_MemberOfPowerCollection ps1:HP_PowerSupply ps2:HP_PowerS
PAGE 102
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.
PAGE 103
Table 3 – Class: HP_PowerSupply Properties Requirement Notes 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 10.2 HP_RegisteredProfile The HP_RegisteredProfile class is defined by the HP Profile Registration Profile.
PAGE 104
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 Properties Requirement Notes Collection Mandatory Key: References HP_PowerRedundancySet Member Mandatory Key: References HP_PowerSupply 10.
PAGE 105
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.
PAGE 106
10.13 HP_PowerMeter HP_PowerMeter is used to represent an association between HP_PowerSupply and CIM_ManagedSystemElement.
PAGE 107
ANNEX A (normative) Change Log Version Date 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 1.1.
PAGE 108
ANNEX B (informative) Acknowledgments 24 Version 1.3.
PAGE 109
ANNEX C (informative) Included WBEM TC CR Numbers CR Number Date CR00106 5/31/06 Version 1.3.
PAGE 110
Bibliography This section contains a list of the external references and dependencies for this specification. 26 Version 1.3.
PAGE 111
HP WBEM TC Document Number: P00104 Date: 04/21/09 Version: 1.2.0 HP Sensors 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.
PAGE 112
Contents 1 2 2.1 2.2 2.3 3 4 5 6 7 7.1 7.2 7.3 7.4 7.5 7.6 7.7 8 9 9.1 9.2 9.3 10 10.1 10.2 10.3 10.4 10.5 10.6 10.7 11 Scope ............................................................................................................................................. 6 Normative References ................................................................................................................... 6 Approved References .................................................................................
PAGE 113
Table 6 – Class: HP_MemberOfSensorCollection .............................................................................................. 15 Table 7 – Class: HP_HostedSensorCollection ................................................................................................... 15 Table 8 – Class: HP_SystemSensor................................................................................................................... 15 Table 9 – Class: HP_AssociatedSensor ...................................
PAGE 114
Foreword The HP Sensors Profile P00104 was prepared by the HP WBEM TC. 4 Version 1.2.
PAGE 115
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. Version 1.2.
PAGE 116
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. 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.
PAGE 117
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 refer
PAGE 118
Scoping Class: Same as DSP1017 – Sensor Profile Extends: DMTF DSP1017, Sensors Profile 1.0.0 Specializes: HP WBEM TC P00107, HP Consolidated Status Profile 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. Table 1 – Related Profiles Profile Name Organization Version Relationship DSP1017 – Sensors Profile DMTF 1.0.0 Mandatory P00100 – HP Profile Registration Profile HP WBEM TC 1.
PAGE 119
CIM_ComputerSystem see referencing profile 1 1 HP_GroupSystemSpecificCollection see HP Consolidated Status profile CIM_NumericSensor see DMTF Sensors Profile HP_SystemSensor HP_HostedSensorCollection 0..* HP_SensorCollection HP_RegisteredProfile see HP profile registration profile 0..1 HP_MemberOfSensorCollection 1 CIM_ManagedSystemElement 1..* See referencing profile * HP_ElementConformsToProfile (see HP Profile Registration profile) 1..* HP_NumericSensor NumericSensorType HP_AssociatedSensor 1.
PAGE 120
CIM_MemberOfCollection see HP Consolidated Status profile CIM_SystemDevice see DMTF Sensors Profile HP_MemberOfSensorCollection HP_SystemSensor HP_GroupHostedCollection see HP Consolidated Status profile HP_HostedSensorCollection Figure 2 – HP Sensors 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.
PAGE 121
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.
PAGE 122
profile1:CIM_RegisteredProfile CIM_ElementConformsToProfile RegisteredName: Base System Profile system1:CIM_ComputerSystem HP_HostedSensorCollection CIM_ReferencedProfile profile1:CIM_RegisteredProfile RegisteredName: Sensors Profile sensorcollection1:HP_Sens orCollection HP_SystemSensor GroupOperationalStatus: (OK) HP_ExtendsProfile tempsensor2:HP_Nu mericSensor profile1:HP_RegisteredProfile OperationalStatus: (OK) RegisteredName: HP Sensors Profile HP_MemberOfSensorCollection tempsensor1:HP_Nu m
PAGE 123
system1:CIM_ComputerSystem HP_SystemFan fan1:HP_Fan OperationalStatus: (OK) HP_AssociatedSensor HP_SystemSensor sensor1:HP_NumericSensor SensorType: (Tachometer) Figure 4 – HP Fan Profile: Associated Sensor Object Diagram Version 1.2.
PAGE 124
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.
PAGE 125
Properties Requirement OtherRegisteredOrganization 10.3 Mandatory Description “HP WBEM TC” 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.
PAGE 126
10.7 HP_AssociatedSensor HP_AssociatedSensor is used to represent an association between HP_NumericSensor and CIM_ManagedSystemElement.
PAGE 127
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 1.1.0 7/17/08 Version 1.2.
PAGE 128
ANNEX B (informative) Acknowledgments 18 Version 1.2.
PAGE 129
ANNEX C (informative) Included WBEM TC CR Numbers CR Number Date CR00106 5/31/06 Version 1.2.
PAGE 130
Bibliography This section contains a list of the external references and dependencies for this specification. 20 Version 1.2.
PAGE 131
HP WBEM TC Document Number: P00105 Date: 3/4/2010 Version: 2.0.0 HP Base Server Profile © Copyright 2009 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.
PAGE 132
Contents 1 2 3 4 5 6 7 8 9 10 11 Scope ............................................................................................................................................. 6 Normative References ................................................................................................................... 6 2.1 Approved References .................................................................................................................... 6 2.2 References Under Development ........
PAGE 133
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 ..............................................................................................................................
PAGE 134
Foreword The HP Base Server Profile (P00105) was prepared by the HP WBEM TC. 4 Version 2.0.
PAGE 135
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. 5 Version 2.0.
PAGE 136
1 Scope The HP Base Server profile extends the management capability of referencing profiles by adding the capability to represent HP base servers. 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.
PAGE 137
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 permissib
PAGE 138
5 Synopsis Profile Name: HP Base Server Profile Version: 2.0.0 Organization: HP WBEM TC CIM Schema Version: 2.12 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. Table 1 – Related Profiles Profile Name Organization Version Relationship DSP1004 – Base Server profile DMTF 1.0.0 Extends P00100 – HP Profile Registration Profile HP WBEM TC 1.0.
PAGE 139
6 Description HP_ManagementProcessor (see HP Management Processor Lite profile) * ComputerSystem HP_BladeEnclosureCS (see DMTF Base Server profile) HP_MPComponentCS (see HP Blade System Lite profile) HP_ComputerSystemChassis 1 1 1 1 HP_ComputerSystemPakcage (see HP Base Server Physical Asset profile) HP_ComputerSystem HP_BladeSystemComponent SecondaryOwnerPager SecondaryOwnerContact SecondaryOwnerName PrimaryOwnerPager 1 1 1 1 HP_EthernetDevice (see HP Base Server Physical Asset profile) H
PAGE 140
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.
PAGE 141
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.
PAGE 142
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.
PAGE 143
32571 Cell Board 32572 Blade HP_ComputerSystem.Dedicated[ ] and HP_ComputerSystem.OtherDedicatedDescription[ ] arrays must be populated as follows: System HP_ComputerSystem. Dedicated[ ] HP_ComputerSystem.
PAGE 144
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 Dedicated[0]: 0 (Not Dedicated) Empty Dedicated[0]: 2 (Other) “Multi-node” Dedicated[0]: 32568 (Virtual Partition) Empty Dedicated[0]: 32570 (Virtual System) Empty (Non-cellular servers) Examples: - Proliant DL585 - Integrity rx6600 Multi-node (Single chassis with multiple servers) Examples: - Proliant 100 series - T2 Spartan Virtual par
PAGE 145
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.
PAGE 146
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.
PAGE 147
A compliant implementation shall support all the operations in the default list for each class, unless the Requirements column states something other than Mandatory. 8.3 HP_ComputerSystem All operations are supported as described by DSP200 v1.2. 9 9.1 Use Cases 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.
PAGE 148
system1: HP_ComputerSystem: HP_ComputerSystemPackage chassis1: HP_ComputerSystemChassis HP_SystemProcessor HP_SystemFan proc1: HP_Processor fan1: HP_Fan proc2: HP_Processor fan2: HP_Fan fan3: HP_Fan CIM_ElementConformsToProfile HP_ExtendsProfile prof3: CIM_RegisteredProfile RegisteredOrg: DMTF (2) RegisteredName: Base Server CIM_ReferencedProfile CIM_ReferencedProfile CIM_ReferencedProfile prof2: CIM_RegisteredProfile prof1: CIM_RegisteredProfile prof8: CIM_RegisteredProfile RegisteredOrg: DM
PAGE 149
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.
PAGE 150
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).
PAGE 151
system1: HP_ComputerSystem: HP_HostedCoolingCollection OperationalStatus[0]: Degraded HP_HostedPowerCollection col1 : HP_CoolingCollection col2: HP_PowerSupplyCollection HP_SystemFan GroupOperationalStatus[0]: Degraded GroupOperationalStatus[0]: OK HP_SystemPowerSupply HP_MemberOfCoolingCollection fan1: HP_Fan HP_MemberOfPowerCollection OperationalStatus[0]: Degraded ps1: HP_PowerSupply OperationalStatus[0]: OK fan2: HP_Fan OperationalStatus[0]: OK ps2: HP_PowerSupply OperationalStatus[0]: OK f
PAGE 152
• 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
PAGE 153
Table 7 – Class: HP_ComputerSystem Properties Requireme nt 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.
PAGE 154
Class Durable Name(s) Source ID Information Circumstances for Change None Defined Table 10 – Correlatable IDs generated by this Profile Class Correlatable ID(s) Source ID Information Circumstances for Change None Defined 24 Version 2.0.
PAGE 155
ANNEX A (normative) Change Log 25 Version 2.0.
PAGE 156
ANNEX B (informative) Acknowledgments 26 Version 2.0.
PAGE 157
ANNEX C (informative) Included WBEM TC CR Numbers CR Number Date CR00103 6/14/06 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.
PAGE 158
Bibliography This section contains a list of the external references and dependencies for this specification. 28 Version 2.0.
PAGE 159
HP WBEM TC Document Number: P00106 Date: 3/04/2011 Version: 1.1.0 HP CPU 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.
PAGE 160
Contents Foreword ....................................................................................................................................................... 5 Introduction.................................................................................................................................................... 6 1 Scope ....................................................................................................................................................
PAGE 161
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 1.1.
PAGE 162
Tables Table 1 – Related Profiles ............................................................................................................................. 9 Table 2 – Processor Status Mapping Table ................................................................................................ 12 Table 3 – Operations: HP_Processor ........................................................................................................ 13 Table 4 – Operations: HP_ProcessorCore ...........................
PAGE 163
Foreword The HP CPU Profile P00106 was prepared by the HP WBEM TC. 1.1.
PAGE 164
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. 6 1.
PAGE 165
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. 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.
PAGE 166
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.
PAGE 167
5 Synopsis Profile Name: HP CPU Profile Version: 1.1.0 Organization: HP WBEM TC CIM Schema Version: 2.13 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. Table 1 – Related Profiles Profile Name Organization P00100 – HP Profile Registration Profile HP WBEM TC 1.0.0 Mandatory P00108 – HP CPU Physical Asset Profile HP WBEM TC 1.0.
PAGE 168
6 Description HP_RegisteredProfile (see HP Profile Registration Profile) HP_RealizesProcessor (see HP CPU Physical Asset Profile) 0..1 HP_ElementConformsToProfile (see HP Profile Registration profile) 1 HP_ProcessorChip (see HP CPU Physical Asset Profile) HP_ComputerSystem (see HP Base Server Profile) HP_ProcessorCollection * 1 1..* HP_SystemProcessor HP_ProcessorElementCapabilities 1 * 0..
PAGE 169
ProcessorCapabilities CIM_AssociatedCacheMemory CIM_SystemDevice (see DMTF CPU Profile) (see DMTF Base Server profile) HP_AssociatedCacheMemory HP_SystemProcessor HP_ProcessorCapabilities HP_AssociatedProcessorCacheMemory Memory Processor ProcessorCore HardwareThread (see DMTF CPU Profile) (see DMTF CPU Profile) (see DMTF CPU Profile) (see DMTF CPU Profile) HP_CacheMemory HP_Processor HP_ProcessorCore HP_HardwareThread ConcreteComponent HP_ProcessorCoreComponent HP_HWThreadComponent
PAGE 170
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.
PAGE 171
8 Methods None. 8.1 Profile Conventions for Operations Support for operations for each profile class (including associations) is specified in the following subclauses. 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.
PAGE 172
Table 4 – Operations: HP_ProcessorCore 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.4 HP_HardwareThread The table below lists operations that either have special requirements beyond those from DSP0200 or shall not be supported.
PAGE 173
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. For simplicity most of the properties have been removed from the classes.
PAGE 174
10 CIM Elements Table 6 – CIM Elements – HP CPU Profile Element Name Requirement Description 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.
PAGE 175
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.
PAGE 176
Table 13 – Class: HP_CacheMemory Properties Requirement Notes 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.
PAGE 177
Table 16 – Class: HP_ProcessorCapabilities Properties Requirement VirtualizationTechnologyStatus Notes 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.
PAGE 178
ANNEX A (normative) Change Log 20 Version Date Description 0.1 3/15/06 Initial Draft 0.2 6/7/06 Updates to match DMTF CPU profile 0.9.3. 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 1.0 7/11/06 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.
PAGE 179
ANNEX B (informative) Acknowledgments 1.1.
PAGE 180
ANNEX C (informative) Included WBEM TC CR Numbers 22 CR Number Date CR00104 6/28/2006 Title Create HP Profiles for the CPU model. 1.1.
PAGE 181
Bibliography This section contains a list of the external references and dependencies for this specification. 1.1.
PAGE 182
HP WBEM TC Document Number: P00107 Date: 8/2/06 Version: 1.0.0 HP CPU Consolidated Status 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.
PAGE 183
Contents Foreword ....................................................................................................................................................... 5 Introduction.................................................................................................................................................... 6 1 Scope ....................................................................................................................................................
PAGE 184
Figures Figure 1 – CPU Consolidated Status Profile: Class Diagram ..................................................................... 10 Figure 2 – CPU Consolidated Status Profile: Inheritance Hierarchy .......................................................... 10 Figure 3 – CPU Consolidated Status Profile (Logical CPU Propagation) ................................................... 13 Figure 4 – CPU Consolidated Status Profile (Physical CPU Propagation) .................................................
PAGE 185
Tables Table 1 – Related Profiles ............................................................................................................................. 9 Table 2 – Operations: HP_ProcessorCollection ........................................................................................ 12 Table 3 – CIM Elements – HP CPU Consolidated Status Profile ............................................................... 14 Table 4 – Class: HP_ProcessorCollection ..............................................
PAGE 186
Foreword The HP CPU Consolidated Status Profile P00107 was prepared by the HP WBEM TC. Version 1.0.
PAGE 187
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.
PAGE 188
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. 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.
PAGE 189
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.
PAGE 190
5 Synopsis Profile Name: HP CPU Consolidated Status profile Version: 1.0.0 Organization: HP WBEM TC CIM Schema Version: 2.12 Central Class: HP_ProcessorCollection Scoping Class: HP_ComputerSystem 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. Table 1 – Related Profiles Profile Name Organization P00100 – HP Profile Registration Profile HP WBEM TC 1.0.
PAGE 191
HP_GroupSystemSpecificCollection (see HP Consolidated Status profile) HP_RegisteredProfile HP_ComputerSystem (see HP Profile Registration Profile) (see HP Base Server Profile) 1 1 HP_ProcessorGroupHostedCollection * * HP_ProcessorCollection HP_ElementConformsToProfile 1 1 HP_PhysicalMemberOfProcessorCollection HP_LogicalMemberOfProcessorCollection * * HP_ProcessorChip HP_ProcessorCore (see HP CPU Physical Asset Profile) (see HP CPU Profile) Figure 1 – CPU Consolidated Status Profile: Clas
PAGE 192
properties GroupOperationalStatus and GroupStatusDescription which are used by the HP_ComputerSystem class provider to update its overall status. 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_ProcessorCollection There may be one or more instance of HP_ProcessorCollection instantiated.
PAGE 193
• 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. 8.2 HP_ProcessorCollection 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.
PAGE 194
9 9.1 Use Cases 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”.
PAGE 195
system1: HP_ComputerSystem HP_ProcessorGroupHostedCollection coll1: HP_ProcessorCollection GroupOperationalStatus[0]: Failed HP_PhysicalMemberOfProcessorCollection chip1: HP_ProcessorChip OperationalStatus[0]: OK chip2: HP_ProcessorChip OperationalStatus[0]: Failed Figure 4 – CPU Consolidated Status Profile (Physical CPU Propagation) 10 CIM Elements Table 3 – CIM Elements – HP CPU Consolidated Status Profile Element Name Requirement Description Classes HP_ProcessorCollection Mandatory See sectio
PAGE 196
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.
PAGE 197
Table 7 – Class: HP_PhysicalMemberOfProcessorCollection Properties Requirement Notes Collection Mandatory Key: References HP_ProcessorCollection Member Mandatory Key: References HP_ProcessorChip 10.5 HP_RegisteredProfile Implementation shall implement an instance of HP_RegisteredProfile in the Interop namespace with the values specified.
PAGE 198
ANNEX A (normative) Change Log Version Date 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. Version 1.0.
PAGE 199
ANNEX B (informative) Acknowledgments 18 Version 1.0.
PAGE 200
ANNEX C (informative) Included WBEM TC CR Numbers CR Number Date CR00104 6/28/2006 Version 1.0.0 Title Create HP Profiles for the CPU model.
PAGE 201
Bibliography This section contains a list of the external references and dependencies for this specification. 20 Version 1.0.
PAGE 202
HP WBEM TC Document Number: P00108 Date: 4/18/07 Version: 1.0.0 HP CPU Physical Asset 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.
PAGE 203
Contents Foreword ....................................................................................................................................................... 5 Introduction.................................................................................................................................................... 6 1 Scope ....................................................................................................................................................
PAGE 204
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 ...................................
PAGE 205
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 .....................
PAGE 206
Foreword The HP CPU Physical Asset Profile P00108 was prepared by the HP W BEM TC. Version 1.0.
PAGE 207
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. 6 Version 1.0.
PAGE 208
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. 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.
PAGE 209
3.3 conditional used to indicate requirements strictly to be followed in order to conform to the document when the specified conditions are met 3.4 mandatory used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted 3.5 may used to indicate a course of action permissible within the limits of the document 3.6 need not used to indicate a course of action permissible within the limits of the document 3.
PAGE 210
5 Synopsis Profile Name: HP CPU Physical Asset Profile Version: 1.0.0 Organization: HP WBEM TC CIM Schema Version: 2.12 Central Class: HP_ProcessorChip Scoping Class: Same as parent profile 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. Table 1 – Related Profiles Profile Name Organization P00100 – HP Profile Registration Profile HP WBEM TC 1.0.
PAGE 211
6 Description HP_ProcessorCollection HP_RegisteredProfile See HP CPU Consolidated Status profile (see HP Profile Registration Profile) 1 0..1 Chip (see DMTF Physical Asset Profile) HP_ElementConformsToProfile (see HP Profile Registration profile) HP_ComputerSystemChassis 1..
PAGE 212
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.
PAGE 213
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 • 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. 8.
PAGE 214
9 9.1 Use Cases 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.
PAGE 215
chassis1: HP_ComputerSystemChassis (see HP Base Server Physical Asset Profile) HP_SystemPhysicalProcessor chip1: HP_ProcessorChip HP_RealizesProcessor HP_AssociatedProcessorCacheMemory proc1: HP_Processor (see HP CPU Profile) HP_CacheMemory (see HP CPU Profile) HP_RealizesProcessorCache pcache1: HP_PhysicalMemoryCache Figure 4 – HP CPU Physical Asset Profile: Object Diagram with External Cache 14 Version 1.0.
PAGE 216
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 Element Name Requirement Description Classes 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.
PAGE 217
Table 7 – Class: HP_SystemPhysicalProcessor Properties Requirement Notes GroupComponent Mandatory REF:HP_ComputerSystemChassis PartComponent Mandatory REF:HP_ProcessorChip 11 Durable Names and Correlatable IDs Table 8 – Durable Names generated by this Profile Class Durable Name(s) Source ID Information Circumstances for Change None Table 9 – Correlatable IDs generated by this Profile Class Correlatable ID(s) Source ID Information Circumstances for Change None 16 Version 1.0.
PAGE 218
ANNEX A (normative) Change Log Version Date 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 Version 1.0.
PAGE 219
ANNEX B (informative) Acknowledgments 18 Version 1.0.
PAGE 220
ANNEX C (informative) Included WBEM TC CR Numbers CR Number Date CR00104 6/28/2006 Version 1.0.0 Title Create HP Profiles for the CPU model.
PAGE 221
Bibliography This section contains a list of the external references and dependencies for this specification. 20 Version 1.0.
PAGE 222
HP WBEM TC Document Number: P00109 Date: 12/19/08 Version: 1.1.0 HP Record Log 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.
PAGE 223
HP Record Log Profile Contents Foreword ....................................................................................................................................................... 4 Introduction.................................................................................................................................................... 5 1 Scope ..................................................................................................................................................
PAGE 224
HP Record Log Profile 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 .......
PAGE 225
HP Record Log Profile Foreword The HP Record Log Profile P00109 was prepared by the HP WBEM TC. 4 Version 1.1.
PAGE 226
HP Record Log 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 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. Version 1.1.
PAGE 227
HP Record Log Profile 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. 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.
PAGE 228
HP Record Log Profile 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.
PAGE 229
HP Record Log Profile 5 Synopsis Profile Name: HP Record Log Profile Version: 1.1.0 Organization: HP WBEM TC CIM Schema Version: 2.13 Central Class: HP_CommonRecordLog Scoping Class: Same as parent profile 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. Table 1 – Related Profiles 8 Profile Name Organization Version Relationship P00100 – HP Profile Registration Profile HP WBEM TC 1.
PAGE 230
HP Record Log Profile 6 Description HP_RegisteredProfile (see HP Profile Registration Profile) HP_ElementConformsToProfile (see HP Profile Registration profile) ManagedSystemElement (see HP Base Server Profile) 1..* Log RecordForLog RecordLog LogEntry (see DMTF Record Log Profile) (see DMTF Record Log Profile) 0..1 1..* HP_UseOfLog HP_LogManagesRecord HP_CommonRecordLog HP_CommonLogEntry 1..
PAGE 231
HP Record Log Profile 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.
PAGE 232
HP Record Log Profile 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.
PAGE 233
HP Record Log Profile 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.
PAGE 234
HP Record Log Profile 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.
PAGE 235
HP Record Log Profile 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.
PAGE 236
HP Record Log Profile 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.
PAGE 237
HP Record Log Profile 8 8.1 Methods 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.
PAGE 238
HP Record Log Profile Table 3 – HP_CommonLogEntry.Repair() Method Return Values Value 8.5 Description 0 Request was successfully executed 1 Method is not supported in the implementation 2 Error occurred 3 Timeout 4 Failed Profile Conventions for Operations Support for operations for each profile class (including associations) is specified in the following subclauses. Each sub-clause includes either a statement “All operations are supported as described by DSP200 v1.
PAGE 239
HP Record Log Profile 9 9.1 Use Cases Object Diagrams CIM_ElementConformsToProfile system1: HP_ComputerSystem profile1:CIM_RegisteredProfile rec2: HP_CommonLogEntry RegisteredName: Base System HP_UseOfLog HP_LogManagesRecord CIM_ReferencedProfile profile2:CIM_RegisteredProfile InstanceID: HPQ: log1.rec2 CreationTimeStamp: 2006.05.31 04:56 RecordFormat: *string DeviceID*uint8 Record* RecordData: *10.0.
PAGE 240
HP Record Log Profile 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.
PAGE 241
HP Record Log Profile 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.
PAGE 242
HP Record Log Profile 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.
PAGE 243
HP Record Log Profile System1: HP_ComputerSystem * * HP_UseOfLog HP_UseOfLog * * Log1: HP_CommonRecordLog Log2 : HP_CommonRecordLog Name: “HP Hardware Log” Name: “Copy HP Hardware Log” 1 HP_LogManagesRecord 1 HP_LogManagesRecord * * Rec1 :HP_CommonLogRecord CreationTimeStamp:2006.05.31 14:34 Rec2 : HP_CommonLogRecord CreationTimeStamp:2006.05.31 04:56 Figure 5 – Copy of SEL instance diagram 22 Version 1.1.
PAGE 244
HP Record Log Profile 10 CIM Elements Table 4 – CIM Elements – HP Record Log Profile Element Name Requirement Description 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 10.1 Optional See sections 7.3 and 10.
PAGE 245
HP Record Log Profile 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.
PAGE 246
HP Record Log Profile 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.
PAGE 247
HP Record Log Profile 11 Durable Names and Correlatable IDs Table 10 – Durable Names generated by this Profile Class Durable Name(s) Source ID Information 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.
PAGE 248
HP Record Log Profile Table 11 – Correlatable IDs generated by this Profile Class Correlatable ID(s) Source ID Information CIM_RecordFor Log InstanceID Identifier of the instance of the Record. CIM_Indication IndicationIdentifier Unique identification of this instance of an indication on the system.
PAGE 249
HP Record Log Profile Class Correlatable ID(s) Source ID Information failure, would include in this array the IndicationIdentifier for the original indication for the failure. HP_CommonRe cordLogIndicatio n RecordLogInstanceID Identifier of the instance of the entry in the RecordLog. This can be used to identify the RecordLog with the new entries. HP_CommonRe cordLogIndicatio n LogRecordInstanceIDs[] Array of identifiers of of the instances of LogRecords.
PAGE 250
HP Record Log Profile Class Version 1.1.0 Correlatable ID(s) Source ID Information indication.
PAGE 251
HP Record Log Profile ANNEX A (normative) Change Log 30 Version Date Description 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.
PAGE 252
HP Record Log Profile ANNEX B (informative) Acknowledgments Version 1.1.
PAGE 253
HP Record Log Profile ANNEX C (informative) Included WBEM TC CR Numbers CR Number 32 Date Title Version 1.1.
PAGE 254
HP Record Log Profile Bibliography This section contains a list of the external references and dependencies for this specification. Version 1.1.
PAGE 255
HP WBEM TC Document Number: P00110 Date: 08/01/06 Version: 1.
PAGE 257
HP Memory Profile Contents Foreword ...................................................................................................................................................... 4 Introduction .................................................................................................................................................. 5 1 Scope ........................................................................................................................................................
PAGE 258
HP Memory Profile Foreword The HP Memory Profile P00110 was prepared by the HP WBEM TC. 4 HP Confidential Version 1.
PAGE 259
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).
PAGE 260
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. 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.
PAGE 261
HP Memory Profile 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
PAGE 262
HP Memory Profile CIM Schema Version: 2.13 Central Class: HP_Memory Scoping Class: Same as parent profile 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. Table 1 – Related Profiles Profile Name Organization P00100 – HP Profile Registration Profile HP WBEM TC 1.0 Mandatory DSP1026 – System Memory Profile DMTF 1.0 Mandatory P00111 – HP Memory Physical Asset profile HP WBEM TC 1.
PAGE 263
HP Memory Profile CIM_SystemDevice (see DMTF Base Server profile) 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.
PAGE 264
HP Memory Profile 8 Methods None. 8.1 Profile Conventions for Operations Support for operations for each profile class (including associations) is specified in the following subclauses. 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.
PAGE 265
HP Memory Profile 9 9.1 Use Cases 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. system1 : HP_ComputerSystem HP_SystemMemory memory1 : HP_Memory HP_RealizesMemoryModule mm1 : HP_MemoryModule HP_RealizesMemoryModule mm2 : HP_MemoryModule Figure 3 – HP Memory Profile: Object diagram with two memory modules Version 1.
PAGE 266
HP Memory Profile 10 CIM Elements Table 3 – CIM Elements – HP Memory Profile Element Name Requirement Description Classes 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 Indications None defined in this profile 10.1 HP_Memory HP_Memory extends the class CIM_Memory in ways that are specific to HP systems.
PAGE 267
HP Memory Profile Properties Requirement Notes RegisteredOrganization Mandatory Other (1) OtherRegisteredOrganization Mandatory “HP WBEM TC” RegisteredName Mandatory “HP Memory” RegisteredVersion Mandatory “1.
PAGE 268
HP Memory Profile ANNEX A (normative) Change Log 14 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 Confidential Version 1.
PAGE 269
HP Memory Profile ANNEX B (informative) Acknowledgments Version 1.
PAGE 270
HP Memory Profile ANNEX C (informative) Included WBEM TC CR Numbers 16 CR Number Date CR00106 7/26/06 Title Create HP profile for the logical and physical system memory model HP Confidential Version 1.
PAGE 271
HP Memory Profile Bibliography This section contains a list of the external references and dependencies for this specification. Version 1.
PAGE 272
HP WBEM TC Document Number: P00111 Date: 05/25/2012 Version: 2.1.0 HP Memory Physical Asset 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.
PAGE 273
Contents Foreword ....................................................................................................................................................... 6 Introduction.................................................................................................................................................... 7 1 Scope ....................................................................................................................................................
PAGE 274
10.17 HP_SystemMemoryModuleSlot ................................................................................................ 31 10.18 HP_SystemMemoryBoardSlot .................................................................................................. 31 10.19 HP_MemoryModuleSlotOnBoard ............................................................................................. 32 10.20 HP_RegisteredProfile ..........................................................................................
PAGE 275
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) ......................................................
PAGE 276
Tables Table 1 – Related Profiles ........................................................................................................................... 10 Table 2 Memory type .................................................................................................................................. 15 Table 3 Memory Technology....................................................................................................................... 15 Table 6 – Class: HP_MemoryCollection ............
PAGE 277
Foreword The HP Memory Physical Asset Profile P00111 was prepared by the HP WBEM TC. 6 2.1.
PAGE 278
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. 2.1.
PAGE 279
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. 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.
PAGE 280
3.3 conditional used to indicate requirements strictly to be followed in order to conform to the document when the specified conditions are met 3.4 mandatory used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted 3.5 may used to indicate a course of action permissible within the limits of the document 3.6 need not used to indicate a course of action permissible within the limits of the document 3.
PAGE 281
5 Synopsis Profile Name: HP Memory Physical Asset Profile Version: 2.1.0 Organization: HP WBEM TC CIM Schema Version: 2.13 Central Class: HP_MemoryModule Scoping Class: HP_ComputerSystem 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.
PAGE 282
CIM_ComputerSystem (see referencing profile) 1 1 CIM_RedundancySet HP_GroupSystemSpecificCollection HP_RegisteredProfile (see HP Consolidated Status Profile) (see HP Consolidated Status Profile) (see HP Profile Registration Profile) HP_HostedMemoryCollection 0..
PAGE 283
CIM_Container CIM_PackageInConnector see DMTF Physical Asset profile HP_SystemMemoryBoard see DMTF Physical Asset profile HP_SystemMemoryModule HP_MemoryModuleOnBoard HP_SystemMemoryBoardSlot HP_SystemMemoryModuleSlot HP_MemoryModuleSlotOnBoard HP_MemoryBoardInSlot CIM_MemberOfCollection CIM_ElementInConnector see HP Consolidated Status profile HP_MemberOfMemoryCollection see DMTF Physical Asset profile HP_MemberOfMemoryRedundancySet CIM_Realizes HP_MemoryModuleInSlot see DMTF Physical Asset
PAGE 284
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.
PAGE 285
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.
PAGE 286
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.
PAGE 287
Value 2 3 4 5 6 7 8 9 .. ValueMap FastPageMode EdoPageMode BurstEdoPageMode Synchronous RDRAM RDIMM UDIMM 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.
PAGE 288
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.
PAGE 289
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.
PAGE 290
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.
PAGE 291
system1: HP_ComputerSystem HP_HostedMemoryCollection Mmcol1: HP_MemoryCollection GroupOperationalStatus[0]: Failed HP_MemberOfMemoryCollection Mm1: HP_MemoryModule OperationalStatus[0]: OK Mm2: HP_MemoryModule OperationalStatus[0]: Failed Ms3: HP_MemoryModuleSlot HP_SystemMemoryModule HP_MemoryModuleInSlot HP_MemoryModuleInSlot HP_SystemMemoryModule Ms1: HP_MemoryModuleSlot Ms2_HP_MemoryModuleSlot Ms4: HP_MemoryModuleSlot HP_SystemMemoryModuleSlot Csc1: HP_ComputerSystemChassis Figure 3 – Mem
PAGE 292
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”.
PAGE 293
system1: HP_ComputerSystem OperationalStatus[0]: Failed HP_HostedMemoryCollection Mmcol1: HP_MemoryCollection GroupOperationalStatus[0]: Failed HP_MemberOfMemoryCollection HP_MemoryModuleOnBoard Mb1 : HP_MemoryBoard Mm1: HP_MemoryModule OperationalStatus[0]: Failed OperationalStatus[0]: OK Mm2: HP_MemoryModule OperationalStatus[0]: OK HP_MemoryBoardInSlot HP_SystemMemoryModule HP_SystemMemoryBoard HP_MemoryModuleInSlot HP_MemoryModuleInSlot Csc1: HP_ComputerSystemChassis Mbs1: HP_MemoryBoardSlo
PAGE 294
system1: HP_ComputerSystem HP_HostedMemoryRedundancySet OperationalStatus[0]: Degraded HP_HostedMemoryCollection Mmcol1: HP_MemoryCollection GroupOperationalStatus[0]: Degraded HP_MemberOfMemoryCollection HP_MemoryModuleOnBoard Mb1 : HP_MemoryBoard Mm1: HP_MemoryModule OperationalStatus[0]: Degraded OperationalStatus[0]: OK Mm2: HP_MemoryModule OperationalStatus[0]: Failed HP_MemoryBoardInSlot HP_SystemMemoryModule Mbred1:HP_MemoryRedundancySet HP_MemberOfMemoryRedundancySet RedundancyStatus: De
PAGE 295
10 CIM Elements Table 4 – CIM Elements – HP Memory Physical Asset Profile Element Name Requirement Description 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.
PAGE 296
Table 5 – Class: HP_MemoryCollection Properties Requirement InstanceID 10.2 Mandatory Notes Key: “HPQ::” where is the name of the provider that implements this class and is a unique value for the instance. HP_MemoryRedundancySet HP_ MemoryRedundancySet extends the class CIM_RedundancySet in ways that are specific to HP memory implementations.
PAGE 297
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.
PAGE 298
Table 11 – Class: HP_ MemoryModule Properties Requirement Notes Tag Mandatory Key: “HPQ::” where is the name of the provider that implements this class and is a unique value for the instance. 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.
PAGE 299
Table 12 – Class: HP_MemoryBoard Properties Requirement Notes Tag Mandatory Key: “HPQ::” where is the name of the provider that implements this class and is a unique value for the instance. 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.
PAGE 300
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.
PAGE 301
Table 19 – Class: HP_MemoryModuleSlot Properties Requirement Notes Tag Mandatory Key: “HPQ::” where is the name of the provider that implements this class and is a unique value for the instance. 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.
PAGE 302
Table 20 – Class: HP_MemoryBoardSlot Properties Requirement Notes Tag Mandatory Key: “HPQ::” where is the name of the provider that implements this class and is a unique value for the instance. 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.
PAGE 303
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 10.20 HP_RegisteredProfile Implementation shall implement an instance of HP_RegisteredProfile in the Interop namespace with the values specified.
PAGE 304
ANNEX A (normative) Change Log Version Date Description 0.1 7/12/06 Initial Draft 0.2 7/20/06 Updates made based on feedback from the WBEM TC Updates made based on feedback from WBEM TC sub-team review: 0.
PAGE 305
Version Date Description CIM_PhysicalElement • Properties are adjusted for HP_MemoryBoard and HP_MemoryRedundancySet o o • • HP_MemoryRedundancySet  Added: AvailableMemory, TotalMemory, ConfigurationsAvailable, TargetConfiguration, CurrentConfiguration  Removed: OSMemSize, TypeAvailable, RivState, SubSystemStatus, TotalMemSize HP_MemoryBoard:  Added: AvailableMemory, TotalMemory  Removed: TotalMemorySize, OSMemorySize Classes renamed: o HP_MemoryModuleCollection now HP_MemoryCollection
PAGE 306
ANNEX B (informative) Acknowledgments 2.1.
PAGE 307
ANNEX C (informative) Included WBEM TC CR Numbers CR Number Date 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 Title Added HP_MemoryModule.
PAGE 308
Bibliography This section contains a list of the external references and dependencies for this specification. 2.1.
PAGE 309
HP WBEM TC Document Number: P00114 Date: 10/08/2009 Version: 1.4.0 HP Base Server Physical Asset Profile © Copyright 2008, 2009 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.
PAGE 310
Contents Foreword ....................................................................................................................................................... 3 Introduction.................................................................................................................................................... 4 1 Scope ....................................................................................................................................................
PAGE 311
Foreword The HP Base Server Physical Asset profile (P00114) was prepared by the HP WBEM TC. Version 1.4.
PAGE 312
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. 4 Version 1.4.
PAGE 313
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. 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.
PAGE 314
3.3 conditional used to indicate requirements strictly to be followed in order to conform to the document when the specified conditions are met 3.4 mandatory used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted 3.5 may used to indicate a course of action permissible within the limits of the document 3.6 need not used to indicate a course of action permissible within the limits of the document 3.
PAGE 315
5 Synopsis Profile Name: HP Base Server Physical Asset Profile Version: 1.4.0 Organization: HP WBEM TC CIM Schema Version: 2.12 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. Table 1 – Related Profiles Profile Name DSP1011 – Physical Asset profile 6 Organization DMTF Version 1.
PAGE 316
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 7.1.1 HP_ComputerSystemChassis 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.
PAGE 317
• • • • • “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.
PAGE 318
(Single chassis with multiple servers) e.g T2 Spartan Virtual partition “Virtual partition” Example: - vPar Virtual system “Virtual system” Examples: - HPVM guest - Xen guest 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.
PAGE 319
8 Methods None. 8.1 Profile Conventions for Operations Support for operations for each profile class (including associations) is specified in the following subclauses. 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.
PAGE 320
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).
PAGE 321
Table 4 – Class: HP_ComputerSystemChassis Properties Requirement Notes 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.
PAGE 322
11 Durable Names and Correlatable IDs Table 7 – Durable Names generated by this Profile Class Durable Name(s) Source ID Information Circumstances for Change HP_ComputerSy stemPackage UUID UUID from SMBIOS Chassis replacement HP_ComputerSy stemChassis SerialNumber Serial Number from SMBIOS Chassis replacement HP_ComputerSy stemChassis VirtualSerialNumber Virtual Serial Number as provided by Virtual Connect Logical server deletion / addition HP_ComputerSy stemChassis VirtualUUID Virtual UUID
PAGE 323
ANNEX A (normative) Change Log Version Date Description 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 Version 1.4.
PAGE 324
ANNEX B (informative) Acknowledgments 16 Version 1.4.
PAGE 325
ANNEX C (informative) Included WBEM TC CR Numbers CR Number Date 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 Version 1.4.
PAGE 326
Bibliography This section contains a list of the external references and dependencies for this specification. 18 Version 1.4.
PAGE 327
HP WBEM TC Document Number: P00115 Date: 09/11/08 Version: 1.1.0 HP Fan Physical Asset 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.
PAGE 328
Contents 1 2 2.1 2.2 2.3 3 4 5 6 7 7.1 7.2 7.3 7.4 7.5 8 9 9.1 9.2 10 10.1 10.2 10.3 10.4 10.5 11 Scope ..................................................................................................................................... 5 Normative References ........................................................................................................... 5 Approved References ............................................................................................................
PAGE 329
Foreword The HP Fan Physical Asset Profile P00115 was prepared by the HP WBEM TC. Version 1.1.
PAGE 330
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. 4 Version 1.1.
PAGE 331
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. 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.
PAGE 332
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 refer
PAGE 333
Scoping Class: Same as parent profile Extends: DMTF DSP1011, Physical Asset Profile 1.0.0 The HP Fan Physical Asset profile extends DMTF DSP1011 to add physical fan characteristics that are specific to HP systems. Table 1 – Related Profiles Profile Name Organization Version Relationship DSP1011 – Physical Asset Profile DMTF 1.0.0 Mandatory P00100 – HP Profile Registration Profile HP WBEM TC 1.0.0 Mandatory P00102 – HP Fan Profile HP WBEM TC 1.0.
PAGE 334
CIM_Realizes see DMTF Physical Asset profile HP_RealizesFan CIM_Container see DMTF Physical Asset profile HP_SystemPhysicalFan CIM_PackageInSlot see DMTF Physical Asset profile HP_FanInSlot Figure 2 – HP Fan Physical Asset 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.
PAGE 335
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.
PAGE 336
system1:CIM_ComputerSystem HP_HostedCoolingCollection coolingcollection1:HP_Cooli ngCollection GroupOperationalStatus: (OK) HP_SystemFan HP_SystemFan fan2:HP_Fan OperationalStatus: (OK) HP_MemberOfCoolingCollection fan1:HP_Fan HP_MemberOfCoolingCollection OperationalStatus: (OK) HP_RealizesFan HP_RealizesFan Fm1:HP_FanModule Fm2:HP_FanModule OperationalStatus: (OK) Element Name: “Fan 1” FanType: 11 (Chassis) Description: Fan 1 provides cooling for the Chassis: Status is OK.
PAGE 337
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. 10 CIM Elements The implementation requirements for the classes and properties described in this section are defined in the “Implementation Requirements” section (Section 7).
PAGE 338
OtherRegisteredOrganization 10.3 Mandatory “HP WBEM TC” 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.
PAGE 339
ANNEX A (normative) Change Log Version Date 0.1 5/30/06 Initial draft 1.0 5/31/06 Updated properties and fixed cross reference errors 1.0 11/29/06 1.0.
PAGE 340
ANNEX B (informative) Acknowledgments 14 Version 1.1.
PAGE 341
ANNEX C (informative) Included WBEM TC CR Numbers CR Number Date CR00106 5/31/06 Create HP profile for the environmental model CR00143 9/11/08 Detailed string properties Version 1.1.
PAGE 342
Bibliography This section contains a list of the external references and dependencies for this specification. 16 Version 1.1.
PAGE 343
HP WBEM TC Document Number: P00116 Date: 11/29/06 Version: 1.0.2 HP Power Supply Physical Asset 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.
PAGE 344
Contents 1 2 2.1 2.2 2.3 3 4 5 6 7 7.1 7.2 7.3 7.4 8 9 9.1 9.2 10 10.1 10.2 10.3 10.4 10.5 11 Scope ..................................................................................................................................... 5 Normative References ........................................................................................................... 5 Approved References ............................................................................................................
PAGE 345
Foreword The HP Power Supply Physical Asset Profile P00116 was prepared by the HP WBEM TC. Version 1.0.
PAGE 346
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. 4 Version 1.0.
PAGE 347
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. 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.
PAGE 348
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 refer
PAGE 349
Scoping Class: Same as parent profile Extends: DMTF DSP1011, Physical Asset Profile 1.0.0 The HP Power Supply Physical Asset profile extends DMTF DSP1011 to add physical power supply characteristics that are specific to HP systems. Table 1 – Related Profiles Profile Name Organization Version Relationship DSP1011 – Physical Asset Profile DMTF 1.0.0 Mandatory P00100 – HP Profile Registration Profile HP WBEM TC 1.0.0 Mandatory P00103 – HP Power Supply Profile HP WBEM TC 1.0.
PAGE 350
Figure 1 – HP Power Supply Physical Asset Profile: Class Diagram CIM_Container CIM_Realizes see DMTF Physical Asset profile see DMTF Physical Asset profile HP_RealizesPowerSupply HP_SystemPhyiscalPowerSupply CIM_PackageInSlot see DMTF Physical Asset profile HP_PowerSupplyInSlot Figure 2 – HP Power Supply Physical Asset Profile: Inheritance Hierarchy Diagram 7 Implementation Requirements This section details the requirements related to the arrangement of instances and properties of instances for
PAGE 351
9 9.1 Use Cases 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.
PAGE 352
system1:CIM_ComputerSystem HP_HostedPowerCollection powercollection1:HP_Power Collection GroupOperationalStatus: (OK) HP_SystemPowerSupply ps2:HP_PowerSupply OperationalStatus: (OK) HP_MemberOfPowerCollection ps1:HP_PowerSupply OperationalStatus: (OK) HP_RealizesPowerSupply ps1:HP_PowerSupplyModule HP_RealizesPowerSupply ps2:HP_PowerSupplyModule HP_PowerSupplyInSlot psslot1:CIM_Slot HP_PowerSupplyInSlot psslot2:CIM_Slot psslot3:CIM_Slot psslot4:CIM_Slot CIM_Container HP_SystemPhysicalPower Su
PAGE 353
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 Power Supply Profile Element Name Requirement Description Classes 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.
PAGE 354
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.
PAGE 355
ANNEX A (normative) Change Log Version Date 0.1 5/30/06 Initial draft 1.0 5/31/06 Updated properties and fixed cross reference errors 1.0 11/29/06 1.0.1 5/16/08 1.0.2 7/17/08 Version 1.0.
PAGE 356
ANNEX B (informative) Acknowledgments 14 Version 1.0.
PAGE 357
ANNEX C (informative) Included WBEM TC CR Numbers CR Number Date CR00106 5/31/06 Version 1.0.
PAGE 358
Bibliography This section contains a list of the external references and dependencies for this specification. 16 Version 1.0.
PAGE 359
HP WBEM TC Document Number: P00117 Date: 06/04/2012 Version: 1.1.0 HP Ethernet Teaming © Copyright 20012 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.
PAGE 360
Contents Foreword ....................................................................................................................................................... 6 Introduction.................................................................................................................................................... 7 1 Scope ....................................................................................................................................................
PAGE 361
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.
PAGE 362
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 .......................
PAGE 363
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 .....................................................................
PAGE 364
Foreword The HP Ethernet Teaming Profile P00117 was prepared by the HP WBEM TC. 6 Version 1.1.
PAGE 365
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. Version 1.1.
PAGE 366
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. 2 Normative References The following referenced documents are indispensable for the application of this document.
PAGE 367
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 perm
PAGE 368
4 Symbols and Abbreviated Terms None. 5 Synopsis Profile Name: HP Ethernet Teaming Version: 1.1.0 Organization: HP WBEM TC CIM Schema Version: 2.12 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 Table 1 – Related Profiles Profile Name Organization Version Relationship DSP1014 – Ethernet Port Profile DMTF 1.0.
PAGE 369
HP_RegisteredProfile HP_GroupSystemSpecificCollectin -See HP Profile Registration Profile -See HP Consolidated Status Profile 1 HP_ElementConformsToProfile CIM_SoftwareIdentity HP_EthernetMemberOfCollection HP_EthernetCollection -Defined in this profile -See DMTF DSP 1023 Firmware Inventory Profile 1 1 CIM_ElementSoftwareIdentity 1 1 * 1 1 HP_EthernetGroupHostedCollection HP_EthernetMemberOfCollection HP_EthernetPort -Defined in this profile 1 HP_EthernetPortStatisticalData 1 1 HP_ComputerSy
PAGE 370
CIM_EthernetPort CIM_EthernetPortStatistics -See DMTF Ethernet Port Profile CIM_SystemDevice -See DMTF Ethernet Port Profile HP_EthernetPort HP_EthernetStatistics HP_EthernetDevice CIM_RedundancySet CIM_SystemSpecificCollection CIM_MemberOfCollection - HP_GroupRedundancySet -See HP Consolidated Status Profile HP_GroupSystemSpecificCollection -See HP Consolidated Status Profile HP_EthernetMemberOfCollection -See HP Consolidated Status Profile HP_EthernetTeam HP_EthernetCollection CIM_ElementS
PAGE 371
CIM_MemberOfCollection -See HP Consolidated Status Profile HP_EthernetTeamMember CIM_DeviceSAPImplementation -See DMTF Ethernet Port Profile HP_EthernetPortToLANEndpoint CIM_BindsToLANEndpoint -See DMTF Ethernet Port Profile HP_IPBindsToEthernetLANEndpoint -Role -MemberOperationalStatus -MemberStatusDescriptions CIM_HostedCollection CIM_Dependecy CIM_HostedAccessPoint -See DMTF Ethernet Port Profile HP_GroupHostedCollection HP_EthernetTeamToLANEndpoint HP_EthernetLANHostedAccessPoint CIM_LANEnd
PAGE 372
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.
PAGE 373
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.
PAGE 374
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.
PAGE 375
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.
PAGE 376
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.
PAGE 377
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.
PAGE 378
addition to the optional ControllerVersion property, when the controller version is of integer type.Methods None. 8.1 Profile Conventions for Operations Support for operations for each profile class (including associations) is specified in the following subclauses. Each sub-clause includes either a statement “All operations are supported as described by DSP200 v1.
PAGE 379
Table 5 – Operations: HP_EthernetTeamMember Operation Requirement Messages Associators Unspecified None AssociatorNames Unspecified None References Unspecified None ReferenceNames Unspecified None 8.6 HP_HostedEthernetTeam Table 6 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.
PAGE 380
Table 8 – Operations: HP_EthernetTeamToLANEndpoint Operation Requirement Messages Associators Unspecified None AssociatorNames Unspecified None References Unspecified None ReferenceNames Unspecified None 8.10 HP_EthernetLANHostedAccessPoint Table 9 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.
PAGE 381
Table 11 – Operations: HP_EthernetPortStatisticalData Operation Requirement Messages Associators Unspecified None AssociatorNames Unspecified None References Unspecified None ReferenceNames Unspecified None 8.14 HP_EthernetLANEndpointStatisticallData Table 12 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.
PAGE 382
Table 13– Operations: HP_EthernetMemberOfCollection Operation Requirement Messages Associators Unspecified None AssociatorNames Unspecified None References Unspecified None ReferenceNames Unspecified None 8.17 HP_EthernetGroupHostedCollection Table 14 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.
PAGE 383
profile1:HP_RegisteredProfile HP_EthernetMemberOfCollection HP_ElementConformstToProfile collection1:HP_EthernetCollection fw1:CIM_SoftwareIdentity CIM_ElementSoftwareIdentity HP_EthernetGroupHostedCollection port1:HP_EthernetPort HP_EthernetPortStatisticalData HP_EthernetDevice stats1:HP_EthernetStatistics HP_EthernetPortToLANEndpoint system1:HP_ComputerSystem HP_EthernetLANHostedAccessPoint endpoint1:HP_EthernetLANEndpoint HP_EthernetLANEndpointStatisticalData CIM_IPProtocolEndpoint HP_IPBindsT
PAGE 384
profile1:HP_RegisteredProfile HP_EthernetMemberOfCollection HP_ElementConformstToProfile collection1:HP_EthernetCollection fw1:CIM_SoftwareIdentity CIM_ElementSoftwareIdentity HP_EthernetGroupHostedCollection port1:HP_EthernetPort HP_EthernetortStatisticalData stats1:HP_EthernetStatistics HP_EthernetDevice HP_EthernetPortToLANEndpoint system1:HP_ComputerSystem stats2:HP_EthernetStatistics HP_EthernetLANHostedAccessPoint endpoint1:HP_EthernetLANEndpoint -VLANId: 1 -VLANName: One HP_EthernetLANEnd
PAGE 385
CIM_IPProtocolEndpoint CIM_IPProtocolEndpoint system1:HP_ComputerSystem HP_EthernetLANHostedAccessPoint HP_EthernetLANHostedAccessPoint HP_EthernetGroupHostedCollection collection1:HP_EthernetCollection HP_IPBindsToHPEthernetLANEndpoint HP_IPBindsToEthernetLANEndpoint HP_EthernetDevice HP_EthernetMemberOfCollection endpoint1:HP_EthernetLANEndpoint endpoint2:HP_EthernetLANEndpoint -VLANId: 1 -VLANName: One -VLANId: 2 -VLANName: Two HP_EthenetPortToLANEndpoint port1:HP_EthernetPort HP_EthernetP
PAGE 386
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.
PAGE 387
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.
PAGE 388
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.
PAGE 389
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.
PAGE 390
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.
PAGE 391
Table 15 – CIM Elements – HP Ethernet Teaming Profile Element Name Requirement Description 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.
PAGE 392
10.3 HP_EthernetTeam HP_EthernetTeam is used to represent a Team of Ethernet Ports in a managed system. Table 18 – Class: HP_EthernetTeam Properties 10.4 Requirement Notes 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.
PAGE 393
Properties 10.7 Requirement Notes VLANId Conditional See Section 7.6.2 VLANName Conditional See Section 7.6.3 HP_EthernetPortToLANEndpoint HP_EthernetPortToLANEndpoint is used to associate an Ethernet LAN Endpoint to an Ethernet Port in a managed system. Table 22 – Class: HP_EthernetPortToLANEndpoint Properties Requirement Notes Antecedent Mandatory Key: References HP_EthernetPort Dependent Mandatory Key: References HP_EthernetLANEndpoint 10.
PAGE 394
Table 26 – Class: HP_EthernetStatistics Properties Requirement Notes 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
PAGE 395
10.15 HP_EthernetMemberOfCollection HP_EthernetMemberOfCollection is used to associate Ethernet Ports and Ethernet Teams to the Ethernet Collection in a managed system. Table 30 – Class: HP_EthernetMemberOfCollection Properties Requirement Notes Collection Mandatory Key: References HP_EthernetCollection Member Mandatory Key: References HP_EthernetPort or HP_EthernetTeam 10.
PAGE 396
Table 343 – Class: HP_RegisteredProfile Properties ExtendedControllerVersion Requirement Conditional Notes See Section 7.17.1 11 Durable Names and Correlatable IDs Table 35 – Durable Names generated by this Profile Class HP_EthernetPort Durable Name(s) PermanentAddress Source ID Information Permanent MAC Address Circumstances for Change None Table 36 – Correlatable IDs generated by this Profile Class 38 Correlatable ID(s) Source ID Information Circumstances for Change Version 1.1.
PAGE 397
ANNEX A (normative) Change Log Version Date Description 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.
PAGE 398
ANNEX B (informative) Acknowledgments 40 Version 1.1.
PAGE 399
ANNEX C (informative) Included WBEM TC CR Numbers CR Number Date 00109 00117 Version 1.1.0 Title Ethernet Teaming on Proliant and Integrity Systems 1/9/2012 Added HP_EthernetPortController class and ExtendedControllerVersion property.
PAGE 400
Bibliography This section contains a list of the external references and dependencies for this specification. 42 Version 1.1.
PAGE 401
HP WBEM TC Document Number: P00119 Date: 04/22/2011 Version: 1.0.5 HP FC HBA Profile © Copyright 2006, 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.
PAGE 402
Contents Foreword ....................................................................................................................................................... 5 Introduction.................................................................................................................................................... 6 1 Scope ....................................................................................................................................................
PAGE 403
10.20 HPFCHBA_FCPortFCPortStatistics ......................................................................................... 25 10.21 HPFCHBA_FCPortLogicalPortGroup ....................................................................................... 26 10.22 HPFCHBA_FCPortSCSIProtocolEndpoint ............................................................................... 26 10.23 HPFCHBA_SCSIProtocolControllerFCPort .............................................................................. 26 10.
PAGE 404
Table 19 – Class: HPFCHBA_ComputerSystemSCSIProtocolController .................................................. 24 Table 20 – Class: HPFCHBA_ComputerSystemLogicalPortGroup ............................................................ 25 Table 21 – Class: HPFCHBA_ComputerSystemSoftwareIdentityDrv ........................................................ 25 Table 22 – Class: HPFCHBA_SystemServiceAccessPoint ........................................................................
PAGE 405
Foreword The HP FC HBA Profile P00119 was prepared by the HP WBEM TC. Version 1.0.
PAGE 406
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. 6 HP FC HBA Profile Version 1.0.
PAGE 407
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. 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.
PAGE 408
3.3 conditional used to indicate requirements strictly to be followed in order to conform to the document when the specified conditions are met 3.4 mandatory used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted 3.5 may used to indicate a course of action permissible within the limits of the document 3.6 need not used to indicate a course of action permissible within the limits of the document 3.
PAGE 409
4 Symbols and Abbreviated Terms 4.1 FC Fibre Channel 4.2 HBA Host Bus Adapter 5 Synopsis Profile Name: HP FC HBA Profile Version: 1.0.5 Organization: HP WBEM TC CIM Schema Version: 2.12 Central Class: HPFCHBA_ComputerSystem Scoping Class: CIM_ComputerSystem Extends: SMI-S 1.2.0, FC HBA Profile Specializes: HP WBEM TC P00107, HP Consolidated Status Profile The HP FC HBA profile extends SMI-S 1.2.
PAGE 410
Figure 1 – HP FC HBA Profile: Class Diagram 10 HP FC HBA Profile Version 1.0.
PAGE 411
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.
PAGE 412
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 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.
PAGE 413
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.
PAGE 414
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 ElementName property shall be implemented. This property contains a user friendly name for the HBA. 7.7.3 IdentifyingNumber IdentifyingNumber property shall be implemented.
PAGE 415
7.10.1 Classifications Classifications property shall be implemented. This property contains 11 (BIOS). 7.10.2 Name Name property shall be implemented. This property contains the port’s worldwide 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.
PAGE 416
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”.
PAGE 417
9 9.1 Use Cases 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. Version 1.0.
PAGE 418
Figure 2 – HP FC HBA Profile: Object Diagram 18 HP FC HBA Profile Version 1.0.
PAGE 419
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.
PAGE 420
Element Name Requirement Description 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.
PAGE 421
10.3 HPFCHBA_PortController HPFCHBA_PortController is is a logical device corresponding to a hardware network port controller. Table 6 – Class: HPFCHBA_PortController Properties Requirement Notes HPFCHBA_PortController CIM_PortController ControllerType Mandatory See Section 7.3.1 DeviceID Mandatory See Section 7.3.2 Name Mandatory See Section 7.3.3 10.4 HPFCHBA_FcPortStatistics HPFCHBA_FcPortStatistics is the set of statistics for the FC port.
PAGE 422
10.7 HPFCHBA_Product HPFCHBA_Product is used to aggregate physical element of the FC HBA. Table 10 – Class: HPFCHBA_Product Properties Requirement Notes HPFCHBA_Product CIM_Product ElementName Mandatory See Section 7.7.1 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.
PAGE 423
Table 13 – Class: HPFCHBA_FirmwareIdentityBIOS Properties Requirement Notes HPFCHBA_FirmwareIdentityBIOS CIM_SoftwareIdentity Classifications Mandatory See Section 7.10.1 Name Mandatory See Section 7.10.2 VersionString Mandatory See Section 7.10.3 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.
PAGE 424
10.13 HPFCHBA_GroupSystemSpecificCollection HPFCHBA_GroupSystemSpecificCollection is used to represent the group status of all FC HBAs. Table 16 – Class: HPFCHBA_GroupSystemSpecificCollection Properties Requirement Notes HPFCHBA_GroupSystemSpecificCollection HP_GroupSystemSpecificCollection GroupOperationalStatus Mandatory See Section 7.13.1 CIM_SystemSpecificCollection 10.
PAGE 425
10.17 HPFCHBA_ComputerSystemLogicalPortGroup HPFCHBA_ComputerSystemLogicalPortGroup is used to represent an association between HPFCHBA_ComputerSystem and HPFCHBA_LogicalPortGroup. Table 20 – Class: HPFCHBA_ComputerSystemLogicalPortGroup Properties Requirement Notes Antecedent Mandatory Key: References HPFCHBA_ComputerSystem Dependent Mandatory Key: References HPFCHBA_ LogicalPortGroup 10.
PAGE 426
10.21 HPFCHBA_FCPortLogicalPortGroup HPFCHBA_FCPortLogicalPortGroup is used to represent an association between HPFCHBA_FCPort and HPFCHBA_LogicalPortGroup. Table 24 – Class: HPFCHBA_FCPortLogicalPortGroup Properties Requirement Notes Member Mandatory Key: References HPFCHBA_FCPort Collection Mandatory Key: References HPFCHBA_LogicalPortGroup 10.
PAGE 427
10.25 HPFCHBA_PhysicalPackagePortController HPFCHBA_PhysicalPackagePortController is used to represent an association between HPFCHBA_PortController and HPFCHBA_PhysicalPackage. Table 28 – Class: HPFCHBA_PhysicalPackagePortController Properties Requirement Notes Antecedent Mandatory Key: References HPFCHBA_PhysicalPackage Dependent Mandatory Key: References HPFCHBA_ PortController 10.
PAGE 428
10.29 HPFCHBA_ProductPhysicalComponent HPFCHBA_ProductPhysicalComponent is used to represent an association between HPFCHBA_Product and HPFCHBA_PhysicalPackage. Table 32 – Class: HPFCHBA_ProductPhysicalComponent Properties Requirement Notes GroupComponent Mandatory Key: References HPFCHBA_Product PartComponent Mandatory Key: References HPFCHBA_PhysicalPackage 10.
PAGE 429
10.33 HPFCHBA_FCPortGroupSystemSpecific HPFCHBA_FCPortGroupSystemSpecific used to represent an association between CIM_FCPort and HPFCHBA_GroupSystemSpecificCollection. Table 36 – Class: HPFCHBA_FCPortGroupSystemSpecific Properties Requirement Notes Member Mandatory Key: References CIM_FCPort Collection Mandatory Key: References HPFCHBA_GroupSystemSpecificCollection 10.34 HP_RegisteredProfile The HP_RegisteredProfile class is defined by the HP Profile Registration Profile.
PAGE 430
11 Durable Names and Correlatable IDs Table 39 – Durable Names generated by this Profile Class Durable Name(s) Source ID Information 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 D
PAGE 431
ANNEX A (normative) Change Log Version Date Description 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 Version 1.0.
PAGE 432
ANNEX B (informative) Acknowledgments 32 HP FC HBA Profile Version 1.0.
PAGE 433
ANNEX C (informative) Included WBEM TC CR Numbers CR Number Date CR0111 8/31/2006 Version 1.0.
PAGE 434
Bibliography This section contains a list of the external references and dependencies for this specification. 34 HP FC HBA Profile Version 1.0.
PAGE 435
HP WBEM TC Document Number: P00120 Date: 03/01/10 Version: 1.0.1 HP Storage Enclosure Profile © Copyright 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.
PAGE 436
Contents Foreword ....................................................................................................................................................... 5 Introduction.................................................................................................................................................... 6 1 Scope ....................................................................................................................................................
PAGE 437
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 ...........................
PAGE 438
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 ....................
PAGE 439
Foreword The HP Storage Enclosure Profile (P00120) was prepared by the HP WBEM TC. Version 1.0.
PAGE 440
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. 6 Version 1.0.
PAGE 441
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 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.
PAGE 442
3.3 conditional used to indicate requirements strictly to be followed in order to conform to the document when the specified conditions are met 3.4 mandatory used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted 3.5 may used to indicate a course of action permissible within the limits of the document 3.6 need not used to indicate a course of action permissible within the limits of the document 3.
PAGE 443
5 Synopsis Profile Name: HP Storage Enclosure Profile Version: 1.0.1 Organization: HP WBEM TC CIM Schema Version: 2.18.1 Extends: DMTF DSP1011, Physical Asset Profile 1.0.2 The HP Storage Enclosure Profile extends the DMTF physical asset profile to add the ability to model and represent HP Storage Enclosures.
PAGE 444
6 Description See HP Profile Registration Profile HP_RegisteredProfile HP_ElementConformsToProfile CIM_ComputerSystem CIM_Chassis CIM_ComputerSystem see Referencing Profile (Array, HHRC) HP_StorageEnclosure SystemPackaging HP_StorageEnclosureProcessor SystemComponent CIM_PhysicalPackage ElementSoftwareIdentity Container HP_DriveCage SoftwareIdentity Enclosure Firmware See DMTF Software Identity Profile CIM_Container CIM_PhysicalPackage (Disk) CIM_Realizes HP_DiskDrive See SNIA Disk Drive Lit
PAGE 445
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.
PAGE 446
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.
PAGE 447
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.
PAGE 448
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. 8.
PAGE 449
9 9.
PAGE 450
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.
PAGE 451
External Storage Subsystem (MSA) Base Server Array Profile HPSA_PhysicalPackage: abcd Storage Subsystem CIM_ComputerSystem HPSA_ArraySystem:abcd SystemPackaging ComponentCS see Referencing Profile (HHRC) OperationalStatus[]=”2" SystemDevice PhysicalElementLocation HPSA_ArraySystemLocation: abcd ChassisName = “CHASS1” HPSA_SPIPort:abcd Front End Port = SCSI SystemComponent Container HPSA_StorageEnclosure:SE1 SystemPackaging HPSA_StorageEnclosureProcessor:SE1 Location=”2" (Internal) PhysicalEle
PAGE 452
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.
PAGE 453
HHRC Server Chassis HP_Chassis:CS1 HP_ComputerSystem:CS1 HPSA_PortController:abcd SystemComponent No Location info HP_ComputerSystemPackage Logicalidentity Internal Storage Enclosure Container HPSA_StorageEnclosureLocation: SE1 ElemInfoTagDesc = Box ElemtInfoTag = “1” SystemComponent HPSA_ArraySystem:abcd OperationalStatus[]=”2" PhysicalElementLocation HPSA_StorageEnclosure:SE1 SystemPackaging HPSA_StorageEnclosureProcessor:SE1 SystemPackaging Location=”1" (Internal) HPSA_PhysicalPackage: abcd
PAGE 454
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.
PAGE 455
Table 5 – Class: HP_StorageEnclosureProcessor Properties Requirement Notes 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.
PAGE 456
Table 7 – Class: HP_DriveCage Properties Requirement Notes CreationClassName M Key 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.
PAGE 457
Table 10 – Class: CIM_SystemContainer Properties Requirement Notes GroupComponent M Key, Containing physical package PartComponent M Key, CIM_PhysicalElement 10.7 HP_RegisteredProfile Implementation shall implement an instance of HP_RegisteredProfile in the Interop namespace with the values specified.
PAGE 458
ANNEX A (normative) Change Log 24 Version Date Description .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.
PAGE 459
ANNEX B (informative) Acknowledgments Version 1.0.
PAGE 460
ANNEX C (informative) Included WBEM TC CR Numbers 26 CR Number Date CR00113 8/23/06 Title Create HP Storage related profiles Version 1.0.
PAGE 461
Bibliography This section contains a list of the external references and dependencies for this specification. Version 1.0.
PAGE 462
HP WBEM TC Document Number: P00121 Date: 04/04/2011 Version: 2.0.0 HP Smart Array Profile © Copyright 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.
PAGE 463
Contents 1 SCOPE .................................................................................................................................................. 9 2 NORMATIVE REFERENCES ................................................................................................................ 9 2.1 2.2 2.3 APPROVED REFERENCES .................................................................................................................. 9 SNIA SMI-S 1.
PAGE 464
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.
PAGE 465
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.
PAGE 466
Figures Figure 1 – HP Smart Array profile: HHRC Class Diagram Figure 2 – HP Smart Array profile: HHRC SA specific Class Diagram Figure 3 – HP Smart Array profile: HHR Ports Class Diagram Figure 4 – HP Smart Array profile: Array Controller Class Diagram Figure 5 – HP Smart Array profile: Block Services Class Diagram Figure 6 – HP Smart Array profile: Disk Drive Lite class diagram Figure 7 – HP Smart Array profile: Extent Mapping Class Diagram Figure 8 – HP Smart Array profile: Disk Sparing Class Diagram Figu
PAGE 467
PAGE 468
Foreword The HP Smart Array Profile (P00121) was prepared by the HP WBEM TC. Version 2.0.
PAGE 469
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. 8 Version 2.0.
PAGE 470
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. 2 Normative References The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies.
PAGE 471
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 permi
PAGE 472
5 Synopsis Profile Name: HP Smart Array Profile Version: 2.0.0 Organization: HP WBEM TC CIM Schema Version: 2.22 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.
PAGE 473
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) 12 Version 2.0.
PAGE 474
6.
PAGE 475
The Host Hardware RAID Controller profile is used to model PCI based Smart Array HBAs.
PAGE 476
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.
PAGE 477
Product HP_ComputerSystem HP Base Server ComputerSystem HPSA_Product SystemComponent PortController HPSA_ArraySystem ProductPhysicalComponent PhysicalPackage SystemDevice HPSA_PhysicalPackage HPSA_PortController SystemPackaging LogicalIdentity CentralClass Realizes See DMTF Physical Asset Profile ComputerSystem ControlledBy SASPort SCSIProtocolEndPoint HPSA_ArrayController HPSA_ISASPort UsageRestriction:Backend Only DeviceSAPImplementation ComponentCS HPSA_SCSIProtocolEndpoint See HP Array C
PAGE 478
igure 2 – HP Smart Array profile: HHRC SA specific Class Diagram HPSA_ISASPort HPSA_SASPhy ConcreteComponent ElementStatisticalData HPSA_LogicalPortStatistics UsageRestriction:Backend Only DeviceSAPImplementation ElementStatisticalData HPSA_SASPhyStatistics HPSA_ATAProtocolEndpoint Role: Initiator HPSA_ATAInitiatorTargetLogicalUnitPath HPSA_SCSIProtocolEndpoint BindsTo Role: Initiator HPSA_SCSIInitiatorTargetLogicalUnitPath See SAS Initiator Ports HPSA_StorageExtent HPSA_StorageExtent Primor
PAGE 479
See Multiple Computer System RedundancySet HPSA_RedundancySet HPSA_ArraySystem SystemPackaging SystemComponent Central Class HostedCollection ComputerSystem HPSA_PhysicalPackage HPSA_ArrayController MemberOfCollection ComponentCS PhysicalPackage SystemPackaging HPSA_ArrayControllerPhysicalPackage Container HP_Location PhysicalElementLocation HP_Location PhysicalElementLocation HPSA_ArraySystemLocation See HP Location HPSA_ArrayControllerLocation See HP Location Figure 4 – HP Smart Array pr
PAGE 480
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).
PAGE 481
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.
PAGE 482
6.
PAGE 483
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). 22 Version 2.0.
PAGE 484
6.5 Extent Mapping HPSA_ArraySystem StoragePool HPSA_StoragePool HostedStoragePool Concrete Pool AllocatedFromStoragePool StorageVolume HPSA_StorageVolume SystemDevice ConcreteComponent BasedOn DiskDrive StorageExtent HPSA_StorageExtent Primoridal Extent 1 1 HPSA_DiskDrive SystemDevice MediaPresent Realizes Figure 7 – HP Smart Array profile: Extent Mapping Class Diagram The Extent Mapping profile (Defined in SNIA SMI-S version 1.0.
PAGE 485
6.6 Disk Sparing StorageExtent StoragePool HPSA_StoragePool StorageRedundancySet HPSA_StorageExtent ConcreteComponent HPSA_StorageExtent MemberOfCollection HPSA_StorageRedundancySet Concrete Pool HPSA_StorageExtent HPSA_StorageExtent IsSpare Spare Figure 8 – HP Smart Array profile: Disk Sparing Class Diagram The Disk Sparing profile is used to model spare drives for raid sets.
PAGE 486
6.
PAGE 487
6.
PAGE 488
Reason for Status If none of the Failed and none of the Degraded conditions are met OK 6.9 Monitoring and Performance (MNP) Data HPSA_ArraySystem SystemDevice CIM_MediaAccessStatData DiskDrive HPSA_MediaAccessStatData HPSA_DiskDrive ElementStatisticalData 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.
PAGE 489
ComputerSystem SoftwareIdentity HPSA_ArraySystem HPSA_Firmware InstalledSoftwareIdentity CentralClass ElementSoftwareIdentity 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.
PAGE 490
HPSA_ArraySystem HPSA_TSASSCSIProtocolEndpoint Target Port / SAS Target Port MediaPresent HPSA_DiskDriveStorageExtent HPSA_TSASSCSIProtocolEndpoint HPSA_DiskDrive CIM_SAPAvailableForElement HPSA_DiskDriveTSASSCSIPE CIM_DeviceSAPImplementation HPSA_TSASPortTSASSCSIPE DiskDrive Lite CIM_SystemDevice HPSA_ArraySystemStorageExtent HPSA_TSASPort CIM_SystemDevice HPSA_ArraySystemDiskDrive HPSA_TSASPort CIM_HostedAccessPoint HPSA_ArraySystemTSASSCSIPE CIM_SystemDevice HPSA_ArraySystemTSASPort HPSA_S
PAGE 491
HHRC HPSA_PortController LogicalIdentity HPSA_ArraySystemPortController HPSA_ArraySystem CIM_ControlledBy HPSA_PortControllerISASPort CIM_SystemDevice HPSA_ArraySystemISASPort HPSA_ISASPort CIM_HostedAccessPoint HPSA_ArraySystemISASSCSIPE HPSA_ISASPort CIM_DeviceSAPImplementation HPSA_ISASPortISASSCSIPE HPSA_ISASSCSIProtocolEndpoint HPSA_ISASSCSIProtocolEndpoint Initiator Port / SAS Initiator Figure 14 – HP Smart Array profile: Initiator Port Class Diagram Multi-path support The following figure s
PAGE 492
System HPSA_PortController ElementName: “Smart Array xxx in slot n” LogicalIdentity HPSA_ArraySystemPortController CIM_ComponentCS HPSA_ComputerSystemArraySystem HP_ComputerSystem SystemDevice (not currently populated by WMI) Consolidated Status HPSA_StorageSpecificCollection HPSA_ArraySystem CIM_SystemDevice HPSA_ArraySystemISASPort MemberOfCollection HPSA_StorageSpecificCollection ElementName: “Smart Array xxx in slot n” HPSA_ISASPort HPSA_ISASSCSIProtocolEndpoint Initiator Port / SAS Initiat
PAGE 493
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 PortController HP_ComputerSystem SystemDevice HP Base Server ControlledBy HPSA_PortController LogicalIdentity HPSA_ArraySystem CentralClass HPSA_ISASPort SystemDevice DeviceSAP Implementa tion HPSA_ISASSCSIProtocolEndPoint HostedAccessPoint Role: Initiator Connec
PAGE 494
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.
PAGE 495
HPSA_ArrayController.RebuildPriority Value indicates the current controller rebuild priority. Table 5 - HP Smart Array profile: HPSA_ArrayController.RebuildPriority Value 0 1 2 3 4 ValueMap Unknown Low Medium High N/A HPSA_ArrayController.ExpandPriority Value indicates the current controller expand priority. Table 6 - HP Smart Array profile: HPSA_ArrayController.ExpandPriority Value 0 1 2 3 4 ValueMap Unknown Low Medium High N/A HPSA_ArrayController.
PAGE 496
Value 0 1 2 3 ValueMap Unknown ACCEL_BATTERY ACCEL_CAPACITOR 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 0 1 2 3 4 ValueMap Unknown OK Failed Not Fully charged Not Present HPSA_ArrayController.CacheSizeTotal Total size of cache memory installed on the controller in bytes. HPSA_ArrayController.
PAGE 497
Value 0 1 2 3 4 ValueMap Unknown OK Temporarily disabled Permanently disabled 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.
PAGE 498
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.
PAGE 499
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 0 1 2 3 4 5 7.3.3 ValueMap Unknown Parallel SATA SAS SATALogical SASLogical HPSA_DiskDrive.MediaType Value indicates the media type of the disk. Table 166 - HP Smart Array profile: HPSA_DiskDrive.MediaType Value 0 1 2 7.3.4 ValueMap Unknown Rotational Platters Solid State HPSA_DiskDrive.
PAGE 500
Value 0 1 8 16 7.3.6 ValueMap Unknown SAS/SATA serial Narrow Wide 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.
PAGE 501
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.
PAGE 502
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.
PAGE 503
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 0 1 2 7.4.3 ValueMap Unknown Enabled Disabled HPSA_StorageVolume.
PAGE 504
Value ValueMap 0x8000 0x8001 0x8002 0x8003 0x8004 0x8005 0x8006 0x8007 0x8008 0x8009 0x800A OperationalStatus[0] Physical Drive improperly connected Expanding Overheated Overheating Interim Recovery Not Configured Not Yet Available Queued For Expansion Ready For Recovery Recovering Wrong Drive Replaced Degraded (3) Degraded (3) Degraded (3) Degraded (3) Degraded (3) Degraded (3) Degraded (3) Degraded (3) Degraded (3) Degraded (3) Degraded (3) Table 28 - HP Smart Array profile: HPSA_StorageVolume.
PAGE 505
Value 4 7.4.8 ValueMap Description 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 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.
PAGE 506
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.
PAGE 507
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.
PAGE 508
Value 3 5 7.8 ValueMap Passive Path Error 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.
PAGE 509
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.
PAGE 510
7.12.2 HPSA_ EncProtocolEndpoint.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.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 0 2 3 5 7.
PAGE 511
Value 4 32768 7.15 ValueMap Partitioned Connectivity/Passive 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. 8.1 Profile Conventions for Operations Support for operations for each profile class (including associations) is specified in the following subclauses.
PAGE 512
9 9.
PAGE 513
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.
PAGE 514
9.1.
PAGE 515
9.
PAGE 516
HP_ComputerSystem:88 RegisteredProfile HP Base Server SNIA “Array” HPSA_Product:02 ProductPhysicalComponent Name = “MSA500” ElementConformsToProfile PhysicalElementLocation HPSA_Location:02 HPSA_PhysicalPackage:02 HPSA_SPIPort:01 ElemInfoTagDesc = ChassisName ElemInfoTag = “BladeStor01” SystemPackaging HPSA_SCSIProtocolEndpoint:02 SystemDevice HPSA_ArraySystem:02 SystemComponent HostedAccessPoint Dedicated:3,15 ComponentCS SAPAvailableForElement HPSA_SCSIProtocolController:02 ProtocolContr
PAGE 517
9.2.
PAGE 518
9.
PAGE 519
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.
PAGE 520
9.
PAGE 521
9.
PAGE 522
9.
PAGE 523
9.8.1 Before drive failure HPSA_StorageExtent:001 OPStatus = “OK” MemberOfCollection ConcreteComponent HPSA_StoragePool:1 HPSA_StorageExtent:002 Concrete Pool OPStatus = “OK” HPSA_StorageRedundancySet:A HPSA_StorageExtent:003 OPStatus = “OK” AllocatedFromStoragePool HPSA_StorageExtent:004 IsSpare Spare OPStatus = “OK” HPSA_StorageVolume:100 OpStatus = “OK” Figure 27 - HP Smart Array profile: Disk sparing – Pre failure Figure 7 shows a three drive raid set with one spare drive.
PAGE 524
9.8.
PAGE 525
9.8.
PAGE 526
9.8.
PAGE 527
9.8.
PAGE 528
9.
PAGE 529
9.
PAGE 530
9.12 9.12.1 Multi-path support example 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.
PAGE 531
CIM_SystemDevice HPSA_ArraySystemISASPort HPSA_ArraySystem HPSA_ISASPort CIM_HostedAccessPoint HPSA_ArraySystemTSASSCSIPE HPSA_ISASSCSIProtocolEndpoint CIM_SystemDevice HPSA_ArraySystemTSASPort HPSA_ISASSCSIProtocolEndpoint CIM_HostedAccessPoint HPSA_ArraySystemISASSCSIPE HPSA_ISASPort CIM_DeviceSAPImplementation HPSA_ISASPortISASSCSIPE DiskDrive Lite Initiator Port / SAS Initiator HPSA_DiskDrive HPSA_TSASPort HPSA_TSASSCSIProtocolEndpoint CIM_SAPAvailableForElement HPSA_DiskDriveTSASSCSIPE CI
PAGE 532
System LogicalIdentity HPSA_ArraySystemPortController HPSA_PortController CIM_SystemDevice HPSA_ArraySystemISASPort CIM_ComponentCS HPSA_ComputerSystemArraySystem HP_ComputerSystem SystemDevice (not currently populated by WMI) Consolidated Status HPSA_StorageSpecificCollection MemberOfCollection HPSA_StorageSpecificCollection HPSA_ArraySystem HPSA_ISASPort HPSA_StorageVolume HPSA_ISASSCSIProtocolEndpoint HPSA_SCSIInitiatorTargetLogicalUnitPath CIM_HostedAccessPoint HPSA_ArraySystemTSASSCSIPE H
PAGE 533
10 CIM Elements The implementation requirements for the classes and properties described in this section are defined in the “Implementation Requirements” section (see Section 7). Table 34 – CIM Elements – HP Smart Array Profile Element Name Requirement Description Classes 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.
PAGE 534
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 CacheSerialN
PAGE 535
Table 37 – Class: HPSA_DiskDrive Properties Requirem ent 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.
PAGE 536
Table 39 – Class: HPSA_StorageVolume Properties Identify() 10.6 Requirement M Notes See Section 7.5.1 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.
PAGE 537
Properties Requirement Notes ManagedElement M Key, Ref CIM_ManagedElement Stats M Key, Ref CIM_StatisticalData 10.8 HP_RegisteredProfile Implementation shall implement an instance of HP_RegisteredProfile in the Interop namespace with the values specified.
PAGE 538
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.
PAGE 539
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.
PAGE 540
ANNEX B (Informative) Acknowledgments Version 2.0.
PAGE 541
ANNEX C (Informative) Included WBEM TC CR Numbers CR Number Date 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 Title Added new properties and operational status for Smart Drive Carrier Authentication. CR00173 4/06/2011 Added new classes to represent HPSA_SmartCarrierAppFirmware and HPSA_SmartCarrierBootldrFirmware for reporting Smart Drive Carrier FW information.
PAGE 542
Bibliography This section contains a list of the external references and dependencies for this specification. Version 2.0.
PAGE 543
HP WBEM TC Document Number: P00122 Date: 06/04/2012 Version: 2.1.0 HP SAS HBA Profile © Copyright 2012 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.
PAGE 544
Contents Foreword ....................................................................................................................................................... 5 Introduction.................................................................................................................................................... 6 1 Scope ....................................................................................................................................................
PAGE 545
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 ....................................................
PAGE 546
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 ...............
PAGE 547
Foreword The HP SAS HBA Profile (P00122) was prepared by the HP WBEM TC. Version 2.1.
PAGE 548
Introduction The information in this specification should be sufficient for a provider or consumer of this data to identify unambiguously the classes, properties, methods, and values that shall be instantiated and manipulated to represent HP SAS controller HBAs. The target audience for this specification is implementers who are writing CIM based providers or consumers of management interfaces representing the component described in this document. 6 Version 2.1.
PAGE 549
1 Scope The HP SAS HBA profile is an autonomous profile to describe management aspects of HP SAS HBA controllers and their attached storage devices. This profile extends certain profiles and sub-profiles defined in SNIA SMI-S version 1.2. 2 Normative References The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies.
PAGE 550
3.2 cannot used for statements of possibility and capability, whether material, physical or causal 3.3 conditional used to indicate requirements strictly to be followed in order to conform to the document when the specified conditions are met 3.4 mandatory used to indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted 3.5 may used to indicate a course of action permissible within the limits of the document 3.
PAGE 551
4 Symbols and Abbreviated Terms None. 5 Synopsis Profile Name: HP SAS HBA Profile Version: 2.0.0 Organization: HP WBEM TC CIM Schema Version: 2.18.1 Extends: SNIA Host Hardware RAID Controller profile. The HP SAS HBA Profile extends the SNIA HHRC profile to add the ability to model and represent HP SAS controllers. Central Class: HPSAS_PortController Table 1 – Related Profiles Profile Name Organization Version Relationship P00100 HP Profile Registration Profile HP WBEM TC 1.0.
PAGE 552
6.
PAGE 553
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.
PAGE 554
6.
PAGE 555
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.
PAGE 556
6.
PAGE 557
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.
PAGE 558
6.5 Disk Sparing StorageExtent StoragePool StorageRedundancySet HPSAS_StorageExtent MemberOfCollection ConcreteComponent HPSAS_StoragePool HPSAS_StorageRedundancySet Concrete Pool ConcreteComponent MemberOfCollection HPSAS_StorageExtent HPSAS_StorageExtent IsSpare Spare Figure 5 - HP SAS HBA profile: Disk Sparing Class Diagram The Disk Sparing profile is used to model spare drives for raid sets.
PAGE 559
HHRC CIM_RegisteredProfile SNIA “HHRC” HP_ExtendsProfile ComputerSystem PortController HP_RegisteredProfile HP WBEM TC “SAS HBA” Interop Namespace HPSAS_ArraySystem LogicalIdentity HPSAS_PortController CentralClass ElementConformsToProfile 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.
PAGE 560
6.
PAGE 561
6.8 Location information An instance of HP_Location sub class will be associated to applicable physical packages by CIM_PhysicalElementLocation. 6.9 Software Inventory Firmware version is supported for SAS HBAs. Firmware version will be reported in an instance of CIM_SoftwareIdentity as defined in DMTF Software Inventory profile DSP1023.
PAGE 562
7.1.2 HPSAS_DiskDrive.DriveConfiguration Indicates the how the drive has been configured by the controller. Supported values are: Table 4 - HP SAS HBA profile: HPSAS_DiskDrive.DriveConfiguration Value 0 1 2 3 4 7.1.3 ValueMap Unknown Unconfigured Data Spare Non RAID HPSAS_DiskDrive.DriveRotationalSpeed Value indicates the rotational speed of the drive in Revolutions per minute. 7.1.4 HPSAS_DiskDrive.
PAGE 563
• 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.
PAGE 564
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 0 1 2 3 4 5 7.1.11 ValueMap Unknown OK 56 day threshold passed 5 percent threshold passed 2 percent threshold passed SSD Wear Out HPSAS_DiskDrive.SmartCarrierAuthStatus This value indicates the status of the Smart Carrier Authentication if the controller supports hard drive and SmartCarrier Authentication.
PAGE 565
Table 7 - HP SAS HBA profile: HPSAS_StorageVolume.FaultTolerance Value 0 1 2 3 4 5 6 7 7.2.3 ValueMap Unknown RAID 0 RAID 1 RAID 1+0 RAID 4 RAID 5 RAID 51 RAID 6 HPSAS_StorageVolume.OSName This should display the volume name as it is known to the operating system if known otherwise it shall either show “Unknown” or not be assigned a value. 7.3 HPSAS_StorageExtent The HPSAS_StorageExtent class has been extended from CIM_StorageExtent class as defined in SNIA Block Services profile. 7.3.
PAGE 566
9.
PAGE 567
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.
PAGE 568
9.1.
PAGE 569
Figure 10 shows the physical instances for the same embedded SAS HBA. Instances of HP_Location classes are used to define location strings for each physical package. Version 2.1.
PAGE 570
9.
PAGE 571
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.
PAGE 572
The Non RAID pool shows one Storage Extent that is not part of any RAID configuration. 9.
PAGE 573
9.5 Disk Sparing - Drive failure example The following sections describe the implementation of Disk Sparing for SAS HBA controllers. 9.5.
PAGE 574
9.5.
PAGE 575
9.5.3 Drive Failed – Rebuild complete HPSAS_StorageExtent:001 OPStatus = “OK” MemberOfCollection ConcreteComponent HPSAS_StoragePool:1 HPSAS_StorageRedundancySet:A Concrete Pool ConcreteComponent MemberOfCollection HPSAS_StorageExtent:003 AllocatedFromStoragePool Spare OPStatus = “ERROR” IsSpare HPSAS_StorageExtent:004 OPStatus = “OK” HPSAS_StorageVolume:100 OpStatus = “OK” Figure 16 - HP SAS HBA profile: Drive Failed – Rebuild complete Figure shows that the rebuild operation has completed.
PAGE 576
9.5.
PAGE 577
we see that the “degraded” status of a logical drive has been consolidated into HPSAS_ArraySystem.OperationalStatus[0]. 9.
PAGE 578
10 CIM Elements The implementation requirements for the classes and properties described in this section are defined in the “Implementation Requirements” section (see Section 7). Table 8 – CIM Elements – HP SAS HBA Profile Element Name Requirement Description 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.
PAGE 579
Table 10 – Class: HPSAS_StorageVolume Properties Requirement Notes 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 Properties OSName 10.4 Requirement O Notes See Section 7.3.
PAGE 580
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 10=’Firmware’ in the [0] element. Manufacturer Mandatory Indicates the manufacturer of the firmware, e.g. “HP”.
PAGE 581
ANNEX A (normative) Change Log Version Date Description .001 09/08/06 Initial Draft .002 10/08/06 Updated per WBEM TC review 10/06/06 1.0.1 03/01/10 Verified the profile against SMI-S 1.3.0 spec for compliance and updated the Synopsis section with corresponding version number for individual profiles 1.0.1.001 03/04/10 Changed the version of the profile shown in the footers Added 2010 to copyright string 1.1.0 27/10/10 2.0.0 23/05/2011 Version 2.0.0 created from CR00172 2.1.
PAGE 582
ANNEX B (Informative) Acknowledgments 40 Version 2.1.
PAGE 583
ANNEX C (Informative) Included WBEM TC CR Numbers CR Number Date CR00112 9/08/06 Create HP Profile for HP SAS HBA CR00165 10/27/10 Clarification of SAS Profile Title 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 CR00172 05/23/2011 Add new properties and operational status for Solid State Drive life information.
PAGE 584
Bibliography This section contains a list of the external references and dependencies for this specification. 42 Version 2.1.
PAGE 585
HP WBEM TC Document Number: P00124 Date: 03/25/09 Version: 1.2.0 HP Location Profile © Copyright 2008, 2009 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.
PAGE 586
Contents Foreword ....................................................................................................................................................... 5 Introduction.................................................................................................................................................... 6 1 Scope ....................................................................................................................................................
PAGE 587
Figures Figure 1 – Location Class Diagram ............................................................................................................... 9 Figure 2 – Location Full Containment Implemented ................................................................................... 17 Figure 3 – Location without physical side of model .................................................................................... 18 Figure 4 – Typical Location Implementation ......................................
PAGE 588
Tables Table 1 – Related Profiles ............................................................................................................................. 9 Table 2 – ElementLocationTagDesc Values ............................................................................................... 12 Table 3 – LocationInfoDesc defined tags.................................................................................................... 13 Table 4 – CIM Elements – HP Profile Registration Profile ...........
PAGE 589
Foreword The HP Location Profile (P00124) was prepared by the HP WBEM TC. Version 1.2.
PAGE 590
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. 6 Version 1.2.
PAGE 591
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. 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.
PAGE 592
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.
PAGE 593
Extends: N/A Table 1 – Related Profiles Profile Name Organization Version Relationship Behavior None 6 Description CIM_ElementLocation HP_ElementLocation CIM_ManagedElement CIM_Location HP_Location ElementLocationTagDesc ElementLocationTag LocationInformation LocationInfoDesc Figure 1 – Location Class Diagram Figure 1 shows the class diagram for the Location Profile.
PAGE 594
7 Implementation Requirements 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.
PAGE 595
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.
PAGE 596
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.
PAGE 597
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.
PAGE 598
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.
PAGE 599
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.
PAGE 600
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.
PAGE 601
loc1:HP_Location ElementLocationTagDesc: Chassis ElementLocationTag: “2” LocationInformation[0] – (not used) LocationInfoDesc[0] – (not used) chassis2:CIM_Chassis HP_ElementLocation CIM_Container loc3:HP_Location ElementLocationTagDesc: Slot ElementLocationTag: “1” LocationInformation[0]: (not used) LocationInfoDesc[0]: (not used) CIM_Container chslt1:HP_Slot HP_ElementLocation HP_ComputerSystemPackage chassis1 : HP_ComputerSystemChassis chslt2:HP_Slot HP_ElementLocation system1: HP_ComputerSystem CI
PAGE 602
HP_ComputerSystemPackage chassis1 : HP_ComputerSystemChassis system1: HP_ComputerSystem CIM_SystemDevice loc1:HP_Location fan3:HP_Fan HP_ElementLocation ElementLocationTagDesc:Fan ElementLocationTag:”3" LocationInformation[0] – “1" LocationInfoDesc[0] – Slot LocationInformation[1] – “3” LocationInfoDesc[1] – Chassis LocationInformation[2] – “2" LocationInfoDesc[2] – Slot LocationInformation[3] – “2” LocationInfoDesc[3] – Chassis Figure 3 – Location without physical side of model A typical implementat
PAGE 603
HP_ComputerSystemPackage chassis1 : HP_ComputerSystemChassis system1: HP_ComputerSystem loc1:HP_Location ElementLocationTagDesc:Hood Tag ElementLocationTag:”Fan 1" LocationInformation[0] – (not used) LocationInfoDesc[0] – (not used) CIM_SystemDevice loc1:HP_Location fan3:HP_Fan HP_ElementLocation HP_ElementLocation ElementLocationTagDesc:Memory Module ElementLocationTag:”1" LocationInformation[0] – “1” LocationInfoDesc[0] – Socket mm1:HP_MemoryModule mem1:HP_Memory port1:CIM_LogicalPort HP_RealizesM
PAGE 604
Table 5 – Class: HP_Location Properties Requirement Notes 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.
PAGE 605
ANNEX A (normative) Change Log Version Date Description .001 8/21/06 Initial Draft .002 8/24/06 Incorporate feedback from 8/23 WBEM TC review. .003 6/4/07 Added Blade specific enumerations. Updated the following: 1.1.0 1.2.0 Version 1.2.0  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.
PAGE 606
ANNEX B (informative) Acknowledgments 22 Version 1.2.
PAGE 607
ANNEX C (informative) Included WBEM TC CR Numbers CR Number Date CR00143 9/11/08 Minor update 3/25/09 Version 1.2.
PAGE 608
Bibliography This section contains a list of the external references and dependencies for this specification. 24 Version 1.2.
PAGE 609
HP WBEM TC Document Number: P00125 Date: 4/8/09 Version: 2.1.0 HP Blade System Lite Profile © Copyright 2008, 2009 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.
PAGE 610
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.1.
PAGE 611
Contents 1 2 3 4 5 6 7 8 9 Scope ............................................................................................................................................. 7 Normative References ................................................................................................................... 7 2.1 Approved References .................................................................................................................... 7 2.2 References Under Development ................
PAGE 612
9.2 9.3 9.4 10 10.1 10.2 10.3 10.4 10.5 10.6 10.7 10.8 10.9 10.10 10.11 11 Determine if Server is a Blade ..................................................................................................... 19 Determine if Server is a Node ..................................................................................................... 20 Determine Blade or Node Location ............................................................................................. 20 CIM Elements ......................
PAGE 613
Foreword The HP Blade System Lite Profile P00125 was prepared by the HP WBEM TC. Version 2.1.
PAGE 614
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. 6 Version 2.1.
PAGE 615
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).
PAGE 616
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 permi
PAGE 617
5 Synopsis Profile Name: HP Blade System Lite Profile Version: 2.1.0 Organization: HP WBEM TC CIM Schema Version: 2.12 Central Class: HP_BladeEnclosureCS Scoping Class: Same as parent profile 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.
PAGE 618
6 Description HP_RegisteredProfile CIM_SoftwareIdentity (see HP Profile Registration Profile) (see DMTF DSP 1023 Software Inventory Profile) HP_BladeCSLocation 1 CIM_InstalledSoftwareIdentity HP_ElementConformsToProfile (see HP Profile Registration profile) (see HP Location Profile) Reference Blade bay or Server Node 1 1 1 * 1 CIM_ElementSoftwareIdentity 1 HP_BladeEnclosureCS Dedicated: 2 (Other) OtherDedicatedDescriptions: “Modular” for c-class; “Mult-node” for SL systems 0..
PAGE 619
HP_GroupSystemSpecificCollection CIM_MemberOfCollection see HP Consolidated Status profile see HP Consolidated Status profile HP_MemberOfBladeEnclosureCollection CIM_SystemComponent HP_GroupHostedCollection HP_BladeEnclosureCollection CIM_ComputerSystem see HP Consolidated Status profile HP_BladeEnclosureGroupHostedCollection HP_Location see HP Location profile HP_BladeSystemComponent HP_BladeEnclosureCS HP_BladeCSLocation HP_ElementLocation see HP Location profile HP_BladeCSElementLocation
PAGE 620
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.
PAGE 621
7.4.8 HP_BladeEnclosureCS.OperationalStatus This property shall be supported by the operational status of the shared enclosure sub-systems. Multinode 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.
PAGE 622
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. Multi-node server chassis that do not report status SHALL NOT populate this 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.
PAGE 623
8 Methods 8.1 Profile Conventions for Operations Support for operations for each profile class (including associations) is specified in the following subclauses. 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.
PAGE 624
8.10 HP_BladeCSElementLocation All other operations are supported as defined in DSP0200 v1.2. 9 Use Cases 9.
PAGE 625
loc1: HP_BladeCSLocation fw1:CIM_SoftwareIdentity profile1:CIM_RegisteredProfile RegisteredName: HP Blade System Lite ElementConformsToProfile ElementLocationTagDesc: Blade(24) ElementLocationTag: “blade1” LocationInfoDesc: Blade Bay(14) LocationInformation: “2” CIM_InstalledSoftwareIdentity CIM_ElementSoftwareIdentity encl1: HP_BladeEnclosureCS HP_BladeCSElementLocation MemberOfBladeEnclosureCollection HP_BladeSystemComponent system1: HP_ComputerSystem (blade) bcoll1:HP_BladeEnclosureCollection Bl
PAGE 626
MemberOfBladeEnclosureCollection Encl2: HP_BladeEnclosureCS loc3: HP_BladeCSLocation HP_BladeSystemComponent bcoll1:HP_BladeEnclosureCollection ElementLocationTagDesc: Blade(24) ElementLocationTag:"blade3" LocationInfoDesc: BladeBay(14) LocationInformation: "1" Blade3:CIM_ComputerSystem (blade) Dedicated:0 (Not Dedicated) HP_BladeCSElementLocation encl1: HP_BladeEnclosureCS MemberOfBladeEnclosureCollection HP_BladeCSElementLocation HP_BladeSystemComponent BladeEnclosureGroupHostedCollection blade1:
PAGE 627
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 rd th enclosure indicated by “encl1” and is present in the 3 and 4 blade bays.
PAGE 628
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”.
PAGE 629
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.
PAGE 630
Table 5 – Class – HP_RegisteredProfile Properties Requirement Notes RegisteredOrganization Mandatory Other (1) OtherRegisteredOrganization Mandatory “HP WBEM TC” RegisteredName Mandatory “HP Blade System Lite” RegisteredVersion Mandatory “2.1.0” 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.
PAGE 631
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.
PAGE 632
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 10=’Firmware’ in the [0] element. Manufacturer Mandatory Indicates the manufacturer of the firmware, e.g. “HP”.
PAGE 633
ANNEX A (normative) Change Log Version Date 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.
PAGE 634
ANNEX B (informative) Acknowledgments 26 Version 2.1.
PAGE 635
ANNEX C (informative) Included WBEM TC CR Numbers CR Number Date 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 Title CR00123 6/5/2007 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 Version 2.1.
PAGE 636
Bibliography This section contains a list of the external references and dependencies for this specification. 28 Version 2.1.
PAGE 637
HP WBEM TC Document Number: P00127 Date: 1/14/2011 Version: 2.0.0 HP Software Inventory and Update Profile © Copyright 2006, 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.
PAGE 638
CONTENTS Introduction.................................................................................................................................................... 3 1 Scope .................................................................................................................................................... 4 2 Normative References ........................................................................................................................... 4 2.1 Approved References ........
PAGE 639
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.
PAGE 640
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.) 2 Normative References The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies.
PAGE 641
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.
PAGE 642
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.
PAGE 643
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 Firmware Storage Device
PAGE 644
3.6 Bundles Bundle SoftwareIdentities will have the Classifications[] = “Software Bundle” as defined in the CIM_SoftwareIdentity MOF.
PAGE 645
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.
PAGE 646
system1: ComputerSystem HostedCollection SystemFWCollection : SystemSpecificCollection InstalledSoftwareIdentity InstalledSoftwareIdentity InstalledSoftwareIdentity MemberOfCollection MemberOfCollection InstalledSoftwareIdentity Swbun : SoftwareIdentity Classifications[0] : “Software Bundle” InstallState : Installed IdentityInfoTypes[] :{ “HPQ:SoftwareCategory”} IdentityInfoValues[] :{“System Firmware Recipie”} OrderedComponent AssignedSequence:0 Swid1: SoftwareIdentity Swid3 : SoftwareIdentity
PAGE 647
system1: ComputerSystem System2: ComputerSystem InstalledSoftwareIdentity HostedCollection swid1: SoftwareIdentity MajorVersion : 1 MinorVersion : 0 RevisionNumber : 10 BuildNumber : 20 VersionString : “1.0.10.20” IdentityInfoTypes[] :{ “HPQ:SoftwarePath”, “HPQ:SoftwareFamily”} IdentityInfoValues[] :{“C:\Program Files\hpwbem”, “HPQ:hpwmiver.
PAGE 648
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 providerspecific) to point to a file share of all possible installable components.
PAGE 649
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.
PAGE 650
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.
PAGE 651
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 7 Method is not supported in the implementation Table 5 – CIM_SoftwareRepositoryService.
PAGE 652
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.
PAGE 653
5.3 Software Repository Service Use Cases 5.3.1 Hierarchical Collections Figure 6 – SoftwareRepositoryService – Hierarchical Collections Version 2.0.
PAGE 654
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.
PAGE 655
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.
PAGE 656
ANNEX 1 (informative) Acknowledgments The authors wish to acknowledge the following people. Editor: • Kevin Brusky Contributors: 20 • Kevin BruskyBarbara Craig • Peter Mellquist • John Planow • Christina Shaw • Aaraj Thyagaraj HP Software Inventory and Update Profile Version 2.0.