A P P E N D I X A

Oracle’s Sun-Supported CIM Classes

This appendix identifies the properties for Oracle supported CIM classes

Topics include:

Document Conventions | Oracle_NumericSensor
Oracle_AssociatedIndicatorLED | Oracle_PhysicalAssetCapabilities
Oracle_AssociatedSensor | Oracle_PhysicalComponent
Oracle_Chassis | Oracle_PhysicalElementCapabilities
Oracle_ComputerSystem | Oracle_PhysicalMemory
Oracle_ComputerSystemPackage | Oracle_PhysicalPackage
Oracle_Container | Oracle_Processor
Oracle_ElementCapabilities | Oracle_ProcessorChip
Oracle_ElementConformsToProfile | Oracle_Realizes
Oracle_EnabledLogicalElementCapabilities | Oracle_RegisteredProfile
Oracle_HWCompErrorOkIndication | Oracle_RecordLog
Oracle_IndicatorLED | Oracle_ReferencedProfile
Oracle_InstCreation | Oracle_Sensor
Oracle_InstDeletion | Oracle_SpSystemComponent
Oracle_LogEntry | Oracle_SystemDevice
Oracle_LogManagesRecord | Oracle_ThresholdIndication
Oracle_Memory | Oracle_UseOfLog

##

Document Conventions

The following document conventions apply to this appendix:

- Each class table within this appendix describes only the properties supported by ILOM. For all possible properties of a class, see the corresponding DMTF CIM Schema 2.18.1 at:

`http://www.dmtf.org/standards/cim/cim_schema_v2181/`

- An Oracle Sun-specific property (added by Oracle Sun-derived classes) will have the word Sun-specific.

- Key-property rows are shown first in each class table, in alpha-numerical ascending order.

- Non-key-property rows are after key-property rows, in alpha-numerical ascending order.

- The term controller refers to the hardware entity on which management software resides, for example, the service processor (SP) or chassis monitoring module (CMM). The term controllee refers to the hardware entity that is controlled by the controller, for example, the host system (SYS) or the chassis (CH).

- As of ILOM 3.0.14, the Oracle Sun CIM classes have been renamed from Sun_xxx to Oracle_xxx. Prior to ILOM 3.0.14, the Oracle Sun CIM classes should be referenced as Sun_xxxx and not Oracle_xxx as described in this guide.

##

Oracle_AssociatedIndicatorLED

Description: | The `Oracle_AssociatedIndicatorLED` class associates an LED to a physical element.
Inheritance: | `CIM_Dependency`
Properties: | For a description of the supported properties for the `Oracle_AssociatedIndicatorLED` class, see TABLE A-1. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-1), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Indicator LED

Note - The Indicator LED profile specifies the `CIM_AssociatedIndicatorLED` class. However, the `CIM_AssociatedIndicatorLED` class does not exist in version 2.1.8.1 of the CIM Schema. Therefore, Oracle uses the `CIM_AssociatedIndicatorLED` class that is identified in the Experimental CIM Schema 2.18.1 and renamed it to `Oracle_AssociatedIndicatorLED`.

TABLE A-1 Properties for Oracle_AssociatedSensor
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`Antecedent` | `CIM_ManagedSystem` REF | The `Antecedent` property is a mandatory key property. Indicates the `ManagedSystemElement` that has an associated LED. | Object path to an instance of `CIM_ManagedSystemElement`.
`Dependent` `` `` | `Oracle_IndicatorLED` REF | The `Dependent` property is a mandatory key property. Represents the indicator LED of the managed element. | Object path to an instance of `Oracle_IndicatorLED`.

##

Oracle_AssociatedSensor

Description: | The `Oracle_AssociatedSensor` class associates a sensor to the physical element.
Inheritance: | CIM_AssociatedSensor
Properties: | For a description of the supported properties for the `Oracle_AssociatedSensor` class, see TABLE A-2. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-2), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Sensor

TABLE A-2 Properties for Oracle_AssociatedSensor
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`Antecedent` | `CIM_Sensor` REF | The `Antecedent` property is a mandatory key property. Represents the sensor for the managed element. | Object path to an instance of `CIM_Sensor`.
`Dependent` `` `` | `CIM_PhysicalElement` REF | The `Dependent` property is a mandatory key property. The `ManagedSystemElement` for which information is measured by the sensor. | `Object path to an instance of the CIM_PhysicalElement` `that the sensor belongs.`

##

Oracle_Chassis

Description: | The `Oracle_Chassis` class represents the physical elements that enclose other elements.
Inheritance: | CIM_Chassis
Properties: | For a description of the supported properties for the `Oracle_Chassis` class, see TABLE A-3. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-3), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Physical Asset

TABLE A-3 Properties for Oracle_Chassis
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`CreationClassName` | string | The `CreationClassName` property is a mandatory key property `CreationClassName` indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. | Set to `Oracle_Chassis`
`Tag` | string | The `Tag` property is a mandatory key property. The `Tag` property is an arbitrary string that uniquely identifies the physical element and serves as the key of the element. The `Tag` property can contain information such as asset tag or serial number data. The key for `PhysicalElement` is placed very high in the object hierarchy in order to independently identify the hardware or entity, regardless of physical placement in or on cabinets, adapters, and so on. For example, a hot-swappable or removable component can be taken from its containing (scoping) Package and be temporarily unused. The object still continues to exist and can be inserted into a different scoping container. Therefore, the key for `PhysicalElement` is an arbitrary string and is defined independently of any placement or location-oriented hierarchy. | Set to component NAC name
`CanBeFRUed` | boolean | The `CanBeFRUed` property is a boolean that indicates whether this `PhysicalElement` can be FRUed (TRUE) or not (FALSE). | Will be set to `TRUE` or `FALSE` depending on whether the component is considered to be a FRU by the platform.
`ChassisPackageTyp`e | uint16[] | The `ChassisPackageType` property indicates the physical form factor for the type of chassis. This property may have a value when the `PackageType` property contains the value 3 `Chassis Frame`. A value of 28 Blade Enclosure indicates the Chassis is designed to contain one or more `PhysicalPackage(s)` of `PackageType` 16 "Blade" or PackageType 17 "Blade Expansion". Definition type values include any of the following: {Unknown, Other, SMBIOS Reserved, Desktop, Low Profile Desktop, Pizza Box, Mini Tower, Tower, Portable, LapTop, Notebook, Hand Held, Docking Station, All in One, Sub Notebook, Space-Saving, Lunch Box, Main System Chassis, Expansion Chassis, SubChassis, Bus Expansion Chassis, Peripheral Chassis, Storage Chassis, SMBIOS Reseved, Sealed-Case PC, SMBIOS Reserved, CompactPCI, AdvancedTCA, Blade Enclosure, DMTF Reserved, Vendor Reserved} Values for the definition types are: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, .., 0x8000..0xFFFF} | Will be set to 17 (Main System Chassis)
`ChassisTypeDescription` | string | The `ChassisTypeDescription` is a string providing more information on the ChassisPackageType. | Will have appropriate description.
`Description` | string | Textual description of the object. | Will have appropriate description.
`ElementName` | string | The `ElementName` property is a user-friendly name. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note - The `Name` property of `ManagedSystemElement` is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where `Name` exists and is not a Key (such as for instances of `LogicalDevice`), the same information can be present in both the `Name` and `ElementName` properties. | Set to component NAC name.
`HealthState` | uint16[] | Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The following values apply: 0 (Unknown) - The implementation cannot report on `HealthState` at this time. 5 (OK) - The element is fully functional and is operating within normal operational parameters and without error. 10 (Degraded/Warning) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. 15 (Minor Failure) - All functionality is available but some might be degraded. 20 (Major Failure) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. 25 (Critical Failure) - The element is non-functional and recovery might not be possible. 30 (Non-recoverable Error) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. DMTF has reserved the unused portion of the continuum for additional health states in the future. | Will have appropriate value depending on whether the component is in error state or not.
`Manufacturer` | string | The `Manufacturer` property is the name of the organization responsible for producing the `PhysicalElement`. This organization might be the entity from whom the Element is purchased, but this is not necessarily true. The latter information is contained in the vendor property of `CIM_Product.` | Will have appropriate value if the chassis is considered a FRU by the platform.
`Model` | string | The `Model` property is the name by which the `PhysicalElement` is generally known. | Will have appropriate value if the chassis is considered a FRU by the platform.
`OperationalStatus` | uint16[] | The `OperationalStatus` property indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. Enumeration definitions can include any of the following: {Unknown, Other, OK, Degraded, Stressed, Predictive Failure, Error, Non-Recoverable Error, Starting, Stopping, Stopped, In Service, No Contact, Lost Communication, Aborted, Dormant, Supporting Entity in Error, Completed, Power Mode, DMTF Reserved, Vendor Reserved} Values for the above definition are as follows: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, .., 0x8000..} | `OperationalStatus[0]` will have appropriate value depending on whether the component is in error state or not.
`PartNumber` | string | Part number assigned by the organization that is responsible for producing or manufacturing the `PhysicalElement` | Will have appropriate value if the chassis is considered a FRU by the platform.
`SKU` | string | The SKU property is the stock-keeping unit number for this `PhysicalElement`. | Will have appropriate value if the chassis is considered a FRU by the platform.
`SerialNumber` | string | The SerialNumber property is a manufacturer-allocated number used to identify the physical element. | Will have appropriate value if the chassis is considered a FRU by the platform.
`StatusDescriptions` | string | That `StatusDescriptions` property describes the various `OperationalStatus` array values. For example, if `Stopping` is the value assigned to `OperationalStatus`, then this property may contain an explanation as to why an object is being stopped. Note that entries in this array are correlated with those at the same array index in `OperationalStatus`. | `StatusDescriptions`[0`]` will have appropriate description on the reason for the value of `OperationalStatus[`0`]`

##

Oracle_ComputerSystem

Description: | The `Oracle_ComputerSystem` class represents a special collection of Sun system managed elements. This collection provides computer capabilities and serves as an aggregation point to associate one or more of the following elements: file system, operating system, processor and memory (volatile and non-volatile storage).
Inheritance: | `CIM_ComputerSystem`
Properties | For a description of the supported properties for the `Oracle_ComputerSystem` class, see TABLE A-4. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-4), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profiles | Base Server Service Processor

TABLE A-4 Attributes for Oracle_ComputerSystem
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`CreationClassName` | string | The `CreationClassName` property is a mandatory key property. `CreationClassName` indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. | Set value to: `Oracle_ComputerSystem.`
`Name` | string | The `Name` attribute is a mandatory key CIM property. The inherited `Name` serves as the key of a system instance in an enterprise environment. | Implementation-dependent value representing unique ID of the `ComputerSystem`.
`Dedicated[]` | string | The `Dedicated[]` property enumerates the purpose(s) to which the `ComputerSystem` is dedicated, if any, and what functionality is provided. Functionality definitions can include any of the following: {Not Dedicated, Unknown, Other, Storage, Router, Switch, Layer 3 Switch, Central Office Switch, Hub, Access Server, Firewall, Print, I/O, Web Caching, Management, Block Server, File Server, Mobile User Device, Repeater, Bridge/Extender, Gateway, Storage Virtualizer, Media Library, ExtenderNode, NAS Head, Self-contained NAS, UPS, IP Phone, Management Controller, Chassis Manager, Host-based RAID controller, Storage Device Enclosure, Desktop, Laptop, Virtual Tape Library, Virtual Library System, DMTF Reserved, Vendor Reserved} Values for the above functionality definitions are as follows: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36..32567, 32568..65535} | For `ComputerSystem` instance representing the controller, the `Dedicated[0]` value will be set to `28` (Management Controller). For `ComputerSystem` instance representing the controllee, `Dedicated[0]` to `0` (Not Dedicated).
`ElementName` | string | The `ElementName` property is a user-friendly name. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note - The `Name` property of `ManagedSystemElement` is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where `Name` exists and is not a key (such as for instances of `LogicalDevice`), the same information can be present in both the `Name` and `ElementName` properties. | For `ComputerSystem` instance representing the controller, the `ElementName` will be set to the controller or hostname. For `ComputerSystem` instance representing the controllee, the `ElementName` will be set to the host product name.
EnabledDefault | string | The `EnabledDefault` property is an enumerated value indicating an administrator's default or startup configuration for the Enabled State of an element. By default, the element is `Enabled` (value=2). Element definitions include any of the following: {Enabled, Disabled, Not Applicable, Enabled but Offline, No Default, Quiesce, DMTF Reserved, Vendor Reserved} Values for the element definitions are as follows: {2, 3, 5, 6, 7, 9, .., 32768..65535} | `EnabledDefault` will be set to default value `2` (`Enabled`)
`EnabledState` | uint16[] | `EnabledState` is an integer enumeration that indicates the enabled and disabled states of an element. It can also indicate the transitions between these requested states. For example, `Shutting` `Down` (value=4) and `Starting` (value=10) are transient states between `enabled` and `disabled`. The following text briefly summarizes the various enabled and disabled states: Enabled (2) indicates that the element is or could be executing commands, will process any queued commands, and queues new requests. Disabled (3) indicates that the element will not execute commands and will drop any new requests. Shutting Down (4) indicates that the element is in the process of going to a Disabled state. Not Applicable (5) indicates the element does not support being enabled or disabled. Enabled but Offline (6) indicates that the element might be completing commands, and will drop any new requests. Test (7) indicates that the element is in a test state. Deferred (8) indicates that the element might be completing commands, but will queue any new requests. Quiesce (9) indicates that the element is enabled but in a restricted mode. Starting (10) indicates that the element is in the process of going to an Enabled state. New requests are queued. The following values apply: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11..32767, 32768..65535} Value definitions include: {Unknown, Other, Enabled, Disabled, Shutting Down, Not Applicable, Enabled but Offline, In Test, Deferred, Quiesce, Starting, DMTF Reserved, Vendor Reserved} | For `ComputerSystem` instance representing the controller, the `EnabledState` value will be set to `2` (Enabled). For `ComputerSystem` instance representing the controllee, the `EnabledState` value will be set to appropriate value depending on the power state of the controllee.
`HealthState` | uint16[] | Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The following values apply: 0 (Unknown) - The implementation cannot report on `HealthState` at this time. 5 (OK) - The element is fully functional and is operating within normal operational parameters and without error. 10 (Degraded/Warning) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. 15 (Minor Failure) - All functionality is available but some might be degraded. 20 (Major Failure) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. 25 (Critical Failure) - The element is non-functional and recovery might not be possible. 30 (Non-recoverable Error) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. DMTF has reserved the unused portion of the continuum for additional HealthStates in the future. | For `ComputerSystem` instance representing the controller `EnabledState` will be set to `5` (OK). For `ComputerSystem` instance representing the controllee `HealthState` will be set to appropriate value depending on the value of `OperationalStatus` property.
`IdentifyingDescriptions` | string | The `IdentifyingDescriptions` property is an array of free-form strings providing explanations and details behind the entries in the `OtherIdentifyingInfo` array. Note - Each entry of this array is related to the entry in `OtherIdentifyingInfo` that is located at the same index. | For `ComputerSystem` instance representing the controller, the `IdentifyingDescriptions` will not be set. For `ComputerSystem` instance representing the controllee, the `IdentifyingDescriptions` will be set to the following value: "`CIM:Model:SerialNumber`".
`OperationalStatus` | uint16[] | The `OperationalStatus` indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. However, a few are not and are described here in more detail in the `CIM_ComputerSystem.mof` described in the DMTF CIM schema v2.18.1 Element definitions include any of the following: {Unknown, Other, OK, Degraded, Stressed, Predictive Failure, Error, Non-Recoverable Error, Starting, Stopping, Stopped, In Service, No Contact, Lost Communication, Aborted, Dormant, Supporting Entity in Error, Completed, Power Mode, DMTF Reserved, Vendor Reserved} Values for the above definitions are: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, .., 0x8000..} | For `ComputerSystem` instance representing the controller, the `OperationalStatus[0]` will be set to `2` (OK). For `ComputerSystem` instance representing the controllee, the `OperationalStatus[0]` will be set to appropriate value depending on the power status (starting, stopping) or whether the host has incurred an error or is unknown.
`OtherEnabledState` | string | The `OtherEnabledState` property is a string that describes the enabled or disabled state of the element when the `EnabledState` property is set to `1` (Other). This property must be set to null when `EnabledState` is any value other than 1. | Will be set to empty string.
`OtherIdentifyingInfo` | Sting[] | The `OtherIdentifyingInfo` property captures additional data, beyond System Name information, that could be used to identify a `ComputerSystem`. One example would be to hold the Fibre Channel World-Wide Name (WWN) of a node. Note that if only the Fibre Channel name is available and is unique (able to be used as the System key), then this property would be NULL and the WWN would become the System key, its data placed in the `Name` property. | For `ComputerSystem` instance representing the controller, the `OtherIdentifyingInfo` will not be set. For `ComputerSystem` instance representing the controllee, the `OtherIdentifyingInfo[0]` will be set to the following value: `<product-name>:<SerialNumber>` For more details, refer to the DMTF Base Server Profile.
`RequestedState` | uint16[] | The `RequestedState` property is an integer enumeration that indicates the last requested or desired state for the element, irrespective of the mechanism through which it was requested. The actual state of the element is represented by `EnabledState`. This property is provided to compare the last requested and current enabled or disabled states. Element definitions include any of the following: {Unknown, Enabled, Disabled, Shut Down, No Change, Offline, Test, Deferred, Quiesce, Reboot, Reset, Not Applicable, DMTF Reserved, Vendor Reserved} Values for the above definitions are as follows: {0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, .., 32768..65535} Note - When `EnabledState` is set to `5` (Not Applicable), then this property has no meaning. | Will set to `Not` `Applicable` if there has not been any invocation of `RequestStateChange()` method. Will be set to the correct value of the incoming argument of `RequestStateChange().`
RequestStateChange() | UInt32 | Method for client to request state change. The following state change operations are as follows: {2 , 3, 4, 6, 7, 8, 9, 10, 11, .., 32768..65535"} Definitions for the above values are as follows: {Enabled, Disabled, Shut Down, Offline,Test, Defer, Quiesce, eboot, Reset, DMTF Reserved, Vendor Reserved"} | For `ComputerSystem` instance representing the controller, will support `11` (Reset). For `ComputerSystem` instance representing the controllee, will support `2` ( Enabled), `3` ( Disabled),`4` (Shut Down). This operation is only supported if the user has admin role.

##

Oracle_ComputerSystemPackage

Description: | The `Oracle_ComputerSystemPackage` class is used to associate the instance of `Oracle_ComputerSystem` representing the controllee to the physical package chassis, `Oracle_Chassis`, which realizes the `Oracle_ComputerSystem`.
Inheritance: | `CIM_ComputerSystemPackage`
Properties: | For a description of the supported properties for the `Oracle_ComputerSystemPackage` class, see TABLE A-5. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-5), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Physical asset Base server

TABLE A-5 Properties for Oracle_ComputerSystemPackage
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`Antecedent` | `Oracle_Chassis` REF | The `Antecedent` property is a mandatory key property. The chassis that realizes a `Oracle_ComputerSystem`. | Object path to an instance of `Oracle_Chassis`.
`Dependent` | `Oracle_ComputerSystem` REF | The `Dependent` property is a mandatory key property. Represents the `Oracle_ComputerSystem`. | Object path to the instance of `Oracle_ComputerSystem` representing the controllee.

##

Oracle_Container

Description: | `Oracle_Container` is used to associate a physical package (`CIM_PhysicalPackage`) and a physical element (`CIM_PhyscalElement`) contained in the physical package.
Inheritance: | `CIM_Container`
Properties: | For a description of the supported properties for the `Oracle_Container` class, see TABLE A-6. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-6), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Physical asset

TABLE A-6 Properties for Oracle_Container
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`GroupComponent` | `CIM_PhysicalPackage` REF | The `GroupComponent` property is a mandatory key property. The PhysicalPackage that contains other physical elements, including other packages. | Object path to an instance of `CIM_PhysicalPackage`.
`PartComponent` | `CIM_PhysicalElement` REF | The `PartComponent` property is a mandatory key property. The `PhysicalElement` which is contained in the package. | Object path to an instance of `CIM_ PhysicalElement`.

##

Oracle_ElementCapabilities

Description: | The `Oracle_ElementCapabilities` class is used to associate an instance of `ManagedElements` and its capabilities.
Inheritance: | `CIM_ElementCapabilities`
Properties: | For a description of the supported properties for the `Oracle_ElementCapabilities` class, see TABLE A-7. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-7), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Base server

TABLE A-7 Properties for Oracle_ElementCapabilities
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`Capabilities` | `CIM_Capabilities` REF | The `Capabilities` property is a mandatory key property. The `Capabilities` object that is associated with the element. | Object path to an instance of `Oracle_EnabledLogicalElementCapabilities`.
`ManagedElement` | `CIM_ManagedElement` REF | The `ManagedElement` property is a mandatory key property. Identifies the managed element. | Object path to an instance of `Oracle_ComputerSystem`.

##

Oracle_ElementConformsToProfile

Description: | `Oracle_ElementConformsToProfile` associates the instance of `Oracle_ComputerSystem` representing the controllee to the instance of `Oracle_RegisteredProfile` representing the Base Server Profile.
Inheritance: | `CIM_ElementConformsToProfile`
Properties: | For a description of the supported properties for the `Oracle_ElementConformsToProfile` class, see TABLE A-8. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-8), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Profile registration Base server

TABLE A-8 Properties for Oracle_ElementConformsToProfile
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`ElementConformsToProfile` | `Oracle_RegisteredProfile` REF | The `ElementconformsToProfile` property is a mandatory key property. The `RegisteredProfile` to which the `ManagedElement` conforms. | Object path to the instance of `Oracle_RegisteredProfile`.
`ManagedElement` ) | `Oracle_ComputerSystem` REF | The `ManagedElement` property is a mandatory key property. The `Oracle_ComputerSystem`. | Object path to the instance of `Oracle_ComputerSystem` representing the controllee.

##

Oracle_EnabledLogicalElementCapabilities

Description: | `EnabledLogicalElementCapabilities` describes the capabilities supported for changing the state of the associated `EnabledLogicalElement`.
Inheritance: | `CIM_EnabledLogicalElementCapabilities`
Properties: | For a description of the supported properties for the `Oracle_EnabledLogicalElementCapabilities` class, see TABLE A-9. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-9), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Base server

TABLE A-9 Properties for Oracle_EnabledLogicalElementCapabilities
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`InstanceID` | string | The `InstanceID` property is a mandatory key property. Within the scope of the instantiating Namespace, the `InstanceID` property uniquely identifies an instance of this class. The value of `InstanceID` should be constructed using the following preferred algorithm: `<OrgID>:<LocalID>` Where: `<OrgID>` and `<LocalID>` are separated by a colon ’:’ `<OrgID>` must include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating or defining the `InstanceID`, or is a registered ID that is assigned to the business entity by a recognized global authority (This is similar to the `<Schema Name>_<Class Name>` structure of Schema class names). `<OrgID>` must not contain a colon (’:’). The first colon to appear in `InstanceID` must appear between <`OrgID`> and <`LocalID`> . `<LocalID>` is chosen by the business entity and should not be re-used to identify different underlying (real-world) elements. For DMTF defined instances, the `<OrgID>` must be set to ’CIM’. If the above preferred algorithm is not used, the defining entity must ensure that the resultant `InstanceID` is not re-used across any instance IDs produced by this or other providers for this instance’s NameSpace. | Represents the unique ID of the `EnabledLogicalElementCapabilities.`
`Description` | string | Textual description of the object. | Appropriate descriptions.
`ElementName` | string | The `ElementName` property is a user-friendly name. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note that the `Name` property of `ManagedSystemElement` is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where `Name` exists and is not a Key (such as for instances of `LogicalDevice`), the same information can be present in both the `Name` and `ElementName` properties. | Appropriate value.
`ElementNameEditSupported` | boolean | The boolean indicates whether the `ElementName` can be modified. | Set to False.
`RequestedStatesSupported` | uint16[] | Indicates the possible states that can be requested when using the method `RequestStateChange` on the `EnabledLogicalElement`. The following values apply: {2, 3, 4, 6, 7, 8, 9, 10, 11} Definitions for the above values are as follows: {Enabled, Disabled, Shut Down, Offline, Test, Defer, Quiesce, Reboot, Reset} | For the `EnabledLogicalElementCapabilities` instance representing the controller, `RequestedStatesSupported`[0] will be set to `11` (Reset). For the `EnabledLogicalElementCapabilities` instance representing the controllee, `RequestedStatesSupported`[] will be set to `2` (Enabled), `3` (Disabled), or `4` (Shut Down).

##

Oracle_HWCompErrorOkIndication

Description: | When a client creates an indication subscription in which the filter indicates that it looks for `CIM_InstModification` in which the modified object is a `PhysicalElement` (that is the query statement is `SourceInstance` ISA `CIM_PhysicalElement`), and it looks for changes in `SourceInstance.OperationalStatus` or `SourceInstance.HealthState` then ILOM CIM-subsystem will generate `Oracle_HWCompErrorOkIndication` indication when it is noticed that a hardware component goes from good to bad, or vice versa.
Inheritance: | `CIM_InstModification`
Properties: | For a description of the supported properties for the `Oracle_HWCompErrorOkIndication` class, see TABLE A-10. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-10), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | None

TABLE A-10 Properties for Oracle_HWCompErrorOkIndication
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`PreviousInstance` | string | A copy of the previous instance whose change generated the Indication. `PreviousInstance` contains older values of an instance’s properties (as compared to `SourceInstance`), selected by the `IndicationFilter`’s query. | String representation of the previous instance of `CIM_PhysicalElement` that is affected.
`SensorObjectPath` `(`SUN-specific`)` | string | Object path of the sensor that causes the hardware component to change operational state. | Appropriate value.
`SourceInstance` | string | A copy of the instance that changed to generate the Indication. `SourceInstance` contains the current values of the properties selected by the indication filter’s query. In the case of `CIM_InstDeletion`, the property values are copied before the instance is deleted. | String representation of the instance of `CIM_PhysicalElement` that is affected.
`SourceInstanceHost` | string | The host name or IP address of the `SourceInstance`. | Will have the value `Oracle_ComputerSystem.Name` of the instance of `Oracle_ComputerSystem` representating the controllee.
`SourceInstanceModelPath` | string | The model path of the`SourceInstance`. The following format must be used to encode the model path: `<NamespacePath>:<ClassName>.<Prop1>=<Value1>, <Prop2>=\”<Value2>,` .. | String representation of the object path of the `SourceInstance`.

##

Oracle_IndicatorLED

Description: | The `Oracle_IndicatorLED` class models the logical aspects of an indicator LED.
Inheritance: | `CIM_IndicatorLED`
Properties: | For a description of the supported properties for the `Oracle_IndicatorLED` class, see TABLE A-11. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-11), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Indicator LED

Note - The Indicator LED profile specifies the `CIM_IndicatorLED` class.`` However, the `CIM_IndicatorLED` class does not exist in version 2.18.1 of the CIM Schema. Therefore, Oracle uses the `CIM_IndicatorLED` class that is identified in the Experimental CIM Schema version 2.18.1 and re-named it to `Oracle_IndicatorLED`.

TABLE A-11 Properties for Oracle_IndicatorLED
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`CreationClassName` | string | The `CreationClassName` property is a mandatory key property. `CreationClassName` indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. | Set to `Oracle_IndicatorLED`.
`DeviceID` | string | The `DeviceID` property is a mandatory key property. An address or other identifying information used to uniquely name the `LogicalDevice`. | Set to the NAC name of the of the LED.
`SystemCreationClassName` | string | The `SystemCreationClassName` property is a mandatory key property. The `SystemCreationClassName` of the scoping system. | Set to `Oracle_ComputerSystem.`
SystemName | string | The system name of the scoping system. | Will be set to `Oracle_ComputerSystem.Name` of the instance of `Oracle_ComputerSystem` that represents the controllee.
`ActivationState` | uint16[] | Indicates the current activity of an LED. An LED may exhibit behaviors that vary greatly in complexity. If the behavior of the LED is simple or a detailed depiction of the behavior is unnecessary to convey to client applications, values other than `5` (ControlPattern) may be used to indicate the behavior. If the behavior is complex and detailed information about the behavior is meaningful to a client, the value `5` (ControlPattern) can be used to indicate the ControlPattern property that describes the behavior. `2` (Lit) shall indicate the LED is continuously illuminated without variation in color or intensity. `3` (Blinking) shall indicate the LED is alternating between illuminated and not illuminated in a regular pattern without variation in color or intensity. The pattern is not indicated. `4` (Off) shall indicate the LED is not illuminated. `5` (ControlPattern) shall indicate the LED is exhibiting behavior that is described using the ControlPattern property. The following values apply: {2, 3, 4, 5, .., 32768..65535} Definitions for the above values are as follows: {Lit, Blinking, Off, Control Pattern, DMTF Reserved, Vendor Reserved} | Appropriate value.
`Color` | uint16[] | Indicates the current color of the LED. If the value of the `ActivationState` property is `4` (Off) this property will indicate the color of the LED the last time it was lit, or it will have the value `2` (Not Applicable). | Appropriate value.
`ControlMode` | uint16[] | Indicates the current control mode for the LED. `2` (Automatic) shall indicate the state of the LED is being controlled by the management infrastructure. `3` (Manual) shall indicate the state of the LED is being controlled by a management client. `4` (Test) shall indicate the LED is in a test mode. The following values apply: {2, 3, 4, .., 32768..65535} Definitions for the above values are as follows: {Automatic, Manual, Test, DMTF Reserved, Vendor Reserved} | Appropriate value.
`ControlPattern` | string | An LED may exhibit a range of behavior from very simple (ex. solid on) to very complicated (for example, a series of blinks of alternating color and duration). `ControlPattern` specifies the vendor or standard behavior exhibited by the LED if it cannot be described using one of the standard behaviors listed for the `ActivationState` property. If `ActivationState` has the value `5` (ControlPattern), the `ControlPattern` property shall not be NULL. The value of `ControlPattern` should be constructed using the following preferred algorithm: `<OrgID>::<Pattern>` Where: `<OrgID>` and < Pattern> are separated by two colons (::) `<OrgID>` includes a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the `ControlPattern` or that is a registered ID assigned to the business entity by a recognized global authority If the definition of the value is specified by the DMTF, the value of `<OrgID>` must be "DMTF" `<Pattern>` is chosen by the business entity and should not be reused to identify different underlying (real-world) behaviors. If the behavior specified for the LED adheres to a standard or proprietary specification, `<Pattern>` should be a uniquely assigned value identifying the behavior. If the behavior for the LED is described using a standard or proprietary grammar,`<Pattern>` should be prefixed with a uniquely assigned identifier for the grammar. | Appropriate value.
`ElementName` | string | Specifies an identifier for the LED. The value of `ElementName` should be constructed using the following preferred algorithm: `<OrgID>::<LocalID>` Where: `<OrgID>` and `<LocalID>` are separated by two colons (::) `<OrgID>` includes a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the `ControlPattern` or that is a registered ID assigned to the business entity by a recognized global authority `<LocalID>` is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. | Set to the NAC name of the LED.
`EnabledDefault` | uint16[] | An enumerated value indicating an administrator’s default or startup configuration for the enabled state of an element. By default, the element is `Enabled` (value=2). Valid values are as follows: {2, 3, 5, 6, 7, 9, .., 32768..65535} Definitions for the valid values are: {Enabled, Disabled, Not Applicable, Enabled but Offline, No Default, Quiesce, DMTF Reserved, Vendor Reserved} | Set to default value `2` (Enabled).
`EnabledState` | uint16[] | Integer enumeration that indicates the enabled and disabled states of an element. It can also indicate the transitions between these requested states. For example, `Shutting` `Down` (value=4) and `Starting` (value=10) are transient states between enabled and disabled. The following values apply: 0 (Unknown) 1 (Other) 2 (Enabled) - The element is or could be executing commands, will process any queued commands, and queues new requests. 3 (Disabled) - The element will not execute commands and will drop any new requests 4 (Shutting Down) - The element is in the process of going to a Disabled state. 5 (Not Applicable) - The element does not support being enabled or disabled. 6 (Enabled but Offline) - The element might be completing commands, and will drop any new requests. 7 (Test) - The element is in a test state. 8 (Deferred) - The element might be completing commands, but will queue any new requests. 9 (Quiesce) - The element is enabled but in a restricted mode. 10 (Starting) - The element is in the process of going to an Enabled state. New requests are queued. 11..32767 (DMTF Reserved) 32768..65539 (Vendor Reserved) | Appropriate value.
`HealthState` | uint16[] | Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The following values apply: 0 (Unknown) - The implementation cannot report on `HealthState` at this time. 5 (OK) - The element is fully functional and is operating within normal operational parameters and without error. 10 (Degraded/Warning) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. 15 (Minor Failure) - All functionality is available but some might be degraded. 20 (Major Failure) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. 25 (Critical Failure) - The element is non-functional and recovery might not be possible. 30 (Non-recoverable Error) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. DMTF has reserved the unused portion of the continuum for additional `HealthStates` in the future. | Appropriate value.
`IndicatedConditions` | uint16[] | The condition indicated by the LED. The following values apply: 2 (Not Applicable) - The LED is currently not assigned an interpretation. 3 (Location) - The LED is used to indicate the location of associated managed elements. 4 (Attention) - The LED is used to indicate the associated managed elements requires the attention of service personnel. 5 (Activity) -The LED is used to indicate activity is occurring for the associated managed elements. The type of activity indicated is specific to the associated managed elements. 6 (Powered On) - The LED is used to indicate if the associated managed elements are receiving power. 7 (Fault) - The LED is used to indicate if the associated managed elements are in a fault, error, or otherwise degraded state. | Appropriate value.
`OperationalStatus` | uint16[] | The `OperationalStatus` property indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. Enumeration values can include any of the following: {Unknown, Other, OK, Degraded, Stressed, Predictive Failure, Error, Non-Recoverable Error, Starting, Stopping, Stopped, In Service, No Contact, Lost Communication, Aborted, Dormant, Supporting Entity in Error, Completed, Power Mode, DMTF Reserved, Vendor Reserved} A list of valid values for the enumeration values include: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, .., 0x8000..} | Appropriate value.
`OtherIndicatedConditionDescription` | string | This property will have a value if `IndicatedCondition` contains the value `1` (Other). | Will have appropriate value if `IndicatedCondition` contains the value `1` (Other).
`RequestedState` | uint16[] | The `RequestedState` property is an integer enumeration that indicates the last requested or desired state for the element, irrespective of the mechanism through which it was requested. The actual state of the element is represented by`EnabledState.` This property is provided to compare the last requested and current enabled or disabled states. Element definitions include any of the following: {Unknown, Enabled, Disabled, Shut Down, No Change, Offline, Test, Deferred, Quiesce, Reboot, Reset, Not Applicable, DMTF Reserved, Vendor Reserved} Values for the above definitions include: {0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, .., 32768..65535} Note - When `EnabledState` is set to `5` ("Not Applicable"), then this property has no meaning. | Set to `12` (Not Applicable).

##

Oracle_InstCreation

Description: | When client creates an indication subscription in which the filter indicates that it looks for `CIM_InstCreation` and `SourceInstance` is a `PhysicalElement` (for example, the query statement contains S`ourceInstance` ISA `CIM_PhysicalElemen`t) then ILOM CIM-subsystem will generate `Oracle_InstCreation` indication when it notices that a hardware component is hot inserted into the chassis.
Inheritance: | `CIM_InstCreation`
Properties: | For a description of the supported properties for the `Oracle_InstCreation`, see TABLE A-12. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-12), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | None

TABLE A-12 Properties for Oracle_InstCreation
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`SourceInstance` | string | A copy of the instance that changed to generate the Indication. `SourceInstance` contains the current values of the properties selected by the Indication Filter’s Query. In the case of `CIM_InstDeletion`, the property values are copied before the instance is deleted. | String representation of the instance of `CIM_PhysicalElement` that is hot-inserted.
`SourceInstanceHost` | string | The host name or IP address of the `SourceInstance`. | Will have the value `Oracle_ComputerSystem.Name` of the instance of `Oracle_ComputerSystem` representing the controllee.
`SourceInstanceModelPath` | string | The model path of the `SourceInstance`. The following format must be used to encode the model path: <NamespacePath>:<ClassName>.<Prop1>=<Value1>, <Prop2>=\”<Value2>, ... | String representation of the object path of the `SourceInstance.`

##

Oracle_InstDeletion

Description: | When client creates an indication subscription in which the filter indicates that it looks for `CIM_InstDeletion` and `SourceInstance` is a `PhysicalElement` (for example, the query statement contains `SourceInstance` ISA `CIM_PhysicalElement`) then ILOM CIM-subsystem will generate `Oracle_InsDeletion` indication when it is noticed that a hardware component is hot removed from the chassis.
Inheritance: | `CIM_InstDeletion`
Properties: | For a description of the supported properties for the `Oracle_InstDeletion` class, see TABLE A-13. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-13), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | None

TABLE A-13 Properties for Oracle_InstDeletion
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`SourceInstance` | string | A copy of the instance that changed to generate the Indication. `SourceInstance` contains the current values of the properties selected by the indication filter’s query. In the case of `CIM_InstDeletion`, the property values are copied before the instance is deleted. | String representation of the instance of `CIM_PhysicalElement` that is hot-removed.
`SourceInstanceHost` | string | The host name or IP address of the `SourceInstance`. | Will have the value `Oracle_ComputerSystem.Name` of the instance of `Oracle_ComputerSystem` representing the controllee.
`SourceInstanceModelPath` | string | The model path of the `SourceInstance`. The following format must be used to encode the model path: <NamespacePath>:<ClassName>.<Prop1>=<Value1>, <Prop2>=\”<Value2>, ... | String representation of the object path of the `SourceInstance`.

##

Oracle_LogEntry

Description: | `Oracle_LogEntry` is used to represent individual log records of IPMI SEL log.
Inheritance: | `CIM_LogEntry`
Properties: | For a description of the supported properties for the `Oracle_LogEntry` class, see TABLE A-14. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-14), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Record log

TABLE A-14 Properties for Oracle_LogEntry
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`InstanceID` | string | The `InstanceID` property is a mandatory key property. Within the scope of the instantiating Namespace, `InstanceID` uniquely identifies an instance of this class. In order to ensure uniqueness within the NameSpace, the value of `InstanceID` should be constructed using the following preferred algorithm: `<OrgID>:<LocalID>` Where: `<OrgID>` and `<LocalID>` are separated by a colon ’:’ `<OrgID>` You must include a copyrighted, trademarked, or otherwise the unique name that is owned by the business entity creating or defining the `InstanceID`, or is a registered ID that is assigned to the business entity by a recognized global authority (This is similar to the <Schema Name>_<Class Name> structure of Schema class names.) `<OrgID>` must not contain a colon (’:’). When using this algorithm, the first colon to appear in `InstanceID` must appear between <`OrgID`> and <`LocalID`>. `<LocalID>` is chosen by the business entity and should not be re-used to identify different underlying (real-world) elements. For DMTF defined instances, the preferred algorithm must be used with the <`OrgID`> set to ’CIM’ If the above preferred algorithm is not used, the defining entity must ensure that the resultant `InstanceID` is not re-used across any `InstanceIDs` produced by this or other providers for this instance’s NameSpace. | Implementation dependent value representing unique ID.
`CreationTimeStamp` | datetime | A `LogEntry` may include a timestamp for the entry. | Appropriate value.
`Description` | string | Textual description of the object. | SEL event description.
`ElementName` | string | The `ElementName` property is a user-friendly name. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note - The `Name` property of `ManagedSystemElement` is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where `Name` exists and is not a Key (such as for instances of `LogicalDevice`), the same information can be present in both the `Name` and `ElementName` properties. | SEL event record ID.
`LogInstanceID` | string | The string containing the log’s `InstanceID`. | Implementation dependent value representing unique ID of the associated `Oracle_RecordLog`.
`LogName` | string | The string containing the log’s `Name.` This property is available for backwards continuity with `CIM_LogRecord`. | Will have the value "SEL Log".
`RecordData` | string | A string containing `LogRecord` data. If the corresponding `RecordFormat` property is <empty>, or cannot be parsed according to the recommended format, `RecordData` should be interpreted as a free-form string. If the `RecordFormat` property contains parseable format information (as recommended in the `RecordFormat` Description qualifier), the `RecordData` string should be parsed in accordance with this format. In this case, `RecordData` should begin with the delimiter character and this character should be used to separate substrings in the manner described. The `RecordData` string can then be parsed by the data consumer and appropriately typed. | Contents of the SEL event data.
`RecordFormat` | string | A string describing the data structure of the information in the property, `RecordData`. If the `RecordFormat` string is <empty>, `RecordData` should be interpreted as a free-form string. To describe the data structure of `RecordData`, the `RecordFormat` string should be constructed as follows: The first character is a delimiter character and is used to parse the remainder of the string into sub-strings. Each sub-string is separated by the delimiter character and should be in the form of a CIM property declaration (for example, datatype and property name). This set of declarations may be used to interpret the similarly delimited `RecordData` property. For example, using a ’*’ delimiter: `RecordFormat` `=` "*string ThisDay*uint32 ThisYear*datetime SomeTime" may be used to interpret: `RecordData` = "*This is Friday*2002*20020807141000.000000-300". | Will have the format used for interpreting the `RecordData` property.
`RecordID` | string | Provides a representation of log entry ordering or pointers and handles for log entries | SEL event record ID.

##

Oracle_LogManagesRecord

Description: | `Oracle_LogManagesRecord` is used to associate the instance of `Oracle_RecordLog` representing the IPMI SEL log to an instance of SEL log record.
Inheritance: | `CIM_LogManagesRecord`
Properties: | For a description of the supported properties for the `Oracle_LogManagesRecord` class, see TABLE A-15. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-15), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Record log

TABLE A-15 Properties for Oracle_LogManagesRecord
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`Log` | `Oracle_RecordLog` REF | The `Log` property is a mandatory key property. Indicates the `Oracle_RecordLog`. | Object path to the instance of `Oracle_RecordLog` representing the IPMI SEL log.
`Record` | `Oracle_LogEntry` REF | The `Record` property is a mandatory key property. Indicates the `Oracle_LogEntry`. | Object path to an instance of `Oracle_LogEntry`.

##

Oracle_Memory

Description: | Provides capabilities and management of memory-related LogicalDevices.
Inheritance: | `CIM_Memory`
Properties: | For a description of the supported properties for the `Oracle_Memory` class, see TABLE A-16. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-16), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | System Memory

TABLE A-16 Properties for Oracle_Memory
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`CreationClassName` | string | The `CreationClassName` property is a mandatory key property. `CreationClassName` indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. | Set to `Oracle_Memory`.
`DeviceID` | string | The `DeviceID` property is a mandatory key property. An address or other identifying information used to uniquely name the `LogicalDevice`. | Implementation dependent value representing unique ID.
`SystemCreationClassName` | string | The `SystemCreationClassName` property is a mandatory key property. Indicates the System`CreationClassName` of the scoping system. | Set to `Oracle_ComputerSystem`.
`SystemName` | string | The `SystemName` property is a mandatory key property. Indicates the `SystemName` of the scoping system. | Will be set to `Oracle_ComputerSystem`.`Name` of the instance of `Oracle_ComputerSystem` that represents the controllee.
`Access` | uint16[] | The `Access` property describes whether the media is readable (value=1), writeable (value=2), or both (value=3). Unknown (0) and Write Once (4) can also be defined. The following values apply: {0, 1, 2, 3, 4} Definitions for the above values are: {Unknown, Readable, Writeable, Read/Write Supported, Write Once} | Set to `3` (Read/Write Supported).
`BlockSize` | uint16[] | Size in bytes of the blocks that form this `StorageExtent`. If the block size is variable, then the maximum block size in bytes should be specified. If the block size is unknown or if a block concept is not valid (for example, for AggregateExtents, Memory or LogicalDisks), enter a `1`. | Set to appropriate value if memory size can be computed.
`ElementName` | string | The `ElementName` property is a user-friendly name. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note - The `Name` property of `ManagedSystemElement` is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where `Name` exists and is not a Key (such as for instances of `LogicalDevice`), the same information can be present in both the `Name` and `ElementName` properties. | Appropriate value.
`EnabledDefault` | uint16[] | Enumerated value indicating an administrator’s default or startup configuration for the enabled state of an element. By default, the element is `2` (Enabled). The following values apply: {2, 3, 5, 6, 7, 9, .., 32768..65535} Definitions for the above values are: {Enabled, Disabled, Not Applicable, Enabled but Offline, No Default, Quiesce, DMTF Reserved, Vendor Reserved} | Set to default value `2` (Enabled).
`EnabledState` | uint16[] | Integer enumeration that indicates the enabled and disabled states of an element. It can also indicate the transitions between these requested states. For example, `Shutting` `Down` (value=4) and `Starting` (value=10) are transient states between enabled and disabled. The following values apply: 0 (Unknown) 1 (Other) 2 (Enabled) - The element is or could be executing commands, will process any queued commands, and queues new requests. 3 (Disabled) - The element will not execute commands and will drop any new requests. 4 (Shutting Down) - The element is in the process of going to a Disabled state. 5 (Not Applicable) - The element does not support being enabled or disabled. 6 (Enabled but Offline) - The element might be completing commands, and will drop any new requests. 7 (Test) - The element is in a test state. 8 (Deferred) - The element might be completing commands, but will queue any new requests. 9 (Quiesce) - The element is enabled but in a restricted mode. 10 (Starting) - The element is in the process of going to an Enabled state. New requests are queued. 11..32767 (DMTF Reserved) 32768..65539 (Vendor Reserved) | Appropriate value.
`HealthState` | uint16[] | Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The following values apply: 0 (Unknown) - The implementation cannot report on `HealthState` at this time. 5 (OK) - The element is fully functional and is operating within normal operational parameters and without error. 10 (Degraded/Warning) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. 15 (Minor Failure) - All functionality is available but some might be degraded. 20 (Major Failure) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. 25 (Critical Failure) - The element is non-functional and recovery might not be possible. 30 (Non-recoverable Error) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. DMTF has reserved the unused portion of the continuum for additional health states in the future. | Appropriate value.
`NumberOfBlocks` | uint16[] | Total number of logically contiguous blocks, of size `BlockSize`, which form this Extent. The total size of the Extent can be calculated by multiplying `BlockSize` by `NumberOfBlocks`. If the `BlockSize` is `1`, this property is the total size of the Extent. | Will have appropriate value if memory size can be computed.
`OperationalStatus` | uint16[] | The `OperationalStatus` property indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. Enumeration values can include any of the following: {Unknown, Other, OK, Degraded, Stressed, Predictive Failure, Error, Non-Recoverable Error, Starting, Stopping, Stopped, In Service, No Contact, Lost Communication, Aborted, Dormant, Supporting Entity in Error, Completed, Power Mode, DMTF Reserved, Vendor Reserved} Possible values for the enumeration values include: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, .., 0x8000..} | Appropriate value.
`RequestedState` | uint16[] | The `RequestedState` property is an integer enumeration that indicates the last requested or desired state for the element, irrespective of the mechanism through which it was requested. The actual state of the element is represented by `EnabledState`. This property is provided to compare the last requested and current enabled or disabled states. Element definitions include any of the following: {Unknown, Enabled, Disabled, Shut Down, No Change, Offline, Test, Deferred, Quiesce, Reboot, Reset, Not Applicable, DMTF Reserved, Vendor Reserved} Values for the above definitions include: {0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, .., 32768..65535} Note - When `EnabledState` is set to 5 (Not Applicable), then this property has no meaning. | Set to `12` (Not Applicable).

##

Oracle_NumericSensor

Description: | A numeric sensor that returns numeric readings and optionally supports thresholds settings.
Inheritance: | `CIM_NumericSensor`
Properties: | For a description of the supported properties for the `Oracle_NumericSensor` class, see TABLE A-17. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-17), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Sensor

TABLE A-17 Properties for Oracle_NumericSensor
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`CreationClassName` | string | The `CreationClassName` property is a mandatory key property. `CreationClassName` indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. | Set to `Oracle_NumericSensor`.
`DeviceID` | string | The `DeviceID` property is a mandatory key property. An address or other identifying information used to uniquely name the `LogicalDevice`. | Set to the NAC name of the sensor.
`SystemCreationClassName` | string | The `SystemCreationClassName` property is a mandatory key property. Indicates the `CreationClassName` for the scoping system. | Will be set to `Oracle_ComputerSystem.Name` of the instance of `Oracle_ComputerSystem` which represents the controllee.
`SystemName` | string | The `SystemName` property is a mandatory key property. Indicates the `SystemName` of the scoping system. | Set to `Oracle_ComputerSystem.Name` of the instance of `Oracle_ComputerSystem` that represents the controllee.
`BaseUnits` | uint16[] | The base unit of the values returned by this sensor. All the values returned by this sensor are represented in the units obtained by (`BaseUnits` * `10` raised to the power of the `UnitModifier`). For example, if `BaseUnits` is Volts and the `UnitModifier` is -6, then the units of the values returned are microvolts. However, if the `RateUnits` property is set to a value other than None, then the units are further qualified as rate units. In the above example, if `RateUnits` is set to Per Second, then the values returned by the sensor are in microvolts/second. The units apply to all numeric properties of the sensor, unless explicitly overridden by the units qualifier. The following values apply: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66} Definitions of above values are: {Unknown, Other, Degrees C, Degrees F, Degrees K, Volts, Amps, Watts, Joules, Coulombs, VA, Nits, Lumens, Lux, Candelas, kPa, PSI, Newtons, CFM, RPM, Hertz, Seconds, Minutes, Hours, Days, Weeks, Mils, Inches, Feet, Cubic Inches, Cubic Feet, Meters, Cubic Centimeters, Cubic Meters, Liters, Fluid Ounces, Radians, Steradians, Revolutions, Cycles, Gravities, Ounces, Pounds, Foot-Pounds, Ounce-Inches, Gauss, Gilberts, Henries, Farads, Ohms, Siemens, Moles, Becquerels, PPM (parts/million), Decibels, DbA, DbC, Grays, Sieverts, Color Temperature Degrees K, Bits, Bytes, Words (data), DoubleWords, QuadWords, Percentage, Pascals} | Appropriate value depending on sensor type.
`CurrentReading` | sint32 | The current value indicated by the sensor. | Appropriate value.
`CurrentState` | string | The current state indicated by the sensor. This is always one of the PossibleStates. | Appropriate value representing current state of the sensor.
`ElementName` | string | The `ElementName` property is a user-friendly name. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note - The `Name` property of `ManagedSystemElement` is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where `Name` exists and is not a Key (such as for instances of `LogicalDevice`), the same information can be present in both the `Name` and `ElementName` properties. | Set to the NAC name of the sensor.
`EnabledDefault` | uint16[] | An enumerated value indicating an administrator’s default or startup configuration for the enabled state of an element. By default, the element is Enabled (value=2). The following values apply: {2, 3, 5, 6, 7, 9, .., 32768..65535} Definitions of the above values are: {Enabled, Disabled, Not Applicable, Enabled but Offline, No Default, Quiesce, DMTF Reserved, Vendor Reserved} | Set to default value `2` (Enabled).
`EnabledState` | uint16[] | Integer enumeration that indicates the enabled and disabled states of an element. It can also indicate the transitions between these requested states. For example, Shutting Down (value=4) and Starting (value=10) are transient states between enabled and disabled. The following values apply: 0 (Unknown) 1 (Other) 2 (Enabled) - The element is or could be executing commands, will process any queued commands, and queues new requests. 3 (Disabled) - The element will not execute commands and will drop any new requests. 4 (Shutting Down) - The element is in the process of going to a Disabled state. 5 (Not Applicable) - The element does not support being enabled or disabled. 6 (Enabled but Offline) - The element might be completing commands, and will drop any new requests. 7 (Test) - The element is in a test state. 8 (Deferred) - The element might be completing commands, but will queue any new requests. 9 (Quiesce) - The element is enabled but in a restricted mode. 10 (Starting) - The element is in the process of going to an Enabled state. New requests are queued. 11..32767 (DMTF Reserved) 32768..65539 (Vendor Reserved) | Will have appropriate value depending on whether the sensor is enabled, disabled or unknown.
`HealthState` | uint16[] | Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The following values apply: 0 (Unknown) - The implementation cannot report on `HealthState` at this time. 5 (OK) - The element is fully functional and is operating within normal operational parameters and without error. 10 (Degraded/Warning) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. 15 (Minor Failure) - All functionality is available but some might be degraded. 20 (Major Failure) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. 25 (Critical Failure) - The element is non-functional and recovery might not be possible. 30 (Non-recoverable Error) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. DMTF has reserved the unused portion of the continuum for additional health states in the future. | Appropriate value.
`LowerThresholdCritical` | sint32 | The sensor’s threshold values specify the ranges (min and max values) for determining whether the sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the `CurrentReading` is between `LowerThresholdCritical` and `Lower` `ThresholdFatal`, then the `CurrentState` is Critical. | Will have appropriate value if sensor supports this threshold. If sensor does not support this threshold, this property will not be set.
`LowerThresholdFatal` | sint32 | The sensor’s threshold values specify the ranges (min and max values) for determining whether the sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the `CurrentReading` is below `LowerThresholdFatal`, then the current state is Fatal. | Will have appropriate value if sensor supports this threshold. If sensor does not support this threshold, this property will not be set.
`OperationalStatus` | uint16[] | The `OperationalStatus` property indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. Enumeration definitions can include any of the following: {Unknown, Other, OK, Degraded, Stressed, Predictive Failure, Error, Non-Recoverable Error, Starting, Stopping, Stopped, In Service, No Contact, Lost Communication, Aborted, Dormant, Supporting Entity in Error, Completed, Power Mode, DMTF Reserved, Vendor Reserved} Values for the enumeration definitions are as follows: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, .., 0x8000..} | Will have appropriate value.
`PossibleStates` | string | `PossibleStates` enumerates the string outputs of the sensor. For example, a switch sensor may output the states On, or Off Another implementation of the switch might output the states Open and Close. Another example is a `NumericSensor` supporting thresholds. This sensor can report the states like Normal, Upper Fatal, Lower Non-Critical, etc. A `NumericSensor` that does not publish readings and thresholds, but can store the data internally and still report its states. | Will have appropriate values depending on the type of the sensor.
`RateUnits` | uint16[] | Specifies if the units returned by this sensor are rate units. All the values returned by this Sensor are represented in the units obtained by (`BaseUnits` * 10 raised to the power of the `UnitModifier`). This is true unless this property (`RateUnits`) has a value different than "None". For example, if `BaseUnits` is Volts and the `UnitModifier` is -6, then the units of the values returned are microvolts. But, if the `RateUnits` property is set to a value other than "None", then the units are further qualified as rate units. In the above example, if `RateUnits` is set to "Per Second", then the values returned by the Sensor are in microvolts/second. The units apply to all numeric properties of the Sensor, unless explicitly overridden by the Units qualifier. Any implementation of `CurrentReading` should be qualified with either a Counter or a Gauge qualifier, depending on the characteristics of the sensor being modeled. | Will be set to 0.
`RequestedState` | uint16[] | The `RequestedState` property is an integer enumeration that indicates the last requested or desired state for the element, irrespective of the mechanism through which it was requested. The actual state of the element is represented by `EnabledState`. This property is provided to compare the last requested and current enabled or disabled states. Element definitions include any of the following: {Unknown, Enabled, Disabled, Shut Down, No Change, Offline, Test, Deferred, Quiesce, Reboot, Reset, Not Applicable, DMTF Reserved, Vendor Reserved} Values for the above definitions are as follows {0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, .., 32768..65535} Note - When `EnabledState` is set to `5` (Not Applicable), then this property has no meaning. | Set to `12` (Not Applicable).
`SensorType` | uint16[] | Identifies the type of the sensor, for example, voltage sensor or temperature sensor. If the type is set to Other, then the `OtherSensorType` Description can be used to further identify the type, or if the sensor has numeric readings, then the type of the sensor can be implicitly determined by the Units. A description of the different Sensor types is as follows: A temperature sensor measures the environmental temperature. Voltage and current sensors measure electrical voltage and current readings. A tachometer measures speed/revolutions of a device. For example, a fan device can have an associated tachometer which measures its speed. A counter is a general purpose sensor that measures some numerical property of a device. A counter value can be cleared, but it never decreases. A switch sensor has states like Open or Close, On or Off, or Upor Down. A Lock has states of Lockedor Unlocked. Humidity, smoke detection and air flow sensors measure the equivalent environmental characteristics. A presence sensor detects the presence of a `PhysicalElement.` A power consumption sensor measures the instantaneous power consumed by a managed element. A power production sensor measures the instantaneous power produced by a managed element such as a power supply or a voltage regulator. A pressure sensor is used to report pressure. | Appropriate value.
|  | The following values apply: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, .., 32768..65535} Definitions of above values are: {Unknown, Other, Temperature, Voltage, Current, Tachometer, Counter, Switch, Lock, Humidity, Smoke Detection, Presence, Air Flow, Power Consumption, Power Production, Pressure, DMTF Reserved, Vendor Reserved} |
`SupportedThresholds` | uint16[] | An array representing the thresholds supported by this sensor. The following values apply: {0, 1, 2, 3, 4, 5} Definitions of above values are: {LowerThresholdNonCritical, UpperThresholdNonCritical, LowerThresholdCritical, UpperThresholdCritical, LowerThresholdFatal, UpperThresholdFatal} | String values of supported thresholds.
`UpperThresholdCritical` | sint32 | The sensor’s threshold values specify the ranges (min and max values) for determining whether the sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the `CurrentReading` is above `UpperThresholdFatal`, then the current state is Fatal. | Will have appropriate value if sensor supports this threshold. If sensor does not support this threshold, then this property will not be set.
`UpperThresholdNonCritical` | sint32 | The sensor’s threshold values specify the ranges (min and max values) for determining whether the sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the `CurrentReading` is between `LowerThresholdNonCritical` and `UpperThresholdNonCritical`, then the sensor is reporting a normal value. If the `CurrentReading` is between `UpperThreshold NonCritical` and `UpperThresholdCritical`, then the `current` `state` is `NonCritical` | Will have appropriate value if sensor supports this threshold. If sensor does not support this threshold, then this property will not be set.

##

Oracle_PhysicalAssetCapabilities

Description: | Provides the capabilities for representing FRU related information for an associated instance of the `CIM_PhysicalElement` subclass.
Inheritance: | `CIM_PhysicalAssetCapabilities`
Properties: | For a description of the supported properties for the `Oracle_PhysicalAssetCapabilities` class, see TABLE A-18. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-18), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Physical asset

TABLE A-18 Properties for Oracle_PhysicalAssetCapabilities
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`InstanceID` | string | The `InstanceID` property is a mandatory key property. Within the scope of the instantiating NameSpace, the `InstanceID` property uniquely identifies an instance of this class. The value of `InstanceID` should be constructed using the following preferred algorithm: `<OrgID>:<LocalID>` Where: `<OrgID>` and `<LocalID>` are separated by a colon ’:’ `<OrgID>` must include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating or defining the `InstanceID`, or is a registered ID that is assigned to the business entity by a recognized global authority (This is similar to the `<Schema` `Name>_<Class Name>` structure of schema class names) `<OrgID>` must not contain a colon (’:’). The first colon to appear in I`nstanceID` must appear between `<OrgID>` and `<LocalID>` `<LocalID>` is chosen by the business entity and should not be re-used to identify different underlying (real-world) elements For DMTF defined instances, the `<OrgID>` must be set to CIM. If the above preferred algorithm is not used, the defining entity must ensure that the resultant `InstanceID` is not re-used across any instance IDs produced by this or other providers for this instance’s NameSpace. | Implementation dependent value representing unique ID of the `PhysicalAssetCapabilities`.
`FRUInfoSupported` | boolean | boolean indicating whether the PartNumber, Serial Number, Model, Manufacturer, and SKU properties of `PhysicalElement` are non-null, non-blank values, and the availability of the complete FRU information. | Will be set to TRUE or FALSE depending on whether the associated instance of `CIM_PhysicalElement` is considered to be a FRU by the platform.

##

Oracle_PhysicalComponent

Description: | The PhysicalComponent class represents any low-level or basic component within a package. A component object either can not or does not need to be decomposed into its constituent parts.
Inheritance: | `CIM_PhysicalComponent`
Properties: | For a description of the supported properties for the `Oracle_PhysicalComponent` class, see TABLE A-19. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-19), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Physical Asset

TABLE A-19 Properties for Oracle_PhysicalComponent
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`CreationClassName` | string | The `CreationClassName` property is a mandatory key property. `CreationClassName` indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. | Set to `Oracle_PhysicalComponent`
`Tag` | string | The `Tag` property is a mandatory key property. An arbitrary string that uniquely identifies the physical element and serves as the key of the element. The `Tag` property can contain information such as asset tag or serial number data. The key for physical element is placed very high in the object hierarchy in order to independently identify the hardware or entity, regardless of physical placement in or on cabinets, adapters, and so on. For example, a hot-swappable or removable component can be taken from its containing (scoping) package and be temporarily unused. The object still continues to exist and can even be inserted into a different scoping container. Therefore, the key for physical element is an arbitrary string and is defined independently of any placement or location-oriented hierarchy. | Set to component NAC name.
`CanBeFRUed` | boolean | A boolean that indicates whether this physical element can be a FRU (TRUE) or not (FALSE). | Will be set to TRUE or FALSE depending on whether the component is considered to be a FRU by the platform.
`Description` | string | The `Description` property provides a textual description of the object | Will have appropriate description.
`ElementName` | string | User-friendly name. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note - The `Name` property of `ManagedSystemElement` is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where `Name` exists and is not a Key (such as for instances of `LogicalDevice`), the same information can be present in both the `Name` and `ElementName` properties. | Set to component NAC name
HealthState | uint16 | Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The possible values are 0 to 30, where 5 means the element is entirely healthy and 30 means the element is completely non-functional. The following continuum is defined: "Non-recoverable Error" (30) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. "Critical Failure" (25) - The element is nonfunctional and recovery might not be possible. "Major Failure" (20) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. "Minor Failure" (15) - All functionality is available but some might be degraded. "Degraded/Warning" (10) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. "OK" (5) - The element is fully functional and is operating within normal operational parameters and without error. | Will have the appropriate value depending on whether the component is in error state or not.
|  | "Unknown" (0) - The implementation cannot report on HealthState at this time. DMTF has reserved the unused portion of the continuum for additional HealthStates in the future. Possible values are: {0, 5, 10, 15, 20, 25, 30, ..} Definitions for the above values are: {Unknown, OK, Degraded/Warning, Minor failure, Major failure, Critical failure, Non-recoverable error, DMTF Reserved} |
`Manufacturer` | string | The name of the organization responsible for producing the `PhysicalElement`. This organization might be the entity from whom the element is purchased, but this is not necessarily true. The latter information is contained in the `Vendor` property of `CIM_Product`. | Will have the appropriate value if the component is considered as a FRU by the platform.
`Model` | string | The name by which the `PhysicalElement` is generally known. | Will have the appropriate value if the component is considered as a FRU by the platform.
`OperationalStatus` | Uint16 [] | Indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. However, a few are not and are described here in more detail. "Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are "overload, overheated, and so on. " "Predictive Failure" indicates that an element is functioning nominally but predicting a failure in the near future." "In Service" describes an element being configured, maintained, cleaned, or otherwise administered." "No Contact" indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it." "Lost Communication" indicates that the `ManagedSystemElement` is known to exist and has been contacted successfully in the past, but is currently unreachable." "Stopped" and "`Aborted`" are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the state and configuration of the element might need to be updated. "Dormant" indicates that the element is inactive or quiesced. | OperationalStatus[0] will have appropriate value depending on whether the component is in error state or not.
|  | "Supporting Entity in Error" indicates that this element might be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower-layer networking problems. "Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded so that a client can tell if the complete operation Completed with OK (passed), Completed with Error (failed), or Completed with Degraded (the operation finished, but it did not complete OK or did not report an error). "Power Mode" indicates that the element has additional power model information contained in the Associated `PowerManagementService` association. `OperationalStatus` replaces the `Status` property on `ManagedSystemElement` to provide a consistent approach to enumerations, to address implementation needs for an array property, and to provide a migration path from today's environment to the future. This change was not made earlier because it required the deprecated qualifier. Due to the widespread use of the existing `Status` property in management applications, it is strongly recommended that providers or instrumentation provide both the |
|  | `Status` and `OperationalStatus` properties. Further, the first value of `OperationalStatus` should contain the primary status for the element. When instrumented, `Status` (because it is single-valued) should also provide the primary status of the element. Possible values are: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, .., 0x8000..} Definitions of the above values are: { Unknown, Other, OK, Degraded, Stressed, Predictive Failure, Error, Non- Recoverable Error, Starting, Stopping, Stopped, In Service, No Contact, Lost Communication, Aborted, Dormant, Supporting Entity in Error, Completed, Power Mode, DMTF Reserved, VendorReserved} |
`PartNumber` | string | The part number assigned by the organization that is responsible for producing or manufacturing the `PhysicalElement`. | Will have the appropriate value if the component is considered a FRU by the platform.
`SKU` | string | The stock-keeping unit number for this `PhysicalElement`. | Will have the appropriate value if the component is considered a FRU by the platform.
`SerialNumber` | string | A manufacturer-allocated number used to identify the `Physical Element`. | Will have the appropriate value if the component is considered a FRU by the platform.
`StatusDescriptions` | String[] | Strings describing the various `OperationalStatus` array values. For example, if "Stopping" is the value assigned to `OperationalStatus`, then this property may contain an explanation as to why an object is being stopped. Note - Note that entries in this array are correlated with those at the same array index in `OperationalStatus`. | `StatusDescriptions[0]` will have appropriate description on the reason for the value of OperationalStatus[0].

##

Oracle_PhysicalElementCapabilities

Description: | `Oracle_PhysicalElementCapabilities` is used to associate an instance of `CIM_PhysicalElement` to its capabilities, `Oracle_PhysicalAssetCapabilities`.
Inheritance: | `CIM_ElementCapabilities`
Properties: | For a description of the supported properties for the `Oracle_PhysicalElementCapabilities` class, see TABLE A-20. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-20), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Physical Asset

TABLE A-20 Properties for Oracle_PhysicalElementCapabilities
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`Capabilities` | `Oracle_PhysicalAssetCapabilities` REF | The `Capabilities` property is a mandatory key property. The Capabilities object associated with the element. | Object path to an instance of `Oracle_PhysicalAssetCapabilities`.
`ManagedElement` | `CIM_PhysicalElement` REF | The `ManagedElement` property is a mandatory key property. Identifies the managed element. | Object path to an instance of `Oracle_PhysicalElement`.

##

Oracle_PhysicalMemory

Description: | `The` `Oracle_PhysicalMemory` is used to represent low-level memory devices such as SIMMs, DIMMs, raw memory chips, and so forth.
Inheritance: | `CIM_PhysicalMemory`
Properties: | For a description of the supported properties for the `Oracle_PhysicalMemory` class, see TABLE A-21. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-21), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Physical asset

TABLE A-21 Properties for Oracle_PhysicalMemory
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`CreationClassName` | string | The `CreationClassName` property is a mandatory key property `CreationClassName` indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. | Set to `Oracle_PhysicalMemory`.
`Tag` | string | The `Tag` property is a mandatory key property The `Tag` property is an arbitrary string that uniquely identifies the physical element and serves as the key of the element. The `Tag` property can contain information such as asset tag or serial number data. The key for `PhysicalElement` is placed very high in the object hierarchy in order to independently identify the hardware or entity, regardless of physical placement in or on cabinets, adapters, and so on. For example, a hot-swappable or removable component can be taken from its containing (scoping) Package and be temporarily unused. The object still continues to exist and can even be inserted into a different scoping container. Therefore, the key for `PhysicalElement` is an arbitrary string and is defined independently of any placement or location-oriented hierarchy. | Set to component NAC name.
`CanBeFRUed` | boolean | The boolean that indicates whether this `PhysicalElement` is a FRU (TRUE) or not (FALSE). | Set to TRUE or FALSE depending on whether the component is considered to be a FRU by the platform.
`Description` | string | Textual description of the object. | Appropriate description.
`FormFactor` | uint16[] | The implementation form factor for the Chip. For example, values such as SIMM (7), TSOP (9) or PGA (10) can be specified. The following values apply: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23} Definitions for the above values are: {Unknown, Other, SIP, DIP, ZIP, SOJ, Proprietary, SIMM, DIMM, TSOP, PGA, RIMM, SODIMM, SRIMM, SMD, SSMP, QFP, TQFP, SOIC, LCC, PLCC, BGA, FPBGA, LGA} | Set to value 8 (DIMM).
`HealthState` | uint16[] | Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The following values apply: 0 (Unknown) - The implementation cannot report on `HealthState` at this time. 5 (OK) - The element is fully functional and is operating within normal operational parameters and without error. 10 (Degraded/Warning) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. 15 (Minor Failure) - All functionality is available but some might be degraded. 20 (Major Failure) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. 25 (Critical Failure) - The element is non-functional and recovery might not be possible. 30 (Non-recoverable Error) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. DMTF has reserved the unused portion of the continuum for additional health states in the future. | Will have appropriate value depending on whether the component is in error state or not.
`MemoryType` | uint16[] | The type of `PhysicalMemory`. Synchronous DRAM is also known as SDRAM. Cache DRAM is also known as CDRAM. CDRAM is also known as Cache DRAM. SDRAM is also known as Synchronous DRAM. BRAM is also known as Block RAM. The following values apply: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26..32567, 32568..65535} Definitions for the above values are: {"Unknown", "Other", "DRAM", "Synchronous DRAM", "Cache DRAM", "EDO", "EDRAM", "VRAM", "SRAM", "RAM", "ROM", "Flash", "EEPROM", "FEPROM", "EPROM", "CDRAM", "3DRAM", "SDRAM", "SGRAM", "RDRAM", "DDR", "DDR-2", "BRAM", "FB-DIMM", "DDR3", "FBD2", "DMTF Reserved","Vendor Reserved" } | Appropriate value.
`Manufacturer` | string | The name of the organization responsible for producing the `PhysicalElement`. This organization might be the entity from whom the Element is purchased, but this is not necessarily true. The latter information is contained in the Vendor property of `CIM_Product`. | Will have appropriate value if the processor chip is considered a FRU by the platform.
`Model` | string | The name by which the `PhysicalElement` is generally known. | Will have appropriate value if the processor chip is considered a FRU by the platform.
`OperationalStatus` | uint16[] | The `OperationalStatus` property indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. Enumeration values can include any of the following: {Unknown, Other, OK, Degraded, Stressed, Predictive Failure, Error, Non-Recoverable Error, Starting, Stopping, Stopped, In Service, No Contact, Lost Communication, Aborted, Dormant, Supporting Entity in Error, Completed, Power Mode, DMTF Reserved, Vendor Reserved} Possible values for the enumeration values include: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, .., 0x8000..} | `OperationalStatus[0]` will have appropriate value depending on whether the component is in error state or not.
`PartNumber` | string | Part number assigned by the organization that is responsible for producing or manufacturing the physical element. | Will have appropriate value if the processor chip is considered a FRU by the platform.
`SKU` | string | The stock-keeping unit number for this physical element. | Will have appropriate value if the processor chip is considered a FRU by the platform.
`SerialNumber` | string | A manufacturer-allocated number used to identify the physical element. | Will have appropriate value if the processor chip is considered a FRU by the platform.
`StatusDescriptions` | string[] | Strings describing the various `OperationalStatus` array values. For example, if Stopping is the value assigned to `OperationalStatus`, then this property might contain an explanation as to why an object is being stopped. Note that entries in this array are correlated with those at the same array index in `OperationalStatus`. | `StatusDescriptions` [0] will have appropriate description on the reason for the value of `OperationalStatus`[0].

##

Oracle_PhysicalPackage

Description: | The `Oracle_PhysicalPackage` class represents physical elements that contain or host other components.
Inheritance: | `CIM_PhysicalPackage`
Properties: | For a description of the supported properties for the `Oracle_PhysicalPackage` class, see TABLE A-22. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-22), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Physical asset

TABLE A-22 Properties for Oracle_PhysicalPackage
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`CreationClassName` | string | The `CreationClassName` property is a mandatory key property `CreationClassName` indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. | Set to `Oracle_PhysicalPackage`.
`Tag` | string | The `Tag` property is a mandatory key property The `Tag` property is an arbitrary string that uniquely identifies the physical element and serves as the key of the element. The `Tag` property can contain information such as asset tag or serial number data. The key for `PhysicalElement` is placed very high in the object hierarchy in order to independently identify the hardware or entity, regardless of physical placement in or on Cabinets, Adapters, and so on. For example, a hot-swappable or removable component can be taken from its containing (scoping) package and be temporarily unused. The object still continues to exist and can even be inserted into a different scoping container. Therefore, the key for `PhysicalElement` is an arbitrary string and is defined independently of any placement or location-oriented hierarchy. | Set to component NAC name.
`CanBeFRUed` | boolean | A boolean that indicates whether this `PhysicalElement` is a FRU (TRUE) or not (FALSE). | Will be set to TRUE or FALSE depending on whether the component is considered to be a FRU by the platform.
`Description` | string | Textual description of the object. | Appropriate description.
`ElementName` | string | The `ElementName` property is a user-friendly name. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note that the `Name` property of `ManagedSystemElement` is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where `Name` exists and is not a Key (such as for instances of `LogicalDevice`), the same information can be present in both the `Name` and `ElementName` properties. | Set to component NAC name.
`HealthState` | uint16[] | Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The following values apply 0 (Unknown) - The implementation cannot report on `HealthState` at this time. 5 (OK) - The element is fully functional and is operating within normal operational parameters and without error. 10 (Degraded/Warning) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. 15 (Minor Failure) - All functionality is available but some might be degraded. 20 (Major Failure) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. 25 (Critical Failure) - The element is non-functional and recovery might not be possible. 30 (Non-recoverable Error) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. DMTF has reserved the unused portion of the continuum for additional health states in the future. | Will have appropriate value depending on whether the component is in error state or not.
`Manufacturer` | string | The name of the organization responsible for producing the `PhysicalElement`. This organization might be the entity from whom the Element is purchased, but this is not necessarily true. The latter information is contained in the `Vendor` property of `CIM_Product`. | Will have appropriate value if the processor chip is considered as a FRU by the platform.
`Model` | string | The name by which the `PhysicalElement` is generally known. | Will have appropriate value if the component is considered as a FRU by the platform.
`OperationalStatus` | Uint16 [] | Indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. However, a few are not and are described here in more detail. "Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are "overload, overheated, and so on. " "Predictive Failure" indicates that an element is functioning nominally but predicting a failure in the near future." "In Service" describes an element being configured, maintained, cleaned, or otherwise administered." "No Contact" indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it." "Lost Communication" indicates that the `ManagedSystemElement` is known to exist and has been contacted successfully in the past, but is currently unreachable." "Stopped" and "Aborted" are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the state and configuration of the element might need to be updated. "Dormant" indicates that the element is inactive or quiesced. "Supporting Entity in Error" indicates that this element might be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower-layer networking problems. "Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded so that a client can tell if the complete operation Completed with OK (passed), Completed with Error (failed), or Completed with Degraded (the operation finished, but it did not complete OK or did not report an error). "Power Mode" indicates that the element has additional power model information contained in the Associated `PowerManagementService` association." | `OperationalStatus[0]` will have appropriate value depending on whether the component is in error state or not.
|  | `OperationalStatus` replaces the `Status` property on `ManagedSystemElement` to provide a consistent approach to enumerations, to address implementation needs for an array property, and to provide a migration path from today's environment to the future. This change was not made earlier because it required the deprecated qualifier. Due to the widespread use of the existing `Status` property in management applications, it is strongly recommended that providers or instrumentation provide both the `Status` and `OperationalStatus` properties. Further, the first value of `OperationalStatus` should contain the primary status for the element. When instrumented, Status (because it is single-valued) should also provide the primary status of the element. Possible values are: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, .., 0x8000..} Definitions of the above values are: { Unknown, Other, OK, Degraded, Stressed, Predictive Failure, Error, Non- Recoverable Error, Starting, Stopping, Stopped, In Service, No Contact, Lost Communication, Aborted, Dormant, Supporting Entity in Error, Completed, Power Mode, DMTF Reserved, Vendor Reserved} |
`PackageType` | uint16[] | Enumeration defining the type of the `PhysicalPackage`. Note that this enumeration expands on the list in the Entity MIB (the attribute, `entPhysicalClass`). The numeric values are consistent with the CIM enumeration numbering guidelines, but are slightly different than the MIB values. Unknown - indicates that the package type is not known. Other - The package type does not correspond to an existing enumerated value. The value is specified using the `OtherPackageType` property. The values Rack through Port or Connector are defined per the Entity-MIB (where the semantics of rack are equivalent to the MIB’s stack value). The other values (for battery, processor, memory, power source or generator and storage media package) are self-explanatory. A value of the blade server should be used when the `PhysicalPackage` contains the operational hardware aspects of a `ComputerSystem`, without the supporting mechanicals such as power and cooling. For example, a blade server (server module) includes processor(s) and memory, and relies on the containing chassis to supply power and cooling. In many respects, a blade can be considered a module or card. However, it is tracked differently by inventory systems and differs in terms of service philosophy. For example, a blade server is intended to be hot-plugged into a hosting enclosure without requiring additional cabling, and does not require a cover to be removed from the enclosure for installation. Similarly, a blade expansion module has characteristics of a blade server and a module or card. However, it is distinct from both due to inventory tracking and service philosophy, and because of its hardware dependence on a blade. A blade expansion module (or card) must be attached to a blade prior to inserting the resultant assembly into an enclosure. The following values apply: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17} Definitions for the above values are: {Unknown, Other, Rack, Chassis/Frame, Cross Connect/Backplane, Container/Frame Slot, Power Supply, Fan, Sensor, Module/Card, Port/Connector, Battery, Processor, Memory, Power Source/Generator, Storage Media Package (e.g., Disk or Tape Drive), Blade, Blade Expansion} | Appropriate value.
`PartNumber` | string | Part number assigned by the organization that is responsible for producing or manufacturing the `PhysicalElement.` | Will have appropriate value if the processor chip is considered a FRU by the platform.
`SKU` | string | The `SKU` property is a manufacturer-allocated number used to identify the `PhysicalElement.` | Will have appropriate value if the processor chip is considered a FRU by the platform.
`SerialNumber` | string | A manufacturer-allocated number used to identify the `PhysicalElement`. | Will have appropriate value if the processor chip is considered a FRU by the platform.
`StatusDescriptions` | string[] | Strings describing the various `OperationalStatus` array values. For example, if "Stopping" is the value assigned to `OperationalStatus`, then this property may contain an explanation as to why an object is being stopped. Note that entries in this array are correlated with those at the same array index in `OperationalStatus`. | `StatusDescriptions`[0] will have appropriate description on the reason for the value of `OperationalStatus`[0].

##

Oracle_Processor

Description: | Identifies capabilities and management of the processor logical device.
Inheritance: | `CIM_Processor`
Properties: | For a description of the supported properties for the `Oracle_Processor` class, see TABLE A-23. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-23), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | CPU

TABLE A-23 Properties for Oracle_Processor
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`CreationClassName` | string | The `CreationClassName` property is a mandatory key property. `CreationClassName` indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. | Set to `Oracle_Processor`.
`DeviceID` | string | The `DeviceID` property is a mandatory key property. The Device ID indicates an address or other identifying information used to uniquely name the `LogicalDevice`. | Will be set to the NAC name of the sensor.
`SystemCreationClassName` | string | The `SystemCreationName` property is a mandatory key property. Indicates the `CreationClassName` of the scoping system. | Set to `Oracle_ComputerSystem.`
`SystemName` | string | The SystemName property is a mandatory key property. Indicates the `SystemName` of the scoping system. | Set to `Oracle_ComputerSystem.Name` of the instance of `Oracle_ComputerSystem` that represents the controllee.
`CPUStatus` | uint16[] | Indicates the current status of the Processor. For example, the processor might be disabled by the user (value=2), or disabled due to a POST error (value=3). Information in this property can be obtained from SMBIOS, the type `4` structure, and the status attribute. The following values are apply: {0, 1, 2, 3, 4, 7} Definitions of above values are: {Unknown, CPU Enabled, CPU Disabled by User, CPU Disabled By BIOS (POST Error), CPU Is Idle, Other} | Appropriate value.
`ElementName` | string | The `ElementName` property is a user-friendly name. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note that the `Name` property of `ManagedSystemElement` is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where `Name` exists and is not a Key (such as for instances of `LogicalDevice`), the same information can be present in both the `Name` and `ElementName` properties. | Will be set to the NAC name of the sensor.
`EnabledDefault` | uint16[] | Eumerated value indicating an administrator’s default or startup configuration for the Enabled State of an element. By default, the element is "Enabled" (value=2). The following values apply: {2, 3, 5, 6, 7, 9, .., 32768..65535} Definitions for the above values are: {Enabled, Disabled, Not Applicable, Enabled but Offline, No Default, Quiesce, DMTF Reserved, Vendor Reserved} | Set to default value `2` (Enabled).
`EnabledState` | uint16[] | Integer enumeration that indicates the enabled and disabled states of an element. It can also indicate the transitions between these requested states. For example, shutting down (value=4) and starting (value=10) are transient states between enabled and disabled. The following values apply: 0 (Unknown) 1 (Other) 2 (Enabled) - The element is or could be executing commands, will process any queued commands, and queues new requests. 3 (Disabled) - The element will not execute commands and will drop any new requests. 4 (Shutting Down) - The element is in the process of going to a Disabled state. 5 (Not Applicable) - The element does not support being enabled or disabled. 6 (Enabled but Offline) - The element might be completing commands, and will drop any new requests. 7 (Test) - The element is in a test state. 8 (Deferred) - The element might be completing commands, but will queue any new requests. 9 (Quiesce) - The element is enabled but in a restricted mode. 10 (Starting) - The element is in the process of going to an Enabled state. New requests are queued. 11..32767 (DMTF Reserved) 32768..65535 (Vendor Reserved) | Appropriate value.
`Family` | uint16[] | The Processor family type. For example, values include Pentium(R) processor with MMX(TM) technology (value=14) and 68040 (value=96). The following values apply: {1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 48, 49, 50, 51, 52, 53, 54, 55, 64, 65, 66, 67, 68, 69, 80, 81, 82, 83, 84, 85, 86, 87, 88, 96, 97, 98, 99, 100, 101, 112, 120, 121, 122, 128, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 160, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 200, 201, 202, 203, 204, 210, 211, 212, 213, 230, 250, 251, 254, 255, 260, 261, 280, 281, 300, 301, 302, 320, 350, 500, 65534, 65535} | Appropriate value.
`HealthState` | uint16[] | Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The following values apply: 0 (Unknown) - The implementation cannot report on `HealthState` at this time. 5 (OK) - The element is fully functional and is operating within normal operational parameters and without error. 10 (Degraded/Warning) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. 15 (Minor Failure) - All functionality is available but some might be degraded. 20 (Major Failure) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. 25 (Critical Failure) - The element is non-functional and recovery might not be possible. 30 (Non-recoverable Error) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. DMTF has reserved the unused portion of the continuum for additional health states in the future. | Appropriate value.
`OperationalStatus` | uint16[] | The `OperationalStatus` property indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. Enumeration definitions can include any of the following: {Unknown, Other, OK, Degraded, Stressed, Predictive Failure, Error, Non-Recoverable Error, Starting, Stopping, Stopped, In Service, No Contact, Lost Communication, Aborted, Dormant, Supporting Entity in Error, Completed, Power Mode, DMTF Reserved, Vendor Reserved} Values for the enumeration definition are as follows: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, .., 0x8000..} | Appropriate value.
`RequestedState` | uint16[] | The `RequestedState` property is an integer enumeration that indicates the last requested or desired state for the element, irrespective of the mechanism through which it was requested. The actual state of the element is represented by `EnabledState`. This property is provided to compare the last requested and current enabled or disabled states. Element definitions include any of the following: {Unknown, Enabled, Disabled, Shut Down, No Change, Offline, Test, Deferred, Quiesce, Reboot, Reset, Not Applicable, DMTF Reserved, Vendor Reserved} Values for the above definitions are: {0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, .., 32768..65535} Note - When `EnabledState` is set to 5 ("Not Applicable"), then this property has no meaning. | Set to 12 (Not Applicable).

##

Oracle_ProcessorChip

Description: | Identifies the integrated circuit hardware for the processor.
Inheritance: | `CIM_Chip`
Properties: | For a description of the supported properties for the `Oracle_ProcessorChip` class, see TABLE A-24. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-24), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Physical asset

TABLE A-24 Properties for Oracle_ProcessorChip
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`CreationClassName` | string | The `CreationClassName` property is a mandatory key property. `CreationClassName` indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. | Set to `Oracle_ProcessorChip`.
`Tag` | string | The `Tag` property is a mandatory key property. The `Tag` property is an arbitrary string that uniquely identifies the physical element and serves as the key of the element. The `Tag` property can contain information such as asset tag or serial number data. The key for `PhysicalElement` is placed very high in the object hierarchy in order to independently identify the hardware or entity, regardless of physical placement in or on cabinets, adapters, and so on. For example, a hot-swappable or removable component can be taken from its containing (scoping) Package and be temporarily unused. The object still continues to exist and can even be inserted into a different scoping container. Therefore, the key for `PhysicalElement` is an arbitrary string and is defined independently of any placement or location-oriented hierarchy. | Set to component NAC name.
`CanBeFRUed` | boolean | The boolean indicates whether this `PhysicalElement` can be a FRU (TRUE) or not (FALSE). | Set to TRUE or FALSE depending on whether the component is considered to be a FRU by the platform.
`Description` | string | Textual description of the object. | Appropriate description.
`ElementName` | string | The `ElementName` property is a user-friendly name. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note that the `Name` property of `ManagedSystemElement` is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where `Name` exists and is not a Key (such as for instances of `LogicalDevice`), the same information can be present in both the `Name` and `ElementName` properties. | Set to component NAC name.
`HealthState` | uint16[] | Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The following values apply: 0 (Unknown) - The implementation cannot report on `HealthState` at this time. 5 (OK) - The element is fully functional and is operating within normal operational parameters and without error. 10 (Degraded/Warning) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. 15 (Minor Failure) - All functionality is available but some might be degraded. 20 (Major Failure) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. 25 (Critical Failure) - The element is non-functional and recovery might not be possible. 30 (Non-recoverable Error) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. DMTF has reserved the unused portion of the continuum for additional health states in the future. | Will have appropriate value depending on whether the component is in error state or not.
`Manufacturer` | string | The name of the organization responsible for producing the physical element. This organization might be the entity from whom the element is purchased, but this is not necessarily true. The latter information is contained in the `Vendor` property of `CIM_Product`. | Will have appropriate value if the processor chip is considered a FRU by the platform.
`Model` | string | The name by which the physical element is generally known. | Will have appropriate value if the processor chip is considered a FRU by the platform.
`OperationalStatus` | uint16[] | The `OperationalStatus` property indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. Enumeration definitions can include any of the following: {Unknown, Other, OK, Degraded, Stressed, Predictive Failure, Error, Non-Recoverable Error, Starting, Stopping, Stopped, In Service, No Contact, Lost Communication, Aborted, Dormant, Supporting Entity in Error, Completed, Power Mode, DMTF Reserved, Vendor Reserved} Values for the above definitions: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, .., 0x8000..} | `OperationalStatus[0]` will have appropriate value depending on whether the component is in error state or not.
`PartNumber` | string | Part number assigned by the organization that is responsible for producing or manufacturing the `PhysicalElement.` | Will have appropriate value if the processor chip is considered a FRU by the platform.
`SKU` | string | The stock-keeping unit number for this `PhysicalElement`. | Will have appropriate value if the processor chip is considered a FRU by the platform.
`SerialNumber` | string | A manufacturer-allocated number used to identify the physical element. | Will have appropriate value if the processor chip is considered a FRU by the platform.
`StatusDescriptions` | string[] | Strings describing the various `OperationalStatus` array values. For example, if Stopping is the value assigned to `OperationalStatus`, then this property may contain an explanation as to why an object is being stopped. Note that entries in this array are correlated with those at the same array index in `OperationalStatus`. | `StatusDescriptions`[0] will have appropriate description on the reason for the value of `OperationalStatus`[0].

##

Oracle_Realizes

Description: | `Oracle_Realizes` is the association that defines the mapping between `LogicalDevices` and the `PhysicalElements` that implement them.
Inheritance: | `CIM_Realizes`
Properties: | For a description of the supported properties for the `Oracle_Realizes` class, see TABLE A-25. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-25), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Physical asset CPU System Memory

TABLE A-25 Properties for Oracle_Realizes
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`Antecedent` | `CIM_PhysicalElement` REF | The `Antecedent` property is a mandatory key property. The physical component that implements the device. | Object path to an instance of `CIM_PhysicalElement`.
`Dependent` | `CIM_LogicalDevice` REF | The `Dependent` property is a mandatory key property. The `LogicalDevice`. | Object path to an instance of `CIM_LogicalDevice`.

##

Oracle_RegisteredProfile

Description: | Provides implementation conformance to a CIM profile.
Inheritance: | `CIM_RegisteredProfile`
Properties: | For a description of the supported properties for the `Oracle_RegisteredProfile` class, see TABLE A-26. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-26), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Profile Registration

TABLE A-26 Properties for Oracle_RegisteredProfile
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`InstanceID` | string | The `InstanceID` property is a key mandatory property. Within the scope of the instantiating NameSpace, the `InstanceID` property uniquely identifies an instance of this class. The value of `InstanceID` should be constructed using the following preferred algorithm: `<OrgID>:<LocalID>` Where: `<OrgID>` and `<LocalID>` are separated by a colon ’:’ `<OrgID>` must include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating or defining the `InstanceID`, or is a registered ID that is assigned to the business entity by a recognized global authority (This is similar to the <Schema Name>_<Class Name> structure of Schema class names). `<OrgID>` must not contain a colon (’:’). The first colon to appear in `InstanceID` must appear between `<OrgID>` and`<LocalID>` . `<LocalID>` is chosen by the business entity and should not be re-used to identify different underlying (real-world) elements For DMTF defined instances, the `<OrgID>` must be set to ’CIM’. If the above preferred algorithm is not used, the defining entity must ensure that the resultant `InstanceID` is not re-used across any instance IDs produced by this or other providers for this instance’s NameSpace. | Implementation dependent value representing unique ID.
`AdvertiseTypes` | uint16[] | Signifies the advertisement for the profile information. It is used by the advertising services of the WBEM infrastructure to determine what should be advertised, using what mechanisms. The property is an array so that the profile might be advertised using several mechanisms. Note - If this property is null/uninitialized, this is equivalent to specifying the value `2` (Not Advertised). | Will have the value 2 (Not Advertised).
`RegisteredName` | string | The name of this registered profile. Since multiple versions can exist for the same `RegisteredName`, the combination of `RegisteredName`, `RegisteredOrganization`, and `RegisteredVersion` must uniquely identify the registered profile within the scope of the organization. | Value of supported profile name.
`RegisteredOrganization` | uint16[] | The organization that defines this profile. The values for this property include: {1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, ..} Definitions for the above values are as follows: {Other, DMTF, CompTIA, Consortium for Service Innovation, FAST, GGF, INTAP, itSMF, NAC, Northwest Energy Efficiency Alliance, SNIA, TM Forum, The Open Group, ANSI, IEEE, IETF, INCITS, ISO, W3C, OGF, DMTF Reserved} | Will have the value 2 (DMTF).
`RegisteredVersion` | string | The version of this profile. The string representing the version must be in the form: M + "." + N + "." + U Where: M - The major version (in numeric form) describing the profile’s creation or last modification. N - The minor version (in numeric form) describing the profile’s creation or last modification. U - The update (for example, errata, patch, and so forth, in numeric form) describing the profile’s creation or last modification. | Will have the value "1.0.0".

##

Oracle_RecordLog

Description: | `Oracle_RecordLog` serves as an aggregation point for log entry objects. It is used to represent the IPMI SEL log. Properties of `Oracle_RecordLog` follow guidelines in IPMI CIM Mapping Guideline.
Inheritance: | `CIM_RecordLog`
Properties: | For a description of the supported properties for the `Oracle_RecordLog` class, see TABLE A-27. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-27), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Record Log

TABLE A-27 Properties for Oracle_RecordLog
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`InstanceID` | string | The `InstanceID` property is a key manadatory property. Within the scope of the instantiating NameSpace, the `InstanceID` property uniquely identifies an instance of this class. The value of `InstanceID` should be constructed using the following preferred algorithm: `<OrgID>:<LocalID>` Where: `<OrgID>` and `<LocalID>` are separated by a colon ’:’ `<OrgID>` must include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating or defining the `InstanceID`, or is a registered ID that is assigned to the business entity by a recognized global authority (This is similar to the <Schema Name>_<Class Name> structure of Schema class names). `<OrgID>` must not contain a colon (’:’). The first colon to appear in `InstanceID` must appear between `<OrgID>` and <LocalID> `<LocalID>` is chosen by the business entity and should not be re-used to identify different underlying (real-world) elements. For DMTF defined instances, the `<OrgID>` must be set to ’CIM’. If the above preferred algorithm is not used, the defining entity must ensure that the resultant `InstanceID` is not re-used across any instance IDs produced by this or other providers for this instance’s NameSpace. | Implementation dependent value representing unique ID.
`CurrentNumberOfRecords` | UInt64 | Current number of records in the Log. | Appropriate value.
ElementName | string | The `ElementName` property is a user-friendly name. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note - The `Name` property of `ManagedSystemElement` is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where `Name` exists and is not a Key (such as for instances of `LogicalDevice`), the same information can be present in both the `Name` and `ElementName` properties. | Will hve the value SEL Log.
EnabledDefault | uint16[] | An enumerated value indicating an administrator’s default or startup configuration for the `EnabledState` of an element. By default, the element is "Enabled" (value=2). The following values apply: {2, 3, 5, 6, 7, 9, .., 32768..65535} Definitions of the above values are: {Enabled, Disabled, Not Applicable, Enabled but Offline, No Default, Quiesce, DMTF Reserved, Vendor Reserved} | Will be set to default value 2 (Enabled).
EnabledState | uint16[] | Integer enumeration that indicates the enabled and disabled states of an element. It can also indicate the transitions between these requested states. For example, shutting down (value=4) and starting (value=10) are transient states between enabled and disabled. The following values apply: 0 (Unknown) 1 (Other) 2 (Enabled) - The element is or could be executing commands, will process any queued commands, and queues new requests. 3 (Disabled) - The element will not execute commands and will drop any new requests. 4 (Shutting Down) - The element is in the process of going to a Disabled state. 5 (Not Applicable) - The element does not support being enabled or disabled. 6 (Enabled but Offline) - The element might be completing commands, and will drop any new requests 7 (Test) - The element is in a test state. 8 (Deferred) - The element might be completing commands, but will queue any new requests. 9 (Quiesce) - The element is enabled but in a restricted mode. 10 (Starting) - The element is in the process of going to an Enabled state. New requests are queued. 11..32767 (DMTF Reserved) 32768..65539 (Vendor Reserved) | Appropriate value.
HealthState | uint16[] | Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The following values apply: 0 (Unknown) - The implementation cannot report on `HealthState` at this time. 5 (OK) - The element is fully functional and is operating within normal operational parameters and without error. 10 (Degraded/Warning) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. 15 (Minor Failure) - All functionality is available but some might be degraded. 20 (Major Failure) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. 25 (Critical Failure) - The element is non-functional and recovery might not be possible. 30 (Non-recoverable Error) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. DMTF has reserved the unused portion of the continuum for additional health states in the future. | Appropriate value.
LogState | uint16[] | `LogState` is an integer enumeration that indicates the current state of a log represented by `CIM_Log` subclasses. `LogState` is to be used in conjunction with the `EnabledState` property to fully describe the current state of the log. The following text briefly summarizes the various log states: Unknown (0) indicates the state of the log is unknown. Normal (2) indicates that the log is or could be executing logging commands, will process any queued log entries, and will queue new logging requests. Erasing (3) indicates that the log is being erased. Not Applicable (4) indicates the log does not support representing a log state. The following values apply: {0, 2, 3, 4, .., 32768..65535} Definitions for the above values are: {Unknown, Normal, Erasing, Not Applicable, DMTF Reserved, Vendor Reserved} | Appropriate value.
MaxNumberOfRecords | UInt64 | Maximum number of records that can be captured in the log. If undefined, a value of zero should be specified. | Appropriate value.
OperationalStatus | uint16[] | The `OperationalStatus` property indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. Enumeration definitions can include any of the following: {Unknown, Other, OK, Degraded, Stressed, Predictive Failure, Error, Non-Recoverable Error, Starting, Stopping, Stopped, In Service, No Contact, Lost Communication, Aborted, Dormant, Supporting Entity in Error, Completed, Power Mode, DMTF Reserved, Vendor Reserved} Values for the enumeration definitions include: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, .., 0x8000..} | Appropriate value.
OverwritePolicy | uint16[] | Integer enumeration that indicates whether the log, represented by the `CIM_Log` subclasses, can overwrite its entries.Unknown (0) indicates the log’s overwrite policy is unknown. Wraps when Full (2) indicates that the log overwrites its entries with new entries when the log has reached its maximum capacity. Never Overwrites (7) indicates that the log never overwrites its entries by the new entries. The following values apply: {0, 2, 7, .., 32768..65535} Definitions for the above values are: {Unknown, Wraps When Full, Never Overwrites, DMTF Reserved, Vendor Reserved} | Will have value 2 (Wraps When Full).
RequestedState | uint16[] | The `RequestedState` proprety is an integer enumeration that indicates the last requested or desired state for the element, irrespective of the mechanism through which it was requested. The actual state of the element is represented by `EnabledState`. This property is provided to compare the last requested and current enabled or disabled states. Element definitions include any of the following: {Unknown, Enabled, Disabled, Shut Down, No Change, Offline, Test, Deferred, Quiesce, Reboot, Reset, Not Applicable, DMTF Reserved, Vendor Reserved} Values for the above definitions are as follows: {0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, .., 32768..65535} Note - When `EnabledState` is set to 5 (Not Applicable), then this property has no meaning. | Will bet set to 12 (Not Applicable).

##

Oracle_ReferencedProfile

Description: | `Oracle_ReferencedProfile` is used to associate an instance of `Oracle_RegisteredProfile` to the instance of`Oracle_RegisteredProfile` representing the Base Server profile. ILOM uses Scoping Class advertisement methodology. See Profile Registration profile for details
Inheritance: | `CIM_ReferencedProfile`
Properties: | For a description of the supported properties for the `Oracle_ReferencedProfile` class, see TABLE A-28. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-28), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Profile Registration

TABLE A-28 Properties for Oracle_ReferencedProfile
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`Antecedent` | `Oracle_RegisteredProfile` REF | The `Antecedent` property is a mandatory key property. Instance of `Oracle_RegisteredProfile`. | Object path to an instance of `Oracle_RegisteredProfile`.
`Dependent` | `Oracle_RegisteredProfile` REF | The `Dependent` property is a mandatory key property. Indicates the `Oracle_RegisteredProfile`. | Object path to the instance of `Oracle_RegisteredProfile` representing the Base Server profile.

##

Oracle_Sensor

Description: | Represents a hardware component capable of measuring the characteristics of a physical property (for example, the temperature or voltage characteristics of a computer system).
Inheritance: | `CIM_Sensor`
Properties: | For a description of the supported properties for the `Oracle_Sensor` class, see TABLE A-29. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-29), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Sensor

TABLE A-29 Properties for Oracle_Sensor
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`CreationClassName` | string | The `CreationClassName` property is a mandatory key property. `CreationClassName` indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. | Set to `Oracle_Sensor`.
`DeviceID` | string | The `DeviceID` property is a mandatory key property. The `DeviceID` property indicates an address or other identifying information used to uniquely name the `LogicalDevice.` | Set to the NAC name of the sensor.
`SystemCreationClassName` | string | The `SystemCreationClassName` property is a mandatory key property. Indicates the `SystemCreationClassName` for the scoping system. | Set to `Oracle_ComputerSystem`.
`SystemName` | string | The `SystemName` property is a mandatory key property. Indicates the `SystemName` of the scoping system. | Set to `Oracle_ComputerSystem.Name` of the instance of `Oracle_ComputerSystem` that represents the controllee.
`CurrentState` | string | The current state indicated by the sensor. This is always one of the `PossibleStates`. | Value representing current state of the sensor.
`ElementName` | string | The `ElementName` property is a user-friendly name. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note that the `Name` property of `ManagedSystemElement` is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where `Name` exists and is not a Key (such as for instances of `LogicalDevice`), the same information can be present in both the `Name` and `ElementName` properties. | Will be set to the NAC name of the sensor.
`EnabledDefault` | uint16[] | An enumerated value indicating an administrator’s default or startup configuration for the enabled state of an element. By default, the element is Enabled (value=2). The following values apply: {2, 3, 5, 6, 7, 9, .., 32768..65535} Definitions for the above values are: {Enabled, Disabled, Not Applicable, Enabled but Offline, No Default, Quiesce, DMTF Reserved, Vendor Reserved}. | Set to default value `2` (Enabled).
`EnabledState` | uint16[] | Integer enumeration that indicates the enabled and disabled states of an element. It can also indicate the transitions between these requested states. For example, shutting down (value=4) and starting (value=10) are transient states between enabled and disabled. The following values apply: 0 (Unknown) 1 (Other) 2 (Enabled) - The element is or could be executing commands, will process any queued commands, and queues new requests. 3 (Disabled) - The element will not execute commands and will drop any new requests. 4 (Shutting Down) - The element is in the process of going to a Disabled state. 5 (Not Applicable) - The element does not support being enabled or disabled. 6 (Enabled but Offline) - The element might be completing commands, and will drop any new requests. 7 (Test) - The element is in a test state. 8 (Deferred) - The element might be completing commands, but will queue any new requests. 9 (Quiesce) - The element is enabled but in a restricted mode. 10 (Starting) - The element is in the process of going to an Enabled state. New requests are queued. 11..32767 (DMTF Reserved) 32768..65535 (Vendor Reserved) | Will have appropriate value depending on whether the sensor is enabled, disabled or unknown.
`HealthState` | uint16[] | Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The following values apply: 0 (Unknown) - The implementation cannot report on `HealthState` at this time. 5 (OK) - The element is fully functional and is operating within normal operational parameters and without error. 10 (Degraded/Warning) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. 15 (Minor Failure) - All functionality is available but some might be degraded. 20 (Major Failure) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. 25 (Critical Failure) - The element is non-functional and recovery might not be possible. 30 (Non-recoverable Error) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. DMTF has reserved the unused portion of the continuum for additional health states in the future. | Appropriate value.
`OperationalStatus` | uint16[] | The `OperationalStatus` property indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. Enumeration values can include any of the following: {Unknown, Other, OK, Degraded, Stressed, Predictive Failure, Error, Non-Recoverable Error, Starting, Stopping, Stopped, In Service, No Contact, Lost Communication, Aborted, Dormant, Supporting Entity in Error, Completed, Power Mode, DMTF Reserved, Vendor Reserved} Possible values for the enumeration values include: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, .., 0x8000..} | Appropriate value.
`PossibleStates` | string | Enumerates the string outputs of the sensor. For example, a switch sensor may output the states On or Off. Another implementation of the switch may output the states Open, and Close. Another example is a `NumericSensor` supporting thresholds. This sensor can report the states like Normal, Upper Fatal, Lower Non-Critical, and so forth. A `NumericSensor` that does not publish readings and thresholds, but can store this data internally and still report its states. | Appropriate values depending on the type of the sensor.
`RequestedState` | uint16[] | The `RequestedState` property is an integer enumeration that indicates the last requested or desired state for the element, irrespective of the mechanism through which it was requested. The actual state of the element is represented by `EnabledState`. This property is provided to compare the last requested and current enabled or disabled states. Element definitions include any of the following: {Unknown, Enabled, Disabled, Shut Down, No Change, Offline, Test, Deferred, Quiesce, Reboot, Reset, Not Applicable, DMTF Reserved, Vendor Reserved} Values for the above definitions include: {0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, .., 32768..65535} Note - When `EnabledState` is set to 5 ("Not Applicable"), then this property has no meaning. Refer to the DMTF CIM `EnabledState` property description for explanations of the values in the `RequestedState` enumeration. | Set to `12` (Not Applicable).
`SensorType` | uint16[] | The type of the sensor, for example, voltage or temperature sensor. If the type is set to Other, then the `OtherSensorType` description can be used to further identify the type, or if the sensor has numeric readings, then the type of the sensor can be implicitly determined by the units. A description of the different sensor types is as follows: A temperature sensor measures the environmental temperature. Voltage and current sensors measure electrical voltage and current readings. A tachometer measures speed/revolutions of a device. For example, a fan device can have an associated tachometer which measures its speed. A counter is a general purpose sensor that measures some numerical property of a Device. A counter value can be cleared, but it never decreases. A switch sensor has states like Open orClose, Onor Off, or, Upor Down. A lock has states of Lockedor Unlocked. Humidity, smoke detection and air flow sensors measure the equivalent environmental characteristics. A presence sensor detects the presence of a PhysicalElement. A power consumption sensor measures the instantaneous power consumed by a managed element. A power production sensor measures the instantaneous power produced by a managed element such as a power supply or a voltage regulator. A pressure sensor is used to report pressure. The following values apply: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, .., 32768..65535} Definitions of above values are: {Unknown, Other, Temperature, Voltage, Current, Tachometer, Counter, Switch, Lock, Humidity, Smoke Detection, Presence, Air Flow, Power Consumption, Power Production, Pressure, DMTF Reserved, Vendor Reserved} | Will have appropriate value.

##

Oracle_SpSystemComponent

Description: | `Oracle_SpSystemComponent` is used to associate the instance of `Oracle_ComputerSystem` representing the controllee and the instance of `Oracle_ComputerSystem` representing the controller.
Inheritance: | `CIM_SystemComponent`
Properties: | For a description of the supported properties for the `Oracle_SpSystemComponent` class, see TABLE A-30. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-30), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Service Processor

TABLE A-30 Properties for Oracle_SpSystemComponent
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`GroupComponent` | `CIM_ComputerSystem` REF | The `GroupComponent` property is a key mandatory property. Indicates the parent system in the association. | Object path to the instance of `Oracle_ComputerSystem` representing the controllee.
`PartComponent` | `CIM_ComputerSystem` REF | The `PartComponent` property is a key mandatory property. Indicates the child element of a system component. | Object path to the instance of `Oracle_ComputerSystem` representing the controller.

##

Oracle_SystemDevice

Description: | Association that represents an explicit relationship in which logical devices are aggregated by a `ComputerSystem`.
Inheritance: | `CIM_SystemDevice`
Properties: | For a description of the supported properties for the `Oracle_SystemDevice` class, see TABLE A-31. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-31), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Base Server System Memory Sensors CPU Indicator LED

TABLE A-31 Properties for Oracle_SystemDevices
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`GroupComponent` | `Oracle_ComputerSystem` REF | The `GroupComponent` property is a key mandatory property. Indicates the `Oracle_ComputerSystem`. | Object path to an instance of `Oracle_ComputerSystem` representing the controllee.
`PartComponent` | `CIM_LogicalDevice` REF | The `PartComponent` property is a key mandatory property. The `PartComponent` is the `LogicalDevice` that is a component of a system. | Object path to an instance of `CIM_LogicalDevice`.

##

Oracle_ThresholdIndication

Description: | When the client creates an indication subscription in which the filter indicates one of the following: `CIM_AlertIndication` and `CIM_AlertIndication.ProbalbleCause` is 52 ("Threshold Crossed") `CIM_ThresholdIndication` The ILOM CIM sub-system will generate an instance of the `Oracle_ThresholdIndication` class when it notices a sensor crossing a threshold.
Inheritance: | `CIM_ThresholdIndication`
Properties: | For a description of the supported properties for the `Oracle_ThresholdIndication` class, see TABLE A-32. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-32), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | None

TABLE A-32 Properties for Oracle_ThresholdIndication
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`AlertingElementFormat` | uint16[] | The format of the `AlertingManagedElement` property is interpretable based upon the value of this property. Values are defined as: `0` - Unknown. The format is unknown or not meaningfully interpretable by a CIM client application. `1` - Other. The format is defined by the value of the OtherAlertingElementFormat property. 2 - CIMObjectPath. The format is a CIMObjectPath, with format <NameSpacePath>:<ClassName>.<Prop1>="<Value1>", <Prop2>="<Value2>", and so forth specifying an instance in the CIM Schema. The following values apply: {0, 1, 2} Definitions for the above values are: {Unknown, Other, CIMObjectPath} | Will have the value `2` (CIMObjectPath).
`AlertingManagedElement` | string | The identifying information of the entity (that is the instance) for which this indication is generated. The property contains the path of an instance, encoded as a string parameter - if the instance is modeled in the CIM Schema. If not a CIM instance, the property contains some identifying string that names the entity for which the Alert is generated. The path or identifying string is formatted per the `AlertingElementFormat` property. | Will have the string representation of the object path of the sensor that crosses the threshold.
`AlertType` | uint16[] | Primary classification of the Indication. The following values are defined: `1` (Other) - Current Indication does not fit into the categories described by this enumeration. `2` (Communications Alert) - Associated with the procedures and/or processes required to convey information from one point to another. `3` (Quality of Service Alert) - A degradation or errors in the performance or function of an entity have occurred. `4` (Processing Error) - A software or processing fault has occurred. `5` (Device Alert) - An equipment or hardware fault has occurred. 6 (Environmental Alert) - Refers to an enclosure in which the hardware resides, or other environmental considerations. `7` (Model Change) - Addresses changes in the information model. For example, it might embed a lifecycle indication to convey the specific model change being alerted. `8` (Security Alert) - Security violations, detection of viruses, or similar issues have occurred. | Will have the value `6` (Environmental Alert).
`Descriptions` | string | Short description for the instance. | Appropriate value describing why the indication is generated.
`HwComponentObjectPath` (Sun-specific) | string | Object path of the associated hardware component. | The object path of an instance of `CIM_PhysicalElement`.
`ObservedValue` | string | A string holding the current reading value that exceeds the threshold. This is modeled as a string for universal mapping, similar to the `CIM_Sensor` properties in the device model. | Appropriate value.
`ProbableCause` | uint16[] | Enumerated value that describes the probable cause of the situation which resulted in the `AlertIndication`. The following values apply: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130} Definitions for the above values are: {Unknown, Other, Adapter/Card Error, Application Subsystem Failure, Bandwidth Reduced, Connection Establishment Error,Communications Protocol Error, Communications Subsystem Failure, Configuration/Customization Error, Congestion, Corrupt Data, CPU Cycles Limit Exceeded, Dataset/Modem Error, Degraded Signal, DTE-DCE Interface Error, Enclosure Door Open, Equipment Malfunction, Excessive Vibration, File Format Error, Fire Detected, Flood Detected, Framing Error, HVAC Problem, Humidity Unacceptable, I/O Device Error, Input Device Error, LAN Error, Non-Toxic Leak Detected, Local Node Transmission Error, Loss of Frame, Loss of Signal, Material Supply Exhausted, Multiplexer Problem, Out of Memory, Output Device Error, Performance Degraded, Power Problem, Pressure Unacceptable, Processor Problem (Internal Machine Error), Pump Failure, Queue SizeExceeded, Receive Failure, Receiver Failure, Remote NodeTransmission Error, Resource ator Nearing Capacity, ResponseTime Excessive, RetransmissionRate Excessive, Software Error, Software Program AbnormallyTerminated, Software Program Error (Incorrect Results), Storage Capacity Problem, Temperature Unacceptable, Threshold Crossed, Timing Problem, Toxic Leak Detected, Transmit Failure, Transmitter Failure, Underlying Resource Unavailable, Version MisMatch, Previous AlertCleared, Login Attempts Failed, Software Virus Detected,Hardware Security Breached, Denial of Service Detected, Security Credential MisMatch, | Set to `52` (Threshold Crossed).
|  | Unauthorized Access, Alarm Received, Loss of Pointer,Payload Mismatch, Transmission Error, Excessive Error Rate, Trace Problem, Element Unavailable,Element Missing, Loss of MultiFrame, Broadcast Channel Failure, Invalid Message Received,Routing Failure, Backplane Failure, Identifier Duplication,Protection Path Failure, Sync Lossor Mismatch, Terminal Problem, Real Time Clock Failure, Antenna Failure, Battery Charging Failure,Disk Failure, Frequency Hopping Failure, Loss of Redundancy, Power Supply Failure, Signal Quality Problem, Battery Discharging, Battery Failure,Commercial Power Problem, FanFailure, Engine Failure, SensorFailure, Fuse Failure, GeneratorFailure, Low Battery, Low Fuel,Low Water, Explosive Gas, High Winds, Ice Buildup, Smoke,Memory Mismatch, Out of CPU Cycles, Software Environment Problem, Software Download Failure, Element Reinitialized, Timeout, Logging Problems, Leak Detected, Protection Mechanism Failure, Protecting Resource Failure, Database Inconsistency,Authentication Failure, Breach of Confidentiality, Cable Tamper,Delayed Information, Duplicate Information, Information Missing, Information Modification,Information Out of Sequence, Key Expired, Non-Repudiation Failure, Out of Hours Activity, Out of Service, Procedural Error,Unexpected Information} |
`ProviderName` | string | The name of the provider generating this indication. | Appropriate value.
`SystemCreationClassName` | string | The `SystemCreationClassName` the scoping system (provider generating this indication). | Will have the value `Oracle_ComputerSystem`.
`SystemName` | string | Indicates the `SystemName` for the scoping system (name for the provider generating this indication). | Will have the value `Oracle_ComputerSystem.Name` of the instance of `Oracle_ComputerSystem` representing the controllee.
`ThresholdIdentifier` | string | Describes the threshold or names the property that represents the threshold, if modeled in the CIM hierarchy. In the latter case, the value should be written as: `<schema name>_ <class name>.<property name>`. | Appropriate value.
`ThresholdValue` | string | Current value of the threshold. This is modeled as a string for universal mapping, similar to the `CIM_Sensor` properties in the device model. | Appropriate value.

##

Oracle_UseOfLog

Description: | The `Oracle_UseOfLog` is used to associate an instance of a `Oracle_RecordLog` to an instance of the`Oracle_ComputerSystem`, which represents the controllee.
Inheritance: | `CIM_UseOfLog`
Properties: | For a description of the supported properties for the `Oracle_UseOfLog` class, see TABLE A-33. Note - For more details about Oracle’s Sun-supported properties (described in TABLE A-33), see the DMTF CIM schema, version 2.18.1, at: `http://www.dmtf.org/standards/cim/cim_schema_v2181/`
Profile: | Record Log Base Server

TABLE A-33 Properties for Oracle_UseOfLog
Property | Data Type | Description | ILOM Value
--- | --- | --- | ---
`Antecedent` | `Oracle_RecordLog` REF | The `Antecedent` property is a mandatory key property. Instance of `Oracle_RecordLog` | Object path to the instance of `Oracle_RecordLog` representing the IPMI SEL log.
`Dependent` | `Oracle_ComputerSystem` REF | The `Dependent` property is a mandatory key property. The `Oracle_ComputerSystem`. | Object path to the instance of `Oracle_ComputerSystem` representing the controllee.

Copyright © 2010, Oracle and/or its affiliates. All rights reserved.