"data": null, "message": "200 OK", "status": "ok" } User root has been logged out $ openbmctool -H 9.108.97.153 -U root -P 0penBmc chassis power status Attempting login... Chassis Power State: Off Host Power State: Off BMC Power State: Ready User root has been logged out $ openbmctool -H 9.108.97.153 -U root -P 0penBmc chassis power on Attempting login... Attempting to Power on...: { "data": null, "message": "200 OK", "status": "ok" } User root has been logged out $ ssh root@9.108.97.153  # cat /var/lib/phosphor-software-manager/pnor/ro/VERSION  IBM-witherspoon-ibm- OP9-v2.0.8-2.7 -prod op-build-v2.0.8-2-gf54aed9 buildroot-2018.02.1-6-ga8d1126 skiboot-v6.0.8 hostboot-d033213-pf8eafb0 occ-084756c linux-4.16.13-openpower1-pcc4b089 petitboot-v1.7.2-p26e7ade machine-xml-7cd20a6 hostboot-binaries-hw080418a.op920 capp-ucode-p9-dd2-v4 sbe-55d6eb2 hcode-hw082318a.op920 5.2.4 Boot order configuration  The Petitboot bootloader can automatically boot (or autoboot) from several types of devices in  a certain order (that is, falling back to later devices if earlier devices cannot be used to  perform a boot). This scenario requires a specific configuration of the device boot order (for  Genesis-based node discovery; and diskful installation. These tasks are described in 5.3,  “xCAT deployment overview” on page 59).  Petitboot must first attempt to boot from the network devices by using DHCP. If the network  devices are not available, Petitboot attempts to boot from the disk devices. By following this  order, the node can obtain its network and boot configuration from the xCAT management  node (for example, the Genesis image or diskless installation) or fall back to boot an OS from  disk if the network boot is not specified (for example, diskful installation). Chapter 5. Nodes and software deployment  57