Kontron CP6003-RC IPMI - Manual (Page 32)

IPMI Firmware CP6003-SA/RA/RC
Page 32 ID 1045-5656, Rev. 2.0
P R E L I M I N A R Y
8.4 Firmware Identification
There are two ways to verify that a IPMI controller resides on a CP6003-SA/RA/RC.
Invoking the IPMI command Get Device ID returns among other information the following
data:
• Manufacturer ID = 3A98h (Kontron IANA ID)
• Product ID = B3C0 for the firmware
• Firmware revision in bytes 4:5 - depends on the core version of the running firmware.
• The SDR revision in byte 13 (OEM part of the response) is a sub-revision of the firmware
revision. It is unique for all versions of the board's firmware.
• The device ID string which can be found by reading the Device Locator Record (SDR
Type 12h) contains the string “BMC:x ... x”. For example, invoking the ipmitool command
ipmitool sdr list mcloc
will return the device ID strings of all available boards. If
the CP6003-SA/RA/RC’s IPMI controller is in BMC mode, this string will be displayed
without change. If the CP6003-SA/RA/RC’s IPMI controller is in SMC mode, then the
string will be changed into “Sxx: x ... x” where xx is the slot number where the board is
residing, e.g. “S09: x ... x”.
8.5 Firmware Upgrade
The standard way to upgrade the IPMI's operational code is to use the open tool “ipmitool” (see
Table 2, Related Publications). This tool allows download and activation of new operational
code and also rollback to the “last known good” operational code. Additionally, the status and
the firmware version of the redundant firmware copies can be checked.
For local or remote firmware upgrade, the following IPMI interfaces are available:
• KCS interface (locally, requires active payload, but fast)
• IPMB (remote, independent of the payload state)
• LAN (remote, via IOL, requires also active payload)
During the download process, the currently running operational code operates as usual until
the activation command is issued. During the activation process, the IPMI controller is off-line
for about 20 seconds while the boot code is re-organizing the firmware storage. Afterwards, it
starts the new operational code. If this doesn't succeed, after a timeout the boot code performs
an automatic rollback to the “last known good” operational code.
8.5.1 Firmware File Formats
Firmware images for upgrade are provided in two formats:
• Firmware in binary format, e.g. FW_IPMI_<BOARD>_<REL>_FWUM.bin,
for usage with “ipmitool fwum ..” commands
• Firmware images in the PICMG defined HPM.1 file format,
e.g. FW_IPMI_<BOARD>_<REL>_FWUM.hpm,
for usage with “ipmitool hpm ..” commands.
where:
<BOARD> identifies to board family of the IPMI firmware (B3C0)
<REL> identifies to release (version) of IPMI firmware.