HP MicroServe, User Manual, Page: 6 / 68

6
interface provides a set of I/O mapped communications registers. The default system base address
for the I/O mapped KCS Interface is 0xCA2 and is byte aligned at this system address. The KCS
interface is accessible to SMS software that is running on the local system. Examples of compatible
SMS software applications are as follows:

IPMI version 2.0 Command Test Tool is a low-level MS-DOS command line tool that enables hex
formatted IPMI commands to be sent to an IPMI BMC that implements the KCS interface. You can
locate this tool on the Intel® website (http://www.intel.com/design/servers/ipmi/tools.htm).

IPMI tool is a utility for managing and configuring devices that support the IPMI version 1.5 and
version 2.0 specifications and can be used in a Linux environment. You can locate this tool on
the IPMI tool website (http://ipmitool.sourceforge.net/index.html). Before using linux ipmitool via
system interface, please make sure installing Linux ipmi driver (Use the shell command “service
ipmi start”).
Sensors
The BMC provide environmental monitoring through IPMI sensors. Sensors will be described in the
SDR repository (IPMI v2.0, Chapter 33 SDR Repository) and can be accessed through the IPMI sensor
device commands (IPMI v2.0, Chapter 35 Sensor Device Commands).
System configuration can be discovered through exploration of the SDR repository. IPMI provides a
sixteen byte string identifier in each SDR. This ASCII based string will need to be interpreted by
system management software. These tokens will be used in the SDR string identifier field and will
provide any distinction needed in addition to the other fields of the SDR.
External Event Generation
The BMC is configured to send its alerts to another event receiver in the system. See IPMIv2.0 Chapter
29 Event Commands for more information. All events commands which are mandatory for an event
generator are implemented in the BMC firmware.
LAN Messaging
The BMC will use on chip NIC to provide support for IPMI messaging over LAN. IPMI messages will
be sent as RMCP packets by on chip NIC, which will pass the messages to the BMC via on chip NIC
where the BMC will receive and respond to the messages. See the IPMIv2.0 specification Chapter 13
IPMI LAN Interface for more information. Four simultaneous LAN sessions will be supported. There is
no limitation on the number of concurrent sessions for a single user.
All mandatory IPMI LAN messaging commands are implemented in the BMC Core Firmware. Section
18.1 of this document contains the list of supported optional LAN messaging commands. RMCP+ is
supported under IPMI 2.0. This protocol enhancement conforms to the overall RMCP format.
Extensions allow for multiple payload types, enhanced authentication, and encryption. Details can be
found in IPMIv2.0 section 13.3 RMCP+.
IPMI Firmware supported optional encryption methods as below table (ID 0~14):