cimprovider(1)

💖 cimprovider(1) 💖

okay so bestie, welcome to cimprovider(1), the little command that handles all your CIM provider drama — disabling, enabling, removing, grouping, listing, and status-checking registered CIM providers and CIM provider modules. it's giving sysadmin main character energy, and you're about to ate. ✨

---

🌸 NAME 🌸

cimprovider — disable, enable, remove, group, list, or display status of registered CIM providers or CIM provider modules 🫶

---

✨ SYNOPSIS ✨

cimprovider -d -m module

cimprovider -e -m module

cimprovider -r -m module [ -p provider ]

cimprovider -g group -m module

cimprovider -l  [ -s | -f | -m module ]

cimprovider -h

cimprovider --help

cimprovider --version

🎀 Remarks 🎀

• the -l option can be run by any user(s) — literally anyone, no gatekeeping 💅
• every other option needs superuser permissions, no cap 👑
• this command disables, enables, or removes one CIM provider module or CIM provider at a time — one at a time, bestie, we're not doing multitasking here 🙈

---

🦋 DESCRIPTION 🦋

so cimprovider is basically a command line interface (CLI) that lets you disable, enable, unregister, group, and list registered CIM providers. here's the vibe breakdown:

• if a CIM provider is disabled, the CIM Server rejects any requests to the provider. blocked. blocked. blocked. 💀
• if a CIM provider is enabled, the CIM Server forwards requests to the provider. slay, it's working ✨
• if a CIM provider is unregistered, the CIM Server will no longer have any information about the provider. it's gone, it's deleted from the group chat 😭

to use cimprovider, cimserver has to be running, and the specified provider module (which is a grouping of providers in the same shared library, iykyk) or provider has to be registered with WBEM Services. no registration, no service 🫶

the first form of cimprovider disables the specified provider module. when a provider module is in the disabled state, any new requests to the providers inside that module get rejected. sorry babes.

the second form enables the providers contained in the specified provider module. they're now ready to accept new requests. their comeback era 🌈

the third form removes (un-registers) the specified provider module and all of its contained providers, or just the specified provider inside the specified provider module. once removed, a provider or provider module must be re-registered — typically by loading its registration schema via the cimmof command. you gotta re-add them yourself, no autopilot 💅

the fourth form sets the provider module group. if the provider module is active, it gets disabled first, the group is set, and then it's enabled again. if the group name is CIMServer, the provider module is loaded into the CIMServer process depending on the UserContext value. specify an empty string to remove from grouping.

the last form lists all the registered provider modules and module status, or all the providers in the specified provider module. and pro tip: to list all providers in all modules, issue a cimprovider -l command, followed by cimprovider -l -m for each listed module. yes, for each one. one by one. we love a lil loop energy 🔁

---

⭐ provider module status values ⭐

these are the moods your provider module can be in:

• OK — the provider module is enabled. thriving. 💖
• Stopping — the provider module is in the process of being disabled. mid-transition, don't perceive it 🙈
• Stopped — the provider module is disabled. resting era.
• Degraded — a failure was detected in an out-of-process provider module. disable and re-enable the provider module to ensure any active indication subscriptions are being served. it needs a lil reset bestie 🔄
• Error — an invalid registration instance was encountered upon CIM Server initialization. not iconic. 💀

---

specifying no options with the cimprovider command displays the command usage. so if you just type it and hit enter, it'll tell you how to use it. helpful queen 🎀

---

👑 Options 👑

the cimprovider command recognizes the following options:

• -d — disables the specified CIM provider module. if user(s) try to disable a module that is already disabled, an error message is returned and no action is taken. 💀
• -e — enables the specified CIM provider module. if user(s) try to enable a module that's already enabled, or try to enable a module that's disabling, an error message is returned and no action is taken. 🙈
• -h, --help — display command usage information. the "help me bestie" button 🫶
• -l — displays all the registered provider modules.
• -m module — specifies the provider module for the operation.
• -p provider — specifies the provider for the operation.
• -r — removes the specified provider module and all of its contained providers. if provider is specified, removes the specified provider in the specified provider module, not affecting any other providers in that module. surgical. precise. 💅
• -g — sets the CIM provider module group. specify an empty string to remove from grouping. if the provider module is active, the provider module is disabled first, the group is set, and it's enabled again. all provider modules with the same group name are loaded into a single agent process — except when overridden by specific UserContext values. if the group name is CIMServer, the provider module is loaded into the CIMServer process depending on the UserContext value. family reunion energy 🌈
• -s — displays the status of provider modules.
• -f — displays the full status of provider modules with group name.
• --version — display CIM Server version number. 👑

---

💀 EXIT STATUS 💀

when an error occurs, an error message is written to stderr and an error value 1 is returned. the following return values are returned:

• 0 — successful completion ✨
• 1 — error 💀

---

🧚 USAGE NOTES 🧚

cimprovider requires that the CIM Server is running. and if an operation takes more than two minutes to be processed, the cimprovider command prints a timeout message and returns an error value. patience is a virtue but two minutes is the limit bestie ⏳

---

🔥 EXAMPLES 🔥

disable provider module "OperatingSystemProvider" and all of its contained providers (placing them in a stopped state):

cimprovider -d -m OperatingSystemProvider

enable provider module "OperatingSystemProvider" and all of its contained providers (placing them in an OK state):

cimprovider -e -m OperatingSystemProvider

remove (un-register) the "OperatingSystemProvider" provider module and all of its contained providers:

cimprovider -r -m OperatingSystemProvider

remove (un-register) the "PG_OperatingSystemProvider" provider that is contained in the "OperatingSystemProvider" provider module:

cimprovider -r -m OperatingSystemProvider -p PG_OperatingSystemProvider

list the registered provider modules:

cimprovider -l

list the registered provider modules and their status (such as OK, Stopping, Stopped):

cimprovider -l -s

list the registered providers which are contained in the "OperatingSystemProvider" provider module:

cimprovider -l -m OperatingSystemProvider

set the group name of the "OperatingSystemProvider" provider module to "CIMServer":

cimprovider -g CIMServer -m OperatingSystemProvider

remove "OperatingSystemProvider" provider module from grouping:

cimprovider -g "" -m OperatingSystemProvider

---

🍓 SEE ALSO 🍓

cimmof(1), cimserver(1).

---

okay that's the whole thing bestie, you're officially a cimprovider girlie now 💅 and that's a wrap on cimprovider(1) — you found it in the cimprovider(1) manual, and honestly? iconic. go forth and manage those providers. no cap. 🎀✨💖