|
Post by mahantesh92 on Jul 16, 2023 23:41:16 GMT
Hello,
As specified in the Redfish schema guide, when "BootSourceOverrideEnabled" is set to "Once", On its next boot cycle, the system boots one time to the boot source override target. Then, the "BootSourceOverrideEnabled" value is reset to "Disabled".
My question is, who is responsible to reset the "BootSourceOverrideEnabled" value to "Disabled" when it was requested by user to be "Once".
Is it the user responsibility or Redfish servers or BIOS/UEFI redfish clients ?
Thanks.
|
|
|
Post by mraineri on Jul 17, 2023 1:39:22 GMT
It really depends on your system design. Some system vendors will have UEFI tell the BMC that it consumed the request and performed the one-time boot, and in other designs the BMC sets it automatically when UEFI reads it out of the BMC. UEFI may not even use Redfish to collect this information; this is also another design detail by the implementer.
However, the user is unaware of this aspect. Redfish as a standard describes what is presented to the user and what behaviors to expect; it does not mandate how this works internal to the system. From their perspective, as long as the settings goes back to Disabled after the one-time boot, then it meets the desired functional behavior.
|
|
|
Post by mahantesh92 on Jul 17, 2023 12:16:14 GMT
Understood, thank you!
|
|