I have a customer that wants me to apply the following two commands...

racadm config -g cfgServerInfo -o cfgServerBootOnce 0 racadm config -g cfgServerInfo -o cfgServerFirstBootDevice PXE

I have used these commands in the past to initiate a one time PXE boot. But this customer is requesting this in order to permanently set the server to PXE boot.

But, when I run these commands and reboot, it does PXE boot, but then the commands appear to revert back to their default. If I run

racadm getconfig -g cfgServerInfo -o cfgServerFirstBootDevice PXE

It is no longer set to 'PXE', it is back to "Normal'

I think this is normal behavior. But the customer seems to believe that by using the other command, cfgServerBootOnce, and setting it to 0, that it should be persistent.

The documentation does sort of seem to support this, but I have never used it this way and I am not having success getting it to behave this way.

Hoping someone can shed some light on this and help me to either understand what I am doing wrong or to help me with supporting information to take back to the customer.

I suggested using this command instead to achieve the desired effect...

racadm set bios.bootsettings.bootseq NIC.Integrated.1-1-1,HardDisk.List.1-1

But they insist that they want me to run the other command.