smispy_lsmplugin(1)

✨ smispy_lsmplugin — the LibstorageMgmt SMI-S Plugin ✨

okay bestie, welcome to smispy_lsmplugin, living in section 1 of the libStorageMgmt manual 💖 this is the one that lets you talk to your storage arrays through the SNIA SMI-S standard, and honestly? iconic.

---

🎀 NAME 🎀

smispy_lsmplugin — the LibstorageMgmt SMI-S Plugin. that's it, that's the name, she's simple and she serves 💅

---

🌸 DESCRIPTION 🌸

so here's the vibe: the LibstorageMgmt SMI-S Plugin lets a LibstorageMgmt user manage storage arrays like EMC VNX/VMAX, HDS AMS and LSI MegaRAID etc. — all via the SNIA SMI-S standard. no cap. ✨

the smispy_lsmplugin executable file is the thing the LibstorageMgmt daemon runs when a client user requests the SMI-S plugin. it's giving backstage crew energy — you don't see her, but the whole show runs on her 🫶

---

🦋 URI 🦋

to actually use this plugin, you gotta set your URI to this format, bestie:

# HTTP connection
smispy://<username>@<smis_provder_host>:<port>?<uri_parameters>

# HTTPS connection
smispy+ssl://<username>@<smis_provder_host>:<port>?<uri_parameters>

now let's break down every single piece, because we do NOT skip parts in this house:

• username — this is the SMI-S provider user account. your little login moment 👑
• smis_provder_host — the SMI-S provider's IP address or DNS name. (yes, the original spells it smis_provder_host, we are keeping that spelling exactly, character for character, no notes 💀)
• port — by default, the SMI-S plugin uses port 5988 for HTTP connections and port 5989 for HTTPS connections. so if your SMI-S provider is on the default ports, you can literally just skip this in the URI. so easy ✨

for non-default ports, SELinux will likely prevent the SMI-S plugin from making a network connection. that's not a vibe, that's a firewall problem 😭

• URI parameters — these are the URI parameters supported by this plugin:
  • namespace=<name_space> — this URI parameter is for LSI MegaRAID and NetApp E-Series only. just those two, bestie, don't get any ideas 🙈
  • system=<system_id> — for those SMI-S providers which support multi-systems (example: EMC ECIM), this URI parameter can be used to limit network communication for the specified system only. the system_id is the ID of the system, and you can grab it from any of these:
    • lsm.System.id — (Python API)
    • lsm_system_id_get() — (C API)
    • lsmcli list --systems — (lsmcli command line)
  • no_ssl_verify=yes — this URI parameter is for HTTPS connections only. with this URI parameter, the SMI-S plugin will not validate the SMI-S provider's server SSL certificate. it's often used for self-signed CA environments, BUT — and listen closely bestie — it's strongly suggested to remove this URI parameter and install the self-signed CA properly instead. 🚨 do not leave this on like an unread group chat, okay? fix the CA fr fr.

---

🌈 Supported Hardware 🌈

the LibstorageMgmt SMI-S plugin is based on the Block Services Package profile, SNIA SMI-S 1.4 or later. any storage system which implements that profile may be supported. so basically, if it speaks the profile, it might just slide in 🧚

wanna know the detailed support status for your exact setup? go query it, queen:

• lsm.Client.capabilities() — (Python API)
• lsm_capabilities() — (C API)
• lsmcli capabilities — (lsmcli command line).

---

🔥 FIREWALL RULES 🔥

by default, this plugin requires access to the SMI-S provider's TCP 5988 port for HTTP connection and TCP 5989 port for HTTPS connection.

that's it. that's the whole rule. open the port or nothing works, iykyk 🔥

---

👀 SEE ALSO 👀

• lsmcli(1)
• lsmd(1)

go read those too, bestie, they're the supporting cast 💜

---

💀 BUGS 💀

found a bug? please report bugs to <libstoragemgmt-devel@lists.sourceforge.net> — tell them everything, they wanna know 🫶

---

👑 AUTHOR 👑

• Gris Ge <fge@redhat.com>
• Tony Asleson <tasleson@redhat.com>

absolute legends, honestly. main character energy from both of them 👑

---

and that's the whole page, babe — this was smispy_lsmplugin, version 1.10.3, dated June 2015, from the libStorageMgmt crew. slay, periodt, go manage some storage arrays ✨💖🎀