Problems with power state change

[StanleyO]

Hello,

  We have some deployments for Lenovo P3 Tiny devices. As part of the deployment, we are making a WSMAN call to change the power state. The affected devices are deploying in a 3 node cluster. 

  When the call is made the node powers off and does not come back on without manual intervention with our separate KVM which still has power control. Below is the code to evaluate the power state and attempt to change the state. If needed I can provide the code from a 3 node cluster that did work. 

  This is my first time trying to deploy using AMT and find it odd that some clusters are fine, but others are not. Lenovo support didn't have any answers. Below is the result from getting power status and also the result of the attempt to change the mode. We are trying to set the status to 8 Power Cycle (Off Hard). is there a better power setting to use when forcing a reboot to PXE?

Thank You in advance, this topic is very new to me.

2024-06-26T11:04:36.1462015Z VERBOSE: ========================================
2024-06-26T11:04:36.1469814Z VERBOSE: Parsing results for current power state...
2024-06-26T11:04:36.1509462Z VERBOSE: Beginning to execute script: 
2024-06-26T11:04:36.1509762Z 
2024-06-26T11:04:36.1510331Z             param([System.Security.SecureString]$secStringPassword)
2024-06-26T11:04:36.1510564Z 
2024-06-26T11:04:36.1511440Z             $credential = New-Object System.Management.Automation.PSCredential ('Administrator', $secStringPassword)
2024-06-26T11:04:36.1511774Z 
2024-06-26T11:04:36.1512112Z             
2024-06-26T11:04:36.1512254Z 
2024-06-26T11:04:36.1512557Z $soapRequest = @"
2024-06-26T11:04:36.1512698Z 
2024-06-26T11:04:36.1513301Z                     <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
2024-06-26T11:04:36.1513549Z 
2024-06-26T11:04:36.1513947Z                         xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
2024-06-26T11:04:36.1514214Z 
2024-06-26T11:04:36.1514640Z                         xmlns:wsman="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd"
2024-06-26T11:04:36.1514898Z 
2024-06-26T11:04:36.1515518Z                         xmlns:n1="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService">
2024-06-26T11:04:36.1522395Z 
2024-06-26T11:04:36.1522899Z                         <s:Header>
2024-06-26T11:04:36.1523077Z 
2024-06-26T11:04:36.1523416Z                             <wsa:Action 
2024-06-26T11:04:36.1524552Z s:mustUnderstand="true">http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService/RequestPowerStateC
2024-06-26T11:04:36.1525075Z hange</wsa:Action>
2024-06-26T11:04:36.1525227Z 
2024-06-26T11:04:36.1534759Z                             <wsa:To s:mustUnderstand="true">https://100.100.61.14:16993/wsman</wsa:To>
2024-06-26T11:04:36.1535177Z 
2024-06-26T11:04:36.1535663Z                             <wsman:ResourceURI 
2024-06-26T11:04:36.1537048Z s:mustUnderstand="true">http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_PowerManagementService</wsman:ResourceURI
2024-06-26T11:04:36.1537677Z >
2024-06-26T11:04:36.1537820Z 
2024-06-26T11:04:36.1538241Z                             <wsa:MessageID 
2024-06-26T11:04:36.1538980Z s:mustUnderstand="true">uuid:e6747be1-e587-4a0b-ad74-40c43347b1eb</wsa:MessageID>
2024-06-26T11:04:36.1539381Z 
2024-06-26T11:04:36.1539813Z                             <wsa:ReplyTo>
2024-06-26T11:04:36.1540044Z 
2024-06-26T11:04:36.1540428Z                                 
2024-06-26T11:04:36.1541351Z <wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
2024-06-26T11:04:36.1541715Z 
2024-06-26T11:04:36.1542170Z                             </wsa:ReplyTo>
2024-06-26T11:04:36.1542419Z 
2024-06-26T11:04:36.1542793Z                             
2024-06-26T11:04:36.1542963Z 
2024-06-26T11:04:36.1543367Z                         </s:Header>
2024-06-26T11:04:36.1543578Z 
2024-06-26T11:04:36.1545840Z                         <s:Body>
2024-06-26T11:04:36.1546065Z 
2024-06-26T11:04:36.1546500Z                             <n1:RequestPowerStateChange_INPUT>
2024-06-26T11:04:36.1546724Z 
2024-06-26T11:04:36.1547003Z                                 <n1:PowerState>8</n1:PowerState>
2024-06-26T11:04:36.1547149Z 
2024-06-26T11:04:36.1547236Z 
2024-06-26T11:04:36.1547322Z 
2024-06-26T11:04:36.1547552Z <n1:ManagedElement>
2024-06-26T11:04:36.1547658Z 
2024-06-26T11:04:36.1548314Z     <wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>
2024-06-26T11:04:36.1548548Z 
2024-06-26T11:04:36.1548808Z     <wsa:ReferenceParameters>
2024-06-26T11:04:36.1548924Z 
2024-06-26T11:04:36.1549492Z         <wsman:ResourceURI>http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ComputerSystem</wsman:ResourceURI>
2024-06-26T11:04:36.1550321Z 
2024-06-26T11:04:36.1550587Z         <wsman:SelectorSet>
2024-06-26T11:04:36.1550703Z 
2024-06-26T11:04:36.1551009Z     <wsman:Selector Name="Name">ManagedSystem</wsman:Selector>
2024-06-26T11:04:36.1551184Z 
2024-06-26T11:04:36.1551416Z </wsman:SelectorSet>
2024-06-26T11:04:36.1551525Z 
2024-06-26T11:04:36.1551614Z 
2024-06-26T11:04:36.1551697Z 
2024-06-26T11:04:36.1551915Z     </wsa:ReferenceParameters>
2024-06-26T11:04:36.1552048Z 
2024-06-26T11:04:36.1552268Z </n1:ManagedElement>
2024-06-26T11:04:36.1552387Z 
2024-06-26T11:04:36.1552459Z 
2024-06-26T11:04:36.1552542Z 
2024-06-26T11:04:36.1552625Z 
2024-06-26T11:04:36.1552694Z 
2024-06-26T11:04:36.1552952Z                             </n1:RequestPowerStateChange_INPUT>
2024-06-26T11:04:36.1553098Z 
2024-06-26T11:04:36.1553321Z                         </s:Body>
2024-06-26T11:04:36.1553422Z 
2024-06-26T11:04:36.1553643Z                     </s:Envelope>
2024-06-26T11:04:36.1553757Z 

[Suneesh]

Hello StanelyO,

Greetings of the day.

We are investigating the matter and will get back to you as soon as possible. If you have any further questions or additional information to share.

Please feel free to reply to this email. We're here to assist you every step of the way.

Best regards,

Suneesh 

[Suneesh]

Hello StanelyO,

Greetings!

For a detailed explanation of supported power states, please refer to the Intel vPro AMT SDK.

https://software.intel.com/sites/manageability/AMT_Implementation_and_Reference_Guide/default.htm?turl=HTMLDocuments%2FWS-Management_Class_Reference%2FAMT_GeneralSettings.htm%23PrivacyLevel

These are list of potentially supported (must meet environmental conditions) power AMT options....

Power up

Sleep

Hibernate

Power Down

Force Reset

Soft Off 

Reset

Power up to BIOS

Reset to BIOS

Reset to IDE-R Image

Power on IDE-R Image

Reset to IDE-R CDROM

Power on to IDE-R CDROM

Reset to PXE

Power on to PXE

At the application level, you may find it easier to use PowerShell to interface with AMT. You can use PowerShell to perform a soft reset to PXE instead of a full power-off by using a WMI command.

https://www.intel.com/content/www/us/en/download/704395/intel-vpro-technology-module-for-windows-powershell.html

Regards,

Suneesh

[Suneesh]

Hello StanelyO,

Greetings!

This is the first follow-up regarding the issue you reported to us.

We wanted to inquire whether you had the opportunity to review the plan of action (POA) we provided.

Feel free to reply to this email, and we'll be more than happy to assist you further.

Regards,

Suneesh

[Suneesh]

Hello StanelyO,

Greetings!

If further assistance is necessary, do not hesitate to reply or create a new thread.

Regards,

Suneesh