SMP_ZONE_ACTIVATE(8)
β¨ smp_zone_activate β the SMP_UTILS glow-up, section 8 of your manual π
okay bestie, sit down, hydrate, because we're about to activate a ZONE and it's giving main character energy.
πΈ NAME πΈ
smp_zone_activate β invoke the ZONE ACTIVATE SMP function. that's it, that's the whole vibe. no cap.
π¦ SYNOPSIS π¦
smp_zone_activate [--expected=EX] [--help] [--hex] [--interface=PARAMS]
[--raw] [--sa=SAS_ADDR] [--verbose] [--version] SMP_DEVICE[,N]
π DESCRIPTION π
So basically? This lil cutie sends a SAS Serial Management Protocol (SMP) ZONE ACTIVATE function request to an SMP target. sending it out into the world like a text you definitely should have thought twice about π«Ά
The SMP target gets ID'd by two things: the SMP_DEVICE and the --sa=SAS_ADDR. Depending on which interface you're rolling with, the SAS_ADDR might just get deduced from the SMP_DEVICE β it's self-sufficient like that, we love a low-maintenance queen.
Now, the mpt interface is a little extra π β it uses SMP_DEVICE to identify an HBA (that's an SMP initiator, iykyk) and it needs the additional ,N tacked on to tell the HBAs apart when there's more than one hanging around. multiple HBAs? not her problem, she needs the ,N. periodt.
And here's the tea on what actually happens: this function, if successful, will cause various zoning-related shadow values (like the zone permission table and the zone phy information, for example) to be copied over to the corresponding current values. glow up achieved β¨
AND β if you've selected the saving-to-"saved"-values option, then those same zoning-related shadow values will also get copied to the corresponding saved values. double the copy, double the slay. π
π₯ OPTIONS π₯
real talk: mandatory arguments to long options are mandatory for short options too. the rules apply to everyone, no favorites.
-E,--expected=EXβ sets the 'expected expander change count' field in the SMP request.EXruns from0to65535inclusive, and0is the default, bestie. whenEXis greater than zero, then if that value doesn't match the expander change count of the SMP target (aka the expander) at the moment the request arrives, the target just... ignores your request π and sets a function result of "invalid expander change count" in the response. she said read the room.-h,--helpβ outputs the usage message and then exits. the classic "what does anything mean" button.-H,--hexβ outputs the response (minus the CRC field, obviously) in hexadecimal. nerdy and proud π-I,--interface=PARAMSβ interface-specific parameters. in this context "interface" means the path through the operating system to the SMP initiator. peep thesmp_utilsman page for the full lore.-r,--rawβ sends the response (again, less the CRC field) to stdout in binary. and every single error message goes to stderr, so the streams stay in their own lanes, as they should. π-s,--sa=SAS_ADDRβ specifies the SAS address of the SMP target device. themptinterface needs this option and it'll typically be an expander's SAS address. heads up:SAS_ADDRis in decimal, but most SAS addresses are shown in hexadecimal (the audacity, honestly). to give a number in hexadecimal, either prefix it with'0x'or put a trailing'h'on it. pick your fighter. π₯-v,--verboseβ increases the verbosity of the output. can be used multiple times β stack it like a chain of sparkle emoji, the more the merrier. β-V,--versionβ prints the version string and then exits. short, sweet, iconic.
π CONFORMING TO π
The SMP ZONE ACTIVATE function was introduced in SAS-2. so yeah, she's got history. vintage, even. π
π§ AUTHORS π§
Written by Douglas Gilbert. the original mastermind, we stan. π«Ά
π REPORTING BUGS π
Report bugs to <dgilbert at interlog dot com>. tell them everything, leave nothing out, be dramatic about it if you must. π
πΈ 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, don't come for her if it breaks, bestie. she said no promises. π
π¦ SEE ALSO π¦
smp_utilssmp_zone_locksmp_zone_unlocksmp_ena_dis_zoning(smp_utils)
ok that's the whole page, go forth and activate responsibly β¨
and that's a wrap on the smp_utils-0.96 era, dated June 2011 β SMP_ZONE_ACTIVATE(8), signing off. mwah. π
π¦ where this page comes from
- debian bookworm: smp-utils 0.99-1 Β· BSD-3-Clause
- debian trixie: smp-utils 0.99-1 Β· BSD-3-Clause
- epel 10: smp_utils 0.99-1.el10_0 Β· BSD-3-Clause
- epel 9: smp_utils 0.99-5.el9 Β· BSD
- fedora 43: smp_utils 0.99-14.fc43 Β· BSD-3-Clause
- fedora 44: smp_utils 0.99-15.fc44 Β· BSD-3-Clause
- opensuse-leap 16.0: smp_utils 0.99-bp160.1.6 Β· BSD-3-Clause AND GPL-2.0-only
- opensuse-leap 16.0: smp_utils 0.99-bp160.1.6 Β· BSD-3-Clause AND GPL-2.0-only
- opensuse-leap 16.0: smp_utils 0.99-bp160.1.6 Β· BSD-3-Clause AND GPL-2.0-only
- opensuse-leap 16.0: smp_utils 0.99-bp160.1.6 Β· BSD-3-Clause AND GPL-2.0-only
- ubuntu jammy: smp-utils 0.99-1 Β· BSD-3-Clause
- ubuntu noble: smp-utils 0.99-1 Β· BSD-3-Clause
- ubuntu resolute: smp-utils 0.99-1build1 Β· BSD-3-Clause
- ubuntu stonking: smp-utils 0.99-1build1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms