1IPMI-CHASSIS-CONFIG(8) System Commands IPMI-CHASSIS-CONFIG(8)
2
6 ipmi-chassis-config - configure chassis fields
7
9 ipmi-chassis-config [OPTION...]
10
12 Ipmi-chassis-config is used to get and set chassis configuration param‐
13 eters, such as boot device and power restore policy configuration. Most
14 IPMI users will not need to use this tool, although some may need it
15 for advanced configuration. For more general chassis management such as
16 power control or identification, please see ipmi-chassis(8) or
17 ipmipower(8).
18 Some chassis configuration may not be stored in non-volatile memory, so
20 users may wish to veryify that new configurations exist after system
21 reboots or to always run ipmi-chassis-config during system initializa‐
22 tion.
23 For configuration of general BMC parameters, platform event filtering
25 (PEF), or sensors, please see the bmc-config(8), ipmi-pef-config(8), or
26 ipmi-sensors-config(8) tools respectively. For some OEM specific con‐
27 figurations, please see ipmi-oem(8).
28 Listed below are general IPMI options, tool specific options, trouble
30 shooting information, workaround information, examples, and known
31 issues. For a general introduction to FreeIPMI please see freeipmi(7).
32 See GENERAL USE below for a description on how most will want to use
33 Ipmi-chassis-config.
34
36 The following options are general options for configuring IPMI communi‐
37 cation and executing general tool commands.
38 -D IPMIDRIVER, --driver-type=IPMIDRIVER
40 Specify the driver type to use instead of doing an auto selec‐
41 tion. The currently available outofband drivers are LAN and
42 LAN_2_0, which perform IPMI 1.5 and IPMI 2.0 respectively. The
43 currently available inband drivers are KCS, SSIF, OPENIPMI, and
44 SUNBMC.
45 --disable-auto-probe
47 Do not probe in-band IPMI devices for default settings.
48 --driver-address=DRIVER-ADDRESS
50 Specify the in-band driver address to be used instead of the
51 probed value. DRIVER-ADDRESS should be prefixed with "0x" for a
52 hex value and '0' for an octal value.
53 --driver-device=DEVICE
55 Specify the in-band driver device path to be used instead of the
56 probed path.
57 --register-spacing=REGISTER-SPACING
59 Specify the in-band driver register spacing instead of the
60 probed value. Argument is in bytes (i.e. 32bit register spacing
61 = 4)
62 --target-channel-number=CHANNEL-NUMBER
64 Specify the in-band driver target channel number to send IPMI
65 requests to.
66 --target-slave-address=SLAVE-ADDRESS
68 Specify the in-band driver target slave number to send IPMI
69 requests to.
70 -h IPMIHOST1,IPMIHOST2,..., --hostname=IPMIHOST1[:PORT],IPMI‐
72 HOST2[:PORT],...
73 Specify the remote host(s) to communicate with. Multiple host‐
74 names may be separated by comma or may be specified in a range
75 format; see HOSTRANGED SUPPORT below. An optional port can be
76 specified with each host, which may be useful in port forwarding
77 or similar situations.
78 -u USERNAME, --username=USERNAME
80 Specify the username to use when authenticating with the remote
81 host. If not specified, a null (i.e. anonymous) username is
82 assumed. The user must have atleast ADMIN privileges in order
83 for this tool to operate fully.
84 -p PASSWORD, --password=PASSWORD
86 Specify the password to use when authenticationg with the remote
87 host. If not specified, a null password is assumed. Maximum
88 password length is 16 for IPMI 1.5 and 20 for IPMI 2.0.
89 -P, --password-prompt
91 Prompt for password to avoid possibility of listing it in
92 process lists.
93 -k K_G, --k-g=K_G
95 Specify the K_g BMC key to use when authenticating with the
96 remote host for IPMI 2.0. If not specified, a null key is
97 assumed. To input the key in hexadecimal form, prefix the string
98 with '0x'. E.g., the key 'abc' can be entered with the either
99 the string 'abc' or the string '0x616263'
100 -K, --k-g-prompt
102 Prompt for k-g to avoid possibility of listing it in process
103 lists.
104 --session-timeout=MILLISECONDS
106 Specify the session timeout in milliseconds. Defaults to 20000
107 milliseconds (20 seconds) if not specified.
108 --retransmission-timeout=MILLISECONDS
110 Specify the packet retransmission timeout in milliseconds.
111 Defaults to 1000 milliseconds (1 second) if not specified. The
112 retransmission timeout cannot be larger than the session time‐
113 out.
114 -a AUTHENTICATION-TYPE, --authentication-type=AUTHENTICATION-TYPE
116 Specify the IPMI 1.5 authentication type to use. The currently
117 available authentication types are NONE, STRAIGHT_PASSWORD_KEY,
118 MD2, and MD5. Defaults to MD5 if not specified.
119 -I CIPHER-SUITE-ID, --cipher-suite-id=CIPHER-SUITE-ID
121 Specify the IPMI 2.0 cipher suite ID to use. The Cipher Suite ID
122 identifies a set of authentication, integrity, and confidential‐
123 ity algorithms to use for IPMI 2.0 communication. The authenti‐
124 cation algorithm identifies the algorithm to use for session
125 setup, the integrity algorithm identifies the algorithm to use
126 for session packet signatures, and the confidentiality algorithm
127 identifies the algorithm to use for payload encryption. Defaults
128 to cipher suite ID 3 if not specified. The following cipher
129 suite ids are currently supported:
130 0 - Authentication Algorithm = None; Integrity Algorithm = None;
132 Confidentiality Algorithm = None
133 1 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
135 None; Confidentiality Algorithm = None
136 2 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
138 HMAC-SHA1-96; Confidentiality Algorithm = None
139 3 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
141 HMAC-SHA1-96; Confidentiality Algorithm = AES-CBC-128
142 6 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
144 None; Confidentiality Algorithm = None
145 7 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
147 HMAC-MD5-128; Confidentiality Algorithm = None
148 8 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
150 HMAC-MD5-128; Confidentiality Algorithm = AES-CBC-128
151 11 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
153 MD5-128; Confidentiality Algorithm = None
154 12 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
156 MD5-128; Confidentiality Algorithm = AES-CBC-128
157 15 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
159 = None; Confidentiality Algorithm = None
160 16 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
162 = HMAC_SHA256_128; Confidentiality Algorithm = None
163 17 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
165 = HMAC_SHA256_128; Confidentiality Algorithm = AES-CBC-128
166 -l PRIVILEGE-LEVEL, --privilege-level=PRIVILEGE-LEVEL
168 Specify the privilege level to be used. The currently available
169 privilege levels are USER, OPERATOR, and ADMIN. Defaults to
170 ADMIN if not specified.
171 --config-file=FILE
173 Specify an alternate configuration file.
174 -W WORKAROUNDS, --workaround-flags=WORKAROUNDS
176 Specify workarounds to vendor compliance issues. Multiple work‐
177 arounds can be specified separated by commas. A special command
178 line flag of "none", will indicate no workarounds (may be useful
179 for overriding configured defaults). See WORKAROUNDS below for a
180 list of available workarounds.
181 --debug
183 Turn on debugging.
184 -?, --help
186 Output a help list and exit.
187 --usage
189 Output a usage message and exit.
190 -V, --version
192 Output the program version and exit.
193
195 The following options are used to read, write, and find differences in
196 configuration values.
197 -o, --checkout
199 Fetch configuration information.
200 -c, --commit
202 Update configuration information from a config file or key
203 pairs.
204 -d, --diff
206 Show differences between stored information and a config file or
207 key pairs.
208 -n FILENAME, --filename=FILENAME
210 Specify a config file for checkout/commit/diff.
211 -e "KEY=VALUE", --key-pair="KEY=VALUE"
213 Specify KEY=VALUE pairs for checkout/commit/diff. Specify KEY by
214 SectionName:FieldName. This option can be used multiple times.
215 On commit, any KEY=VALUE pairs will overwrite any pairs speci‐
216 fied in a file with --filename.
217 -S SECTION, --section=SECTION
219 Specify a SECTION for checkout. This option can be used multiple
220 times.
221 -L, --listsections
223 List available sections for checkout. Some sections in the list
224 may not be checked out by default and may require verbosity to
225 be increased.
226 -v, --verbose
228 Output verbose information. When used with --checkout, addi‐
229 tional uncommon sections and/or fields will be shown.
230 -vv Output very verbose information. Output additional detailed
232 information about what fields can and cannot be checked out, and
233 sometimes the reason why. Sometimes output fields that are iden‐
234 tified as unsupported on the motherboard.
235
237 The following options manipulate hostranged output. See HOSTRANGED SUP‐
238 PORT below for additional information on hostranges.
239 -B, --buffer-output
241 Buffer hostranged output. For each node, buffer standard output
242 until the node has completed its IPMI operation. When specifying
243 this option, data may appear to output slower to the user since
244 the the entire IPMI operation must complete before any data can
245 be output. See HOSTRANGED SUPPORT below for additional informa‐
246 tion.
247 -C, --consolidate-output
249 Consolidate hostranged output. The complete standard output from
250 every node specified will be consolidated so that nodes with
251 identical output are not output twice. A header will list those
252 nodes with the consolidated output. When this option is speci‐
253 fied, no output can be seen until the IPMI operations to all
254 nodes has completed. If the user breaks out of the program
255 early, all currently consolidated output will be dumped. See
256 HOSTRANGED SUPPORT below for additional information.
257 -F NUM, --fanout=NUM
259 Specify multiple host fanout. A "sliding window" (or fanout)
260 algorithm is used for parallel IPMI communication so that slower
261 nodes or timed out nodes will not impede parallel communication.
262 The maximum number of threads available at the same time is lim‐
263 ited by the fanout. The default is 64.
264 -E, --eliminate
266 Eliminate hosts determined as undetected by ipmidetect. This
267 attempts to remove the common issue of hostranged execution tim‐
268 ing out due to several nodes being removed from service in a
269 large cluster. The ipmidetectd daemon must be running on the
270 node executing the command.
271 --always-prefix
273 Always prefix output, even if only one host is specified or com‐
274 municating in-band. This option is primarily useful for script‐
275 ing purposes. Option will be ignored if specified with the -C
276 option.
277
279 Most users of will want to:
280 A) Run with --checkout to get a copy of the current configuration and
282 store it in a file. The standard output can be redirected to a file or
283 a file can be specified with the --filename option.
284 B) Edit the configuration file with an editor.
286 C) Commit the configuration back using the --commit option and specify‐
288 ing the configuration file with the --filename option. The configura‐
289 tion can be committed to multiple hosts in parallel via the hostrange
290 support.
291 Although not typically necessarily, some motherboards do not store con‐
293 figuration values in non-volatile memory. Therefore, after system
294 reboots, some configuration values may have changed. The user may wish
295 to run configuration tools on each boot to ensure configuration values
296 remain.
297
299 The Chassis_Front_Panel_Buttons:Enable_Standby_Button_For_Enter‐
300 ing_Standy, Chassis_Front_Panel_Buttons:Enable_Diagnostic_Inter‐
301 rupt_Button Chassis_Front_Panel_Buttons:Enable_Reset_Button, and Chas‐
302 sis_Front_Panel_Buttons:Enable_Power_Off_Button_For_Power_Off_Only
303 fields may not be able to be checked out on some IPMI systems, there‐
304 fore the checked out value may be blank. Some of these fields may be
305 disableable, while some are not. The Chassis_Power_Conf:Power_Con‐
306 trol_Interval field cannot be checked out. Therefore the checked out
307 value will always be blank.
308
310 Multiple hosts can be input either as an explicit comma separated lists
311 of hosts or a range of hostnames in the general form: prefix[n-m,l-
312 k,...], where n < m and l < k, etc. The later form should not be con‐
313 fused with regular expression character classes (also denoted by []).
314 For example, foo[19] does not represent foo1 or foo9, but rather repre‐
315 sents a degenerate range: foo19.
316 This range syntax is meant only as a convenience on clusters with a
318 prefixNN naming convention and specification of ranges should not be
319 considered necessary -- the list foo1,foo9 could be specified as such,
320 or by the range foo[1,9].
321 Some examples of range usage follow:
323 foo[01-05] instead of foo01,foo02,foo03,foo04,foo05
324 foo[7,9-10] instead of foo7,foo9,foo10
325 foo[0-3] instead of foo0,foo1,foo2,foo3
326 As a reminder to the reader, some shells will interpret brackets ([ and
328 ]) for pattern matching. Depending on your shell, it may be necessary
329 to enclose ranged lists within quotes.
330 When multiple hosts are specified by the user, a thread will be exe‐
332 cuted for each host in parallel up to the configured fanout (which can
333 be adjusted via the -F option). This will allow communication to large
334 numbers of nodes far more quickly than if done in serial.
335 By default, standard output from each node specified will be output
337 with the hostname prepended to each line. Although this output is read‐
338 able in many situations, it may be difficult to read in other situa‐
339 tions. For example, output from multiple nodes may be mixed together.
340 The -B and -C options can be used to change this default.
341 In-band IPMI Communication will be used when the host "localhost" is
343 specified. This allows the user to add the localhost into the hos‐
344 tranged output.
345
347 Most often, IPMI problems are due to configuration problems.
348 IPMI over LAN problems involve a misconfiguration of the remote
350 machine's BMC. Double check to make sure the following are configured
351 properly in the remote machine's BMC: IP address, MAC address, subnet
352 mask, username, user enablement, user privilege, password, LAN privi‐
353 lege, LAN enablement, and allowed authentication type(s). For IPMI 2.0
354 connections, double check to make sure the cipher suite privilege(s)
355 and K_g key are configured properly. The bmc-config(8) tool can be used
356 to check and/or change these configuration settings.
357 Inband IPMI problems are typically caused by improperly configured
359 drivers or non-standard BMCs.
360 In addition to the troubleshooting tips below, please see WORKAROUNDS
362 below to also if there are any vendor specific bugs that have been dis‐
363 covered and worked around.
364 Listed below are many of the common issues for error messages. For
366 additional support, please e-mail the <freeipmi-users@gnu.org> mailing
367 list.
368 "username invalid" - The username entered (or a NULL username if none
370 was entered) is not available on the remote machine. It may also be
371 possible the remote BMC's username configuration is incorrect.
372 "password invalid" - The password entered (or a NULL password if none
374 was entered) is not correct. It may also be possible the password for
375 the user is not correctly configured on the remote BMC.
376 "password verification timeout" - Password verification has timed out.
378 A "password invalid" error (described above) or a generic "session
379 timeout" (described below) occurred. During this point in the protocol
380 it cannot be differentiated which occurred.
381 "k_g invalid" - The K_g key entered (or a NULL K_g key if none was
383 entered) is not correct. It may also be possible the K_g key is not
384 correctly configured on the remote BMC.
385 "privilege level insufficient" - An IPMI command requires a higher user
387 privilege than the one authenticated with. Please try to authenticate
388 with a higher privilege. This may require authenticating to a different
389 user which has a higher maximum privilege.
390 "privilege level cannot be obtained for this user" - The privilege
392 level you are attempting to authenticate with is higher than the maxi‐
393 mum allowed for this user. Please try again with a lower privilege. It
394 may also be possible the maximum privilege level allowed for a user is
395 not configured properly on the remote BMC.
396 "authentication type unavailable for attempted privilege level" - The
398 authentication type you wish to authenticate with is not available for
399 this privilege level. Please try again with an alternate authentication
400 type or alternate privilege level. It may also be possible the avail‐
401 able authentication types you can authenticate with are not correctly
402 configured on the remote BMC.
403 "cipher suite id unavailable" - The cipher suite id you wish to authen‐
405 ticate with is not available on the remote BMC. Please try again with
406 an alternate cipher suite id. It may also be possible the available
407 cipher suite ids are not correctly configured on the remote BMC.
408 "ipmi 2.0 unavailable" - IPMI 2.0 was not discovered on the remote
410 machine. Please try to use IPMI 1.5 instead.
411 "connection timeout" - Initial IPMI communication failed. A number of
413 potential errors are possible, including an invalid hostname specified,
414 an IPMI IP address cannot be resolved, IPMI is not enabled on the
415 remote server, the network connection is bad, etc. Please verify con‐
416 figuration and connectivity.
417 "session timeout" - The IPMI session has timed out. Please reconnect.
419 If this error occurs often, you may wish to increase the retransmission
420 timeout. Some remote BMCs are considerably slower than others.
421 "device not found" - The specified device could not be found. Please
423 check configuration or inputs and try again.
424 "driver timeout" - Communication with the driver or device has timed
426 out. Please try again.
427 "message timeout" - Communication with the driver or device has timed
429 out. Please try again.
430 "BMC busy" - The BMC is currently busy. It may be processing informa‐
432 tion or have too many simultaneous sessions to manage. Please wait and
433 try again.
434 "could not find inband device" - An inband device could not be found.
436 Please check configuration or specify specific device or driver on the
437 command line.
438 "driver timeout" - The inband driver has timed out communicating to the
440 local BMC or service processor. The BMC or service processor may be
441 busy or (worst case) possibly non-functioning.
442
444 With so many different vendors implementing their own IPMI solutions,
445 different vendors may implement their IPMI protocols incorrectly. The
446 following describes a number of workarounds currently available to han‐
447 dle discovered compliance issues. When possible, workarounds have been
448 implemented so they will be transparent to the user. However, some will
449 require the user to specify a workaround be used via the -W option.
450 The hardware listed below may only indicate the hardware that a problem
452 was discovered on. Newer versions of hardware may fix the problems
453 indicated below. Similar machines from vendors may or may not exhibit
454 the same problems. Different vendors may license their firmware from
455 the same IPMI firmware developer, so it may be worthwhile to try work‐
456 arounds listed below even if your motherboard is not listed.
457 If you believe your hardware has an additional compliance issue that
459 needs a workaround to be implemented, please contact the FreeIPMI main‐
460 tainers on <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
461 assumeio - This workaround flag will assume inband interfaces communi‐
463 cate with system I/O rather than being memory-mapped. This will work
464 around systems that report invalid base addresses. Those hitting this
465 issue may see "device not supported" or "could not find inband device"
466 errors. Issue observed on HP ProLiant DL145 G1.
467 spinpoll - This workaround flag will inform some inband drivers (most
469 notably the KCS driver) to spin while polling rather than putting the
470 process to sleep. This may significantly improve the wall clock running
471 time of tools because an operating system scheduler's granularity may
472 be much larger than the time it takes to perform a single IPMI message
473 transaction. However, by spinning, your system may be performing less
474 useful work by not contexting out the tool for a more useful task.
475 authcap - This workaround flag will skip early checks for username
477 capabilities, authentication capabilities, and K_g support and allow
478 IPMI authentication to succeed. It works around multiple issues in
479 which the remote system does not properly report username capabilities,
480 authentication capabilities, or K_g status. Those hitting this issue
481 may see "username invalid", "authentication type unavailable for
482 attempted privilege level", or "k_g invalid" errors. Issue observed on
483 Asus P5M2/P5MT-R/RS162-E4/RX4, Intel SR1520ML/X38ML, and Sun Fire
484 2200/4150/4450 with ELOM.
485 idzero - This workaround flag will allow empty session IDs to be
487 accepted by the client. It works around IPMI sessions that report empty
488 session IDs to the client. Those hitting this issue may see "session
489 timeout" errors. Issue observed on Tyan S2882 with M3289 BMC.
490 unexpectedauth - This workaround flag will allow unexpected non-null
492 authcodes to be checked as though they were expected. It works around
493 an issue when packets contain non-null authentication data when they
494 should be null due to disabled per-message authentication. Those hit‐
495 ting this issue may see "session timeout" errors. Issue observed on
496 Dell PowerEdge 2850,SC1425. Confirmed fixed on newer firmware.
497 forcepermsg - This workaround flag will force per-message authentica‐
499 tion to be used no matter what is advertised by the remote system. It
500 works around an issue when per-message authentication is advertised as
501 disabled on the remote system, but it is actually required for the pro‐
502 tocol. Those hitting this issue may see "session timeout" errors.
503 Issue observed on IBM eServer 325.
504 endianseq - This workaround flag will flip the endian of the session
506 sequence numbers to allow the session to continue properly. It works
507 around IPMI 1.5 session sequence numbers that are the wrong endian.
508 Those hitting this issue may see "session timeout" errors. Issue
509 observed on some Sun ILOM 1.0/2.0 (depends on service processor
510 endian).
511 noauthcodecheck - This workaround flag will tell FreeIPMI to not check
513 the authentication codes returned from IPMI 1.5 command responses. It
514 works around systems to return invalid authentication codes due to
515 hashing or implementation errors. Users are cautioned on the use of
516 this option, as it removes an authentication check verifying the valid‐
517 ity of a packet. However, in most organizations, this is unlikely to be
518 a security issue. Those hitting this issue may see "connection time‐
519 out", "session timeout", or "password verification timeout" errors.
520 Issue observed on Xyratex FB-H8-SRAY.
521 intel20 - This workaround flag will work around several Intel IPMI 2.0
523 authentication issues. The issues covered include padding of usernames,
524 and password truncation if the authentication algorithm is HMAC-
525 MD5-128. Those hitting this issue may see "username invalid", "password
526 invalid", or "k_g invalid" errors. Issue observed on Intel SE7520AF2
527 with Intel Server Management Module (Professional Edition).
528 supermicro20 - This workaround flag will work around several Supermicro
530 IPMI 2.0 authentication issues on motherboards w/ Peppercon IPMI
531 firmware. The issues covered include handling invalid length authenti‐
532 cation codes. Those hitting this issue may see "password invalid"
533 errors. Issue observed on Supermicro H8QME with SIMSO daughter card.
534 Confirmed fixed on newerver firmware.
535 sun20 - This workaround flag will work work around several Sun IPMI 2.0
537 authentication issues. The issues covered include invalid lengthed hash
538 keys, improperly hashed keys, and invalid cipher suite records. Those
539 hitting this issue may see "password invalid" or "bmc error" errors.
540 Issue observed on Sun Fire 4100/4200/4500 with ILOM. This workaround
541 automatically includes the "opensesspriv" workaround.
542 opensesspriv - This workaround flag will slightly alter FreeIPMI's IPMI
544 2.0 connection protocol to workaround an invalid hashing algorithm used
545 by the remote system. The privilege level sent during the Open Session
546 stage of an IPMI 2.0 connection is used for hashing keys instead of the
547 privilege level sent during the RAKP1 connection stage. Those hitting
548 this issue may see "password invalid", "k_g invalid", or "bad rmcpplus
549 status code" errors. Issue observed on Sun Fire 4100/4200/4500 with
550 ILOM, Inventec 5441/Dell Xanadu II, Supermicro X8DTH, Supermicro X8DTG,
551 Intel S5500WBV/Penguin Relion 700, Intel S2600JF/Appro 512X, and Quanta
552 QSSC-S4R//Appro GB812X-CN. This workaround is automatically triggered
553 with the "sun20" workaround.
554 integritycheckvalue - This workaround flag will work around an invalid
556 integrity check value during an IPMI 2.0 session establishment when
557 using Cipher Suite ID 0. The integrity check value should be 0 length,
558 however the remote motherboard responds with a non-empty field. Those
559 hitting this issue may see "k_g invalid" errors. Issue observed on
560 Supermicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin Relion
561 700, and Intel S2600JF/Appro 512X.
562 No IPMI 1.5 Support - Some motherboards that support IPMI 2.0 have been
564 found to not support IPMI 1.5. Those hitting this issue may see "ipmi
565 2.0 unavailable" or "connection timeout" errors. This issue can be
566 worked around by using IPMI 2.0 instead of IPMI 1.5 by specifying
567 --driver-address=LAN_2_0. Issue observed on HP Proliant DL 145.
568 slowcommit - This workaround will slow down commits to the BMC by
570 sleeping one second between the commit of sections. It works around
571 motherboards that have BMCs that can be overwhelmed by commits. Those
572 hitting this issue may see commit errors or commits not being written
573 to the BMC. Issue observed on Supermicro H8QME.
574 veryslowcommit - This workaround will slow down commits to the BMC by
576 sleeping one second between the commit of every key. It works around
577 motherboards that have BMCs that can be overwhelmed by commits. Those
578 hitting this issue may see commit errors or commits not being written
579 to the BMC. Issue observed on Quanta S99Q/Dell FS12-TY.
580
582 # ipmi-chassis-config --checkout
583 Output all configuration information to the console.
585 # ipmi-chassis-config --checkout --filename=chassis-data1.conf
587 Store all BMC configuration information in chassis-data1.conf.
589 # ipmi-chassis-config --diff --filename=chassis-data2.conf
591 Show all difference between the current configuration and the chassis-
593 data2.conf file.
594 # ipmi-chassis-config --commit --filename=chassis-data1.conf
596 Commit all configuration values from the chassis-data1.conf file.
598
600 Upon successful execution, exit status is 0. On error, exit status is
601 1.
602 If multiple hosts are specified for communication, the exit status is 0
604 if and only if all targets successfully execute. Otherwise the exit
605 status is 1.
606
608 On older operating systems, if you input your username, password, and
609 other potentially security relevant information on the command line,
610 this information may be discovered by other users when using tools like
611 the ps(1) command or looking in the /proc file system. It is generally
612 more secure to input password information with options like the -P or
613 -K options. Configuring security relevant information in the FreeIPMI
614 configuration file would also be an appropriate way to hide this infor‐
615 mation.
616 In order to prevent brute force attacks, some BMCs will temporarily
618 "lock up" after a number of remote authentication errors. You may need
619 to wait awhile in order to this temporary "lock up" to pass before you
620 may authenticate again.
621
623 Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
624
626 Copyright © 2008-2012 FreeIPMI Core Team.
627 This program is free software; you can redistribute it and/or modify it
629 under the terms of the GNU General Public License as published by the
630 Free Software Foundation; either version 3 of the License, or (at your
631 option) any later version.
632
634 freeipmi(7), bmc-config(8), ipmi-pef-config(8), ipmi-sensors-config(8),
635 ipmipower(8)
636 http://www.gnu.org/software/freeipmi/
638ipmi-chassis-config 1.2.1 2017-03-22 IPMI-CHASSIS-CONFIG(8)