BMC-INFO(8)

📦
version 1.6.20 · 14 versions
, in arch rolling, centos-stream 10, centos-stream 9

🌸 bmc-info(8) — display BMC information 🌸

okay bestie, welcome to bmc-info 💅 it lives in the System Commands part of the manual, and it's genuinely one of the easiest tools in the whole FreeIPMI family — it just walks up to a BMC and shows you what's inside its brain. no cap.

✨ NAME ✨

bmc-info — display BMC information 🫶

✨ SYNOPSIS ✨

bmc-info [OPTION...]

✨ DESCRIPTION ✨

so what does it actually do? bmc-info displays BMC information, like:

  • device version numbers
  • device support
  • globally unique IDs (guids) 🎀

Listed below (and, like, way below) are general IPMI options, tool specific options, troubleshooting information, workaround information, examples, and known issues. For a general introduction to FreeIPMI, go peek at freeipmi(7). it's giving "read the docs bestie" but in a nice way 💖

✨ GENERAL OPTIONS ✨

these are the general options for configuring IPMI communication and executing general tool commands. the whole squad 🔥

  • -D IPMIDRIVER, --driver-type=IPMIDRIVER — specify the driver type to use instead of doing an auto selection. the currently available outofband drivers are LAN and LAN_2_0, which perform IPMI 1.5 and IPMI 2.0 respectively. the currently available inband drivers are KCS, SSIF, OPENIPMI, SUNBMC, and INTELDCMI. pick your fighter, they're all iconic in their own way 👑
  • --disable-auto-probe — don't probe in-band IPMI devices for default settings. like, mind your own business, respectfully 🙈
  • --driver-address=DRIVER-ADDRESS — specify the in-band driver address to be used instead of the probed value. DRIVER-ADDRESS should be prefixed with "0x" for a hex value and '0' for an octal value. lowkey important, don't forget the prefix fr fr.
  • --driver-device=DEVICE — specify the in-band driver device path to be used instead of the probed path. you get to choose the path, main character energy 🌈
  • --register-spacing=REGISTER-SPACING — specify the in-band driver register spacing instead of the probed value. argument is in bytes (i.e. 32bit register spacing = 4). math but make it cute 🧮
  • --target-channel-number=CHANNEL-NUMBER — specify the in-band driver target channel number to send IPMI requests to. channel assignment: handled 💅
  • --target-slave-address=SLAVE-ADDRESS — specify the in-band driver target slave number to send IPMI requests to. yes bestie, aim your requests precisely 🎯
  • -h IPMIHOST1,IPMIHOST2,...,, --hostname=IPMIHOST1[:PORT],IPMIHOST2[:PORT],... — specify the remote host(s) to communicate with. multiple hostnames may be separated by comma or may be specified in a range format; see HOSTRANGED SUPPORT below. an optional port can be specified with each host, which may be useful in port forwarding or similar situations. if specifying an IPv6 address and port, use the format [ADDRESS]:PORT. so fancy, so correct ✨
  • -u USERNAME, --username=USERNAME — specify the username to use when authenticating with the remote host. if not specified, a null (i.e. anonymous) username is assumed. the user must have atleast USER privileges in order for this tool to operate fully. no VIP pass, no full tour 🎟️
  • -p PASSWORD, --password=PASSWORD — specify the password to use when authenticating with the remote host. if not specified, a null password is assumed. maximum password length is 16 for IPMI 1.5 and 20 for IPMI 2.0. count your characters bestie 🔢
  • -P, --password-prompt — prompt for password to avoid possibility of listing it in process lists. keep that secret secret 🤫
  • -k K_G, --k-g=K_G — specify the K_g BMC key to use when authenticating with the remote host for IPMI 2.0. if not specified, a null key is assumed. to input the key in hexadecimal form, prefix the string with '0x'. e.g., the key 'abc' can be entered with the either the string 'abc' or the string '0x616263'. two paths, same vibe 💜
  • -K, --k-g-prompt — prompt for k-g to avoid possibility of listing it in process lists. again: sneaky 🤐
  • --session-timeout=MILLISECONDS — specify the session timeout in milliseconds. defaults to 20000 milliseconds (20 seconds) if not specified. giving it twenty whole seconds ⏳
  • --retransmission-timeout=MILLISECONDS — specify the packet retransmission timeout in milliseconds. defaults to 1000 milliseconds (1 second) if not specified. the retransmission timeout cannot be larger than the session timeout. not negotiable, that's the rule 🚨
  • -a AUTHENTICATION-TYPE, --authentication-type=AUTHENTICATION-TYPE — specify the IPMI 1.5 authentication type to use. the currently available authentication types are NONE, STRAIGHT_PASSWORD_KEY, MD2, and MD5. defaults to MD5 if not specified. classic choice honestly 🌟
  • -I CIPHER-SUITE-ID, --cipher-suite-id=CIPHER-SUITE-ID — specify the IPMI 2.0 cipher suite ID to use. the Cipher Suite ID identifies a set of authentication, integrity, and confidentiality algorithms to use for IPMI 2.0 communication. the authentication algorithm identifies the algorithm to use for session setup, the integrity algorithm identifies the algorithm to use for session packet signatures, and the confidentiality algorithm identifies the algorithm to use for payload encryption. defaults to cipher suite ID 3 if not specified. the following cipher suite ids are currently supported:
    • 0 — Authentication Algorithm = None; Integrity Algorithm = None; Confidentiality Algorithm = None
    • 1 — Authentication Algorithm = HMAC-SHA1; Integrity Algorithm = None; Confidentiality Algorithm = None
    • 2 — Authentication Algorithm = HMAC-SHA1; Integrity Algorithm = HMAC-SHA1-96; Confidentiality Algorithm = None
    • 3 — Authentication Algorithm = HMAC-SHA1; Integrity Algorithm = HMAC-SHA1-96; Confidentiality Algorithm = AES-CBC-128
    • 6 — Authentication Algorithm = HMAC-MD5; Integrity Algorithm = None; Confidentiality Algorithm = None
    • 7 — Authentication Algorithm = HMAC-MD5; Integrity Algorithm = HMAC-MD5-128; Confidentiality Algorithm = None
    • 8 — Authentication Algorithm = HMAC-MD5; Integrity Algorithm = HMAC-MD5-128; Confidentiality Algorithm = AES-CBC-128
    • 11 — Authentication Algorithm = HMAC-MD5; Integrity Algorithm = MD5-128; Confidentiality Algorithm = None
    • 12 — Authentication Algorithm = HMAC-MD5; Integrity Algorithm = MD5-128; Confidentiality Algorithm = AES-CBC-128
    • 15 — Authentication Algorithm = HMAC-SHA256; Integrity Algorithm = None; Confidentiality Algorithm = None
    • 16 — Authentication Algorithm = HMAC-SHA256; Integrity Algorithm = HMAC_SHA256_128; Confidentiality Algorithm = None
    • 17 — Authentication Algorithm = HMAC-SHA256; Integrity Algorithm = HMAC_SHA256_128; Confidentiality Algorithm = AES-CBC-128

(yes those last two really do use underscores in HMAC_SHA256_128 — she's built different 😭 don't @ me, that's just what the page says 💀)

  • -l PRIVILEGE-LEVEL, --privilege-level=PRIVILEGE-LEVEL — specify the privilege level to be used. the currently available privilege levels are USER, OPERATOR, and ADMIN. defaults to USER if not specified. glow up to ADMIN when you're ready 👑
  • --config-file=FILE — specify an alternate configuration file. your config, your rules 🎀
  • -W WORKAROUNDS, --workaround-flags=WORKAROUNDS — specify workarounds to vendor compliance issues. multiple workarounds can be specified separated by commas. a special command line flag of "none" will indicate no workarounds (may be useful for overriding configured defaults). see WORKAROUNDS below for a list of available workarounds. we love a flexible queen 🌸
  • --debug — turn on debugging. the tea is piping hot ☕
  • -?, --help — output a help list and exit. the built-in bestie 🫶
  • --usage — output a usage message and exit. short and sweet ⭐
  • -V, --version — output the program version and exit. identity check 💖

✨ BMC-INFO OPTIONS ✨

these ones are specific to bmc-info, and honestly? they're the whole point. slay 💅

  • --get-device-id — display only device ID information. just the ID, nothing extra 🎯
  • --get-device-guid — display only device guid. one guid, all vibes 🦋
  • --get-system-guid — display only system guid. system-level uniqueness, iconic 🌟
  • --get-system-info — display only system info. the whole system's little biography 📖
  • --get-channel-info — display only channel information. channel content, curated ✨
  • --interpret-oem-data — attempt to interpret OEM data, such as event data, sensor readings, or general extra info, etc. if an OEM interpretation is not available, the default output will be generated. correctness of OEM interpretations cannot be guaranteed due to potential changes OEM vendors may make in products, firmware, etc. see OEM INTERPRETATION below for confirmed supported motherboard interpretations. we're doing our best and being honest about it 😭🙈

✨ HOSTRANGED OPTIONS ✨

these options manipulate hostranged output. see HOSTRANGED SUPPORT below for additional information on hostranges. it's giving "many hosts, one very organized bestie" 👑

  • -B, --buffer-output — buffer hostranged output. for each node, buffer standard output until the node has completed its IPMI operation. when specifying this option, data may appear to output slower to the user since the the entire IPMI operation must complete before any data can be output. see HOSTRANGED SUPPORT below for additional information. patience is a virtue and also literally required here ⏳
  • -C, --consolidate-output — consolidate hostranged output. the complete standard output from every node specified will be consolidated so that nodes with identical output are not output twice. a header will list those nodes with the consolidated output. when this option is specified, no output can be seen until the IPMI operations to all nodes has completed. if the user breaks out of the program early, all currently consolidated output will be dumped. see HOSTRANGED SUPPORT below for additional information. dedupe queen 🙌
  • -F NUM, --fanout=NUM — specify multiple host fanout. a "sliding window" (or fanout) algorithm is used for parallel IPMI communication so that slower nodes or timed out nodes will not impede parallel communication. the maximum number of threads available at the same time is limited by the fanout. the default is 64. sixty-four little threads all doing their thing 🧵
  • -E, --eliminate — eliminate hosts determined as undetected by ipmidetect. this attempts to remove the common issue of hostranged execution timing out due to several nodes being removed from service in a large cluster. the ipmidetectd daemon must be running on the node executing the command. bye-bye ghost nodes 👋💀
  • --always-prefix — always prefix output, even if only one host is specified or communicating in-band. this option is primarily useful for scripting purposes. option will be ignored if specified with the -C option. sorry -C, you win this round 💅

okay that's the first chunk, bestie — there's more coming, don't go anywhere 🎀

💖 HOSTRANGED SUPPORT 💖

Okay so bestie, here's the tea on feeding this thing multiple hosts at once. You've got two ways: either you write out an explicit comma-separated list of hosts, or you give a range of hostnames in the general form prefix[n-m,l-k,...], where n < m and l < k, etc. 🌈

⚠️ Do not confuse the range form with regular expression character classes — which, yes, also use []. They are not the same thing, no cap. For example, foo[19] does not represent foo1 or foo9 — it's a degenerate range and it literally just means foo19. 💀

This range syntax is meant only as a convenience on clusters that follow a prefixNN naming convention, and honestly specifying ranges is never necessary — the list foo1,foo9 can be written as foo1,foo9, or you could write it as the range foo[1,9]. Either slaps. ✨

Some examples of range usage, for the visual learners:

foo[01-05] instead of foo01,foo02,foo03,foo04,foo05
foo[7,9-10] instead of foo7,foo9,foo10
foo[0-3] instead of foo0,foo1,foo2,foo3

And a lil reminder to the reader (that's you 🫶): some shells will interpret brackets ([ and ]) for pattern matching. Depending on your shell, you may need to enclose ranged lists within quotes. Protect your brackets, they're doing their best. 🎀

When multiple hosts are specified by the user, a thread will be executed for each host in parallel, up to the configured fanout — which you can adjust via the -F option. This lets you talk to large numbers of nodes so much faster than doing it in serial. Main character energy for your cluster. 👑

By default, standard output from each node specified will be output with the hostname prepended to each line. This is readable in many situations, but ngl it can be difficult to read in others — for example, output from multiple nodes may be mixed together. The -B and -C options can be used to change this default. 🙈

In-band IPMI Communication will be used when the host localhost is specified. This allows the user to add the localhost into the hostranged output. Cute, right? 🌸

🔧 GENERAL TROUBLESHOOTING 🔧

Most often, IPMI problems are due to configuration problems. Like, that's the whole vibe. 💅

IPMI over LAN problems involve a misconfiguration of the remote machine's BMC. Double check to make sure the following are configured properly in the remote machine's BMC: IP address, MAC address, subnet mask, username, user enablement, user privilege, password, LAN privilege, LAN enablement, and allowed authentication type(s). For IPMI 2.0 connections, double check to make sure the cipher suite privilege(s) and K_g key are configured properly. The ipmi-config(8) tool can be used to check and/or change these configuration settings. It's giving "have you tried turning it off and on again" but for BMCs. ✨

Inband IPMI problems are typically caused by improperly configured drivers or non-standard BMCs.

In addition to the troubleshooting tips below, please see WORKAROUNDS below to also if there are any vendor specific bugs that have been discovered and worked around. 👀

Listed below are many of the common issues for error messages. For additional support, please e-mail the <freeipmi-users@gnu.org> mailing list. They're lovely, fr fr. 💌

"username invalid" — The username entered (or a NULL username if none was entered) is not available on the remote machine. It may also be possible the remote BMC's username configuration is incorrect. 😭

"password invalid" — The password entered (or a NULL password if none was entered) is not correct. It may also be possible the password for the user is not correctly configured on the remote BMC.

"password verification timeout" — Password verification has timed out. A "password invalid" error (described above) or a generic "session timeout" (described below) occurred. During this point in the protocol it cannot be differentiated which occurred. Rude, honestly. 😤

"k_g invalid" — The K_g key entered (or a NULL K_g key if none was entered) is not correct. It may also be possible the K_g key is not correctly configured on the remote BMC.

"privilege level insufficient" — An IPMI command requires a higher user privilege than the one authenticated with. Please try to authenticate with a higher privilege. This may require authenticating to a different user which has a higher maximum privilege. Level up! 🎮

"privilege level cannot be obtained for this user" — The privilege level you are attempting to authenticate with is higher than the maximum allowed for this user. Please try again with a lower privilege. It may also be possible the maximum privilege level allowed for a user is not configured properly on the remote BMC.

"authentication type unavailable for attempted privilege level" — The authentication type you wish to authenticate with is not available for this privilege level. Please try again with an alternate authentication type or alternate privilege level. It may also be possible the available authentication types you can authenticate with are not correctly configured on the remote BMC.

"cipher suite id unavailable" — The cipher suite id you wish to authenticate with is not available on the remote BMC. Please try again with an alternate cipher suite id. It may also be possible the available cipher suite ids are not correctly configured on the remote BMC. 🔐

"ipmi 2.0 unavailable" — IPMI 2.0 was not discovered on the remote machine. Please try to use IPMI 1.5 instead. Throwback era, but okay. 🦋

"connection timeout" — Initial IPMI communication failed. A number of potential errors are possible, including an invalid hostname specified, an IPMI IP address cannot be resolved, IPMI is not enabled on the remote server, the network connection is bad, etc. Please verify configuration and connectivity. The classic "is it plugged in" moment. 💀

"session timeout" — The IPMI session has timed out. Please reconnect. If this error occurs often, you may wish to increase the retransmission timeout. Some remote BMCs are considerably slower than others. Give them a minute, they're doing their best. 🐢

"device not found" — The specified device could not be found. Please check configuration or inputs and try again.

"driver timeout" — Communication with the driver or device has timed out. Please try again.

"message timeout" — Communication with the driver or device has timed out. Please try again.

"BMC busy" — The BMC is currently busy. It may be processing information or have too many simultaneous sessions to manage. Please wait and try again. She's booked and busy, respect it. 💅

"could not find inband device" — An inband device could not be found. Please check configuration or specify specific device or driver on the command line.

"driver timeout" — The inband driver has timed out communicating to the local BMC or service processor. The BMC or service processor may be busy or (worst case) possibly non-functioning. Worst case!! 😭

🛠️ WORKAROUNDS 🛠️

Okay bestie, listen — the IPMI world is a whole mess of vendors doing their own thing, and sometimes they implement the protocols wrong. Like, not "oops typo" wrong, but "the spec says this and they shipped that" wrong. The following is the whole menu of workarounds currently available for the compliance issues people have discovered out there in the wild. 💀

Where we could, the workarounds just happen automatically so they're transparent to you — no action needed, you're welcome. But some of them you gotta ask for yourself, using the -W option. iykyk.

Some real talk about the hardware list below: it might only mean that's the hardware where somebody first found the problem. Newer versions of the same hardware may have already fixed it. Similar machines from the same vendor may or may not have the same issue — it's giving chaos. And plot twist: different vendors sometimes license their firmware from the same IPMI firmware developer, so it's genuinely worth trying the workarounds below even if your motherboard isn't listed. fr fr.

If you think your hardware has another compliance issue that deserves a workaround, please hit up the FreeIPMI maintainers at <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>. They wanna hear it. 🫶

  • assumeio — this one assumes the inband interfaces talk to system I/O instead of being memory-mapped. It's the fix for systems that report base addresses that are just… wrong. If you're hitting this you might see "device not supported" or "could not find inband device" errors. Observed on the HP ProLiant DL145 G1. ✨
  • spinpoll — this tells some inband drivers (most notably the KCS driver) to spin while polling instead of putting the process to sleep. That can significantly improve the wall clock running time of tools, because your operating system scheduler's granularity may be way bigger than the time it takes to do a single IPMI message transaction. But — and this is the tradeoff, bestie — by spinning, your system may be doing less useful work, because it's not contexting the tool out for a more useful task. 😭
  • authcap — skips the early checks for username capabilities, authentication capabilities, and K_g support, and just lets IPMI authentication succeed. It works around multiple issues where the remote system doesn't properly report username capabilities, authentication capabilities, or K_g status. Hitting this? You might see "username invalid", "authentication type unavailable for attempted privilege level", or "k_g invalid" errors. Observed on Asus P5M2/P5MT-R/RS162-E4/RX4, Intel SR1520ML/X38ML, and Sun Fire 2200/4150/4450 with ELOM. 💅
  • nochecksumcheck — tells FreeIPMI to not check the checksums returned from IPMI command responses. It works around systems that return invalid checksums because of implementation errors, even though the packet is otherwise valid. > Fair warning though: users are cautioned on the use of this option, because it removes validation of packet integrity in a number of circumstances. That said, it's unlikely to be an issue in most situations. You might see "connection timeout", "session timeout", or "password verification timeout" errors. On IPMI 1.5 connections, the "noauthcodecheck" workaround may also be needed too. Observed on Supermicro X9SCM-iiF, Supermicro X9DRi-F, and Supermicro X9DRFR. 🦋
  • idzero — lets the client accept empty session IDs. It works around IPMI sessions that report empty session IDs to the client. You might see "session timeout" errors. Observed on Tyan S2882 with M3289 BMC. 🌸
  • unexpectedauth — allows unexpected non-null authcodes to be checked as though they were expected. It works around an issue where packets contain non-null authentication data when they should be null, because per-message authentication is disabled. You might see "session timeout" errors. Observed on Dell PowerEdge 2850,SC1425. Confirmed fixed on newer firmware. ✨
  • forcepermsg — forces per-message authentication to be used no matter what the remote system advertises. It works around an issue where per-message authentication is advertised as disabled on the remote system, but it's actually required for the protocol. Like, pick a lane, babe. You might see "session timeout" errors. Observed on IBM eServer 325. 🎀
  • endianseq — flips the endian of the session sequence numbers so the session can continue properly. It works around IPMI 1.5 session sequence numbers that are the wrong endian. You might see "session timeout" errors. Observed on some Sun ILOM 1.0/2.0 (depends on service processor endian). 🙈
  • noauthcodecheck — tells FreeIPMI to not check the authentication codes returned from IPMI 1.5 command responses. It works around systems that return invalid authentication codes due to hashing or implementation errors. > Users are cautioned on the use of this option, as it removes an authentication check verifying the validity of a packet. However, in most organizations, this is unlikely to be a security issue. You might see "connection timeout", "session timeout", or "password verification timeout" errors. Observed on Xyratex FB-H8-SRAY, Intel Windmill, Quanta Winterfell, and Wiwynn Windmill. 👑
  • intel20 — works around several Intel IPMI 2.0 authentication issues. The issues covered include padding of usernames, and password truncation if the authentication algorithm is HMAC-MD5-128. You might see "username invalid", "password invalid", or "k_g invalid" errors. Observed on Intel SE7520AF2 with Intel Server Management Module (Professional Edition). 🔥
  • supermicro20 — works around several Supermicro IPMI 2.0 authentication issues on motherboards w/ Peppercon IPMI firmware. The issues covered include handling invalid length authentication codes. You might see "password invalid" errors. Observed on Supermicro H8QME with SIMSO daughter card. Confirmed fixed on newerver firmware. 💜
  • sun20 — works around several Sun IPMI 2.0 authentication issues. The issues covered include invalid lengthed hash keys, improperly hashed keys, and invalid cipher suite records. You might see "password invalid" or "bmc error" errors. Observed on Sun Fire 4100/4200/4500 with ILOM. Heads up: this workaround automatically includes the "opensesspriv" workaround. 🌈
  • opensesspriv — slightly alters FreeIPMI's IPMI 2.0 connection protocol to work around an invalid hashing algorithm used by the remote system. The privilege level sent during the Open Session stage of an IPMI 2.0 connection gets used for hashing keys, instead of the privilege level sent during the RAKP1 connection stage. You might see "password invalid", "k_g invalid", "bad rmcpplus status code", or "privilege level cannot be obtained for this user" errors. Observed on Sun Fire 4100/4200/4500 with ILOM, Inventec 5441/Dell Xanadu II, Supermicro X8DTH, Supermicro X8DTG, Intel S5500WBV/Penguin Relion 700, Intel S2600JF/Appro 512X, Quanta QSSC-S4R/Appro GB812X-CN, Dell C5220, and the OpenIPMI software BMC. This workaround is automatically triggered with the "sun20" workaround. ⭐
  • integritycheckvalue — works around an invalid integrity check value during an IPMI 2.0 session establishment when using Cipher Suite ID 0. The integrity check value should be 0 length, but the remote motherboard responds with a non-empty field. Rude. You might see "k_g invalid" errors. Observed on Supermicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin Relion 700, and Intel S2600JF/Appro 512X. 🍓
  • guidformat — a number of vendors send the bytes of the GUID (like the GUID in --get-device-guid or --get-system-guid) in an alternate format that aligns incorrectly with IPMI, but correctly with other standards. This workaround flag instructs bmc-info to read the GUID and output the GUID based on this common alternate format. 🧚
  • No IPMI 1.5 Support — some motherboards that support IPMI 2.0 have been found to not support IPMI 1.5. Those hitting this issue may see "ipmi 2.0 unavailable" or "connection timeout" errors. You can work around this by using IPMI 2.0 instead of IPMI 1.5 — just specify --driver-type=LAN_2_0. Issue observed on a number of HP and Supermicro motherboards. 😤

🔍 OEM INTERPRETATION 🔍

These motherboards are confirmed to have at least some support by the --interpret-oem-data option. And while it's highly probable the OEM data interpretations would work across other motherboards from the same manufacturer, there are no guarantees. Some of the motherboards below may be rebranded by vendors/distributors. 💅

  • Dell Poweredge R610
  • Dell Poweredge R710
  • Intel SR870BN4/Tiger4

🎀 EXAMPLES 🎀

# bmc-info

Get BMC information of the local machine. Easy. Local queen behavior. 👑

# bmc-info -h ahost -u myusername -p mypassword

Get BMC information of a remote machine using IPMI over LAN. Remote slay. ✨

# bmc-info -h mycluster[0-127] -u myusername -p mypassword

Get BMC information across a cluster using IPMI over LAN. Whole-cluster main character energy. 🔥

🩺 DIAGNOSTICS 🩺

Upon successful execution, exit status is 0. On error, exit status is 1. Simple as that, bestie.

If multiple hosts are specified for communication, the exit status is 0 if and only if all targets successfully execute. Otherwise the exit status is 1. So like, one flop ruins it for everyone. 😭

💀 KNOWN ISSUES 💀

On older operating systems, if you input your username, password, and other potentially security relevant information on the command line, this information may be discovered by other users — like when they use tools such as the ps(1) command or go looking in the /proc file system. Not cute. It's generally more secure to input password information with options like the -P or -K options. Configuring security relevant information in the FreeIPMI configuration file would also be an appropriate way to hide this information. Do that. Please. 🙏

And for real, in order to prevent brute force attacks, some BMCs will temporarily "lock up" after a number of remote authentication errors. So you may need to wait awhile for this temporary "lock up" to pass before you may authenticate again. It's not you, it's them. 🌸

🐛 REPORTING BUGS 🐛

Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>. They're literally waiting for your emails. 🫶

Copyright © 2003-2015 FreeIPMI Core Team.

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version. Iconic licensing, no cap. 👑

👀 SEE ALSO 👀

http://www.gnu.org/software/freeipmi/

And that's a wrap on bmc-info, bestie! 💖 This page is from bmc-info 1.6.20, dated 2026-10-05 — go forth, query your BMCs, and remember: it's not a bug, it's a workaround. Mwah. 💅✨

📦 where this page comes from