1BMC-CONFIG(8) System Commands BMC-CONFIG(8)
2
6 bmc-config - configure BMC values
7
9 bmc-config [OPTION...]
10
12 Bmc-config is used to get and set BMC configuration parameters, such as
13 usernames, passwords, networking information, security, Serial-over-LAN
14 (SOL), and other core IPMI fields. This configuration is required
15 before most IPMI tools can be used to access a machine remotely.
16 The majority of configuration operations require ADMIN privilege when
18 using bmc-config out-of-band. Although connecting via a user with ADMIN
19 privileges is not required for out-of-band use, the vast majority of
20 configuration options will not be retrieved or set.
21 For configuration of chassis, platform event filtering (PEF), or sen‐
23 sors, please see the ipmi-chassis-config(8), ipmi-pef-config(8), or
24 ipmi-sensors-config(8) tools respectively. For some OEM specific con‐
25 figurations, please see ipmi-oem(8).
26 Listed below are general IPMI options, tool specific options, trouble
28 shooting information, workaround information, examples, and known
29 issues. For a general introduction to FreeIPMI please see freeipmi(7).
30 See GENERAL USE below for a description on how most will want to use
31 Bmc-config.
32
34 The following options are general options for configuring IPMI communi‐
35 cation and executing general tool commands.
36 -D, --driver-type=IPMIDRIVER
38 Specify the driver type to use instead of doing an auto selec‐
39 tion. The currently available outofband drivers are LAN and
40 LAN_2_0, which perform IPMI 1.5 and IPMI 2.0 respectively. The
41 currently available inband drivers are KCS, SSIF, OPENIPMI, and
42 SUNBMC.
43 --disable-auto-probe
45 Do not probe in-band IPMI devices for default settings.
46 --driver-address=DRIVER-ADDRESS
48 Specify the in-band driver address to be used instead of the
49 probed value. DRIVER-ADDRESS should be prefixed with "0x" for a
50 hex value and '0' for an octal value.
51 --driver-device=DEVICE
53 Specify the in-band driver device path to be used instead of the
54 probed path.
55 --register-spacing=REGISTER-SPACING
57 Specify the in-band driver register spacing instead of the
58 probed value.
59 -h, --hostname=IPMIHOST1,IPMIHOST2,...
61 Specify the remote host(s) to communicate with. Multiple host‐
62 names may be separated by comma or may be specified in a range
63 format; see HOSTRANGED SUPPORT below.
64 -u, --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
68 assumed. The user must have atleast ADMIN privileges in order
69 for this tool to operate fully.
70 -p, --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
81 Specify the K_g BMC key to use when authenticating with the
82 remote host for IPMI 2.0. If not specified, a null key is
83 assumed. To input the key in hexadecimal form, prefix the string
84 with '0x'. E.g., the key 'abc' can be entered with the either
85 the 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.
97 Defaults to 1000 milliseconds (1 second) if not specified. The
98 retransmission timeout cannot be larger than the session time‐
99 out.
100 -a, --authentication-type=AUTHENTICATION-TYPE
102 Specify the IPMI 1.5 authentication type to use. The currently
103 available authentication types are NONE, STRAIGHT_PASSWORD_KEY,
104 MD2, and MD5. Defaults to MD5 if not specified.
105 -I, --cipher-suite-id=CIPHER-SUITE-ID
107 Specify the IPMI 2.0 cipher suite ID to use. The Cipher Suite ID
108 identifies a set of authentication, integrity, and confidential‐
109 ity algorithms to use for IPMI 2.0 communication. The authenti‐
110 cation algorithm identifies the algorithm to use for session
111 setup, the integrity algorithm identifies the algorithm to use
112 for session packet signatures, and the confidentiality algorithm
113 identifies the algorithm to use for payload encryption. Defaults
114 to cipher suite ID 3 if not specified. The following cipher
115 suite ids are currently supported:
116 0 - Authentication Algorithm = None; Integrity Algorithm = None;
118 Confidentiality Algorithm = None
119 1 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
121 None; Confidentiality Algorithm = None
122 2 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
124 HMAC-SHA1-96; Confidentiality Algorithm = None
125 3 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
127 HMAC-SHA1-96; Confidentiality Algorithm = AES-CBC-128
128 6 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
130 None; Confidentiality Algorithm = None
131 7 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
133 HMAC-MD5-128; Confidentiality Algorithm = None
134 8 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
136 HMAC-MD5-128; Confidentiality Algorithm = AES-CBC-128
137 11 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
139 MD5-128; Confidentiality Algorithm = None
140 12 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
142 MD5-128; Confidentiality Algorithm = AES-CBC-128
143 -l, --privilege-level=PRIVILEGE-LEVEL
145 Specify the privilege level to be used. The currently available
146 privilege levels are USER, OPERATOR, and ADMIN. Defaults to
147 ADMIN if not specified.
148 --config-file=FILE
150 Specify an alternate configuration file.
151 -W, --workaround-flags=WORKAROUNDS
153 Specify workarounds to vendor compliance issues. Multiple work‐
154 arounds can be specified separated by commas. See WORKAROUNDS
155 below for a list of available workarounds.
156 --debug
158 Turn on debugging.
159 -?, --help
161 Output a help list and exit.
162 --usage
164 Output a usage message and exit.
165 -V, --version
167 Output the program version and exit.
168
170 The following options are used to read, write, and find differences in
171 configuration values.
172 -o, --checkout
174 Fetch configuration information.
175 -c, --commit
177 Update configuration information from a config file or key
178 pairs.
179 -d, --diff
181 Show differences between stored information and a config file or
182 key pairs.
183 -n FILENAME, --filename=FILENAME
185 Specify a config file for checkout/commit/diff.
186 -e "KEY=VALUE", --key-pair="KEY=VALUE"
188 Specify KEY=VALUE pairs for checkout/commit/diff. Specify KEY by
189 SectionName:FieldName. This option can be used multiple times.
190 On commit, any KEY=VALUE pairs will overwrite any pairs speci‐
191 fied in a file with --filename.
192 -S "SECTION", --section="SECTION"
194 Specify a SECTION for checkout. This option can be used multiple
195 times.
196 -L, --listsections
198 List available sections for checkout.
199 -v, --verbose
201 Output additional detailed information. In general will output
202 more detailed information about what fields can and cannot be
203 checked out, committed, etc. When used with --checkout, addi‐
204 tional uncommon, unconfigurable, and/or unused fields may be
205 output.
206
208 The following options manipulate hostranged output. See HOSTRANGED SUP‐
209 PORT below for additional information on hostranges.
210 -B, --buffer-output
212 Buffer hostranged output. For each node, buffer standard output
213 until the node has completed its IPMI operation. When specifying
214 this option, data may appear to output slower to the user since
215 the the entire IPMI operation must complete before any data can
216 be output. See HOSTRANGED SUPPORT below for additional informa‐
217 tion.
218 -C, --consolidate-output
220 Consolidate hostranged output. The complete standard output from
221 every node specified will be consolidated so that nodes with
222 identical output are not output twice. A header will list those
223 nodes with the consolidated output. When this option is speci‐
224 fied, no output can be seen until the IPMI operations to all
225 nodes has completed. If the user breaks out of the program
226 early, all currently consolidated output will be dumped. See
227 HOSTRANGED SUPPORT below for additional information.
228 -F, --fanout
230 Specify multiple host fanout. A "sliding window" (or fanout)
231 algorithm is used for parallel IPMI communication so that slower
232 nodes or timed out nodes will not impede parallel communication.
233 The maximum number of threads available at the same time is lim‐
234 ited by the fanout. The default is 64.
235 -E, --eliminate
237 Eliminate hosts determined as undetected by ipmidetect. This
238 attempts to remove the common issue of hostranged execution tim‐
239 ing out due to several nodes being removed from service in a
240 large cluster. The ipmidetectd daemon must be running on the
241 node executing the command.
242 --always-prefix
244 Always prefix output, even if only one host is specified or com‐
245 municating in-band. This option is primarily useful for script‐
246 ing purposes. Option will be ignored if specified with the -C
247 option.
248
250 Most users of will want to:
251 A) Run with --checkout to get a copy of the current configuration and
253 store it in a file. The standard output can be redirected to a file or
254 a file can be specified with the --filename option.
255 B) Edit the configuration file with an editor.
257 C) Commit the configuration back using the --commit option and specify‐
259 ing the configuration file with the --filename option. The configura‐
260 tion can be committed to multiple hosts in parallel via the hostrange
261 support.
262 Although not typically necessarily, some motherboards do not store con‐
264 figuration values in non-volatile memory. Therefore, after system
265 reboots, some configuration values may have changed. The user may wish
266 to run configuration tools on each boot to ensure configuration values
267 remain.
268 Comments throughout the checked out file will give instructions on how
270 to configure the fields. The bmc-config.conf(5) also provides addi‐
271 tional information on the meaning of different fields.
272 For users with large clusters or sets of nodes, you may wish to use the
274 same configuration file for all nodes. The one problem with this is
275 that the IP address and MAC address will be different on each node in
276 your cluster and thus can't be configured through the same config file.
277 The IP address and MAC address in your config file may be overwritten
278 on the command line using --key-pair option. The following example
279 could be used in a script to configure each node in a cluster with the
280 same BMC config file. The script only needs to determine the correct IP
281 address and MAC address to use.
282 # bmc-config --commit -k Lan_Conf:Ip_Address=$MY_IP -k
284 Lan_Conf:Mac_Address=$MY_MAC -n my_bmc.conf
285
287 The UserN:Password fields (where N is a number) cannot be checked out
288 on some systems, therefore the checked out value will always be blank.
289 The UserN:Enable_User field (where N is a number) cannot be checked out
290 on older IPMI systems, therefore the checked out value will sometime be
291 blank. The UserN:Lan_Session_Limit and UserN:Serial_Session_Limit
292 fields (where N is a number) cannot be checked out on some systems,
293 therefore the checked out value will always be blank. If not specified
294 in later commits of configurations, the field may be reset to 0 due to
295 a requirement that other fields (configured along with the session
296 limit) will require an input value for the session limit. Under most
297 conditions, it is not necessary to set this field and most users may
298 choose to ignore it. This field is considered optional by IPMI stan‐
299 dards, and may result in errors when attempting to configure it to a
300 non-zero value. If errors to occur, setting the value back to 0 should
301 resolve problems. The fields Lan_Conf:IP_Address and
302 Lan_Conf:MAC_Address cannot be committed in parallel via hostrange sup‐
303 port. Each machine must be configured with a unique IP Address and MAC
304 Address tuple, therefore we disallow this configuration in bmc-config.
305 On some motherboards, Lan_Conf:MAC_Address may be read only and the MAC
306 address is automatically configured. On some motherboards,
307 Lan_Conf:MAC_Address may be read only and the MAC address is configured
308 via an OEM command. See ipmi-oem(8) to see if OEM configuration for
309 your motherboard is supported. On some motherboards, a number of user
310 configuration fields cannot be read or configured until after a non-
311 null username or non-null password is configured. In some of these
312 cases, an appropriate output in the config file will indicate this sit‐
313 uation. However, not all motherboard corner cases may be detected.
314 Users may wish to play around with the ordering of fields to work
315 around these problems. On some motherboards, OEM Authentication in
316 Lan_Conf_Auth cannot be enabled. However, the default motherboard set‐
317 tings have these fields enabled. Users are advised to disable all OEM
318 Authentication in this section.
319
321 Multiple hosts can be input either as an explicit comma separated lists
322 of hosts or a range of hostnames in the general form: prefix[n-m,l-
323 k,...], where n < m and l < k, etc. The later form should not be con‐
324 fused with regular expression character classes (also denoted by []).
325 For example, foo[19] does not represent foo1 or foo9, but rather repre‐
326 sents a degenerate range: foo19.
327 This range syntax is meant only as a convenience on clusters with a
329 prefixNN naming convention and specification of ranges should not be
330 considered necessary -- the list foo1,foo9 could be specified as such,
331 or by the range foo[1,9].
332 Some examples of range usage follow:
334 foo[01-05] instead of foo01,foo02,foo03,foo04,foo05
335 foo[7,9-10] instead of foo7,foo9,foo10
336 foo[0-3] instead of foo0,foo1,foo2,foo3
337 As a reminder to the reader, some shells will interpret brackets ([ and
339 ]) for pattern matching. Depending on your shell, it may be necessary
340 to enclose ranged lists within quotes.
341 When multiple hosts are specified by the user, a thread will be exe‐
343 cuted for each host in parallel up to the configured fanout (which can
344 be adjusted via the -F option). This will allow communication to large
345 numbers of nodes far more quickly than if done in serial.
346 By default, standard output from each node specified will be output
348 with the hostname prepended to each line. Although this output is read‐
349 able in many situations, it may be difficult to read in other situa‐
350 tions. For example, output from multiple nodes may be mixed together.
351 The -B and -C options can be used to change this default.
352 In-band IPMI Communication will be used when the host "localhost" is
354 specified. This allows the user to add the localhost into the hos‐
355 tranged output.
356
358 Most often, IPMI problems are due to configuration problems. Inband
359 IPMI problems are typically caused by improperly configured drivers or
360 non-standard BMCs. IPMI over LAN problems involve a misconfiguration of
361 the remote machine's BMC. Double check to make sure the following are
362 configured properly in the remote machine's BMC: IP address, MAC
363 address, subnet mask, username, user enablement, user privilege, pass‐
364 word, LAN privilege, LAN enablement, and allowed authentication
365 type(s). For IPMI 2.0 connections, double check to make sure the cipher
366 suite privilege(s) and K_g key are configured properly. The bmc-con‐
367 fig(8) tool can be used to check and/or change these configuration set‐
368 tings.
369 The following are common issues for given error messages:
371 "username invalid" - The username entered (or a NULL username if none
373 was entered) is not available on the remote machine. It may also be
374 possible the remote BMC's username configuration is incorrect.
375 "password invalid" - The password entered (or a NULL password if none
377 was entered) is not correct. It may also be possible the password for
378 the user is not correctly configured on the remote BMC.
379 "password verification timeout" - Password verification has timed out.
381 A "password invalid" error (described above) or a generic "session
382 timeout" (described below) occurred. During this point in the protocol
383 it cannot be differentiated which occurred.
384 "k_g invalid" - The K_g key entered (or a NULL K_g key if none was
386 entered) is not correct. It may also be possible the K_g key is not
387 correctly configured on the remote BMC.
388 "privilege level insufficient" - An IPMI command requires a higher user
390 privilege than the one authenticated with. Please try to authenticate
391 with a higher privilege. This may require authenticating to a different
392 user which has a higher maximum privilege.
393 "privilege level cannot be obtained for this user" - The privilege
395 level you are attempting to authenticate with is higher than the maxi‐
396 mum allowed for this user. Please try again with a lower privilege. It
397 may also be possible the maximum privilege level allowed for a user is
398 not configured properly on the remote BMC.
399 "authentication type unavailable for attempted privilege level" - The
401 authentication type you wish to authenticate with is not available for
402 this privilege level. Please try again with an alternate authentication
403 type or alternate privilege level. It may also be possible the avail‐
404 able authentication types you can authenticate with are not correctly
405 configured on the remote BMC.
406 "cipher suite id unavailable" - The cipher suite id you wish to authen‐
408 ticate with is not available on the remote BMC. Please try again with
409 an alternate cipher suite id. It may also be possible the available
410 cipher suite ids are not correctly configured on the remote BMC.
411 "ipmi 2.0 unavailable" - IPMI 2.0 was not discovered on the remote
413 machine. Please try to use IPMI 1.5 instead.
414 "connection timeout" - Initial IPMI communication failed. A number of
416 potential errors are possible, including an invalid hostname specified,
417 an IPMI IP address cannot be resolved, IPMI is not enabled on the
418 remote server, the network connection is bad, etc. Please verify con‐
419 figuration and connectivity.
420 "session timeout" - The IPMI session has timed out. Please reconnect.
422 If this error occurs often, you may wish to increase the retransmission
423 timeout. Some remote BMCs are considerably slower than others.
424 "device not found" - The specified device could not be found. Please
426 check configuration or inputs and try again.
427 "driver timeout" - Communication with the driver or device has timed
429 out. Please try again.
430 "message timeout" - Communication with the driver or device has timed
432 out. Please try again.
433 "BMC busy" - The BMC is currently busy. It may be processing informa‐
435 tion or have too many simultaneous sessions to manage. Please wait and
436 try again.
437 "could not find inband device" - An inband device could not be found.
439 Please check configuration or specify specific device or driver on the
440 command line.
441 Please see WORKAROUNDS below to also if there are any vendor specific
443 bugs that have been discovered and worked around.
444
446 With so many different vendors implementing their own IPMI solutions,
447 different vendors may implement their IPMI protocols incorrectly. The
448 following lists the workarounds currently available to handle discov‐
449 ered compliance issues.
450 When possible, workarounds have been implemented so they will be trans‐
452 parent to the user. However, some will require the user to specify a
453 workaround be used via the -W option.
454 The hardware listed below may only indicate the hardware that a problem
456 was discovered on. Newer versions of hardware may fix the problems
457 indicated below. Similar machines from vendors may or may not exhibit
458 the same problems. Different vendors may license their firmware from
459 the same IPMI firmware developer, so it may be worthwhile to try work‐
460 arounds listed below even if your motherboard is not listed.
461 "idzero" - This workaround option will allow empty session IDs to be
463 accepted by the client. It works around IPMI sessions that report empty
464 session IDs to the client. Those hitting this issue may see "session
465 timeout" errors. Issue observed on Tyan S2882 with M3289 BMC.
466 "unexpectedauth" - This workaround option will allow unexpected non-
468 null authcodes to be checked as though they were expected. It works
469 around an issue when packets contain non-null authentication data when
470 they should be null due to disabled per-message authentication. Those
471 hitting this issue may see "session timeout" errors. Issue observed on
472 Dell PowerEdge 2850,SC1425. Confirmed fixed on newer firmware.
473 "forcepermsg" - This workaround option will force per-message authenti‐
475 cation to be used no matter what is advertised by the remote system. It
476 works around an issue when per-message authentication is advertised as
477 disabled on the remote system, but it is actually required for the pro‐
478 tocol. Those hitting this issue may see "session timeout" errors.
479 Issue observed on IBM eServer 325.
480 "endianseq" - This workaround option will flip the endian of the ses‐
482 sion sequence numbers to allow the session to continue properly. It
483 works around IPMI 1.5 session sequence numbers that are the wrong
484 endian. Those hitting this issue may see "session timeout" errors.
485 Issue observed on some Sun ILOM 1.0/2.0 (depends on service processor
486 endian).
487 "authcap" - This workaround option will skip early checks for username
489 capabilities, authentication capabilities, and K_g support and allow
490 IPMI authentication to succeed. It works around multiple issues in
491 which the remote system does not properly report username capabilities,
492 authentication capabilities, or K_g status. Those hitting this issue
493 may see "username invalid", "authentication type unavailable for
494 attempted privilege level", or "k_g invalid" errors. Issue observed on
495 Asus P5M2/P5MT-R/RS162-E4/RX4, Intel SR1520ML/X38ML, and Sun Fire
496 2200/4150/4450 with ELOM.
497 "intel20" - This workaround option will work around several Intel IPMI
499 2.0 authentication issues. The issues covered include padding of user‐
500 names, automatic acceptance of a RAKP 4 response integrity check when
501 using the integrity algorithm MD5-128, and password truncation if the
502 authentication algorithm is HMAC-MD5-128. Those hitting this issue may
503 see "username invalid", "password invalid", or "k_g invalid" errors.
504 Issue observed on Intel SE7520AF2 with Intel Server Management Module
505 (Professional Edition).
506 "supermicro20" - This workaround option will work around several Super‐
508 micro IPMI 2.0 authentication issues on motherboards w/ Peppercon IPMI
509 firmware. The issues covered include handling invalid length authenti‐
510 cation codes. Those hitting this issue may see "password invalid"
511 errors. Issue observed on Supermicro H8QME with SIMSO daughter card.
512 Confirmed fixed on newerver firmware.
513 "sun20" - This workaround option will work work around several Sun IPMI
515 2.0 authentication issues. The issues covered include invalid lengthed
516 hash keys, improperly hashed keys, and invalid cipher suite records.
517 Those hitting this issue may see "password invalid" or "bmc error"
518 errors. Issue observed on Sun Fire 4100/4200/4500 with ILOM. This
519 workaround automatically includes the "opensesspriv" workaround.
520 "opensesspriv" - This workaround option will slightly alter FreeIPMI's
522 IPMI 2.0 connection protocol to workaround an invalid hashing algorithm
523 used by the remote system. The privilege level sent during the Open
524 Session stage of an IPMI 2.0 connection is sometimes invalid and used
525 for hashing keys instead of the privilege level sent during the RAKP1
526 connection stage. Those hitting this issue may see "password invalid",
527 "k_g invalid", "bad rmcpplus status code", or "privilege level cannot
528 be obtained for this user " errors. Issue observed on Sun Fire
529 4100/4200/4500 with ILOM, Inventec 5441/Dell Xanadu II, Supermicro
530 X8DTH, Supermicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin
531 Relion 700. This workaround is automatically triggered with the "sun20"
532 workaround.
533 "integritycheckvalue" - This workaround option will work around an
535 invalid integrity check value during an IPMI 2.0 session establishment
536 when using Cipher Suite ID 0. The integrity check value should be 0
537 length, however the remote motherboard responds with a non-empty field.
538 Those hitting this issue may see "k_g invalid" errors. Issue observed
539 on Supermicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin
540 Relion 700.
541 "slowcommit" - This workaround will slow down commits to the BMC by
543 sleeping a small amount between the commit of sections. It works around
544 motherboards that have BMCs that can be overwhelmed by commits. Those
545 hitting this issue may see commit errors or commits not being written
546 to the BMC. Issue observed on Supermicro H8QME.
547
549 # bmc-config --checkout
550 Output all configuration information to the console.
552 # bmc-config --checkout --filename=bmc-data1.conf
554 Store all configuration information in bmc-data1.conf.
556 # bmc-config --diff --filename=bmc-data2.conf
558 Show all difference between the current configuration and the bmc-
560 data2.conf file.
561 # bmc-config --diff --key-pair="lan_conf_misc:gratuitous_arp_inter‐
563 val=8"
564 Show difference with the current configuration and the
566 'lan_conf_misc:gratuitous_arp_interval' of value '8'.
567 # bmc-config --commit --filename=bmc-data1.conf
569 Commit all configuration values from the bmc-data1.conf file.
571 # bmc-config --commit --key-pair="lan_conf_misc:gratuitous_arp_inter‐
573 val=4"
574 Commit key 'lan_conf_misc:gratuitous_arp_interval' of value '4'.
576 # bmc-config --commit --filename=bmc-data-updt.conf --key-
578 pair="lan_conf_misc:gratuitous_arp_interval=4"
579 Commit all configuration values from bmc-data-updt.conf and key
581 'lan_conf_misc:gratuitous_arp_interval' of value '4'.
582
584 On older operating systems, if you input your username, password, and
585 other potentially security relevant information on the command line,
586 this information may be discovered by other users when using tools like
587 the ps(1) command or looking in the /proc file system. It is generally
588 more secure to input password information with options like the -P or
589 -K options. Configuring security relevant information in the FreeIPMI
590 configuration file would also be an appropriate way to hide this infor‐
591 mation.
592 In order to prevent brute force attacks, some BMCs will temporarily
594 "lock up" after a number of remote authentication errors. You may need
595 to wait awhile in order to this temporary "lock up" to pass before you
596 may authenticate again.
597
599 Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
600
602 Copyright © 2003-2010 FreeIPMI Core Team.
603 This program is free software; you can redistribute it and/or modify it
605 under the terms of the GNU General Public License as published by the
606 Free Software Foundation; either version 2 of the License, or (at your
607 option) any later version.
608
610 bmc-config.conf(5), freeipmi(7), ipmi-chassis-config(8), ipmi-pef-con‐
611 fig(8), ipmi-sensors-config(8)
612 http://www.gnu.org/software/freeipmi/
614bmc-config 0.8.8 2010-07-21 BMC-CONFIG(8)