![]() |
The following steps describe how to change the power state of the platform. This section follows the approach of section 9.5 of DSP1027.
|
• If there is an active redirection session (SOL, Storage Redirection, or KVM), then a power cycle or a power off command will be rejected as invalid. See Intel AMT Power State Transitions. • Do not request a second power state change without allowing the first request to complete. Completion in this case is defined as allowing the BIOS to inform Intel AMT that it has completed its tasks. This can take as much as 10 seconds, depending on the OEM platform. • On a platform that supports Connected Standby or Modern Standby, Intel AMT remote control commands do not support transitioning the platform to Sleep state (S3), Connected Standby or Modern Standby. |
1. Retrieve the instance of CIM_PowerManagementService, using the “Name” key equal to “Intel(r) AMT Power Management Service”.
2. Invoke CIM_PowerManagementService.RequestPowerStateChange using the following parameters:
Parameter | Value |
Power State | One of the defined power states |
Managed Element | A reference to the “managed system” object |
Time | NULL |
TimeoutPeriod | NULL |
The following table lists all possible system power states and those states which are able to be changed.
Power State ValueMap | Value | Pre-9.0 | 9.0 |
2 (Power On) | Initiate the transition of the system to full on state (corresponding ACPI state G0/S0) | Y | Y |
3 (Sleep - Light) | Initiate the transition of the system to standby or sleep state (corresponding ACPI state G1/S1 or G1/S2) |
|
|
4 (Sleep - Deep) | Initiate the transition of the system to standby or sleep state (corresponding ACPI state G1/S3). |
| Y |
5 (Power Cycle (Off Soft)) | Transition the system to off state (corresponding ACPI state G2/S5), in which the system consumes a minimal amount of power, followed by a transition to on state (corresponding ACPI state G0/S0). | Y | Y |
6 (Power Off - Hard) | Initiate the transition of the system to power off state (corresponding ACPI state G3), in which the power consumption is zero except for the real-time clock. |
|
|
7 (Hibernate) | Transition the system to hibernation state (corresponding ACPI state G1/S4) – write system context to non-volatile storage, power off the system and devices. |
| Y |
8 (Power Off - Soft) | Initiate the transition of the system to off state (corresponding ACPI state G2/S5), in which the system consumes a minimal amount of power | Y | Y |
9 (Power Cycle (Off Hard)) | Transition the system to power off state (corresponding ACPI state G3), in which the power consumption is zero except for the real-time clock, followed by a transition to on state (corresponding ACPI state G0/S0). |
|
|
10 (Master Bus Reset) | Perform hardware reset on the system. | Y | Y |
11 (Diagnostic Interrupt (NMI)) | Assert an NMI on the system. |
| Y |
12 (Power Off - Soft Graceful) | Perform an orderly transition to power off state (corresponding ACPI state G2/S5), in which the system consumes a minimal amount of power. |
| Y |
13 (Power Off - Hard Graceful) | Perform an orderly transition to power off state (corresponding ACPI state G3), in which the power consumption is zero except for the real-time clock. |
|
|
14 (Master Bus Reset Graceful) | Perform an orderly shutdown of the system followed by hardware reset. |
| Y |
15 (Power Cycle (Off - Soft Graceful)) | Perform an orderly transition of the system to power off state (corresponding ACPI state G2/S5), in which the system consumes a minimal amount of power, followed by a transition to on state (corresponding ACPI state G0/S0). |
|
|
16 (Power Cycle (Off - Hard Graceful)) | Perform an orderly transition of the system to power off state (corresponding ACPI state G3), in which the power consumption is zero except for the realtime clock, followed by a transition to on state (corresponding ACPI state G0/S0). |
|
|
.. | DMTF Reserved. |
|
|
0x7FFF..0xFFFF | Vendor Specific. |
|
|
Click here for a snippet demonstrating this step
You can execute this snippet by inserting it into the execution template found here.
$powerManagementRef =$wsmanConnectionObject.NewReference("SELECT * FROM CIM_PowerManagementService WHERE Name='Intel(r) AMT Power Management Service'")
$inputObject =$powerManagementRef.CreateMethodInput("RequestPowerStateChange")
$inputObject.SetProperty("PowerState","5") # '5' = SoftPowerCycle.
$computerSystemRef =$wsmanConnectionObject.NewReference("SELECT * FROM CIM_ComputerSystem WHERE Name='ManagedSystem'")
$inputObject.SetProperty("ManagedElement",$computerSystemRef)
$outputObject =$powerManagementRef.InvokeMethod($inputObject)
$returnValue =$outputObject.GetProperty("ReturnValue")
|
The method CIM_PowerManagementService.RequestPowerStateChange is blocked locally and is only available to remote users. (It was available locally only in Release 6.1) |
Additional Information
The Power State must one supported by the platform (see Get System Power Management Capabilities). The transition must be valid from the current power state (see Intel AMT Power State Transitions).
As of Release 6.0, Intel AMT does not support the Time and Timeout fields.
Instance Diagram
Classes Used in This Flow
SDK Sample
If there is a sample demonstrating this flow, it is included in the SDK installation file. See SDK Installation Layout for details.
See Also: |
• Supported Power Management States |
Copyright © 2006-2022, Intel Corporation. All rights reserved. |