NVMe-MI
NVMe Management Interface (NVMe-MI) defines commands and architecture for discovering, monitoring, configuring and updating NVMe storage.
Access paths: out-of-band requests use MCTP over supported SMBus/I2C, I3C or PCIe bindings. In-band requests use the host NVMe-MI Send and Receive Admin commands. Supported message categories depend on the mechanism, so not every out-of-band operation can be tunneled in band. [2]
Health summary: NVM Subsystem Health Status Poll returns subsystem status, SMART warnings, composite temperature and life used. Its warning bits invert the corresponding Critical Warning bits; with multiple controllers, a warning on any controller clears the summary bit. Life used returns the highest controller estimate and should be updated once per power-on hour. A value of 100 does not necessarily mean failure. [2]
Temperature: 00h-7Eh encode 0-126 degrees Celsius; 7Fh means at least 127, 80h means older than five seconds, and 81h means a sensor failure. C4h means at most -60 degrees; C5h-FFh encode -59 to -1 in two's complement, while 82h-C3h are reserved. The subsystem temperature is calculated at least every five seconds, but a fresh numeric reading is not guaranteed. [2]
Linux exposes MCTP datagram sockets and separates network identity from endpoint address. Record both when collecting NVMe-MI observations; an EID alone cannot identify a device across different networks. [4]
Relations
- related
- NVMe, Enterprise SSD, NVMe base specification, NVMe backplane, NVMe SMART log, Management Component Transport Protocol, MCTP endpoint ID, Out-of-band storage management, NVMe Composite Temperature
Limitations
- Management access still depends on supported power states and endpoint readiness; a collection timeout does not identify the fault by itself. [5]
Citations
- NVM Express Management Interface 2.1: message mechanisms and NVM Subsystem Health data structure
- Linux kernel documentation: MCTP interfaces, networks and socket addresses
- NVM Express Management Interface 2.2: sections 1.3, 3, 8.1 and Figure 105
- NVM Express: NVMe-MI architecture and specification index
Further reading
Sources & caveats
- Health-field details are scoped to NVMe-MI 2.1. Revision 2.2 was also checked for transport distinctions, endpoint availability and Figure 105; this is not a claim that all devices implement that revision.
- The official specification index lists revision 2.2, ratified 31 July 2026, as current on the access date. [6] No drive or management controller was tested.