Reference Guide
Dell OpenManage Client Instrumentation Reference Guide
file:///T|/htdocs/SOFTWARE/smcliins/cli80/EN/refgd/index.htm[10/19/2012 9:56:27 AM]
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.
ChangeBootOrder (Method)
This method is called to change the boot order within a boot configuration. An ordered array of BootSourceSetting instances is passed to this
method. Each BootSourceSetting instance MUST already be associated with this BootConfigSetting instance via an instance of
OrderedComponent. If not, the implementation MUST return a value of "Invalid Parameter" Upon execution of this method, the value of the
AssignedSequence property on each instance of OrderedComponent will be updated such that the values are monotonically increasing in
correlation with the position of the referenced BootSourceSetting instance in the source input parameter. That is, the first position in the array
will have the lowest value for AssignedSequence. The second position will have the second lowest value, and so on. For BootSourceSetting
instances which are associated with the BootConfigSetting instance via OrderedComponent and not present in the input array, the
AssignedSequence property on the OrderedComponent association will be assigned a value of 0.
DCIM_IPAssignmentSettingData
AddressOrigin
AddressOrigin identifies the method by which the IP Address, Subnet Mask, and Gateway were assigned to the IPProtocolEndpoint.
Possible values are:
0 - Unknown
1 - Other
2 - Not Applicable - Indicates that the application of the IPAssignmentSettingData instance does not affect these properties.
3 - Static - Indicates that values for the properties are contained in the IPAssignmentSettingData instance.
4 - DHCP - Indicates that the values will be assigned via DHCP.
5 - BOOTP - Iindicates that the values will be assigned via BOOTP.
6..32767 - DMTF Reserved
32768.. - Vendor Reserved
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:
<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 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 "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_PowerAllocationSettingData
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:
<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 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 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.
Limit
This property specifies the upper bound, or maximum amount of resource that will be granted for this allocation. For example, a system which
supports memory paging may support setting the Limit of a Memory allocation below that of the VirtualQuantity, thus forcing paging to occur for
this allocation.
PowerAllocationSettingPurpose
When power is consumed by or allocated to a ManagedSystemElement, there may be well-known or meaningful levels of allocation or
consumption for the ManagedSystemElement. The PowerAllocationSettingPurpose property may be used to identify the well known level or
provide context for the interpretation of the other values of the PowerAllocationSettingData instance.
Possible values are:
1 - Other
2 - MaxConAuxiliary - Indicates the instance provides information about the maximum power allocated or consumed by the
ManagedSystemElement as currently configured, while the ManagedSystemElement is turned off and drawing auxiliary power.
3 - MinWhenOn - Indicates the instance provides information about the minimum value for power consumption for which a configuration of the
ManagedSystemElement exists such that when it is powered on and operating in that configuration, the power consumption of the
ManagedSystemElement is guaranteed not to exceed the specified amount.
4 - MaxAsConfigured - Indicates the instance provides information about the maximum power that may be allocated to or consumed by the
ManagedSystemElement as currently configured while powered on. The actual power consumed may be less.
5 - MaxIfAllHotPlug - Indicates the instance provides information about the maximum power allocated or consumed by the
ManagedSystemElement if all components that could be added to the ManagedSystemElement without requiring a power cycle of the
ManagedSystemElement were added to the ManagedSystemElement.
6 - MaxIfAllColdPlug - Indicates the instance provides information about the maximum power allocated or consumed by the
ManagedSystemElement if all components that could be added to the ManagedSystemElement, including those that require a power cycle of the
ManagedSystemElement, were added to the ManagedSystemElement.
7 - Allocated - Indicates the instance provides information about the current power allocated to the ManagedSystemElement.
8 - MinWithoutDegradation - Indicates the instance provides information about the minimum power allocated or consumed by the
ManagedSystemElement with out causing performance degradation.
.. - DMTF Reserved
32768..65535 - Vendor Reserved
Note:
An alternate name for "auxiliary power" is "trickle power".
The type of resource this allocation setting represents.
Possible values are:
1 - Other
2 - Computer System
3 - Processor
4 - Memory
5 - IDE Controller
6 - Parallel SCSI HBA
7 - FC HBA
8 - iSCSI HBA
9 - IB HCA