{
  "status": "shipping",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-21",
  "slug": "out-of-band-management",
  "term": "Out-of-band storage management",
  "aliases": [
    "OOB storage management",
    "Out-of-band management"
  ],
  "definition": "Out-of-band storage management uses a management path separate from the host operating system's normal storage-access path.",
  "note": "NVMe-MI can be used out of band, usually by a baseboard management controller, or in band through the host operating system. The NVMe-MI name alone does not identify which path supplied a reading. [mi-overview]\n\nFor NVMe-MI, endpoint readiness depends on power state and supported access conditions; temporary unresponsiveness is permitted in specified circumstances. A failed collection is not a reported health value. [mi22]",
  "related": [
    "nvme-mi",
    "mctp",
    "mctp-endpoint-id",
    "nvme-smart-log"
  ],
  "citations": [
    {
      "id": "mi-overview",
      "title": "NVM Express: NVMe-MI architecture and specification index",
      "url": "https://nvmexpress.org/specification/nvme-mi-specification/",
      "accessed": "2026-10-21"
    },
    {
      "id": "mi22",
      "title": "NVM Express Management Interface 2.2: sections 1.3, 3, 8.1 and Figure 105",
      "url": "https://nvmexpress.org/wp-content/uploads/NVM-Express-Management-Interface-Specification-Revision-2.2-Ratified-2026.07.31.pdf",
      "accessed": "2026-10-21"
    }
  ],
  "provenance": [
    "NVMe-specific availability limits follow NVMe-MI 2.2 section 8.1. Separating collection failures from health readings is an operational inference, not a measured reliability result."
  ]
}