SMP_CONF_ZONE_MAN_PASS(8)

💖 SMP_CONF_ZONE_MAN_PASS 💖

okay bestie, welcome to smp_conf_zone_man_pass, section 8 of the manual, living in the SMP_UTILS collection. no cap, this one is a whole vibe: it invokes the CONFIGURE ZONE MANAGER PASSWORD function. let's get into it 🫶

---

✨ NAME ✨

smp_conf_zone_man_pass — invoke CONFIGURE ZONE MANAGER PASSWORD function

---

✨ SYNOPSIS ✨

smp_conf_zone_man_pass [--expected=EX] [--fpass=FP] [--help] [--hex]
[--interface=PARAMS] [--new-fpass=NF] [--new-pass=NP] [--password=PA]
[--raw] [--sa=SAS_ADDR] [--save=SAV] [--verbose] [--version]
SMP_DEVICE[,N]

---

✨ DESCRIPTION ✨

so basically 💅 this little icon sends a SAS Serial Management Protocol (SMP) CONFIGURE ZONE MANAGER PASSWORD function request to an SMP target. that's the whole job, she's focused.

the SMP target gets identified by SMP_DEVICE plus the --sa=SAS_ADDR. depending on which interface you're on, the SAS_ADDR might just be deduced from the SMP_DEVICE — free of charge, we love convenience ✨.

now, the mpt interface is a little extra: it uses SMP_DEVICE to identify a HBA (aka an SMP initiator) and it needs that extra ,N to tell the HBAs apart if there's more than one hanging around. multiple HBAs? not her problem, just give her the ,N 🎀

---

✨ OPTIONS ✨

mandatory arguments to long options are mandatory for short options as well. yes bestie, the long and short versions want the same energy 💅

• -E, --expected=EX — sets the 'expected expander change count' field in the SMP request. EX runs from 0 to 65535 inclusive, and 0 is the default. when EX is greater than zero and the value doesn't match the expander change count of the SMP target (i.e. the expander) at the moment the request arrives, then the target straight up ignores the request and sets a function result of "invalid expander change count" in the response. it's giving strict gatekeeping, honestly 🚪
• -F, --fpass=FP — where FP is the name of a file containing the existing password. the password can be in ASCII, in which case it sits on one line surrounded by either single quotes or double quotes. alternatively the password can be given in ASCII hexadecimal: either as bytes separated by space, tab, comma or newline, or as longer strings of hexadecimal bytes where every 2 digits represents a byte. empty lines and lines starting with "#" are ignored. and a line starting with -1 causes all remaining bytes in the password to be filled with 0xff — iconic fill behavior, slay 🔥
• -h, --help — output the usage message then exit. the classic "just tell me what to do" button 🙈
• -H, --hex — output the response (less the CRC field) in hexadecimal.
• -I, --interface=PARAMS — interface specific parameters. in this case "interface" means the path through the operating system to the SMP initiator. peep the smp_utils man page for more info, she explains it better than me 📖
• -N, --new-fpass=NF — where NF is the name of a file containing the new password. the format of this file is the same as the file given in --fpass=FP. twins fr fr 👯
• -n, --new-pass=NP — where NP is the new zone manager password, which may be up to 32 bytes long. this option cannot be given together with the --new-fpass=NF option, pick a lane bestie 😭. the default password is 32 NULLs (zero bytes) and PA is padded with NULLs to the right (to make it 32 bytes long in the request).
• -P, --password=PA — where PA is the existing zone manager password, which may be up to 32 bytes long. this option cannot be given together with the --fpass=FP option. the default password is 32 NULLs (zero bytes) and PA is padded with NULLs to the right (to make it 32 bytes long in the request).
• -r, --raw — send the response (less the CRC field) to stdout in binary. all error messages get sent to stderr instead. messy? no, organized 💅
• -s, --sa=SAS_ADDR — specifies the SAS address of the SMP target device. the mpt interface needs this option and it will typically be an expander's SAS address. the SAS_ADDR is in decimal, but most SAS addresses are shown in hexadecimal. to give a number in hexadecimal, either prefix it with '0x' or put a trailing 'h' on it. two ways, both valid, choose your fighter ⭐
• -S, --save=SAV — set the 'save' field in the SMP request. SAV may take these values: 0 for updating the shadow values (default), 1 for updating the saved values, 2 for updating shadow values and if available the saved values, 3 for updating both saved and shadow values. she has range, she has options 🌈
• -v, --verbose — increase the verbosity of the output. can be used multiple times. stack it up, more is more ✨
• -V, --version — print the version string and then exit.

---

✨ NOTES ✨

hexadecimal bytes (or longer hexadecimal strings) should not have a leading "0x" or a trailing "h" decoration. no extra accessories, the hex wants to be bare 🧚

the "well known" DISABLE password is 32 bytes of 0xff. the new password can only be DISABLED if physical presence is supported and asserted. so yeah, that's a real constraint, not a vibe — pay attention 💀

---

✨ CONFORMING TO ✨

the SMP CONFIGURE ZONE MANAGER PASSWORD function was introduced in SAS-2. periodt 👑

---

✨ AUTHORS ✨

Written by Douglas Gilbert. legend behavior, we respect it 🫶

---

✨ REPORTING BUGS ✨

Report bugs to <dgilbert at interlog dot com>.

---

✨ COPYRIGHT ✨

Copyright © 2011 Douglas Gilbert

This software is distributed under a FreeBSD license. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. so like, no promises bestie, she's doing her best 😭

---

✨ SEE ALSO ✨

smp_utils, smp_zone_lock, smp_rep_zone_man_pass(smp_utils)

---

okay that's the whole page, go forth and configure those zone manager passwords responsibly 💖

this was smp_utils-0.96, dated June 2011, and it's the SMP_CONF_ZONE_MAN_PASS(8) page — mwah, bye bestie 🎀✨