Lines Matching full:bios
1 # Remote BIOS Configuration (RBC) via BMC
11 Current OpenBMC doesn't provide mechanism to configure the BIOS remotely. This
14 Remote BIOS Configuration provides ability for the user to view and modify BIOS
15 setup configuration parameters remotely via a BMC at any Host state. New BIOS
22 2. <https://redfish.dmtf.org/schemas/v1/Bios.v1_1_0.json>
27 1. Mechanism to configure BIOS settings remotely over network interface.
28 2. BMC should support the ability to set the value of all BIOS variables to the
33 send the updated BIOS variables on next BIOS boot only. It will not initiate
34 a BIOS boot immediately.
35 5. In immediate model, BMC should send message to the system firmware (BIOS)
37 6. BMC should support BIOS attribute registry in redfish schema for BIOS
39 7. BMC should provide secure way for updating BIOS setup password settings.
41 Ex: Updating the BIOS password should be support only before end of post.
42 8. Remote BIOS configuration daemon should be independent of interface specific
52 | Remote BIOS configuration (RBC) via BMC …
63 | | HOST/ BIOS +<-KCS->+ HOST-IPMID +<Dbus->+ | |Redfish| …
79 | | | Collect the BIOS data & convert| …
88 BIOS send data in as Proprietary format to the BMC via IPMI interface. There are
89 two types of proprietary XML format files in BIOS configuration. Type-0 contain
90 full BIOS variables in XML format. (Generated by BIOS) Type-1 contain modified
91 BIOS variables in XML format. (Generated by BMC)
93 BIOS must provide BIOS capability via KCS interface in early boot stage. BIOS
100 During BDS phase in BIOS. BIOS must get the existing XML info from BMC. If XML
101 version/checksum is mismatch or XML Type 0 is not present in BMC, then BIOS must
103 BIOS attributes list exist (XML Type 1) in BMC then BIOS must get pending BIOS
104 configuration (XML Type 1) from BMC & update in BIOS region and send updated XML
105 Type 0 to the BMC in order to intact again and then BIOS reset the system to
106 reflect the updated values in BIOS boot.
108 BIOS have default BIOS settings in BIOS non-volatile memory. BIOS can restore
109 the default BIOS configuration based on the flag setting in OEM IPMI command
110 issued during BIOS booting. So, restore default BIOS configuration can be done
117 ### Intel logic for BIOS first boot
123 …| | BIOS | | BMC …
126 … | | | -Responsible for send /recv | |-Responsible for handling BIOS| ||
127 …| | | | | data between BIOS and BMC | | configuratio…
134 …| | Set BIOS capability |<---Req-/Res--> | Set the BIOS capability | | …
136 …| |Set BIOS Pwd hash/Seed |<---Req-/Res--> | Forward to the RBC daemon |--dbus-->| Set BIOSPwd…
140 …| |Init the BIOS config | | | | | …
149 …| | Continue the BIOS boot| | | | | …
155 ### Intel logic for BIOS reset
161 …| | BIOS | | BMC …
164 … | | | -Responsible for send /recv | |-Responsible for handling BIOS| ||
165 …| | | | | data between BIOS and BMC | | configuratio…
172 …| |Set BIOS capability |<---Req-/Res--> | Set the BIOS capability | | …
174 …| |Set BIOS Pwd hash/Seed |<---Req-/Res--> | Forward to the RBC daemon |--dbus-->| Set BIOSPwd…
178 …| |Init the BIOS config | | | | | …
187 …| |Continue the BIOS boot | | | | | …
193 ### Intel BIOS Reset Logic When BMC Has Pending Settings
199 …| | BIOS | | BMC …
203 … | | | -Responsible for send /recv | |-Responsible for handling BIOS| ||
204 …| | | | | data between BIOS and BMC | | configuratio…
211 …| |Set BIOS capability |<---Req-/Res--> | Set the BIOS capability | | …
213 …| |Set BIOS Pwd hash/Seed |<---Req-/Res--> | Forward to the RBC daemon |---dbus->| Set BIOSPwd…
217 …| |Init the BIOS config | | | | | …
231 …| |BIOS. | | | into native to D-bus format | | AllBaseAttr…
238 ## BIOS send the data in BIOS configuration PLDM via MCTP
240 BIOS should update the BIOS settings via Set BIOS table PLDM command- BIOS
243 RBC daemon should create pending BIOS attributes list based on the user input
250 Pending attributes value table once its not valid or updated in BIOS. RBC should
254 non-volatile storage. PLDM daemon should preserve BIOS tables in non-volatile
257 ### BIOS first boot
263 …| | BIOS | | BMC …
266 … | | | -Responsible for send /recv | |-Responsible for handle BIOS |||
267 …| | | | | data between BIOS and BMC | | configurati…
277 …| |Set BIOS string table |<---Req-/Res--> | Get the string table | | …
278 …| | via Set BIOS table | | | | | …
283 …| |Init the BIOS config | | | Send the attributes data in | | …
285 …| |via Set BIOS table | | | by Setting AllBaseAttributes | | …
287 …| | Continue the BIOS boot| | | | | …
293 ### BIOS reset
298 …| | BIOS | | BMC …
301 … | | | -Responsible for send /recv | |-Responsible for handle BIOS |||
302 …| | | | | data between BIOS and BMC | | configurati…
313 …| | using Get BIOS table | | | table | | …
317 …| |Init the BIOS config | | | table | | …
321 …| | Reset the BIOS boot | | | setting AllBaseAttributes | | …
328 ### Complete BIOS BMC flow for BIOS configuration in deferred update model
332 | BIOS | | BMC …
335 | | Send the BIOS capability Support| |--------KCS-------->| |1.Get the complete atttributes dat…
336 | | Send the compressed BIOS file(or)| |-MCTP/KCS/Redfish-->| |2.Validate and convert into …
351 | | Get & Update the BIOS variables | -| -----+ | | …
358 | | Send the updated data to BMC | | | | | Update the BIOS attributes …
364 | | Reset the BIOS for BIOS conf | | NO | …
369 | | Continue the BIOS boot | <-------+ | …
374 ### Complete BIOS BMC flow for BIOS configuration in immediate update model
378 | BIOS | | BMC …
381 | | Send the BIOS capability Support| |--------KCS-------->| |1.Get the complete atttributes dat…
382 | | Send the compressed BIOS file(or)| |-MCTP/KCS/Redfish-->| |2.Validate and convert into …
402 | | Update in the BIOS structure | | | +----------------------------------…
407 | +--------------V------------------+ | | | Update the BIOS atrributes data. …
419 BIOS.
421 ### Redfish interfaces for remote Bios configuration
429 …| | for each request) | | |-Responsible for handle| |-Parse Bios Data,con…
439 …| |3.Change BIOS Password |<---Req-/Res--> | Call RBC D-bus Method |-dbus->| ChangePassword() …
443 …| |5.Update new BIOS setting|<---Req-/Res--->| Call RBC D-bus Method |-dbus->| SetAttribute() …
448 …| |7.Update new BIOS setting|<---Req-/Res--->| Set PendingAttributes |<-dbus-| PendingAttributes …
456 1. Get Current Attributes name and value list: Get the current BIOS settings
458 `https://<BMC>/redfish/v1/Systems/system/Bios`
460 2. Get Attribute Registry: Get the detailed information about Bios Attribute
462 GET Method - `https://<BMC>/redfish/v1/Registries/Bios`
464 3. Change BIOS password: ACTION -
465 `https://<BMC>/redfish/v1/Systems/system/Bios/Actions/Bios.ChangePassword`
468 `https://<BMC>/redfish/v1/Systems/system/Bios/Actions/Bios.ResetBios`
470 5. Update new BIOS settings (single attribute): Use to send the new value for
472 `https://<BMC>/redfish/v1/Systems/system/Bios/Settings` Ex: Attribute name
476 GET Method - `https://<BMC>/redfish/v1/Systems/system/Bios/Settings` - Valid
480 7. Update new BIOS settings (multiple attributes): Use to send the new value for
482 `https://<BMC>/redfish/v1/Systems/system/Bios/Settings` Ex: Attribute name
487 Redfish Host specification definition is not completed and ready BIOS support
488 also not available. There are 1000+ BIOS variables and storing in
493 BIOS must support and follow RBC BIOS configuration flow.
497 Able to change the BIOS configuration via BMC through LAN Able to change the
498 BIOS setup password via BMC Compliance with Redfish will be tested using the