Reference Guide

Property Description
Possible values are:
• 0 = Unknown
• 2 = CPUPowerMode
• 3 = MemoryPowerMode
• 4 = OtherMemoryPowerMode
• 5 = FanPowerMode
SupportedMethods
Each enumeration corresponds to support for the like-named method
of the MetricService.
Possible values are:
• .. = DMTF Reserved
• 32768 = RequestPowerUtilizationLimit
• 32769 = RequestPowerUtilizationAlgorithm
• 32770 = RequestPowerUtilizationAlgorithmEI
• 32771..65535 = Vendor Specific
SupportedRequestedAlgorithms
Array of power utilization algorithms supported by the
RequestPowerUtilizationAlgorithm and
RequestPowerUtilizationAlgorithmEI methods' RequestedAlgorithm
parameter of the associated Service.
SupportedUtilizationLimitUnits
Array of programmatic units for power utilization limit supported by
the RequestPowerUtilizationLimit method's UtilizationLimit
parameter.
DCIM_EnabledLogicalElementCapabilities
Property Description
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. 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 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
236