IPMI Technical Resources

Recent Updates (updated on April 21, 2015)

Specification Update
Description
IPMI v2.0, rev. 1.1
markup for Errata 7,
April 21, 2015
This markup of the IPMI v2.0, rev. 1.1 specifications adds the corrections and clarifications identified in the IPMI v2.0, rev 1.0 Addenda, Errata, and Clarifications revision 7, April 21, 2015. The markup includes the previous errata, but only shows the Errata 7 changes as revisions.
IPMI v2.0, rev. 1.0, Addenda, Errata, and Clarifications revision 7, April 21, 2015 This latest revision lists the cumulative addenda, errata, and clarifications against the revision 1.0 release of the IPMI Second Generation v2.0 specification. Errata 7 adds clarifications and corrections for typographic errors in the IPMI v2.0, rev. 1.1, October 1, 2013 release.
IPMI Platform Management FRU Information Storage Definition, v1.0, Document, Revision 1.3, March 24, 2015 This revision adds multi-record type numbers for definition and use by the NVM Express* working group.

IPMI v2.0, rev. 1.1 markup for Errata 6, February 11, 2014

This markup of the IPMI v2.0, rev. 1.1 specification adds the corrections and clarifications identified in the IPMI v2.0, rev. 1.0 Addenda, Errata, and Clarifications revision 6, February 11, 2014 document. Only the Errata 6 changes are shown as revisions.

IPMI v2.0, rev. 1.0, Addenda, Errata, and Clarifications revision 6, February 11, 2014

This latest revision lists the cumulative addenda, errata, and clarifications against the revision 1.0 release of the IPMI Second Generation v2.0 specification. Errata 6 adds clarifications and corrections for typographic errors in the IPMI v2.0, rev. 1.1, October 1, 2013 release.

IPMI v2.0, rev. 1.1, October 1, 2013

This new revision of the IPMI v2.0 specification includes all errata, clarifications, and addenda up to and including IPMI v2.0 rev. 1.0 Errata 5. The most significant change to the specification is the addition of support for IPv6 Addressing for IPMI over LAN sessions and LAN Alerting.

IPMI v2.0, rev. 1.0 markup for Errata 5, October 1, 2013

This is a markup showing the revisions added by Errata 5 over the IPMI v2.0 rev. 1.0 Errata 4 markup. The markup also includes the Errata 1 through Errata 4 changes, but only shows the Errata 5 changes as revisions.

Specifications

The Intelligent Platform Management Interface Initiative derives its name from the main specification, which defines the messages and system interface to platform management hardware. It comprises four main specifications:

  • Intelligent Platform Management Interface (IPMI)
  • Intelligent Platform Management Bus (IPMB)
  • IPMI Platform Management FRU Information Storage Definition
  • Intelligent Chassis Management Bus (ICMB)

The IPMB specification defines an internal management bus for extending platform management within a chassis, while the ICMB specification defines the external management bus between IPMI enabled systems.

Note: Before implementing the IPMI specifications, see the Adopter's Agreement.

Download Specifications

Title Published
Description
v2.0 specifications:
IPMI v2.0, rev. 1.1
markup for Errata 7


April 21, 2015 This markup of the IPMI v2.0, rev. 1.1 specifications adds the corrections and clarifications identified in the IPMI v2.0, rev 1.0 Addenda, Errata, and Clarifications revision 7, April 21, 2015. The markup includes the previous errata, but only shows the Errata 7 changes as revisions.
IPMI v2.0, rev. 1.0, Addenda, Errata, and Clarifications revision 7 April 21, 2015 This latest revision lists the cumulative addenda, errata, and clarifications against the revision 1.0 release of the IPMI Second Generation v2.0 specification. Errata 7 adds clarifications and corrections for typographic errors in the IPMI v2.0, rev. 1.1, October 1, 2013 release.
IPMI, v2.0 rev. 1.1 specification

October 1, 2013

This latest revision of the IPMI, v2.0, specification includes all errata, clarifications, and addenda up to and including IPMI, v2.0, rev. 1.0 Errata 5. The most significant change to the specification is the addition of support for IPv6 Addressing for IPMI over LAN sessions and LAN Alerting.

IPMI, v2.0, rev. 1.1, specification markup for IPMI v2.0 Errata, revision 6

February 11, 2014 This is a markup showing the revisions added by Errata 6 over the IPMI, v2.0, rev. 1.1. Only the Errata 6 changes are shown.

IPMI, v2.0, Addenda, Errata, and Clarifications, revision 6

February 11, 2014 This latest revision lists the cumulative addenda, errata, and clarifications against the revision 1.0 release of the IPMI Second Generation, v2.0, specification. Errata 6 adds clarifications and corrections for typographic errors in the IPMI, V2.0, rev. 1.1, October 1, 2013 release.

IPMI, v2.0, rev. 1.0, specification markup for IPMI v2.0 Errata, revision 5

October 1, 2013 This is a markup showing the revisions added by Errata 5 over the IPMI, v2.0, rev. 1.0 Errata 4 markup. The markup also includes the Errata 1 through Errata 4 changes, but only shows the Errata 5 changes as revisions.

IPMI, v2.0, Addenda, Errata, and Clarifications, revision 4

June 12, 2009 This latest revision lists the cumulative addenda, errata, and clarifications against the rev. 1.0 release of the IPMI Second Generation, v2.0, specification. Several important additions, corrections and clarifications have been made to the specification, including updates to the boot options, Entity IDs, Sensor Types, and the RAKP description. A corresponding markup of the v2.0 specification is also available.

IPMI, v2.0, rev. 1.0, specification markup for IPMI V2.0/V1.5 errata, revision 4

June 12, 2009 This is a version of the IPMI Second Generation, v2.0, rev. 1.0, specifications with revisions marked cumulatively per revisions 1 through 4 of the IPMI v2.0/v1.5 errata document.

IPMI, v2.0, specifications document, revision 1.0

Feb 12, 2004 This document is the latest version of the Intelligent Platform Management Interface (IPMI) specifications. IPMI, v2.0, includes new features such as "Serial Over LAN" (SOL) for redirecting a baseboard serial port over an IPMI LAN session extended and Remote Management Control Protocol+ (RMCP+) that provides enhanced authentication and confidentiality (encryption) capabilities for IPMI LAN sessions. New infrastructure capabilities deliver new standard and OEM payloads over an IPMI session and a new Firmware Firewall capability simplifies command discovery and enables restricting management feature access across different IPMI interfaces to enhance security. Additionally, the SSIF (SMBus System Interface) supports inexpensive, low pin-count management controllers, extended sensor and entity types, and sensor data record capabilities. To help simplify migrating to the new IPMI, v2.0, capabilities, the main additions and changes from the IPMI, v1.5, specifications are highlighted in this version with blue text. Note that using the IPMI Second Generation, v2.0, Specification requires signing a new Adopter's agreement.
v1.5 specifications:

IPMI, v1.5, rev. 1.1, specification markup for IPMI, v2.0/v1.5, errata, revision 1

June 1, 2004 This version of the IPMI, v1.5, rev. 1.1 specifications contains revisions marked per the Addenda, Errata, and Clarifications document (revision 5) along with additional errata from revision 1 of the IPMI v2.0/v1.5 errata document.

Addenda, Errata, and Clarifications document revision 5 for IPMI, v1.5, rev. 1.1, specification

Jan 29, 2004 This revision lists the cumulative addenda, errata, and clarifications against the rev. 1.1 release of the IPMI, v1.5, specification.

IPMI, v1.5, rev. 1.1, specification markup for errata revision 5

Jan 19, 2004 This is a version of the IPMI, v1.5, rev. 1.1, specifications with revisions marked per the Addenda, Errata, and Clarifications document, revision 5.

IPMI Specification, v1.5, document, revision 1.1

Feb 20, 2002 IPMI, v1.5, adds remote management access over Serial/Modem and LAN connections, and new capabilities for automatic alerting and recovery. IPMI, v1.5, is a superset of and backward compatible with earlier IPMI, v1.0, specification. It also includes extensions to support other existing and emergent standards. See IPMI, v1.5, white paper overview for brief outline of the features and changes in IPMI, v1.5. The revision 1.1 update of the IPMI, v1.5, specification incorporates important errata and addenda that address issues discovered in the original document, revision 1.0, release of the specification. A companion addenda and errata document (revision 5) separately lists the errata and addenda that have been included.
Supporting specifications:

IPMI Platform Management FRU Information Storage Definition, v1.0, Document, Revision 1.3, March 24, 2015

March 24, 2015 This revision adds multi-record type numbers for definition and use by the NVM Express* working group.

IPMI CIM Mapping Guideline, v0.60

February 6, 2006 This draft document from Intel, Dell, HP, and Avocent describes how Distributed Management Task Force, Inc. (DMTF) CIM platform management objects can be generated and populated using IPMI as the interface to the platform management subsystem. This document is provided to IPMI Adopters, Promoters, and Contributors for review. Please read agreements and information at front of document for information on providing feedback. Version 0.60 provides significant additions over the previous v0.50 posting, including classes and processes for mapping IPMI Entities and FRU information, and additional information on sensor mapping and instantiation.

IPMB Specification, v1.0

November 15, 1999 This specification defines an internal management bus for extending platform management within a chassis.

IPMB Address Allocation, v1.0

September 16, 1998 This document presents the allocation and use of I2C slave addresses for devices on the IPMB.

ICMB Specification, v1.0, document, revision 1.3

April 2, 2003 This document defines an external management bus between IPMI enabled systems. This update adds new commands for supporting Group Chassis Control capabilities. Group Chassis Control provides a mechanism to enable power, reset, and diagnostic interrupt control of multiple chassis using a single broadcast command on the ICMB.

Platform Event Trap Specification, v1.0, revision 1.00

December, 7, 1998 This specification defines a common format for SNMP Traps generated by platform management hardware, BIOS, or system boot agents.

Software Tools

Title Published Description
IPMI, V2.0, Conformance Test Suite (ICTS) Prototype, V6.02 July 26, 2005

The IPMI, V2.0, Conformance Test Suite (ICTS) is designed to verify IPMI, V2.0, conformance. ICTS, V6.02, provides support for the IPM, V2.0, conformance testing as well support for previous IPMI versions (IPMI, V1.5, and IPMI, V1.0). It also includes bug fixes found in ICTS, V6.01. Please refer to the release notes and updated user guides for details and list of all the new changes. This software is provided to IPMI adopters only for their internal evaluation.

Note: This tool is a prototype version and is provided "as-is" with no support.

IPMI, V2.0, V1.5, and V1.0, Reference Drivers
January 13, 2005 Intel is offering several IPMI, V2.0, V1.5, and V1.0, drivers reference implementation. The IPMI, V2.0, reference driver supports IA-64 and IA-32 under Windows* NT, Windows* 2000, and Windows* 2003. In addition to the KCS and SMIC interfaces, the IPMI, V2.0, reference driver supports SSIF interface as well. The IPMI, V1.5, reference driver supports both IA-64 and IA-32 under Windows* .NET/2000. The IPMI, V1.0, is available for the Windows* NT/2000, NetWare*, and Linux* OS's. All drivers support the KCS and SMIC interfaces. You must be an IPMI Adopter to use this software. It is provided "as is" with no support.
IPMI, V2.0, Command Test Tool
January 13, 2005

The IPMI command test tool is a low-level MS-DOS* command line tool that allows hex-formatted IPMI commands to be sent to an IPMI baseboard management controller (BMC) that implements the KCS or/and SSIF interfaces. This can be used as an aid in developing and testing IPMI enabled systems. The tool can also send commands to satellite management controllers located on the primary IPMB behind the BMC. This version has been designed to work with IPMI, V2.0; IPMI, V1.5; and IPMI, V1.0, systems. An option for use with IPMI, V0.9, systems is also provided.

Note: this file contains a readme file, a binary file, and source code for the utility.

SAF-TE: SCSI Accessed Fault Tolerant Enclosures Interface Specification

This specification defines a set of SCSI commands for setting drive status information, including status for RAID arrays, into a disk drive array enclosure. The drive array enclosure may be a separate enclosure, or the same enclosure. The specification also defines commands for managing hot-swap drive slots and returning environmental health information for a drive enclosure.

The status commands are typically used by the enclosure manufacturer to assert lights or other indicators that provide information to the user about the state of the drives in the array. This can include statuses such as "rebuilding," "fault," and "hot spare." The SCSI accessed fault tolerant enclosures (SAF-TE) status setting commands are typically issued either by an intelligent disk controller or by software—for example, RAID software—running under the operating system. Other parties on the SCSI bus may elect to access the status information as a means of determining the state of the physical drives in the array.

In addition, SAF-TE commands can be used to report certain environmental information about the enclosure, such as temperature, voltage, power supply, and fan health.

While the 04/14/97 revision is marked "Intermediate Review," this document is the de-facto and most widely deployed version of the specification and is recommended as the basis for any new implementations. 

Note that a number of enclosure implementations have been based on the 08/27/96 revision of the specification. This version was the original SAF-TE, V1.0, specification plus addenda. These documents, plus documents highlighting the differences against the 04/14/97 version, are included in the SAF-TE Archive Zip* file. It is highly recommended that software and controllers make provision for differences between the versions.