Kontron CP6002 IPMI - Manual (Page 11)

CP6002 IPMI Firmware User Guide
ID: 1039-1613, Rev. 2.0 Page 11
To use the “kipmi” command, refer to the CP6002 uEFI BIOS User Guide. When EFI stores the
configuration, it creates an ‘IPMI Device Information Record’ entry in the SMBIOS table. This
record contains information about (among others):
• Type of the supported interface (KCS style)
• Selected interrupt (10, 11 or none).
This information is required by the CP6002 payload’s IPMI OS kernel drivers for Linux during
their loading time. After the loading, most available IPMI communications tools which access
the IPMI controller via IPMI OS drivers should work (e.g. ‘ipmicmd’, ‘ipmitool’, etc.).
Now it is possible to use such a tool to issue the “Set Firmware Parameters” OEM IPMI com-
mand to modify the configuration again. Changing the interrupt number always requires an EFI
restart for a correct set up of the SMBIOS table.
2.3 IPMI Setup for the Rack
For a working IPMI configuration the SDRR of the BMC must be filled with all sensor data re-
cords of all IPMI controllers in the rack. After every system start the BMC uses the SDRR to
initialize all sensors of all boards. The SDRR setup must be done by a management tool e.g.
the open Linux tool ‘ipmitool’. The command then is:
ipmitool sdr fill sensors
This will only work if the IPMI controller of the BMC is addressed. This addressing is the default
if the ‘ipmitool’ is running on the payload side of the board where the BMC is residing.