openipmi_conparms(7)

💖 NAME 💖

openipmi_cmdparms — Connection parmeters for OpenIPMI

okay bestie, yes, the manual name up top is openipmi_conparms (that's the page you're reading, openipmi_conparms(7)) but the NAME section literally says openipmi_cmdparms and we are not touching it, we keep the receipts exactly as they are 💅

---

✨ SYNOPSIS ✨

smi smi-num

lan [-U username] [-P password] [-p[2] port] [-A authtype] [-L
privilege] [-s] [-Ra auth alg] [-Ri integ alg] [-Rc conf algo] [-Rl]
[-Rk bmc key] [-H hackname] host [ host]

---

🦋 DESCRIPTION 🦋

The connection parameters for OpenIPMI vary depending on the connection type. This document describes the standard connection types; others may be available from OEMs.

that's it, that's the whole vibe check. different connection type → different params. periodt ✨

---

🎀 OPTIONS 🎀

• smi-num — The SMI interface for the local connection. There may be more than one BMC connection on a system and they are generally numbered, like /dev/ipmi0, /dev/ipmi1, etc. so yeah, you just hand it a number and it knows which one you mean 🫶
• -U username — Use the given username for the LAN connection. If none is given, then no username is used. no username, no problem, we simply don't have one 🙈
• -P password — The password to use for the connection. If none is given, the user is assumed to have an empty password. empty password is the default, and yes that means what you think it means 👀
• -p[2] port — The UCP port to connect to. This defaults to the standard 623 port, so it is not necessary unless a special port is required. Note that since you can have two connections (hosts), -p is for the first host and -p2 is for the second host. two hosts, two ports, no confusion, we stay organized 💅
• -A authtype — The authentication type to use, one of rmcp+, md5, md2, straight, or none. If you don't supply this, the most secure one available is chosen, in the order given in the previous list. so it's ranking them, most secure first, and it just picks the best one for you. slay, it's looking out for you 🔥
• -L privilege — The privilege to use for the connection. Lower privileges cannot execute some commands. Privileges are: callback, user, operator, admin, and oem. The default is admin. lowkey powerful by default, as you should be 👑
• -Ra authentication algorithm — Set the RMCP+ authentication algorithm to use. Options are: bmcpick, rakp_none, rakp_hmac_sha1, and rakp_hmac_md5. The bmcpick option is used by default, which means the BMC picks the algorithm it wants to use. letting the BMC have main character energy and choose, iconic honestly ✨
• -Ri integrity algorithm — The RMCP+ integrity algorithm to use. This ensures that the data has not be altered between the sender and receiver. Valid options are: bmcpick, none, hmac_sha1, hmac_md5, and md5. The bmcpick option is used by default, which means the BMC picks the algorithm it wants to use. integrity!! it's literally in the name, the data arrives un-altered, fr fr 🫶
• -Rc confidentiality algorithm — The RMCP+ confidentiality (encryption) algorithm to use. This keeps evesdroppers from seeing the data. Valid values are: bmcpick, aes_cbc_128, xrc4_128, and xrc_40. The bmcpick option is used by default, which means the BMC picks the algorithm it wants to use. no peeking, no eavesdropping, we keep it private 🔒 (well, we keep it private with whatever algorithm gets picked 🙈)
• -Rl — If this is specified, the username is looked up using the privilege level along with the username. This allows the same name to have different passwords with different privilege levels. so like, same name, different passwords depending on privilege. lowkey genius 🧚
• -Rk BMC Key — If the system requires two-key lookups, this specifies the second key (the BMC key) to use. This is ignored if two-key lookups are not enabled by the BMC. if the BMC doesn't do two-key lookups, this whole option just sits there ignored 💀
• -H hackname — Well, it always happens. Things in the field don't work quite like they are supposed to. There was some vagueness in the first IPMI specs and different vendors interpreted RMCP+ in different ways. This allows different options to be supported. Try different hacks if your RMCP+ systems don't authenticate properly. These are:
  • rakp3_wrong_rolem — Some systems use the incorrect Role(m) field in a specific authentication message (the RAKP3 message). This is a common problem. common!! so if your auth is acting up, this one is a strong suspect 😭
  • rmcpp_integ_sik — The original IPMI 2.0 spec specified the incorrect key to use for the integrity key. This forces use of the Session Initiation Key. The default is to use K(1). so by default it's K(1), and this flag forces the Session Initiation Key instead. the spec said the wrong thing, we cope 💀
• -s — Make two connections to the BMC. This means the BMC has two different IP addresses/ports that are equivalent. If this is specified, a second host must be supplied. This is not the same as two connections to two different BMCs. This must be a connection to the same BMC. read that again bestie — same BMC, two equivalent addresses/ports, NOT two different BMCs 🚨
• host — The IP address (either by name lookup or specified directly) to connect to. If the -s is specified, two hosts must be supplied. name lookup or direct, both work, and with -s you gotta give it two 🫶

⚠️ heads up: The -Ra, -Ri, -Rc, -Rk and -Rl options only apply to RMCP+ connections and will be ignored if the connection does not support RMCP+ or if a non-RMCP+ authentication type is specified. so if you're not doing RMCP+, those five are just decoration, don't come crying to me 😭

---

🌈 SEE ALSO 🌈

ipmish(8), openipmicmd(8), solterm(1)

go read those too, they're the rest of the friend group 💜

---

💀 KNOWN PROBLEMS 💀

This is excessively complicated, but the defaults should be good.

ngl it IS a lot of options. but the defaults ate, so just vibe with them ✨

---

🎀 AUTHOR 🎀

Corey Minyard <cminyard@mvista.com>

---

and that's the whole page bestie!! this was openipmi_conparms(7) from OpenIPMI, dated 05/13/03 — yeah it's an elder, and it still slays 💅✨🦋