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