1IPMI-RAW(8) System Commands IPMI-RAW(8)
2
6 ipmi-raw - execute IPMI commands by hex values
7
9 ipmi-raw [OPTION...] [<lun> <netfn> COMMAND-HEX-BYTES...]
10
12 Ipmi-raw is used to execute IPMI commands by hex values. Hex values may
13 be input on the command line, a file via the --file option, or via
14 stdin if neither of the previous are specified.
15 Listed below are general IPMI options, tool specific options, trouble
17 shooting information, workaround information, examples, and known is‐
18 sues. For a general introduction to FreeIPMI please see freeipmi(7).
19
21 The following options are general options for configuring IPMI communi‐
22 cation and executing general tool commands.
23 -D IPMIDRIVER, --driver-type=IPMIDRIVER
25 Specify the driver type to use instead of doing an auto selec‐
26 tion. The currently available outofband drivers are LAN and
27 LAN_2_0, which perform IPMI 1.5 and IPMI 2.0 respectively. The
28 currently available inband drivers are KCS, SSIF, OPENIPMI,
29 SUNBMC, and INTELDCMI.
30 --disable-auto-probe
32 Do not probe in-band IPMI devices for default settings.
33 --driver-address=DRIVER-ADDRESS
35 Specify the in-band driver address to be used instead of the
36 probed value. DRIVER-ADDRESS should be prefixed with "0x" for a
37 hex value and '0' for an octal value.
38 --driver-device=DEVICE
40 Specify the in-band driver device path to be used instead of the
41 probed path.
42 --register-spacing=REGISTER-SPACING
44 Specify the in-band driver register spacing instead of the
45 probed value. Argument is in bytes (i.e. 32bit register spacing
46 = 4)
47 --target-channel-number=CHANNEL-NUMBER
49 Specify the in-band driver target channel number to send IPMI
50 requests to.
51 --target-slave-address=SLAVE-ADDRESS
53 Specify the in-band driver target slave number to send IPMI re‐
54 quests to.
55 -h IPMIHOST1,IPMIHOST2,..., --hostname=IPMIHOST1[:PORT],IPMI‐
57 HOST2[:PORT],...
58 Specify the remote host(s) to communicate with. Multiple host‐
59 names may be separated by comma or may be specified in a range
60 format; see HOSTRANGED SUPPORT below. An optional port can be
61 specified with each host, which may be useful in port forwarding
62 or similar situations. If specifying an IPv6 address and port,
63 use the format [ADDRESS]:PORT.
64 -u USERNAME, --username=USERNAME
66 Specify the username to use when authenticating with the remote
67 host. If not specified, a null (i.e. anonymous) username is as‐
68 sumed. The required user privilege will depend on the raw com‐
69 mands executed.
70 -p PASSWORD, --password=PASSWORD
72 Specify the password to use when authenticationg with the remote
73 host. If not specified, a null password is assumed. Maximum
74 password length is 16 for IPMI 1.5 and 20 for IPMI 2.0.
75 -P, --password-prompt
77 Prompt for password to avoid possibility of listing it in
78 process lists.
79 -k K_G, --k-g=K_G
81 Specify the K_g BMC key to use when authenticating with the re‐
82 mote host for IPMI 2.0. If not specified, a null key is assumed.
83 To input the key in hexadecimal form, prefix the string with
84 '0x'. E.g., the key 'abc' can be entered with the either the
85 string 'abc' or the string '0x616263'
86 -K, --k-g-prompt
88 Prompt for k-g to avoid possibility of listing it in process
89 lists.
90 --session-timeout=MILLISECONDS
92 Specify the session timeout in milliseconds. Defaults to 20000
93 milliseconds (20 seconds) if not specified.
94 --retransmission-timeout=MILLISECONDS
96 Specify the packet retransmission timeout in milliseconds. De‐
97 faults to 1000 milliseconds (1 second) if not specified. The re‐
98 transmission timeout cannot be larger than the session timeout.
99 -a AUTHENTICATION-TYPE, --authentication-type=AUTHENTICATION-TYPE
101 Specify the IPMI 1.5 authentication type to use. The currently
102 available authentication types are NONE, STRAIGHT_PASSWORD_KEY,
103 MD2, and MD5. Defaults to MD5 if not specified.
104 -I CIPHER-SUITE-ID, --cipher-suite-id=CIPHER-SUITE-ID
106 Specify the IPMI 2.0 cipher suite ID to use. The Cipher Suite ID
107 identifies a set of authentication, integrity, and confidential‐
108 ity algorithms to use for IPMI 2.0 communication. The authenti‐
109 cation algorithm identifies the algorithm to use for session
110 setup, the integrity algorithm identifies the algorithm to use
111 for session packet signatures, and the confidentiality algorithm
112 identifies the algorithm to use for payload encryption. Defaults
113 to cipher suite ID 3 if not specified. The following cipher
114 suite ids are currently supported:
115 0 - Authentication Algorithm = None; Integrity Algorithm = None;
117 Confidentiality Algorithm = None
118 1 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
120 None; Confidentiality Algorithm = None
121 2 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
123 HMAC-SHA1-96; Confidentiality Algorithm = None
124 3 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
126 HMAC-SHA1-96; Confidentiality Algorithm = AES-CBC-128
127 6 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
129 None; Confidentiality Algorithm = None
130 7 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
132 HMAC-MD5-128; Confidentiality Algorithm = None
133 8 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
135 HMAC-MD5-128; Confidentiality Algorithm = AES-CBC-128
136 11 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
138 MD5-128; Confidentiality Algorithm = None
139 12 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
141 MD5-128; Confidentiality Algorithm = AES-CBC-128
142 15 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
144 = None; Confidentiality Algorithm = None
145 16 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
147 = HMAC_SHA256_128; Confidentiality Algorithm = None
148 17 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
150 = HMAC_SHA256_128; Confidentiality Algorithm = AES-CBC-128
151 -l PRIVILEGE-LEVEL, --privilege-level=PRIVILEGE-LEVEL
153 Specify the privilege level to be used. The currently available
154 privilege levels are USER, OPERATOR, and ADMIN. Defaults to AD‐
155 MIN if not specified.
156 --config-file=FILE
158 Specify an alternate configuration file.
159 -W WORKAROUNDS, --workaround-flags=WORKAROUNDS
161 Specify workarounds to vendor compliance issues. Multiple work‐
162 arounds can be specified separated by commas. A special command
163 line flag of "none", will indicate no workarounds (may be useful
164 for overriding configured defaults). See WORKAROUNDS below for a
165 list of available workarounds.
166 --debug
168 Turn on debugging.
169 -?, --help
171 Output a help list and exit.
172 --usage
174 Output a usage message and exit.
175 -V, --version
177 Output the program version and exit.
178
180 The following options are specific to ipmi-raw.
181 --file=CMD-FILE
183 Specify a file to read command requests from.
184 --no-session
186 If performing out of band communication, do not establish an
187 IPMI session and send raw packets without having established a
188 session/authenticating. This option is predominantly for testing
189 the few IPMI packets that can work outside of a session and
190 should not be used by the majority of users.
191
193 The following options manipulate hostranged output. See HOSTRANGED SUP‐
194 PORT below for additional information on hostranges.
195 -B, --buffer-output
197 Buffer hostranged output. For each node, buffer standard output
198 until the node has completed its IPMI operation. When specifying
199 this option, data may appear to output slower to the user since
200 the the entire IPMI operation must complete before any data can
201 be output. See HOSTRANGED SUPPORT below for additional informa‐
202 tion.
203 -C, --consolidate-output
205 Consolidate hostranged output. The complete standard output from
206 every node specified will be consolidated so that nodes with
207 identical output are not output twice. A header will list those
208 nodes with the consolidated output. When this option is speci‐
209 fied, no output can be seen until the IPMI operations to all
210 nodes has completed. If the user breaks out of the program
211 early, all currently consolidated output will be dumped. See
212 HOSTRANGED SUPPORT below for additional information.
213 -F NUM, --fanout=NUM
215 Specify multiple host fanout. A "sliding window" (or fanout) al‐
216 gorithm is used for parallel IPMI communication so that slower
217 nodes or timed out nodes will not impede parallel communication.
218 The maximum number of threads available at the same time is lim‐
219 ited by the fanout. The default is 64.
220 -E, --eliminate
222 Eliminate hosts determined as undetected by ipmidetect. This
223 attempts to remove the common issue of hostranged execution tim‐
224 ing out due to several nodes being removed from service in a
225 large cluster. The ipmidetectd daemon must be running on the
226 node executing the command.
227 --always-prefix
229 Always prefix output, even if only one host is specified or com‐
230 municating in-band. This option is primarily useful for script‐
231 ing purposes. Option will be ignored if specified with the -C
232 option.
233
235 Multiple hosts can be input either as an explicit comma separated lists
236 of hosts or a range of hostnames in the general form: prefix[n-m,l-
237 k,...], where n < m and l < k, etc. The later form should not be con‐
238 fused with regular expression character classes (also denoted by []).
239 For example, foo[19] does not represent foo1 or foo9, but rather repre‐
240 sents a degenerate range: foo19.
241 This range syntax is meant only as a convenience on clusters with a
243 prefixNN naming convention and specification of ranges should not be
244 considered necessary -- the list foo1,foo9 could be specified as such,
245 or by the range foo[1,9].
246 Some examples of range usage follow:
248 foo[01-05] instead of foo01,foo02,foo03,foo04,foo05
249 foo[7,9-10] instead of foo7,foo9,foo10
250 foo[0-3] instead of foo0,foo1,foo2,foo3
251 As a reminder to the reader, some shells will interpret brackets ([ and
253 ]) for pattern matching. Depending on your shell, it may be necessary
254 to enclose ranged lists within quotes.
255 When multiple hosts are specified by the user, a thread will be exe‐
257 cuted for each host in parallel up to the configured fanout (which can
258 be adjusted via the -F option). This will allow communication to large
259 numbers of nodes far more quickly than if done in serial.
260 By default, standard output from each node specified will be output
262 with the hostname prepended to each line. Although this output is read‐
263 able in many situations, it may be difficult to read in other situa‐
264 tions. For example, output from multiple nodes may be mixed together.
265 The -B and -C options can be used to change this default.
266 In-band IPMI Communication will be used when the host "localhost" is
268 specified. This allows the user to add the localhost into the hos‐
269 tranged output.
270
272 Most often, IPMI problems are due to configuration problems.
273 IPMI over LAN problems involve a misconfiguration of the remote ma‐
275 chine's BMC. Double check to make sure the following are configured
276 properly in the remote machine's BMC: IP address, MAC address, subnet
277 mask, username, user enablement, user privilege, password, LAN privi‐
278 lege, LAN enablement, and allowed authentication type(s). For IPMI 2.0
279 connections, double check to make sure the cipher suite privilege(s)
280 and K_g key are configured properly. The ipmi-config(8) tool can be
281 used to check and/or change these configuration settings.
282 Inband IPMI problems are typically caused by improperly configured
284 drivers or non-standard BMCs.
285 In addition to the troubleshooting tips below, please see WORKAROUNDS
287 below to also if there are any vendor specific bugs that have been dis‐
288 covered and worked around.
289 Listed below are many of the common issues for error messages. For ad‐
291 ditional support, please e-mail the <freeipmi-users@gnu.org> mailing
292 list.
293 "username invalid" - The username entered (or a NULL username if none
295 was entered) is not available on the remote machine. It may also be
296 possible the remote BMC's username configuration is incorrect.
297 "password invalid" - The password entered (or a NULL password if none
299 was entered) is not correct. It may also be possible the password for
300 the user is not correctly configured on the remote BMC.
301 "password verification timeout" - Password verification has timed out.
303 A "password invalid" error (described above) or a generic "session
304 timeout" (described below) occurred. During this point in the protocol
305 it cannot be differentiated which occurred.
306 "k_g invalid" - The K_g key entered (or a NULL K_g key if none was en‐
308 tered) is not correct. It may also be possible the K_g key is not cor‐
309 rectly configured on the remote BMC.
310 "privilege level insufficient" - An IPMI command requires a higher user
312 privilege than the one authenticated with. Please try to authenticate
313 with a higher privilege. This may require authenticating to a different
314 user which has a higher maximum privilege.
315 "privilege level cannot be obtained for this user" - The privilege
317 level you are attempting to authenticate with is higher than the maxi‐
318 mum allowed for this user. Please try again with a lower privilege. It
319 may also be possible the maximum privilege level allowed for a user is
320 not configured properly on the remote BMC.
321 "authentication type unavailable for attempted privilege level" - The
323 authentication type you wish to authenticate with is not available for
324 this privilege level. Please try again with an alternate authentication
325 type or alternate privilege level. It may also be possible the avail‐
326 able authentication types you can authenticate with are not correctly
327 configured on the remote BMC.
328 "cipher suite id unavailable" - The cipher suite id you wish to authen‐
330 ticate with is not available on the remote BMC. Please try again with
331 an alternate cipher suite id. It may also be possible the available ci‐
332 pher suite ids are not correctly configured on the remote BMC.
333 "ipmi 2.0 unavailable" - IPMI 2.0 was not discovered on the remote ma‐
335 chine. Please try to use IPMI 1.5 instead.
336 "connection timeout" - Initial IPMI communication failed. A number of
338 potential errors are possible, including an invalid hostname specified,
339 an IPMI IP address cannot be resolved, IPMI is not enabled on the re‐
340 mote server, the network connection is bad, etc. Please verify configu‐
341 ration and connectivity.
342 "session timeout" - The IPMI session has timed out. Please reconnect.
344 If this error occurs often, you may wish to increase the retransmission
345 timeout. Some remote BMCs are considerably slower than others.
346 "device not found" - The specified device could not be found. Please
348 check configuration or inputs and try again.
349 "driver timeout" - Communication with the driver or device has timed
351 out. Please try again.
352 "message timeout" - Communication with the driver or device has timed
354 out. Please try again.
355 "BMC busy" - The BMC is currently busy. It may be processing informa‐
357 tion or have too many simultaneous sessions to manage. Please wait and
358 try again.
359 "could not find inband device" - An inband device could not be found.
361 Please check configuration or specify specific device or driver on the
362 command line.
363 "driver timeout" - The inband driver has timed out communicating to the
365 local BMC or service processor. The BMC or service processor may be
366 busy or (worst case) possibly non-functioning.
367 "internal IPMI error" - An IPMI error has occurred that FreeIPMI does
369 not know how to handle. Please e-mail <freeipmi-users@gnu.org> to re‐
370 port the issue.
371
373 With so many different vendors implementing their own IPMI solutions,
374 different vendors may implement their IPMI protocols incorrectly. The
375 following describes a number of workarounds currently available to han‐
376 dle discovered compliance issues. When possible, workarounds have been
377 implemented so they will be transparent to the user. However, some will
378 require the user to specify a workaround be used via the -W option.
379 The hardware listed below may only indicate the hardware that a problem
381 was discovered on. Newer versions of hardware may fix the problems in‐
382 dicated below. Similar machines from vendors may or may not exhibit the
383 same problems. Different vendors may license their firmware from the
384 same IPMI firmware developer, so it may be worthwhile to try work‐
385 arounds listed below even if your motherboard is not listed.
386 If you believe your hardware has an additional compliance issue that
388 needs a workaround to be implemented, please contact the FreeIPMI main‐
389 tainers on <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
390 assumeio - This workaround flag will assume inband interfaces communi‐
392 cate with system I/O rather than being memory-mapped. This will work
393 around systems that report invalid base addresses. Those hitting this
394 issue may see "device not supported" or "could not find inband device"
395 errors. Issue observed on HP ProLiant DL145 G1.
396 spinpoll - This workaround flag will inform some inband drivers (most
398 notably the KCS driver) to spin while polling rather than putting the
399 process to sleep. This may significantly improve the wall clock running
400 time of tools because an operating system scheduler's granularity may
401 be much larger than the time it takes to perform a single IPMI message
402 transaction. However, by spinning, your system may be performing less
403 useful work by not contexting out the tool for a more useful task.
404 authcap - This workaround flag will skip early checks for username ca‐
406 pabilities, authentication capabilities, and K_g support and allow IPMI
407 authentication to succeed. It works around multiple issues in which the
408 remote system does not properly report username capabilities, authenti‐
409 cation capabilities, or K_g status. Those hitting this issue may see
410 "username invalid", "authentication type unavailable for attempted
411 privilege level", or "k_g invalid" errors. Issue observed on Asus
412 P5M2/P5MT-R/RS162-E4/RX4, Intel SR1520ML/X38ML, and Sun Fire
413 2200/4150/4450 with ELOM.
414 nochecksumcheck - This workaround flag will tell FreeIPMI to not check
416 the checksums returned from IPMI command responses. It works around
417 systems that return invalid checksums due to implementation errors, but
418 the packet is otherwise valid. Users are cautioned on the use of this
419 option, as it removes validation of packet integrity in a number of
420 circumstances. However, it is unlikely to be an issue in most situa‐
421 tions. Those hitting this issue may see "connection timeout", "session
422 timeout", or "password verification timeout" errors. On IPMI 1.5 con‐
423 nections, the "noauthcodecheck" workaround may also needed too. Issue
424 observed on Supermicro X9SCM-iiF, Supermicro X9DRi-F, and Supermicro
425 X9DRFR.
426 idzero - This workaround flag will allow empty session IDs to be ac‐
428 cepted by the client. It works around IPMI sessions that report empty
429 session IDs to the client. Those hitting this issue may see "session
430 timeout" errors. Issue observed on Tyan S2882 with M3289 BMC.
431 unexpectedauth - This workaround flag will allow unexpected non-null
433 authcodes to be checked as though they were expected. It works around
434 an issue when packets contain non-null authentication data when they
435 should be null due to disabled per-message authentication. Those hit‐
436 ting this issue may see "session timeout" errors. Issue observed on
437 Dell PowerEdge 2850,SC1425. Confirmed fixed on newer firmware.
438 forcepermsg - This workaround flag will force per-message authentica‐
440 tion to be used no matter what is advertised by the remote system. It
441 works around an issue when per-message authentication is advertised as
442 disabled on the remote system, but it is actually required for the pro‐
443 tocol. Those hitting this issue may see "session timeout" errors. Is‐
444 sue observed on IBM eServer 325.
445 endianseq - This workaround flag will flip the endian of the session
447 sequence numbers to allow the session to continue properly. It works
448 around IPMI 1.5 session sequence numbers that are the wrong endian.
449 Those hitting this issue may see "session timeout" errors. Issue ob‐
450 served on some Sun ILOM 1.0/2.0 (depends on service processor endian).
451 noauthcodecheck - This workaround flag will tell FreeIPMI to not check
453 the authentication codes returned from IPMI 1.5 command responses. It
454 works around systems that return invalid authentication codes due to
455 hashing or implementation errors. Users are cautioned on the use of
456 this option, as it removes an authentication check verifying the valid‐
457 ity of a packet. However, in most organizations, this is unlikely to be
458 a security issue. Those hitting this issue may see "connection time‐
459 out", "session timeout", or "password verification timeout" errors.
460 Issue observed on Xyratex FB-H8-SRAY, Intel Windmill, Quanta Winter‐
461 fell, and Wiwynn Windmill.
462 intel20 - This workaround flag will work around several Intel IPMI 2.0
464 authentication issues. The issues covered include padding of usernames,
465 and password truncation if the authentication algorithm is HMAC-
466 MD5-128. Those hitting this issue may see "username invalid", "password
467 invalid", or "k_g invalid" errors. Issue observed on Intel SE7520AF2
468 with Intel Server Management Module (Professional Edition).
469 supermicro20 - This workaround flag will work around several Supermicro
471 IPMI 2.0 authentication issues on motherboards w/ Peppercon IPMI
472 firmware. The issues covered include handling invalid length authenti‐
473 cation codes. Those hitting this issue may see "password invalid" er‐
474 rors. Issue observed on Supermicro H8QME with SIMSO daughter card.
475 Confirmed fixed on newerver firmware.
476 sun20 - This workaround flag will work work around several Sun IPMI 2.0
478 authentication issues. The issues covered include invalid lengthed hash
479 keys, improperly hashed keys, and invalid cipher suite records. Those
480 hitting this issue may see "password invalid" or "bmc error" errors.
481 Issue observed on Sun Fire 4100/4200/4500 with ILOM. This workaround
482 automatically includes the "opensesspriv" workaround.
483 opensesspriv - This workaround flag will slightly alter FreeIPMI's IPMI
485 2.0 connection protocol to workaround an invalid hashing algorithm used
486 by the remote system. The privilege level sent during the Open Session
487 stage of an IPMI 2.0 connection is used for hashing keys instead of the
488 privilege level sent during the RAKP1 connection stage. Those hitting
489 this issue may see "password invalid", "k_g invalid", or "bad rmcpplus
490 status code" errors. Issue observed on Sun Fire 4100/4200/4500 with
491 ILOM, Inventec 5441/Dell Xanadu II, Supermicro X8DTH, Supermicro X8DTG,
492 Intel S5500WBV/Penguin Relion 700, Intel S2600JF/Appro 512X, Quanta
493 QSSC-S4R/Appro GB812X-CN, and Dell C5220. This workaround is automati‐
494 cally triggered with the "sun20" workaround.
495 integritycheckvalue - This workaround flag will work around an invalid
497 integrity check value during an IPMI 2.0 session establishment when us‐
498 ing Cipher Suite ID 0. The integrity check value should be 0 length,
499 however the remote motherboard responds with a non-empty field. Those
500 hitting this issue may see "k_g invalid" errors. Issue observed on Su‐
501 permicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin Relion
502 700, and Intel S2600JF/Appro 512X.
503 No IPMI 1.5 Support - Some motherboards that support IPMI 2.0 have been
505 found to not support IPMI 1.5. Those hitting this issue may see "ipmi
506 2.0 unavailable" or "connection timeout" errors. This issue can be
507 worked around by using IPMI 2.0 instead of IPMI 1.5 by specifying
508 --driver-type=LAN_2_0. Issue observed on a number of HP and Supermicro
509 motherboards.
510
512 # ipmi-raw 0 6 01
513 Execute command 0x01 with LUN 0x0 and NETFN 0x06 on the local machine.
515 # ipmi-raw -h ahost -u myusername -p mypassword 0 6 01
517 Execute command 0x01 with LUN 0x0 and NETFN 0x06 on a remote machine
519 using IPMI over LAN.
520 # ipmi-raw -h mycluster[0-127] -u myusername -p mypassword 0 6 01
522 Execute command 0x01 with LUN 0x0 and NETFN 0x06 across a cluster using
524 IPMI over LAN.
525 # ipmi-raw
527 Read LUN, NETFN, command and request data from standard input.
529 # ipmi-raw -f command-file
531 Read LUN/FN, command and request data from given file instead of stan‐
533 dard input.
534 # ipmi-raw < command-file
536 Read LUN, NETFN, command and request data from file as standard input.
538
540 Upon successful execution, exit status is 0. On error, exit status is
541 1.
542 If multiple hosts are specified for communication, the exit status is 0
544 if and only if all targets successfully execute. Otherwise the exit
545 status is 1.
546
548 On older operating systems, if you input your username, password, and
549 other potentially security relevant information on the command line,
550 this information may be discovered by other users when using tools like
551 the ps(1) command or looking in the /proc file system. It is generally
552 more secure to input password information with options like the -P or
553 -K options. Configuring security relevant information in the FreeIPMI
554 configuration file would also be an appropriate way to hide this infor‐
555 mation.
556 In order to prevent brute force attacks, some BMCs will temporarily
558 "lock up" after a number of remote authentication errors. You may need
559 to wait awhile in order to this temporary "lock up" to pass before you
560 may authenticate again.
561
563 Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
564
566 Copyright © 2005-2015 FreeIPMI Core Team
567 This program is free software; you can redistribute it and/or modify it
569 under the terms of the GNU General Public License as published by the
570 Free Software Foundation; either version 3 of the License, or (at your
571 option) any later version.
572
574 freeipmi.conf(5), freeipmi(7), ipmi-config(8), ipmi-oem(8)
575 http://www.gnu.org/software/freeipmi/
577IPMI Raw version 1.6.11 2023-06-07 IPMI-RAW(8)