1IPMI-SEL(8) System Commands IPMI-SEL(8)
2
6 ipmi-sel - display SEL entries
7
9 ipmi-sel [OPTION...]
10
12 Ipmi-sel is used to view and manage System Event Log (SEL) entries. SEL
13 records store system event information and may be useful for debugging
14 problems. Ipmi-sel does not inform the user if an event is particu‐
15 larly good or bad, just that the event occurred. Users may wish to use
16 the --output-event-state option to output the analyzed state.
17 Listed below are general IPMI options, tool specific options, trouble
19 shooting information, workaround information, examples, and known is‐
20 sues. For a general introduction to FreeIPMI please see freeipmi(7).
21 To perform some advanced SEL management, please see bmc-device(8).
22
24 The following options are general options for configuring IPMI communi‐
25 cation and executing general tool commands.
26 -D IPMIDRIVER, --driver-type=IPMIDRIVER
28 Specify the driver type to use instead of doing an auto selec‐
29 tion. The currently available outofband drivers are LAN and
30 LAN_2_0, which perform IPMI 1.5 and IPMI 2.0 respectively. The
31 currently available inband drivers are KCS, SSIF, OPENIPMI,
32 SUNBMC, and INTELDCMI.
33 --disable-auto-probe
35 Do not probe in-band IPMI devices for default settings.
36 --driver-address=DRIVER-ADDRESS
38 Specify the in-band driver address to be used instead of the
39 probed value. DRIVER-ADDRESS should be prefixed with "0x" for a
40 hex value and '0' for an octal value.
41 --driver-device=DEVICE
43 Specify the in-band driver device path to be used instead of the
44 probed path.
45 --register-spacing=REGISTER-SPACING
47 Specify the in-band driver register spacing instead of the
48 probed value. Argument is in bytes (i.e. 32bit register spacing
49 = 4)
50 --target-channel-number=CHANNEL-NUMBER
52 Specify the in-band driver target channel number to send IPMI
53 requests to.
54 --target-slave-address=SLAVE-ADDRESS
56 Specify the in-band driver target slave number to send IPMI re‐
57 quests to.
58 -h IPMIHOST1,IPMIHOST2,..., --hostname=IPMIHOST1[:PORT],IPMI‐
60 HOST2[:PORT],...
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. An optional port can be
64 specified with each host, which may be useful in port forwarding
65 or similar situations. If specifying an IPv6 address and port,
66 use the format [ADDRESS]:PORT.
67 -u USERNAME, --username=USERNAME
69 Specify the username to use when authenticating with the remote
70 host. If not specified, a null (i.e. anonymous) username is as‐
71 sumed. The user must have atleast USER privileges in order for
72 this tool to operate fully.
73 -p PASSWORD, --password=PASSWORD
75 Specify the password to use when authenticationg with the remote
76 host. If not specified, a null password is assumed. Maximum
77 password length is 16 for IPMI 1.5 and 20 for IPMI 2.0.
78 -P, --password-prompt
80 Prompt for password to avoid possibility of listing it in
81 process lists.
82 -k K_G, --k-g=K_G
84 Specify the K_g BMC key to use when authenticating with the re‐
85 mote host for IPMI 2.0. If not specified, a null key is assumed.
86 To input the key in hexadecimal form, prefix the string with
87 '0x'. E.g., the key 'abc' can be entered with the either the
88 string 'abc' or the string '0x616263'
89 -K, --k-g-prompt
91 Prompt for k-g to avoid possibility of listing it in process
92 lists.
93 --session-timeout=MILLISECONDS
95 Specify the session timeout in milliseconds. Defaults to 20000
96 milliseconds (20 seconds) if not specified.
97 --retransmission-timeout=MILLISECONDS
99 Specify the packet retransmission timeout in milliseconds. De‐
100 faults to 1000 milliseconds (1 second) if not specified. The re‐
101 transmission timeout cannot be larger than the session timeout.
102 -a AUTHENTICATION-TYPE, --authentication-type=AUTHENTICATION-TYPE
104 Specify the IPMI 1.5 authentication type to use. The currently
105 available authentication types are NONE, STRAIGHT_PASSWORD_KEY,
106 MD2, and MD5. Defaults to MD5 if not specified.
107 -I CIPHER-SUITE-ID, --cipher-suite-id=CIPHER-SUITE-ID
109 Specify the IPMI 2.0 cipher suite ID to use. The Cipher Suite ID
110 identifies a set of authentication, integrity, and confidential‐
111 ity algorithms to use for IPMI 2.0 communication. The authenti‐
112 cation algorithm identifies the algorithm to use for session
113 setup, the integrity algorithm identifies the algorithm to use
114 for session packet signatures, and the confidentiality algorithm
115 identifies the algorithm to use for payload encryption. Defaults
116 to cipher suite ID 3 if not specified. The following cipher
117 suite ids are currently supported:
118 0 - Authentication Algorithm = None; Integrity Algorithm = None;
120 Confidentiality Algorithm = None
121 1 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
123 None; Confidentiality Algorithm = None
124 2 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
126 HMAC-SHA1-96; Confidentiality Algorithm = None
127 3 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
129 HMAC-SHA1-96; Confidentiality Algorithm = AES-CBC-128
130 6 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
132 None; Confidentiality Algorithm = None
133 7 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
135 HMAC-MD5-128; Confidentiality Algorithm = None
136 8 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
138 HMAC-MD5-128; Confidentiality Algorithm = AES-CBC-128
139 11 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
141 MD5-128; Confidentiality Algorithm = None
142 12 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
144 MD5-128; Confidentiality Algorithm = AES-CBC-128
145 15 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
147 = None; Confidentiality Algorithm = None
148 16 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
150 = HMAC_SHA256_128; Confidentiality Algorithm = None
151 17 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
153 = HMAC_SHA256_128; Confidentiality Algorithm = AES-CBC-128
154 -l PRIVILEGE-LEVEL, --privilege-level=PRIVILEGE-LEVEL
156 Specify the privilege level to be used. The currently available
157 privilege levels are USER, OPERATOR, and ADMIN. Defaults to OP‐
158 ERATOR if not specified.
159 --config-file=FILE
161 Specify an alternate configuration file.
162 -W WORKAROUNDS, --workaround-flags=WORKAROUNDS
164 Specify workarounds to vendor compliance issues. Multiple work‐
165 arounds can be specified separated by commas. A special command
166 line flag of "none", will indicate no workarounds (may be useful
167 for overriding configured defaults). See WORKAROUNDS below for a
168 list of available workarounds.
169 --debug
171 Turn on debugging.
172 -?, --help
174 Output a help list and exit.
175 --usage
177 Output a usage message and exit.
178 -V, --version
180 Output the program version and exit.
181
183 The following options are specific to ipmi-sel.
184 -v Output verbose output. This option will output event direction.
186 Event direction may be useful to differentiate severity between
187 some events. For example, some motherboards may issue an event
188 both when a temperature exceeds a threshold and when it goes
189 back down below it.
190 -vv Output very verbose output. This option will output additional
192 information than verbose output. Most notably it will output ad‐
193 ditional hex codes to given information on ambiguous SEL en‐
194 tries, such as OEM codes. For example, it will output Generator
195 ID hex codes for sensors without names, event type codes for OEM
196 events, and record types for OEM records. This information may
197 be useful if you are writing a parser outside of ipmi-sel to in‐
198 terpret OEM information.
199 -i, --info
201 Show general information about the SEL.
202 --display=RECORD-IDS-LIST
204 Display SEL records by record id. Accepts space or comma sepa‐
205 rated lists.
206 --exclude-display=RECORD-IDS-LIST
208 Exclude display of SEL records by record id. Accepts space or
209 comma separated lists.
210 --display-range=START-END
212 Display SEL records from record id START to END.
213 --exclude-display-range=START-END
215 Exclude display of SEL records from record id START to END.
216 --date-range=DATE-DATE
218 Display SEL records with events occurring in the specified date
219 range. Dates may be specified in MM/DD/YYYY, MM-DD-YYYY or the
220 ISO 8601 YYYY-MM-DDTHH:MM:SS format. For the non ISO 8601 for‐
221 mats, the month may be specified as a numeral or its abbreviated
222 string name. The current local system time can be specified with
223 "now". Note that non-timestamped records will not be displayed
224 automatically because they do not possess a timestamp.
225 --exclude-date-range=DATE-DATE
227 Exclude display of SEL records with events occurring in the
228 specified date range. Dates may be specified in MM/DD/YYYY, MM-
229 DD-YYYY or the ISO 8601 YYYY-MM-DDTHH:MM:SS format. For the non
230 ISO 8601 formats, the month may be specified as a numeral or its
231 abbreviated string name. The current local system time can be
232 specified with "now". Note that non-timestamped records will be
233 displayed automatically because they do not possess a timestamp.
234 -t SENSOR-TYPE-LIST, --sensor-types=SENSOR-TYPE-LIST
236 Specify sensor types to show SEL events for. Multiple types can
237 be separated by commas or spaces. A special command line type of
238 "all", will indicate all types should be shown (may be useful
239 for overriding configured defaults). Users may specify sensor
240 types by string (see --list-sensor-types below) or by number
241 (decimal or hex).
242 -T SENSOR-TYPE-LIST, --exclude-sensor-types=SENSOR-TYPE-LIST
244 Specify sensor types to not show SEL events for. Multiple types
245 can be separated by commas or spaces. A special command line
246 type of "none", will indicate no types should be excluded (may
247 be useful for overriding configured defaults). Users may specify
248 sensor types by string (see --list-sensor-types below) or by
249 number (decimal or hex).
250 -L, --list-sensor-types
252 List sensor types.
253 --tail=count
255 Display approximately the last count SEL records. The display
256 count is calculated by approximating the record ids of the last
257 SEL records. It's correctness depends highly on the SEL imple‐
258 mentation by the vendor.
259 --clear
261 Clear SEL.
262 --post-clear
264 Identical to --clear, except the SEL clearing will be performed
265 after SEL event records are displayed. This option is useful for
266 scripting if users intend to log SEL events to another log, then
267 immediately clear SEL. Unlike calling --clear in another execu‐
268 tion of ipmi-sel, this option will use SEL reservations to no‐
269 tify the user if a SEL change has occurred while displaying and
270 clearing the SEL. This can protect users from a race, where a
271 new SEL event is unknowingly generated before clearing the SEL.
272 Note that SEL reservations are optionally implemented by vendors
273 and may not be available on all machines.
274 --delete=RECORD-IDS-LIST
276 Delete records by record id in the SEL. Accepts space or comma
277 separated lists.
278 --delete-range=START-END
280 Delete record ids from START to END in the SEL.
281 --system-event-only
283 Output only system event records (i.e. don't output OEM
284 records).
285 --oem-event-only
287 Output only OEM event records (i.e. don't output system event
288 records).
289 --output-manufacturer-id
291 For OEM SEL record types, output the manufacturer ID along with
292 event data when available.
293 --output-event-state
295 Output event state in output. This will add an additional output
296 reporting if an event should be viewed as NOMINAL, WARNING, or
297 CRITICAL. The event state is an interpreted value based on the
298 configuration file /etc/freeipmi//freeipmi_interpret_sel.conf
299 and the event direction. See freeipmi_interpret_sel.conf(5) for
300 more information.
301 --event-state-config-file=FILE
303 Specify an alternate event state configuration file. Option ig‐
304 nored if --output-event-state not specified.
305 --hex-dump
307 Hex-dump SEL entries.
308 --interpret-oem-data
310 Attempt to interpret OEM data, such as event data, sensor read‐
311 ings, or general extra info, etc. If an OEM interpretation is
312 not available, the default output will be generated. Correctness
313 of OEM interpretations cannot be guaranteed due to potential
314 changes OEM vendors may make in products, firmware, etc. See OEM
315 INTERPRETATION below for confirmed supported motherboard inter‐
316 pretations.
317 --output-oem-event-strings
319 Some motherboards support an IPMI OEM extension that returns the
320 string output for a system event. Such string output may be ben‐
321 eficial for determining the meaning behind OEM specific events.
322 This option will use the OEM event string to describe all system
323 events in the ipmi-sel output. This option differs from --inter‐
324 pret-oem-data option in that all system events will output the
325 vendor supplied event string, not just events that are OEM spe‐
326 cific. The event string may be very different from the normal
327 FreeIPMI event string output. If an OEM event strings is not
328 available, the default output will be output. This option is
329 confirmed to work for Fujitsu iRMC S1 and iRMC S2 systems.
330 --entity-sensor-names
332 Output sensor names prefixed with their entity id and instance
333 number when appropriate. This may be necessary on some mother‐
334 boards to help identify what sensors are referencing. For exam‐
335 ple, a motherboard may have multiple sensors named 'TEMP'. The
336 entity id and instance number may help clarify which sensor
337 refers to "Processor 1" vs. "Processor 2".
338 --no-sensor-type-output
340 Do not show sensor type output for each entry. On many systems,
341 the sensor type is redundant to the name of the sensor. This can
342 especially be true if --entity-sensor-names is specified. If
343 the sensor name is sufficient, or if the sensor type is of no
344 interest to the user, this option can be specified to condense
345 output.
346 --comma-separated-output
348 Output fields in comma separated format.
349 --no-header-output
351 Do not output column headers. May be useful in scripting.
352 --non-abbreviated-units
354 Output non-abbreviated units (e.g. 'Amps' instead of 'A'). May
355 aid in disambiguation of units (e.g. 'C' for Celsius or
356 Coulombs).
357 --legacy-output
359 Output in legacy format. Newer options may not be applicable to
360 legacy output.
361
363 This tool requires access to the sensor data repository (SDR) cache for
364 general operation. By default, SDR data will be downloaded and cached
365 on the local machine. The following options apply to the SDR cache.
366 --flush-cache
368 Flush a cached version of the sensor data repository (SDR)
369 cache. The SDR is typically cached for faster subsequent access.
370 However, it may need to be flushed and re-generated if the SDR
371 has been updated on a system.
372 --quiet-cache
374 Do not output information about cache creation/deletion. May be
375 useful in scripting.
376 --sdr-cache-recreate
378 If the SDR cache is out of date or invalid, automatically recre‐
379 ate the sensor data repository (SDR) cache. This option may be
380 useful for scripting purposes.
381 --sdr-cache-file=FILE
383 Specify a specific sensor data repository (SDR) cache file to be
384 stored or read from. If this option is used when multiple hosts
385 are specified, the same SDR cache file will be used for all
386 hosts.
387 --sdr-cache-directory=DIRECTORY
389 Specify an alternate directory for sensor data repository (SDR)
390 caches to be stored or read from. Defaults to the home directory
391 if not specified.
392 --ignore-sdr-cache
394 Ignore SDR cache related processing. May lead to incomplete or
395 less useful information being output, however it will allow
396 functionality for systems without SDRs or when the correct SDR
397 cannot be loaded.
398
400 By IPMI definition, all IPMI times and timestamps are stored in local‐
401 time. However, in many situations, the timestamps will not be stored in
402 localtime. Whether or not a system truly stored the timestamps in lo‐
403 caltime varies on many factors, such as the vendor, BIOS, and operating
404 system. The following options will allow the user to adjust the inter‐
405 pretation of the stored timestamps and how they should be output.
406 --utc-to-localtime
408 Assume all times are reported in UTC time and convert the time
409 to localtime before being output.
410 --localtime-to-utc
412 Convert all localtime timestamps to UTC before being output.
413 --utc-offset=SECONDS
415 Specify a specific UTC offset in seconds to be added to time‐
416 stamps. Value can range from -86400 to 86400 seconds. Defaults
417 to 0.
418
420 The following options manipulate hostranged output. See HOSTRANGED SUP‐
421 PORT below for additional information on hostranges.
422 -B, --buffer-output
424 Buffer hostranged output. For each node, buffer standard output
425 until the node has completed its IPMI operation. When specifying
426 this option, data may appear to output slower to the user since
427 the the entire IPMI operation must complete before any data can
428 be output. See HOSTRANGED SUPPORT below for additional informa‐
429 tion.
430 -C, --consolidate-output
432 Consolidate hostranged output. The complete standard output from
433 every node specified will be consolidated so that nodes with
434 identical output are not output twice. A header will list those
435 nodes with the consolidated output. When this option is speci‐
436 fied, no output can be seen until the IPMI operations to all
437 nodes has completed. If the user breaks out of the program
438 early, all currently consolidated output will be dumped. See
439 HOSTRANGED SUPPORT below for additional information.
440 -F NUM, --fanout=NUM
442 Specify multiple host fanout. A "sliding window" (or fanout) al‐
443 gorithm is used for parallel IPMI communication so that slower
444 nodes or timed out nodes will not impede parallel communication.
445 The maximum number of threads available at the same time is lim‐
446 ited by the fanout. The default is 64.
447 -E, --eliminate
449 Eliminate hosts determined as undetected by ipmidetect. This
450 attempts to remove the common issue of hostranged execution tim‐
451 ing out due to several nodes being removed from service in a
452 large cluster. The ipmidetectd daemon must be running on the
453 node executing the command.
454 --always-prefix
456 Always prefix output, even if only one host is specified or com‐
457 municating in-band. This option is primarily useful for script‐
458 ing purposes. Option will be ignored if specified with the -C
459 option.
460
462 Multiple hosts can be input either as an explicit comma separated lists
463 of hosts or a range of hostnames in the general form: prefix[n-m,l-
464 k,...], where n < m and l < k, etc. The later form should not be con‐
465 fused with regular expression character classes (also denoted by []).
466 For example, foo[19] does not represent foo1 or foo9, but rather repre‐
467 sents a degenerate range: foo19.
468 This range syntax is meant only as a convenience on clusters with a
470 prefixNN naming convention and specification of ranges should not be
471 considered necessary -- the list foo1,foo9 could be specified as such,
472 or by the range foo[1,9].
473 Some examples of range usage follow:
475 foo[01-05] instead of foo01,foo02,foo03,foo04,foo05
476 foo[7,9-10] instead of foo7,foo9,foo10
477 foo[0-3] instead of foo0,foo1,foo2,foo3
478 As a reminder to the reader, some shells will interpret brackets ([ and
480 ]) for pattern matching. Depending on your shell, it may be necessary
481 to enclose ranged lists within quotes.
482 When multiple hosts are specified by the user, a thread will be exe‐
484 cuted for each host in parallel up to the configured fanout (which can
485 be adjusted via the -F option). This will allow communication to large
486 numbers of nodes far more quickly than if done in serial.
487 By default, standard output from each node specified will be output
489 with the hostname prepended to each line. Although this output is read‐
490 able in many situations, it may be difficult to read in other situa‐
491 tions. For example, output from multiple nodes may be mixed together.
492 The -B and -C options can be used to change this default.
493 In-band IPMI Communication will be used when the host "localhost" is
495 specified. This allows the user to add the localhost into the hos‐
496 tranged output.
497
499 Most often, IPMI problems are due to configuration problems.
500 IPMI over LAN problems involve a misconfiguration of the remote ma‐
502 chine's BMC. Double check to make sure the following are configured
503 properly in the remote machine's BMC: IP address, MAC address, subnet
504 mask, username, user enablement, user privilege, password, LAN privi‐
505 lege, LAN enablement, and allowed authentication type(s). For IPMI 2.0
506 connections, double check to make sure the cipher suite privilege(s)
507 and K_g key are configured properly. The ipmi-config(8) tool can be
508 used to check and/or change these configuration settings.
509 Inband IPMI problems are typically caused by improperly configured
511 drivers or non-standard BMCs.
512 In addition to the troubleshooting tips below, please see WORKAROUNDS
514 below to also if there are any vendor specific bugs that have been dis‐
515 covered and worked around.
516 Listed below are many of the common issues for error messages. For ad‐
518 ditional support, please e-mail the <freeipmi-users@gnu.org> mailing
519 list.
520 "username invalid" - The username entered (or a NULL username if none
522 was entered) is not available on the remote machine. It may also be
523 possible the remote BMC's username configuration is incorrect.
524 "password invalid" - The password entered (or a NULL password if none
526 was entered) is not correct. It may also be possible the password for
527 the user is not correctly configured on the remote BMC.
528 "password verification timeout" - Password verification has timed out.
530 A "password invalid" error (described above) or a generic "session
531 timeout" (described below) occurred. During this point in the protocol
532 it cannot be differentiated which occurred.
533 "k_g invalid" - The K_g key entered (or a NULL K_g key if none was en‐
535 tered) is not correct. It may also be possible the K_g key is not cor‐
536 rectly configured on the remote BMC.
537 "privilege level insufficient" - An IPMI command requires a higher user
539 privilege than the one authenticated with. Please try to authenticate
540 with a higher privilege. This may require authenticating to a different
541 user which has a higher maximum privilege.
542 "privilege level cannot be obtained for this user" - The privilege
544 level you are attempting to authenticate with is higher than the maxi‐
545 mum allowed for this user. Please try again with a lower privilege. It
546 may also be possible the maximum privilege level allowed for a user is
547 not configured properly on the remote BMC.
548 "authentication type unavailable for attempted privilege level" - The
550 authentication type you wish to authenticate with is not available for
551 this privilege level. Please try again with an alternate authentication
552 type or alternate privilege level. It may also be possible the avail‐
553 able authentication types you can authenticate with are not correctly
554 configured on the remote BMC.
555 "cipher suite id unavailable" - The cipher suite id you wish to authen‐
557 ticate with is not available on the remote BMC. Please try again with
558 an alternate cipher suite id. It may also be possible the available ci‐
559 pher suite ids are not correctly configured on the remote BMC.
560 "ipmi 2.0 unavailable" - IPMI 2.0 was not discovered on the remote ma‐
562 chine. Please try to use IPMI 1.5 instead.
563 "connection timeout" - Initial IPMI communication failed. A number of
565 potential errors are possible, including an invalid hostname specified,
566 an IPMI IP address cannot be resolved, IPMI is not enabled on the re‐
567 mote server, the network connection is bad, etc. Please verify configu‐
568 ration and connectivity.
569 "session timeout" - The IPMI session has timed out. Please reconnect.
571 If this error occurs often, you may wish to increase the retransmission
572 timeout. Some remote BMCs are considerably slower than others.
573 "device not found" - The specified device could not be found. Please
575 check configuration or inputs and try again.
576 "driver timeout" - Communication with the driver or device has timed
578 out. Please try again.
579 "message timeout" - Communication with the driver or device has timed
581 out. Please try again.
582 "BMC busy" - The BMC is currently busy. It may be processing informa‐
584 tion or have too many simultaneous sessions to manage. Please wait and
585 try again.
586 "could not find inband device" - An inband device could not be found.
588 Please check configuration or specify specific device or driver on the
589 command line.
590 "driver timeout" - The inband driver has timed out communicating to the
592 local BMC or service processor. The BMC or service processor may be
593 busy or (worst case) possibly non-functioning.
594 "internal IPMI error" - An IPMI error has occurred that FreeIPMI does
596 not know how to handle. Please e-mail <freeipmi-users@gnu.org> to re‐
597 port the issue.
598
600 Some timestamps in the SEL may report a date of 1-Jan-1970, the epoch
601 for SEL timestamps. This timestamp is not necessarily incorrect. It
602 usually indicates a hardware event that occurred before a timestamp in
603 firmware has been initialized. For example, certain hardware components
604 will have their internal clocks reset during a power cycle.
605 However, if the internal clock of the SEL appears to be regularly in‐
607 correct, you may need to set the SEL time. This can be done using bmc-
608 device(8).
609 The following are common SEL related messages.
611 "sel config file parse error" - A parse error was found in the sel
613 event interpretation configuration file. Please see freeipmi_inter‐
614 pret_sel.conf(5).
615
617 With so many different vendors implementing their own IPMI solutions,
618 different vendors may implement their IPMI protocols incorrectly. The
619 following describes a number of workarounds currently available to han‐
620 dle discovered compliance issues. When possible, workarounds have been
621 implemented so they will be transparent to the user. However, some will
622 require the user to specify a workaround be used via the -W option.
623 The hardware listed below may only indicate the hardware that a problem
625 was discovered on. Newer versions of hardware may fix the problems in‐
626 dicated below. Similar machines from vendors may or may not exhibit the
627 same problems. Different vendors may license their firmware from the
628 same IPMI firmware developer, so it may be worthwhile to try work‐
629 arounds listed below even if your motherboard is not listed.
630 If you believe your hardware has an additional compliance issue that
632 needs a workaround to be implemented, please contact the FreeIPMI main‐
633 tainers on <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
634 assumeio - This workaround flag will assume inband interfaces communi‐
636 cate with system I/O rather than being memory-mapped. This will work
637 around systems that report invalid base addresses. Those hitting this
638 issue may see "device not supported" or "could not find inband device"
639 errors. Issue observed on HP ProLiant DL145 G1.
640 spinpoll - This workaround flag will inform some inband drivers (most
642 notably the KCS driver) to spin while polling rather than putting the
643 process to sleep. This may significantly improve the wall clock running
644 time of tools because an operating system scheduler's granularity may
645 be much larger than the time it takes to perform a single IPMI message
646 transaction. However, by spinning, your system may be performing less
647 useful work by not contexting out the tool for a more useful task.
648 authcap - This workaround flag will skip early checks for username ca‐
650 pabilities, authentication capabilities, and K_g support and allow IPMI
651 authentication to succeed. It works around multiple issues in which the
652 remote system does not properly report username capabilities, authenti‐
653 cation capabilities, or K_g status. Those hitting this issue may see
654 "username invalid", "authentication type unavailable for attempted
655 privilege level", or "k_g invalid" errors. Issue observed on Asus
656 P5M2/P5MT-R/RS162-E4/RX4, Intel SR1520ML/X38ML, and Sun Fire
657 2200/4150/4450 with ELOM.
658 nochecksumcheck - This workaround flag will tell FreeIPMI to not check
660 the checksums returned from IPMI command responses. It works around
661 systems that return invalid checksums due to implementation errors, but
662 the packet is otherwise valid. Users are cautioned on the use of this
663 option, as it removes validation of packet integrity in a number of
664 circumstances. However, it is unlikely to be an issue in most situa‐
665 tions. Those hitting this issue may see "connection timeout", "session
666 timeout", or "password verification timeout" errors. On IPMI 1.5 con‐
667 nections, the "noauthcodecheck" workaround may also needed too. Issue
668 observed on Supermicro X9SCM-iiF, Supermicro X9DRi-F, and Supermicro
669 X9DRFR.
670 idzero - This workaround flag will allow empty session IDs to be ac‐
672 cepted by the client. It works around IPMI sessions that report empty
673 session IDs to the client. Those hitting this issue may see "session
674 timeout" errors. Issue observed on Tyan S2882 with M3289 BMC.
675 unexpectedauth - This workaround flag will allow unexpected non-null
677 authcodes to be checked as though they were expected. It works around
678 an issue when packets contain non-null authentication data when they
679 should be null due to disabled per-message authentication. Those hit‐
680 ting this issue may see "session timeout" errors. Issue observed on
681 Dell PowerEdge 2850,SC1425. Confirmed fixed on newer firmware.
682 forcepermsg - This workaround flag will force per-message authentica‐
684 tion to be used no matter what is advertised by the remote system. It
685 works around an issue when per-message authentication is advertised as
686 disabled on the remote system, but it is actually required for the pro‐
687 tocol. Those hitting this issue may see "session timeout" errors. Is‐
688 sue observed on IBM eServer 325.
689 endianseq - This workaround flag will flip the endian of the session
691 sequence numbers to allow the session to continue properly. It works
692 around IPMI 1.5 session sequence numbers that are the wrong endian.
693 Those hitting this issue may see "session timeout" errors. Issue ob‐
694 served on some Sun ILOM 1.0/2.0 (depends on service processor endian).
695 noauthcodecheck - This workaround flag will tell FreeIPMI to not check
697 the authentication codes returned from IPMI 1.5 command responses. It
698 works around systems that return invalid authentication codes due to
699 hashing or implementation errors. Users are cautioned on the use of
700 this option, as it removes an authentication check verifying the valid‐
701 ity of a packet. However, in most organizations, this is unlikely to be
702 a security issue. Those hitting this issue may see "connection time‐
703 out", "session timeout", or "password verification timeout" errors.
704 Issue observed on Xyratex FB-H8-SRAY, Intel Windmill, Quanta Winter‐
705 fell, and Wiwynn Windmill.
706 intel20 - This workaround flag will work around several Intel IPMI 2.0
708 authentication issues. The issues covered include padding of usernames,
709 and password truncation if the authentication algorithm is HMAC-
710 MD5-128. Those hitting this issue may see "username invalid", "password
711 invalid", or "k_g invalid" errors. Issue observed on Intel SE7520AF2
712 with Intel Server Management Module (Professional Edition).
713 supermicro20 - This workaround flag will work around several Supermicro
715 IPMI 2.0 authentication issues on motherboards w/ Peppercon IPMI
716 firmware. The issues covered include handling invalid length authenti‐
717 cation codes. Those hitting this issue may see "password invalid" er‐
718 rors. Issue observed on Supermicro H8QME with SIMSO daughter card.
719 Confirmed fixed on newerver firmware.
720 sun20 - This workaround flag will work work around several Sun IPMI 2.0
722 authentication issues. The issues covered include invalid lengthed hash
723 keys, improperly hashed keys, and invalid cipher suite records. Those
724 hitting this issue may see "password invalid" or "bmc error" errors.
725 Issue observed on Sun Fire 4100/4200/4500 with ILOM. This workaround
726 automatically includes the "opensesspriv" workaround.
727 opensesspriv - This workaround flag will slightly alter FreeIPMI's IPMI
729 2.0 connection protocol to workaround an invalid hashing algorithm used
730 by the remote system. The privilege level sent during the Open Session
731 stage of an IPMI 2.0 connection is used for hashing keys instead of the
732 privilege level sent during the RAKP1 connection stage. Those hitting
733 this issue may see "password invalid", "k_g invalid", or "bad rmcpplus
734 status code" errors. Issue observed on Sun Fire 4100/4200/4500 with
735 ILOM, Inventec 5441/Dell Xanadu II, Supermicro X8DTH, Supermicro X8DTG,
736 Intel S5500WBV/Penguin Relion 700, Intel S2600JF/Appro 512X, Quanta
737 QSSC-S4R/Appro GB812X-CN, and Dell C5220. This workaround is automati‐
738 cally triggered with the "sun20" workaround.
739 integritycheckvalue - This workaround flag will work around an invalid
741 integrity check value during an IPMI 2.0 session establishment when us‐
742 ing Cipher Suite ID 0. The integrity check value should be 0 length,
743 however the remote motherboard responds with a non-empty field. Those
744 hitting this issue may see "k_g invalid" errors. Issue observed on Su‐
745 permicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin Relion
746 700, and Intel S2600JF/Appro 512X.
747 assumemaxsdrrecordcount - This workaround will inform SDR reading to
749 stop reading after a known maximum number of SDR records have been
750 read. This will work around systems that have miss-implemented SDR
751 reading functions. Those hitting this issue may see "SDR record count
752 invalid" errors. Issue observed on unspecified Inspur motherboard.
753 assumesystemevent - This workaround option will assume invalid SEL
755 record types are system event records. Records may be formatted cor‐
756 rectly but report invalid record types. Those hitting this issue may
757 see "Unknown SEL Record Type" errors. Output may be unknown, pray for
758 the best. This option is confirmed to work around compliances issues on
759 HP DL 380 G5 motherboards.
760 No IPMI 1.5 Support - Some motherboards that support IPMI 2.0 have been
762 found to not support IPMI 1.5. Those hitting this issue may see "ipmi
763 2.0 unavailable" or "connection timeout" errors. This issue can be
764 worked around by using IPMI 2.0 instead of IPMI 1.5 by specifying
765 --driver-type=LAN_2_0. Issue observed on a number of HP and Supermicro
766 motherboards.
767
769 The following motherboards are confirmed to have atleast some support
770 by the --interpret-oem-data option. While highly probable the OEM data
771 interpretations would work across other motherboards by the same manu‐
772 facturer, there are no guarantees. Some of the motherboards below may
773 be rebranded by vendors/distributors.
774 Dell Poweredge 2900, Dell Poweredge 2950, Dell Poweredge R610, Dell
776 Poweredge R710, Fujitsu iRMC S1 and iRMC S2 systems, Gigabyte
777 MD90-FS0-ZB, Gigabyte MG20-OP0-ZB/Penguin Computing Relgion X1904GT,
778 Intel S5500WB/Penguin Computing Relion 700, Intel S2600JF/Appro 512X,
779 Intel S2600GZ, Intel S2600WP, Intel S5000PAL, Intel Windmill, Intel
780 S2600KP, Intel S2600KPR, Intel S2600WT2, Intel S2600WTT, Inventec
781 5441/Dell Xanadu II, Inventec 5442/Dell Xanadu III, Quanta S99Q/Dell
782 FS12-TY, Quanta QSSC-S4R/Appro GB812X-CN, Quanta Winterfell, Sun X4140
783 Supermicro X7DBR-3, Supermicro X7DB8, Supermicro X8DTN, Supermicro
784 X7SBI-LN4, Supermicro X8DTH, Supermicro X8DTG, Supermicro X8DTU, Super‐
785 micro X8DT3-LN4F, Supermicro X8DTU-6+, Supermicro X8DTL, Supermicro
786 X8DTL-3F, Supermicro X8SIL-F, Supermicro X9SCL, Supermicro X9SCM, Su‐
787 permicro X8DTN+-F, Supermicro X8SIE, Supermicro X9SCA-F-O, Supermicro
788 H8DGU-F, Supermicro X9DRi-F, Supermicro X9DRI-LN4F+, Supermicro X9SPU-
789 F-O, Supermicro X9SCM-iiF, Supermicro X10SLM-F, Wiwynn Windmill,
790 Wistron/Dell Poweredge C6220.
791
793 # ipmi-sel
794 Show all SEL records on the local machine.
796 # ipmi-sel -h ahost -u myusername -p mypassword
798 Show all SEL records of a remote machine using IPMI over LAN.
800 # ipmi-sel -h mycluster[0-127] -u myusername -p mypassword
802 Show all SEL records across a cluster using IPMI over LAN.
804 # ipmi-sel --delete=44,82
806 Delete SEL records 44 and 82 on the local machine.
808 # ipmi-sel --delete-all
810 Delete all SEL entries on the local machine.
812 # ipmi-sel --delete-range=12-42
814 Delete SEL entries in the range 12 to 42 on the local machine.
816
818 Upon successful execution, exit status is 0. On error, exit status is
819 1.
820 If multiple hosts are specified for communication, the exit status is 0
822 if and only if all targets successfully execute. Otherwise the exit
823 status is 1.
824
826 On older operating systems, if you input your username, password, and
827 other potentially security relevant information on the command line,
828 this information may be discovered by other users when using tools like
829 the ps(1) command or looking in the /proc file system. It is generally
830 more secure to input password information with options like the -P or
831 -K options. Configuring security relevant information in the FreeIPMI
832 configuration file would also be an appropriate way to hide this infor‐
833 mation.
834 In order to prevent brute force attacks, some BMCs will temporarily
836 "lock up" after a number of remote authentication errors. You may need
837 to wait awhile in order to this temporary "lock up" to pass before you
838 may authenticate again.
839
841 Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
842
844 Copyright © 2003-2015 FreeIPMI Core Team.
845 This program is free software; you can redistribute it and/or modify it
847 under the terms of the GNU General Public License as published by the
848 Free Software Foundation; either version 3 of the License, or (at your
849 option) any later version.
850
852 freeipmi(7), bmc-device(8), ipmiseld(8), ipmi-config(8), freeipmi_in‐
853 terpret_sel.conf(5)
854 http://www.gnu.org/software/freeipmi/
856ipmi-sel 1.6.11 2023-06-07 IPMI-SEL(8)