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

The Reference Guide contains the

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

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

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

8 = Defer

9 = Quiesce

10 = Reboot

11 = Reset

DCIM_LCDPanelCapabilities

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

SupportedDisplayDataCategories

Identifies the category of data to be displayed on the LCD Panel.

Possible values are:

2 = None

3 = User Specified

4 = Default

5 = IPv4 Address

6 = IDRAC MAC Address

7 = Service Tag

8 = System Name

9 = IPv6 Address

10 = Ambient

11 = System Power

DCIM_PowerManagementCapabilities

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.

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

PowerChangeCapabilities

An enumeration indicating the specific power-related capabilities of a managed element. Since this is an array, multiple values may be specified.

Possible values are:

0 = Unknown

1 = Other

2 = Power Saving Modes Entered Automatically - Indicates that a managed element can change its power state based on usage or other criteria

3 = Power State Settable - Indicates that the RequestPowerStateChange method is supported

4 = Power Cycling Supported - Indicates that the RequestPowerStateChange method can be invoked with the PowerState input variable set to 'Power Cycle (Off Soft)'

5 = Timed Power On Supported - Indicates that the RequestPowerStateChange method can be invoked with the PowerState input variable set to 'Power On' and the Time parameter set to a specific date and time, or

interval, for power-on

.

6 = Off Hard Power Cycling Supported

7 = HW Reset Supported

8 = Graceful Shutdown Supported - Indicates that the managed element can be sent a hardware signal requesting an orderly shutdown prior to the requested power state change.

PowerStatesSupported

An enumeration that indicates the power states supported by a managed element. Because this is an array, multiple values can be specified. The current values in the enumeration are:

2 = On - Corresponds to ACPI state G0 or S0 or D0.

3 = Sleep - Light - Corresponds to ACPI state G1, S1/S2, or D1.

4 = Sleep - Deep - Ccorresponds to ACPI state G1, S3, or D2.

5 = Power Cycle (Off - Soft) - Corresponds to ACPI state G2, S5, or D3, but where the managed element is set to return to power state "On" at a pre-determined time.

6 = Off - Hard, corresponding to ACPI state G3, S5, or D3.

7 = Hibernate (Off - Soft) - Corresponds to ACPI state S4, where the state of the managed element is preserved and will be recovered upon powering on.

8 = Off - Soft, corresponding to ACPI state G2, S5, or D3.

9 = Power Cycle (Off-Hard) - Corresponds to the managed element reaching the ACPI state G3 followed by ACPI state S0.

10 = Master Bus Reset, corresponds to the system reaching ACPI state S5 followed by ACPI state S0. This is used to represent system master bus reset.

11 = Diagnostic Interrupt (NMI) - Corresponds to the system reaching ACPI state S5 followed by ACPI state S0. This is used to represent system non-maskable interrupt.

12 = Off - Soft Graceful - Equivalent to Off Soft but preceded by a request to the managed element to perform an orderlyshutdown.

13 = Off - Hard Graceful - Equivalent to Off Hard but preceded by a request to the managed element to perform an orderly shutdown.

14 = Master Bus Rest Graceful - Equivalent to Master Bus Reset but preceded by a request to the managed element to perform an orderly shutdown.