White Papers

Power Utilization Management Profile
service1 : DCIM_OEMPowerUtilizationManagementService
PowerUtilizationMode : 3 (Dynamic)
PowerUtilizationAlgorithm : 7 (Active Power Utilization)
PendingPowerUtilizationAlgorithm : 3 (Custtom Settings Based)
sys1 : ComputerSystem
cap1 : DCIM_OEMPowerUtilizationManagementCapabilities
SupportedMethods: {32769 (RequestPowerUtilizationAlgorithm) }
SupportedRequestedAlgorithms: { 2 (None), 3 (Custom Settings
Based), 4 (Maximum Performance), 5(Minimum Performance),
6(OS Specific), 7 (Active Power Utilization)}
RequiredCustomSettings : { 2 (CPUPowerMode), 3
(MemoryPowerMode), 4 (OtherMemoryPowerMode),
5(FanPowerMode)
HostedService
ElementCapabilities
ServiceAffectsElement
customsettingdata1 :
DCIM_OEMPowerUtilizationCustomSettingData
CPUPowerMode : 4 (OS Demand Based)
MemoryPowerMode : 1 (Other)
OtherMemoryPowerMode : 1067
FanPowerMode : 3 (Min Power)
ElementSettingData
Is Pending : 2(Is Pending)
Is Current : 2(Is Not Current)
Figure 4 – Power Utilization Management Profile: After RequestPowerUtilizationAlgorithm()
9.2.3 After the Managed System Reboot
Figure 5 represents an instantiation of Power Utilization Management Profile after the reboot of the
managed system. The pending settings have been applied, and the service1.PowerUtilizationAlgorithm
property reflects the executed method’s RequestedAlgorithms parameter value. Customsettingdata1 is
not pending, but reflects the current custom settings as ElementSettingData association’s properties
indicate.
24 Version 1.0.0a