Dell OpenManage Client Instrumentation Version 8.1 : Reference Guide : Page 81

The Reference Guide contains the

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

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

NumberOfHardwareThreads Number of hardware threads available for the processor. May be obtained from SMBIOS v2.5 4 offset 25h.

NumberOfProcessorCores Number of processor cores available for processor. This number would not include cores disabled by hardware and may be obtained from SMBIOS 2.5 Type 4 offset 23h.

DCIM_AccountManagementCapabilities

ElementNameEditSupported Boolean indicating whether the ElementName can be modified.

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

OperationsSupported

OperationsSupported describes the type of operations that are supported for an Account associated with the AccountManagementService.

Possible values are:

2 = Create - Iindicates the AccountManagementService may be used to create new accounts.

3 = Modify - Indicates that the associated Accounts may be modified.

4 = Delete - Indicates that associated Accounts may be deleted.

.. = DMTF Reserved

0x8000..0xFFFF = Vendor Reserved

DCIM_BootServiceCapabilities

BootStringsSupported

An enumeration indicating the boot string properties in the CIM_BootSourceSetting which are supported. If the array contains a value, then all the BootSourceSetting instances managed by the service are guaranteed to

have a non-null value for the corresponding property.Since this is an array, multiple values may be specified.

Possible values are:

2 = BootString

3 = BIOSBootString

4 = StructuredBootString

ElementName

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

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

ElementNameEditSupported Boolean indicating whether the ElementName can be modified.

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

DCIM_PlatformWatchdogServiceCapabilities

ActionOnExpirationSupported

ActionOnExpirationSupported indicates the actions which can be performed when the watchdog timer expires. See CIM_PlatformWatchdogService.ActionOnExpiration for a description of the values.

Possible values are:

2 = None - Status Only

3 = System Reset

4 = System Power Off

5 = System Power Off, then On

6 = Generate System NonMaskableInterrupt (NMI)

7 = Generate System Management Interrupt (SMI)

8 = Reset Monitored Entity

ElementName

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

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

ElementNameEditSupported Boolean indicating whether the ElementName can be modified.

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

LastExpirationDataSupported

LastExpirationDataSupported indicates the data which is provided on the last expiration of the watchdog timer. The values in the enumeration are: A value set to 2 = "Time" indicates that the time of the last expiration is

provided.

RequestedStatesSupported

RequestedStatesSupported indicates the possible states that can be requested when using the method RequestStateChange on the EnabledLogicalElement.

Possible values are:

2 = Enabled

3 = Disabled

4 = Shut Down

6 = Offline

7 = Test