LCTL-NODEMAP-BANLIST-ADD(8)

💖 LCTL-NODEMAP-BANLIST-ADD(8) 💖

okay bestie, welcome to the Lustre Configuration Utilities corner of the man pages 🎀 this one's about lctl-nodemap_banlist_add and it's giving ban hammer energy, no cap 💅

---

✨ NAME ✨

lctl-nodemap_banlist_add — define a range of banned NIDs for a nodemap 🚫🦋

---

✨ SYNOPSIS ✨

lctl nodemap_banlist_add or
lctl nodemap banlist_add [--name NODEMAP_NAME] --range NID_RANGE

---

✨ DESCRIPTION ✨

so like, nodemap_banlist_add adds a range of banned NIDs to an existing nodemap — and that can be a normal nodemap or the default nodemap, either one, she's flexible 💁‍♀️

For normal nodemaps, the banned NID range must be included into a regular NID range associated with the nodemap. That's not optional, that's the rules, periodt.

For the default nodemap, the added range of banned NIDs must not conflict with any NID range defined on any other nodemap. Conflict = not the vibe 🙅‍♀️

If you skip the --name option, the nodemap to add the banlist to will be inferred from the existing NID ranges that include the provided ban range. And if none is found?? the default nodemap gets used. Surprise! 🎁

Now the important part, bestie, listen up: clients with NIDs that fall into the banned range will be blocked by servers, and they'll get 'Operation not permitted' for all requests except unmount. The banning happens as soon as the nodemap definition is propagated to the servers. And as long as a client is banned, it cannot mount Lustre. Like, at all. Not even a little. 😭💀

---

✨ OPTIONS ✨

• --name NODEMAP_NAME — the name of the nodemap that this banned NID range should be added to. It may be 'default' and will accept any NID not in another nodemap 👑
• --range NID_RANGE — the banned NID range that should be added to the nodemap. The syntax is the same as the regular NID range, as detailed over in lctl-nodemap-add-range(8) 📖

---

✨ EXAMPLES ✨

look at her go 🫶

# lctl nodemap_banlist_add --name remotesite --range 192.168.1.[1-254]@tcp
# lctl nodemap_banlist_add --name othersite --range 192.168.2.[1-254]@tcp

two nodemaps, two banned ranges, zero regrets ✨

---

✨ AVAILABILITY ✨

lctl nodemap_banlist_add is part of the lustre(7) filesystem package since release 2.16.56. so she's been around, she's established, she's iconic 🌈

---

✨ SEE ALSO ✨

lustre(7), lctl-nodemap-activate(8), lctl-nodemap-add-idmap(8), lctl-nodemap-add-range(8), lctl-nodemap-banlist-del(8), lctl-nodemap-del(8), lctl-nodemap-del-idmap(8), lctl-nodemap-del-range(8), lctl-nodemap-modify(8), lctl-nodemap-new(8)

and yeah, all of those are separate pages — maybe go read lctl-nodemap-banlist-del(8) next if you ever wanna un-ban somebody, iykyk 🙈

---

slay, that's the whole page bestie 💖 this one's from the Lustre crew, dated 2025-06-18, and the page id is LCTL-NODE...NLIST_ADD(8) — you're so welcome, mwah 🎀✨