Technical data

Chapter 3
Diagnostics
Using ipmitool to Request Diagnostic Boot
191
0x04 - "force PXE" bits 0001b in request data byte 3[5:2]
Example 2: Sending an IPMI-over-LAN request to PXE boot blade in slot 4 on next boot
ipmitool -I lan -H 192.168.1.2 -U root -P rootpass -t 0x8e raw 0x00 0x08 0x05 0x80
0x04 0x00 0x00
Where:
"-I lan" specifies the LAN interface should be used by ipmitool
"-H 192.168.1.2" is the IP address of the shelf manager through which the RMCP session will be
established (a hostname can also be specified instead of IP address, if applicable)
"-U root -P rootpass" is the user login information (root/rootpass) for the shelf manager RMCP session
"-t 0x8e" is the target IPMB address for the bridged request (8eh is the address for physical slot 4)
Some versions of ipmitool also support command keywords which can be specified instead of the raw hex
bytes in some cases. For example:
ipmitool chassis bootdev [ pxe | disk | cdrom ]
So the following syntax can also be used to send the IPMI-over-LAN request shown in Example 2:
ipmitool -I lan -H 192.168.1.2 -U root -P rootpass -t 0x8e chassis bootdev pxe
After invoking ipmitool to send the set system boot options request, the specified blade can be rebooted; the
one-time only boot option will be in effect. When specifying PXE boot, the appropriate configuration must
exist on the PXE server so that the boot request from the MAC address associated with the Server blade's
diagnostic boot PXE port will cause the Service OS to be downloaded for diskless boot.