Reference Guide

ManualsBrandsDell ManualsAnalyticsOpenManage Client Instrumentation Version 8.1

The Reference Guide contains the

file:///T|/htdocs/SOFTWARE/smcliins/cli81/en/refgd/index.html[10/19/2012 10:01:19 AM]

105 = Smoke

106 = Memory Mismatch

107 = Out of CPU Cycles

108 = Software Environment Problem

109 = Software Download Failure

110 = Element Reinitialized

111 = Timeout

112 = Logging Problems

113 = Leak Detected

114 = Protection Mechanism Failure

115 = Protecting Resource Failure

116 = Database Inconsistency

117 = Authentication Failure

118 = Breach of Confidentiality

119 = Cable Tamper

120 = Delayed Information

121 = Duplicate Information

122 = Information Missing

123 = Information Modification

124 = Information Out of Sequence

125 = Key Expired

126 = Non-Repudiation Failure

127 = Out of Hours Activity

128 = Out of Service

129 = Procedural Error

130 = Unexpected Information

StartDelay The start delay before polling the event source, in seconds.

DCIM_HDDAlertIndicationSettingData

ElementName

The user-friendly name for this instance of SettingData. In addition, the user-friendly name can be used as an index property for a search or query.

Note: The name does not have to be unique within a namespace.

InstanceID

Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the

following "preferred" algorithm:

Where <OrgID> and <LocalID> are separated by a colon (:), and where <OrgID> must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the

InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to

ensure uniqueness, <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 reused to identify different underlying (real-world) elements. If the above "preferred" algorithm is not used, the defining entity must assure that the resulting

InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance.

For DMTF-defined instances, the "preferred" algorithm must be used with the <OrgID> set to CIM.

DCIM_BaseMetricValue

Duration

Property that represents the time duration over which this metric value is valid. This property should not exist for timestamps that apply only to a point in time but should be defined for values that are considered valid for

a certain time period (ex. sampling). If the "Duration" property exists and is nonNull, the TimeStamp is to be considered the end of the interval.

InstanceID

Within the scope of the instantiating Namespace, InstanceID opaquely and 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:

Where and are separated by a colon ':', and where MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating/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.) In addition, to ensure uniqueness MUST NOT contain a colon (':').

When using this algorithm, the first colon to appear in InstanceID MUST appear between and .

is chosen by the business entity and SHOULD not be re-used to identify different underlying (real-world) elements. If the above 'preferred' algorithm is not used, the defining entity MUST assure that the resultant

InstanceID is not re-used across any InstanceIDs produced by this or other providers for this instance's NameSpace.

For DMTF defined instances, the 'preferred' algorithm MUST be used with the set to 'CIM'.

MetricDefinitionId The key of the BaseMetricDefinition instance for this CIM_BaseMetricValue instance value.

MetricValue The value of the metric represented as a string. Its original data type is specified in CIM_BaseMetricDefinition.

TimeStamp

Identifies the time when the value of a metric instance is computed. Note that this is different from the time when the instance is created. For a given CIM_BaseMetricValue instance, the TimeStamp changes whenever a

new measurement snapshot is taken if Volatile is true. A managmenet application may establish a time series of metric data by retrieving the instances of CIM_BaseMetricValue and sorting them according to their

TimeStamp.

Volatile

If true, Volatile indicates that the value for the next point in time may use the same object and just change its properties (such as the value or timestamp). If false, the existing objects remain unchanged and a new object

is created for the new point in time.

DCIM_LogEntry

CreationTimeStamp A LogEntry may include a timestamp for the entry.

ElementName

A user-friendly name for the object. 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.

InstanceID

Within the scope of the instantiating Namespace, InstanceID opaquely and 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:

Where <OrgID> and <LocalID> are separated by a

colon ':', and where <OrgID> MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating/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.) In

addition, to ensure uniqueness <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. If the above 'preferred' algorithm is not

used, the defining entity MUST assure that the resultant InstanceID is not re-used across any InstanceIDs produced by this or other providers for this instance's NameSpace.

For

DMTF defined instances, the 'preferred' algorithm MUST be used with the <OrgID> set to 'CIM'.

A string containing LogRecord data.