From within the Oracle ILOM software on the SP, the control of when FPGA iPOST (Oracle ILOM POST) is executed during the boot sequence of the SP is managed by the following properties:
/SP/diag mode
/SP/diag trigger
By default, these properties are defined so that the execution of FPGA iPOST is disabled. For example:
... /SP/diag mode=off /SP/diag trigger=all-resets ...
If you change /SP/diag mode to normal to enable iPOST, and if you change /SP/diag trigger from all-resets to any other value (power-on-reset, error-reset, or hw-change), then iPOST will not be executed. In addition, the following message displays on the SER MGT port during the boot sequence to indicate that iPOST has not been executed:
... Starting IPMI Stack: . Done Starting BBR daemon... bbrd started after 0 seconds. Starting SP fishwrap cache daemon: fishwrapd . Done FPGA iPOST skipped Starting Host daemon: hostd . Done Starting Network Controller Sideband Interface Daemon: ncsid . Done Starting Physical Domain Manager: pdm . Done Starting Platform Obfuscation Daemon: pod . Done Starting vbsc daemon: vbsc . Done ...
Workaround A: To have iPOST execute when the SP boots, ensure that the trigger property is set to all-resets when it is enabled.
With the host not running, log in to the SP.
Set the /SP/diag trigger to all-resets.
At the Oracle ILOM CLI, type:
-> set /SP/diag trigger=all-resets
In the Oracle ILOM BUI, left click System Management, and then the Diagnostics entry in the left pane. Then, select all three boxes under the label trigger in the right pane.
Reboot the SP.
The following output should display on the system console:
... Starting IPMI Stack: . Done Starting BBR daemon... bbrd started after 0 seconds. Starting SP fishwrap cache daemon: fishwrapd . Done Running FPGA iPOST Starting Host daemon: hostd . Done Starting Network Controller Sideband Interface Daemon: ncsid . Done Starting Physical Domain Manager: pdm . Done Starting Platform Obfuscation Daemon: pod . Done Starting vbsc daemon: vbsc . Done ...