Unsolved
This post is more than 5 years old
1 Rookie
•
21 Posts
0
1121
March 17th, 2020 16:00
OME API: Power off after firmware update job?
Is there a parameter we can pass to power off servers after a firmware update job? Currently we are just running a power control job against the entire group to power them all off, but are hoping for a more elegant solution.
For example, when we run a Deployment job (to apply a template) we can use
"EndHostPowerState":
with a value of 0 or 1 to control if the server remains on or off after the deployment. Is there anything comparable for firmware update jobs?
No Events found!
DELL-Joey C
Moderator
•
4.2K Posts
•
21K Points
0
March 18th, 2020 01:00
Hello.
I am not very verse with OME API scripting, but I reached out to engineering about it. It seems that there is no specified parameter after an update, due to it should reboot after the update due to CSIOR. So in order to power off the server, you may need to run another shutdown script, similar to the deployment parameter, but it is risk as, the firmware need time to update properly after a reboot to take effect.
ut_fleet
1 Rookie
•
21 Posts
0
March 23rd, 2020 12:00
That all makes sense, but OpenManage handles similar use cases to turn off the servers, like after applying templates (also needs to wait for the template to apply, and then creates a power off job). It seems like it would be straightforward to port this capability to Firmware Update jobs.
DELL-Joey C
Moderator
•
4.2K Posts
•
21K Points
0
March 23rd, 2020 19:00
You have a point. Though, I've reached out to the engineering about the API, on the scripts, and they reply were because of the issue on non-monitoring update that can cause a firmware corruption if a reboot is initiated. It is as designed not to have the command.