Reference Guide

The Reference Guide contains the
file:///T|/htdocs/SOFTWARE/smcliins/cli81/en/refgd/index.html[10/19/2012 10:01:19 AM]
RecordData
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.
RecordFormat
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 (i.e., 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".
RecordID RecordID may be used to provide a representation of log entry ordering or pointers/handles for log entries.
DCIM_IndicatorLEDCapabilities
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:
<OrgID>:<LocalID>
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'.
SupportedActivationStates
SupportedActivationStates indicates the supported activation states for the associated IndicatorLED. See CIM_IndicatorLED.ActivationState for descriptions of the values.
Possible values are:
2 = Lit
3 = Blinking
4 = Off
5 = Control Pattern
.. = DMTF Reserved
32768..65535 = Vendor Reserved
SupportedColors
This property indicates the colors supported by the associated instance of CIM_IndicatorLED.
Possible values are:
1 = Other
3 = White
4 = Red
5 = Green
6 = Blue
7 = Orange
8 = Yellow
9 = Black
.. = DMTF Reserved
32768..65535 = Vendor Reserved
SupportedControlModes
SupportedControlModes indicates the control modes supported for the LED.See CIM_IndicatorLED.CurrentControlMode for more information.
Possible values are:
2 = Automatic
3 = Manual
4 = Test
.. = DMTF Reserved
32768..65535 = Vendor Reserved
SupportedControlPatterns
SupportedControlPatterns describes the control patterns supported by the associated LED. The values of SupportedControlPatterns may be an exact match for values allowed for CIM_IndicatorLED.ControlPatterns or may
indicate general categories of behavior. The interpretation of value is specific to the business entity identified by <OrgID>.
Each value of SupportedControlPatterns is constructed using the following "preferred" algorithm: <OrgID>::<Pattern>
Where <OrgID> and < Pattern> are separated by two colons (::), and where <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. <Pattern> is chosen by the business entity and is not reused to identify different underlying (real-world) behaviors.
If the behavior specified for the LED adheres to a standard or proprietary specification, <Pattern> is a uniquely assigned value identifying the behavior. If the behavior for the LED is described using a standard or
proprietary grammar, <Pattern> is prefixed with a uniquely assigned identifier for the grammar.
SupportedIndicatedConditions
The conditions that may be indicated by the LED.See CIM_IndicatorLED.IndicatedCondition for a description of the values.
Possible values are:
1 = Other
3 = Location
4 = Attention
5 = Activity
6 = Powered On
7 = Fault
.. = DMTF Reserved
32768..65535 = Vendor Reserved
DCIM_ProcessorCapabilities
ElementNameEditSupported Boolean indicating whether the ElementName can be modified.
ElementNameMask
This string expresses the restrictions on ElementName.The mask is expressed as a regular expression.See DMTF standard ABNF with the Profile Users Guide, appendix C for the regular expression syntax permitted.
Since the ElementNameMask can describe the maximum lengthof the ElementName, then the requirements expressed in this property takes precidence of any length expressed in MaxElementNameLen.
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:
<OrgID>:<LocalID>
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>.