Srikar Pyda

Hey Tex, Really appreciate your prompt response. I tried following the procedure you outlined above. Unfortunately, the boot order did not change. 1. Get current BIOS boot order ```spyda@pdx01-m01-h16-cpu-1:~$ curl...

On a separate note, you mentioned that the bios attribute "SetBootOrderEn" is used to enable disabled devices in the boot order. Is there a separate bios attribute that I can...

Hey Tex, I was able to use this secondary workflow that you provided: ``` [root@localhost ~]# curl -k -u root:calvin -X PATCH 'https://192.168.0.120/redfish/v1/Systems/System.Embedded.1' --insecure -H "Content-Type: application/json" -d '{"Boot":{"BootOrder":["Boot0003"]}}' -i...

Hey Tex, I went ahead and upgraded both the IDRAC and BIOS on the machine (IDRAC:7.20.10.05/BIOS:2.4.4). Neither option 1 (setting the SetBootOrderFqdd1 attribute) or option 3 (setting the BootSourceOverrideTarget) that...

Hey Tex, I wanted to follow up here. I am currently using option 3 to configure my Dell to HTTP boot. Afterwards, I lock the BMC down and enable System...

Hey Tex, The issue is that a new BootOption 0001 was added (internally, by the server) after system lockdown mode was enabled. Prior to locking the server down, there were...

Hey Tex, Yes, the new boot device is at the top of the boot order. The server keeps booting back into it. Just to clarify the new boot device is...

Hey Tex, Sorry, the above example is bad as Boot0001 is reported as an unavailable entry: Here the boot order of a different Dell XE9860 with the same issue: ...

Hi @texroemer , Just wanted to follow up. Did the iDRAC team come back with any details? Thanks, Srikar

Hey @texroemer , Thanks for the update. Is there a work-around I can use until September? Thanks, Srikar