hpionIBMblade(1)
π
hpionIBMblade β an OpenHPI sample app (that's hpionIBMblade(1) in the OpenHPI manual, bestie)
okay so picture this: you've got an IBM Blade with a Basedboard Management Controller (BMC), and you've got two openhpi plugins that both want to talk about it. This little demo app is literally the blueprint for making them share. β¨
πΈ SYNOPSIS πΈ
hpionIBMblade [-D nn] [-N host[:port]] [-C <cfgfile>] [ -X ] [ -h ]
hpionIBMblade [--domain nn] [--host=host[:port]] [--cfgfile=file] [--debug] [--help]
π¦ DESCRIPTION π¦
So hpionIBMblade is a sample application that shows how two (2) openhpi plugins can be used to display and manage resources of an IBM Blade with Basedboard Management Controller (BMC). That's the whole vibe. π«Ά
Here's the cute part: both the ipmi and snmp_bc plugin have the same IBM Blade target, and the resources from both plugins get combined so you see one complete view of the IBM Blade. Two plugins, one blade, zero drama. π
β οΈ @@ WARNING @@ RESTRICTIONS @@ WARNING @@ RESTRICTIONS @@ WARNING @@ RESTRICTIONS @@ β οΈ This client application is designed to run only inband on an IBM Blade with Basedboard Management Controller (BMC). Like, only only. Do not come in out-of-band expecting a slay. π«
And if no domain or host is selected, hpionIBMblade uses the default domain as specified in the openhpiclient.conf file. Easy. π
β¨ OPTIONS β¨
π Help Options π
-h,--helpβ Show help options. The classic "what does this do again" button, we love her.
π Application Options π
-D nn,--domain=nnβ Select domain idnn. Pick your domain, bestie.-X,--debugβ Display debug messages. Turn it on when you want the app to overshare.-N "host[:port]",--host="host[:port]"β Open session to the domain served by the daemon at the specified URL (host:port). This option overrides theOPENHPI_DAEMON_HOSTandOPENHPI_DAEMON_PORTenvironment variables. Ifhostcontains':'(for example an IPv6 address) then enclose it in square brackets. For example:"[::1]"or"[::1]:4743". IPv6 girlies, the brackets are not optional, I'm sorry. π-C "file",--cfgfile="file"β Use passed file as client configuration file. This option overrides theOPENHPICLIENT_CONFenvironment variable. Your config, your rules. π
π SAMPLE CONFIGURATION FILE π
fr fr just copy this and adjust the bits that are yours:
handler libipmi {
entity_root = "{SYSTEM_CHASSIS,2}"
name = "smi"
addr = 0
}
handler libsnmp_bc {
host = "bc.mm.ip.address"
version = "3"
community = "bc_community"
entity_root = "{SYSTEM_CHASSIS,1}"
security_name = "myid"
passphrase = "mypassword"
security_level = "authNoPriv"
auth_type = "MD5"
}
Two handlers, two plugins, one combined view. it's giving teamwork. π§
π₯ SEE ALSO π₯
the whole friend group, in original order:
hpi_shellhpialarmshpifanhpiresethpitophpidomainhpigensimdatahpisensorhpitreehpielhpiiinvhpisettimehpiwdthpieventshpipowerhpithreshpixmlohdomainlistohhandlerohparam
π AUTHORS π
Authors of this man page β show some respect, they ate:
- Peter D Phan (
pdphan@users.sourceforge.net) - Ulrich Kleber (
ulikleber@users.sourceforge.net) - Anton Pak (
avpak@users.sourceforge.net)
k bye bestie π
this was hpionIBMblade(1) from OpenHPI, version 4.0.0, dated 2023-01-26 β mwah, go read the config file and stan two plugins at once π¦
π¦ where this page comes from
- opensuse-leap 16.0: openhpi-clients 3.8.0.ge4631e8a-bp160.1.14 Β· BSD-3-Clause
- opensuse-leap 16.0: openhpi-clients 3.8.0.ge4631e8a-bp160.1.14 Β· BSD-3-Clause
- opensuse-leap 16.0: openhpi-clients 3.8.0.ge4631e8a-bp160.1.14 Β· BSD-3-Clause
- opensuse-leap 16.0: openhpi-clients 3.8.0.ge4631e8a-bp160.1.14 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms