lsm_initi..._id_verify(3)

💖 lsm_initiator_id_verify — bestie's guide to checking if your initiator id is even real 💖

okay so welcome to the Libstoragemgmt C API Manual girlies ✨ this one's lsm_initiator_id_verify(3) and she's a little baddie whose whole job is telling you whether an initiator id is valid. no cap.

---

✨ NAME ✨

lsm_initiator_id_verify — Verifies if initiator id is valid. 💅

---

🎀 SYNOPSIS 🎀

int lsm_initiator_id_verify (const char *init_id,
lsm_access_group_init_type *init_type);

---

🦋 ARGUMENTS 🦋

• init_id — String to verify. that's it, that's the whole vibe, just a lil string that needs a vibe check 🌸
• init_type — lsm_access_group pointer. The type of initiator ID. lowkey the fun part: you may set it to LSM_ACCESS_GROUP_INIT_TYPE_UNKNOWN and this function will try iSCSI and WWPN for you, then modify this argument to the valid type of initiator type. it's giving helpful fr fr 🫶

---

🌈 VERSION 🌈

1.0 — iconic, the original era ✨

---

💜 DESCRIPTION 💜

Verifies whether specified initiator is valid, and here's the checklist bestie:

• iSCSI:
  • Starting with "iqn", "eui", or "naa". so if it doesn't start with one of those three? not me accepting it 🙈
• WWPN:
  • 16 hex digits(0-9a-fA-F). exactly 16. count them. i'm literally begging you to count them 💀

---

⭐ RETURN ⭐

Error code as enumerated by 'lsm_error_number', so here's the tea:

• LSM_ERR_OK
  • Is valid initiator. 🎉 slay! she passed the vibe check, main character energy confirmed 👑
• LSM_ERR_INVALID_ARGUMENT
  • Not a valid initiator or any argument is NULL. 😭 either the id is sus or somebody passed a NULL, and honestly both are giving chaos.

---

🫶 little reminder bestie: if init_type was LSM_ACCESS_GROUP_INIT_TYPE_UNKNOWN going in, it comes back out changed. don't be surprised, that's the whole point, iykyk ✨

---

okay that's the page!! this was lsm_initiator_id_verify, brought to you by the Libstoragemgmt C API Manual, version 1.0, dated February 2026. mwah, go verify some initiator ids responsibly 💖✨🎀🦋🌸