Management Component Transport Protocol

Management Component Transport Protocol (MCTP) is a protocol designed by the Distributed Management Task Force (DMTF) to support communications between different intelligent hardware components that make up a platform management subsystem, providing monitoring and control functions inside a managed computer system. This protocol is independent of the underlying physical bus properties, as well as the data link layer messaging used on the bus. The MCTP communication model includes a message format, transport description, message exchange patterns, and operational endpoint characteristics.[1][2]

MCTP allows the transmission of a wide variety of management commands over alternative types of links. Simplified nature of the protocol and reduced encapsulation overheads make MCTP suitable for implementation and processing within system firmware and integrated baseboard management controllers (BMCs), on a wide range of platforms – including servers, workstations and embedded devices.[1][3][4] The following table describes which protocols MCTP can encapsulate, and what kind of protocols MCTP can be run over:

MCTP protocol support[5]
Protocol Can encapsulate Can transmit over
PCI Express MI VDM
NVM Express Management Messages No
CXL (Fabric Manager, Type 3 DCCI) Yes No
Platform Level Data Model Yes No
NC-SI, Ethernet Yes No
USB No Yes
I2C/SMBus, I3C (incl. PCIe) No Yes
Serial Port No Yes
ACPI PCC No Yes
UCIe No Yes
KCS No Yes
MMBI (incl. PCIe) No Yes

For example, Intel's network interface controllers (NICs) include support for MCTP over PCI Express and SMBus since 2012, allowing these NICs to be controlled and monitored at a low level over MCTP. Exposed configuration and monitoring operations include power management, control of Address Resolution Protocol (ARP) offloading, configuration of the out-of-band management traffic (which can be separated from the Ethernet traffic visible to the operating system by using RMCP ports filtering, a separate MAC address, or through VLAN tagging), and handling of NIC's interrupts and error conditions.[3][6][7]

DMTF also defines the Management Controller Host Interface (MCHI), which includes a set of discovery options and registration commands, allowing UEFI, BIOS or the operating system to communicate with a MCTP-enabled BMC. Discovery options include PCI/PCI Express class codes as part of the PCI configuration space, MCHI Description Table and control methods defined and exported via ACPI, and data structures exported via SMBIOS.[8]

See also

edit

References

edit
  1. ^ a b Tom Slaight (2007). "Management Component Transport Protocol (MCTP)" (PDF). Intel. Archived from the original (PDF) on November 9, 2013. Retrieved November 9, 2013.
  2. ^ Amar Kapadia (June 18, 2012). "MCTP: This protocol is a key tool in server management to maximize ROI". networkworld.com. Retrieved November 9, 2013.
  3. ^ a b Eliel Louzoun (2013). "MCTP over PCIe Implementation". PCI-SIG. Archived from the original (PDF) on November 9, 2013. Retrieved November 9, 2013.
  4. ^ "Management Component Transport Protocol (MCTP) Serial Transport Binding" (PDF). DMTF. July 21, 2010. Retrieved February 26, 2014.
  5. ^ "PMCI | DMTF". www.dmtf.org. (list of standards)
  6. ^ "Intel Ethernet Controller I210 Datasheet" (PDF). Intel. 2013. pp. 1, 15, 52, 621–776. Retrieved November 9, 2013.
  7. ^ "Intel Ethernet Controller X540 Product Brief" (PDF). Intel. 2012. Retrieved February 26, 2014.
  8. ^ "Management Component Transport Protocol (MCTP) Host Interface Specification" (PDF). DMTF. July 21, 2010. Retrieved February 26, 2014.
edit