NVME-OCP-SET-TELE(1)

💅 NVME-OCP-SET-TELE(1) — like, the nvme-ocp-set-telemetry-profile page, bestie

okay so this is a page straight out of the NVMe Manual, and it's all about one very specific little subcommand. buckle up 🎀

---

✨ NAME ✨

nvme-ocp-set-telemetry-profile — the one that Sets your Telemetry Profile, no cap.

---

🌸 SYNOPSIS 🌸

nvme [<global-options>] ocp set-telemetry-profile <device>
                        [--telemetry-profile-select=<tps> | -t <tps>]

that's the whole vibe. nvme, then optional global options, then ocp set-telemetry-profile, then your device, then optionally which profile you want. periodt. 💅

---

🦋 DESCRIPTION 🦋

so for the NVMe device you hand it, this sets the OCP Set Telemetry Profile Feature. that's it. that's the whole job. and honestly? she ate. 🔥

the <device> parameter is mandatory — like, you cannot skip it, she's not optional, she's the main character. and it can be either:

• the NVMe character device (ex: /dev/nvme0)
• or the block device (ex: /dev/nvme0n1)

both work, pick your fighter 🫶

⚠️ real talk though: this will only work on OCP compliant devices that support this feature. results for any other device are undefined. undefined!! like, we don't know what happens, and we're not gonna find out. 🙈

on success it returns 0. otherwise you get an error code. that's the deal. 💀

---

💖 OPTIONS 💖

• -t <tps>, --tps=<tps> — Telemetry Profile Select. the device shall collect debug data per the specified profile number. yes, "shall". she's being formal. 👑

🐚 also note: the synopsis spells the long form out as --telemetry-profile-select=<tps>, so if you were looking for that exact spelling, there it is. iykyk.

---

🌈 GLOBAL OPTIONS 🌈

these are defined at the top-level nvme command and — good news — they're available to this subcommand too. so you get all this for free: 🎁

• --dry-run — print the command that would be executed, but do not actually execute it. it's giving "manifesting the command". ✨
• --no-ioctl-probing — disable probing for 64-bit IOCTL support.
• --no-retries — disable retry logic on transient errors. one shot, one opportunity. 💀
• -o <fmt>, --output-format=<fmt> — set the reporting format to normal, tabular, json, or binary. only one output format may be used at a time. pick one, bestie, you can't have all four. 🙅‍♀️
• --output-format-version=<version> — select the output format version. version 1 uses the original field naming, while version 2 (default) provides more consistent and script-friendly field names. other versions are rejected. 🚫
• --quiet — suppress informational messages. errors are still reported, and --quiet cancels any --verbose for the library log level. she's quiet, not silent, okay? 🤫
• --set-options=<key=value>[,<key=value>...] — set libnvme library options for this invocation. supported keys are force-4k, mi-probe-enabled, test-base-dir and test-sysfs-dir. 🛠️
• --timeout=<ms> — set the timeout for the command in milliseconds. infinite or -1 waits without a time limit (0xffffffff). so like... forever. 🕰️
• -v, --verbose — increase the level of detail in the output. may be specified multiple times to further increase verbosity. live your truth, stack those -vs. 📈

💡 these options can also be set as machine-wide defaults in nvme-cli.conf(5). and a command-line flag always overrides the file. always. no exceptions. 👑

---

🎀 EXAMPLES 🎀

• has the program issue a set-telemetry-profile command to use profile five:

# nvme ocp set-telemetry-profile /dev/nvme0 -t 5

look at her go. profile five. iconic. ⭐

---

👑 NVME 👑

part of the nvme-user suite. that's the family. that's the bloodline. 🧚

---

okay that's literally the whole page!! 🍓 this gem is from the NVMe crew, dated 10/30/2026 — go forth, set some telemetry profiles, and stay OCP compliant 💜🦋