Kontron AM5010 IPMI - Manual (Page 28)

IPMI Firmware User Guide AM5010
Page 28 © 2008 Kontron AG ID 1022-2948, Rev. 1.0
The information provided there includes: IPMI specification revision (v1.5), type of
supported interface (KCS), its base address (CA2h) and interrupt number for it (10, 11 or
none), and the IPMB address of the controller (depending on the module slot/bay). Some of
this information may be needed by software drivers or applications, for example the Linux
OpenIPMI driver looks for the SMBIOS IPMI entry while detecting system interfaces, and it
does make usage of the interrupt number provided there. Making changes ‘manually’ leaves
SMBIOS IPMI entry with not-up-to-date values until next reboot.
6.6 Firmware / Module Identification
There are two ways to determine via IPMI that a MMC resides on an AM5010.
• The response on the IPMI command “Get Device ID” offers among others the following
response data:
o Manufacturer ID = 3A98h (Kontron IANA ID)
o Device ID = 04h (H8S2166)
o Product ID = 5010
o Firmware Revision - depends on running firmware.
• The Device ID String which can be found by reading the the Management Controller
Device Locator Record (SDR Type 12h) contains the string “AM5010”. For a module
being placed in bay B3 the Device ID String will be “B3: AM5010”.
6.7 FRU Information
6.7.1 Structure and Functionality
The MMC provides 4 kB non-volatile storage space for FRU information. Some of the data
stored there, like Module Current Requirements record or E-Keying information (refer to
AMC.0 specification for details), are mandatory for module functionality in the ATCA/AMC
environment. Refer to [2] Platform Management FRU Information Storage Definition
document for details).
Please note that missing FRU information possibly will prevent the AMC module from being
accepted by the carrier controller during the Hot Swap process and the module will possibly
get no payload power.
Full low level access to read or write a module’s FRU Information is provided by regular
IPMI FRU Device commands. Please be careful when writing FRU information directly using
standard IPMI commands. Damaging the FRU Information may lead to a non working
payload.
6.7.2 Download
Normally the user does not need download the FRU information because the module is
shipped with the data which describes best the module capabilities and requirements.
Remember that FRU information might be damaged by a write access to the IPMI FRU
Device using standard IPMI commands.