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
20 issues. 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
57 requests 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.
66 -u USERNAME, --username=USERNAME
68 Specify the username to use when authenticating with the remote
69 host. If not specified, a null (i.e. anonymous) username is
70 assumed. The user must have atleast USER privileges in order for
71 this tool to operate fully.
72 -p PASSWORD, --password=PASSWORD
74 Specify the password to use when authenticationg with the remote
75 host. If not specified, a null password is assumed. Maximum
76 password length is 16 for IPMI 1.5 and 20 for IPMI 2.0.
77 -P, --password-prompt
79 Prompt for password to avoid possibility of listing it in
80 process lists.
81 -k K_G, --k-g=K_G
83 Specify the K_g BMC key to use when authenticating with the
84 remote host for IPMI 2.0. If not specified, a null key is
85 assumed. To input the key in hexadecimal form, prefix the string
86 with '0x'. E.g., the key 'abc' can be entered with the either
87 the string 'abc' or the string '0x616263'
88 -K, --k-g-prompt
90 Prompt for k-g to avoid possibility of listing it in process
91 lists.
92 --session-timeout=MILLISECONDS
94 Specify the session timeout in milliseconds. Defaults to 20000
95 milliseconds (20 seconds) if not specified.
96 --retransmission-timeout=MILLISECONDS
98 Specify the packet retransmission timeout in milliseconds.
99 Defaults to 1000 milliseconds (1 second) if not specified. The
100 retransmission timeout cannot be larger than the session time‐
101 out.
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
158 OPERATOR 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
193 additional hex codes to given information on ambiguous SEL
194 entries, such as OEM codes. For example, it will output Genera‐
195 tor ID hex codes for sensors without names, event type codes for
196 OEM events, and record types for OEM records. This information
197 may be useful if you are writing a parser outside of ipmi-sel to
198 interpret 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 or MM-DD-YYYY for‐
220 mat. The month may be specified as a numeral or its abbreviated
221 string name. The current local system time can be specified with
222 "now". Note that non-timestamped records will not be displayed
223 automatically because they do not possess a timestamp.
224 --exclude-date-range=DATE-DATE
226 Exclude display of SEL records with events occurring in the
227 specified date range. Dates may be specified in MM/DD/YYYY or
228 MM-DD-YYYY format. The month may be specified as a numeral or
229 its abbreviated string name. The current local system time can
230 be specified with "now". Note that non-timestamped records will
231 be displayed automatically because they do not possess a time‐
232 stamp.
233 -t SENSOR-TYPE-LIST, --sensor-types=SENSOR-TYPE-LIST
235 Specify sensor types to show SEL events for. Multiple types can
236 be separated by commas or spaces. A special command line type of
237 "all", will indicate all types should be shown (may be useful
238 for overriding configured defaults). Users may specify sensor
239 types by string (see --list-sensor-types below) or by number
240 (decimal or hex).
241 -T SENSOR-TYPE-LIST, --exclude-sensor-types=SENSOR-TYPE-LIST
243 Specify sensor types to not show SEL events for. Multiple types
244 can be separated by commas or spaces. A special command line
245 type of "none", will indicate no types should be excluded (may
246 be useful for overriding configured defaults). Users may specify
247 sensor types by string (see --list-sensor-types below) or by
248 number (decimal or hex).
249 -L, --list-sensor-types
251 List sensor types.
252 --tail=count
254 Display approximately the last count SEL records. The display
255 count is calculated by approximating the record ids of the last
256 SEL records. It's correctness depends highly on the SEL imple‐
257 mentation by the vendor.
258 --clear
260 Clear SEL.
261 --post-clear
263 Identical to --clear, except the SEL clearning will be performed
264 after SEL event records are displayed. This option is useful for
265 scripting if users intend to log SEL events to another log, then
266 immediately clear SEL. Unlike calling --clear in another execu‐
267 tion of ipmi-sel, this option will use SEL reservations to
268 notify the user if a SEL change has occurred while displaying
269 and clearing the SEL. This can protect users from a race, where
270 a new SEL event is unknowingly generated before clearing the
271 SEL. Note that SEL reservations are optionally implemented by
272 vendors and may not be available on all machines.
273 --delete=RECORD-IDS-LIST
275 Delete records by record id in the SEL. Accepts space or comma
276 separated lists.
277 --delete-range=START-END
279 Delete record ids from START to END in the SEL.
280 --system-event-only
282 Output only system event records (i.e. don't output OEM
283 records).
284 --oem-event-only
286 Output only OEM event records (i.e. don't output system event
287 records).
288 --output-manufacturer-id
290 For OEM SEL record types, output the manufacturer ID along with
291 event data when available.
292 --output-event-state
294 Output event state in output. This will add an additional output
295 reporting if an event should be viewed as NOMINAL, WARNING, or
296 CRITICAL. The event state is an interpreted value based on the
297 configuration file /etc/freeipmi//freeipmi_interpret_sel.conf
298 and the event direction. See freeipmi_interpret_sel.conf(5) for
299 more information.
300 --event-state-config-file=FILE
302 Specify an alternate event state configuration file. Option
303 ignored if --output-event-state not specified.
304 --hex-dump
306 Hex-dump SEL entries.
307 --interpret-oem-data
309 Attempt to interpret OEM data, such as event data, sensor read‐
310 ings, or general extra info, etc. If an OEM interpretation is
311 not available, the default output will be generated. Correctness
312 of OEM interpretations cannot be guaranteed due to potential
313 changes OEM vendors may make in products, firmware, etc. See OEM
314 INTERPRETATION below for confirmed supported motherboard inter‐
315 pretations.
316 --output-oem-event-strings
318 Some motherboards support an IPMI OEM extension that returns the
319 string output for a system event. Such string output may be ben‐
320 eficial for determining the meaning behind OEM specific events.
321 This option will use the OEM event string to describe all system
322 events in the ipmi-sel output. This option differs from --inter‐
323 pret-oem-data option in that all system events will output the
324 vendor supplied event string, not just events that are OEM spe‐
325 cific. The event string may be very different from the normal
326 FreeIPMI event string output. If an OEM event strings is not
327 available, the default output will be output. This option is
328 confirmed to work for Fujitsu iRMC S1 and iRMC S2 systems.
329 --entity-sensor-names
331 Output sensor names prefixed with their entity id and instance
332 number when appropriate. This may be necessary on some mother‐
333 boards to help identify what sensors are referencing. For exam‐
334 ple, a motherboard may have multiple sensors named 'TEMP'. The
335 entity id and instance number may help clarify which sensor
336 refers to "Processor 1" vs. "Processor 2".
337 --no-sensor-type-output
339 Do not show sensor type output for each entry. On many systems,
340 the sensor type is redundant to the name of the sensor. This can
341 especially be true if --entity-sensor-names is specified. If
342 the sensor name is sufficient, or if the sensor type is of no
343 interest to the user, this option can be specified to condense
344 output.
345 --comma-separated-output
347 Output fields in comma separated format.
348 --no-header-output
350 Do not output column headers. May be useful in scripting.
351 --non-abbreviated-units
353 Output non-abbreviated units (e.g. 'Amps' instead of 'A'). May
354 aid in disambiguation of units (e.g. 'C' for Celsius or
355 Coulombs).
356 --legacy-output
358 Output in legacy format. Newer options may not be applicable to
359 legacy output.
360
362 This tool requires access to the sensor data repository (SDR) cache for
363 general operation. By default, SDR data will be downloaded and cached
364 on the local machine. The following options apply to the SDR cache.
365 -f, --flush-cache
367 Flush a cached version of the sensor data repository (SDR)
368 cache. The SDR is typically cached for faster subsequent access.
369 However, it may need to be flushed and re-generated if the SDR
370 has been updated on a system.
371 -Q, --quiet-cache
373 Do not output information about cache creation/deletion. May be
374 useful in scripting.
375 --sdr-cache-recreate
377 If the SDR cache is out of date or invalid, automatically recre‐
378 ate the sensor data repository (SDR) cache. This option may be
379 useful for scripting purposes.
380 --sdr-cache-file=FILE
382 Specify a specific sensor data repository (SDR) cache file to be
383 stored or read from. If this option is used when multiple hosts
384 are specified, the same SDR cache file will be used for all
385 hosts.
386 --sdr-cache-directory=DIRECTORY
388 Specify an alternate directory for sensor data repository (SDR)
389 caches to be stored or read from. Defaults to the home directory
390 if not specified.
391 --ignore-sdr-cache
393 Ignore SDR cache related processing. May lead to incomplete or
394 less useful information being output, however it will allow
395 functionality for systems without SDRs or when the correct SDR
396 cannot be loaded.
397
399 By IPMI definition, all IPMI times and timestamps are stored in local‐
400 time. However, in many situations, the timestamps will not be stored in
401 localtime. Whether or not a system truly stored the timestamps in
402 localtime varies on many factors, such as the vendor, BIOS, and operat‐
403 ing system. The following options will allow the user to adjust the
404 interpretation of the stored timestamps and how they should be output.
405 --utc-to-localtime
407 Assume all times are reported in UTC time and convert the time
408 to localtime before being output.
409 --localtime-to-utc
411 Convert all localtime timestamps to UTC before being output.
412 --utc-offset=SECONDS
414 Specify a specific UTC offset in seconds to be added to time‐
415 stamps. Value can range from -86400 to 86400 seconds. Defaults
416 to 0.
417
419 The following options manipulate hostranged output. See HOSTRANGED SUP‐
420 PORT below for additional information on hostranges.
421 -B, --buffer-output
423 Buffer hostranged output. For each node, buffer standard output
424 until the node has completed its IPMI operation. When specifying
425 this option, data may appear to output slower to the user since
426 the the entire IPMI operation must complete before any data can
427 be output. See HOSTRANGED SUPPORT below for additional informa‐
428 tion.
429 -C, --consolidate-output
431 Consolidate hostranged output. The complete standard output from
432 every node specified will be consolidated so that nodes with
433 identical output are not output twice. A header will list those
434 nodes with the consolidated output. When this option is speci‐
435 fied, no output can be seen until the IPMI operations to all
436 nodes has completed. If the user breaks out of the program
437 early, all currently consolidated output will be dumped. See
438 HOSTRANGED SUPPORT below for additional information.
439 -F NUM, --fanout=NUM
441 Specify multiple host fanout. A "sliding window" (or fanout)
442 algorithm is used for parallel IPMI communication so that slower
443 nodes or timed out nodes will not impede parallel communication.
444 The maximum number of threads available at the same time is lim‐
445 ited by the fanout. The default is 64.
446 -E, --eliminate
448 Eliminate hosts determined as undetected by ipmidetect. This
449 attempts to remove the common issue of hostranged execution tim‐
450 ing out due to several nodes being removed from service in a
451 large cluster. The ipmidetectd daemon must be running on the
452 node executing the command.
453 --always-prefix
455 Always prefix output, even if only one host is specified or com‐
456 municating in-band. This option is primarily useful for script‐
457 ing purposes. Option will be ignored if specified with the -C
458 option.
459
461 Multiple hosts can be input either as an explicit comma separated lists
462 of hosts or a range of hostnames in the general form: prefix[n-m,l-
463 k,...], where n < m and l < k, etc. The later form should not be con‐
464 fused with regular expression character classes (also denoted by []).
465 For example, foo[19] does not represent foo1 or foo9, but rather repre‐
466 sents a degenerate range: foo19.
467 This range syntax is meant only as a convenience on clusters with a
469 prefixNN naming convention and specification of ranges should not be
470 considered necessary -- the list foo1,foo9 could be specified as such,
471 or by the range foo[1,9].
472 Some examples of range usage follow:
474 foo[01-05] instead of foo01,foo02,foo03,foo04,foo05
475 foo[7,9-10] instead of foo7,foo9,foo10
476 foo[0-3] instead of foo0,foo1,foo2,foo3
477 As a reminder to the reader, some shells will interpret brackets ([ and
479 ]) for pattern matching. Depending on your shell, it may be necessary
480 to enclose ranged lists within quotes.
481 When multiple hosts are specified by the user, a thread will be exe‐
483 cuted for each host in parallel up to the configured fanout (which can
484 be adjusted via the -F option). This will allow communication to large
485 numbers of nodes far more quickly than if done in serial.
486 By default, standard output from each node specified will be output
488 with the hostname prepended to each line. Although this output is read‐
489 able in many situations, it may be difficult to read in other situa‐
490 tions. For example, output from multiple nodes may be mixed together.
491 The -B and -C options can be used to change this default.
492 In-band IPMI Communication will be used when the host "localhost" is
494 specified. This allows the user to add the localhost into the hos‐
495 tranged output.
496
498 Most often, IPMI problems are due to configuration problems.
499 IPMI over LAN problems involve a misconfiguration of the remote
501 machine's BMC. Double check to make sure the following are configured
502 properly in the remote machine's BMC: IP address, MAC address, subnet
503 mask, username, user enablement, user privilege, password, LAN privi‐
504 lege, LAN enablement, and allowed authentication type(s). For IPMI 2.0
505 connections, double check to make sure the cipher suite privilege(s)
506 and K_g key are configured properly. The ipmi-config(8) tool can be
507 used to check and/or change these configuration settings.
508 Inband IPMI problems are typically caused by improperly configured
510 drivers or non-standard BMCs.
511 In addition to the troubleshooting tips below, please see WORKAROUNDS
513 below to also if there are any vendor specific bugs that have been dis‐
514 covered and worked around.
515 Listed below are many of the common issues for error messages. For
517 additional support, please e-mail the <freeipmi-users@gnu.org> mailing
518 list.
519 "username invalid" - The username entered (or a NULL username if none
521 was entered) is not available on the remote machine. It may also be
522 possible the remote BMC's username configuration is incorrect.
523 "password invalid" - The password entered (or a NULL password if none
525 was entered) is not correct. It may also be possible the password for
526 the user is not correctly configured on the remote BMC.
527 "password verification timeout" - Password verification has timed out.
529 A "password invalid" error (described above) or a generic "session
530 timeout" (described below) occurred. During this point in the protocol
531 it cannot be differentiated which occurred.
532 "k_g invalid" - The K_g key entered (or a NULL K_g key if none was
534 entered) is not correct. It may also be possible the K_g key is not
535 correctly configured on the remote BMC.
536 "privilege level insufficient" - An IPMI command requires a higher user
538 privilege than the one authenticated with. Please try to authenticate
539 with a higher privilege. This may require authenticating to a different
540 user which has a higher maximum privilege.
541 "privilege level cannot be obtained for this user" - The privilege
543 level you are attempting to authenticate with is higher than the maxi‐
544 mum allowed for this user. Please try again with a lower privilege. It
545 may also be possible the maximum privilege level allowed for a user is
546 not configured properly on the remote BMC.
547 "authentication type unavailable for attempted privilege level" - The
549 authentication type you wish to authenticate with is not available for
550 this privilege level. Please try again with an alternate authentication
551 type or alternate privilege level. It may also be possible the avail‐
552 able authentication types you can authenticate with are not correctly
553 configured on the remote BMC.
554 "cipher suite id unavailable" - The cipher suite id you wish to authen‐
556 ticate with is not available on the remote BMC. Please try again with
557 an alternate cipher suite id. It may also be possible the available
558 cipher suite ids are not correctly configured on the remote BMC.
559 "ipmi 2.0 unavailable" - IPMI 2.0 was not discovered on the remote
561 machine. Please try to use IPMI 1.5 instead.
562 "connection timeout" - Initial IPMI communication failed. A number of
564 potential errors are possible, including an invalid hostname specified,
565 an IPMI IP address cannot be resolved, IPMI is not enabled on the
566 remote server, the network connection is bad, etc. Please verify con‐
567 figuration and connectivity.
568 "session timeout" - The IPMI session has timed out. Please reconnect.
570 If this error occurs often, you may wish to increase the retransmission
571 timeout. Some remote BMCs are considerably slower than others.
572 "device not found" - The specified device could not be found. Please
574 check configuration or inputs and try again.
575 "driver timeout" - Communication with the driver or device has timed
577 out. Please try again.
578 "message timeout" - Communication with the driver or device has timed
580 out. Please try again.
581 "BMC busy" - The BMC is currently busy. It may be processing informa‐
583 tion or have too many simultaneous sessions to manage. Please wait and
584 try again.
585 "could not find inband device" - An inband device could not be found.
587 Please check configuration or specify specific device or driver on the
588 command line.
589 "driver timeout" - The inband driver has timed out communicating to the
591 local BMC or service processor. The BMC or service processor may be
592 busy or (worst case) possibly non-functioning.
593 "internal IPMI error" - An IPMI error has occurred that FreeIPMI does
595 not know how to handle. Please e-mail <freeipmi-users@gnu.org> to
596 report the issue.
597
599 Some timestamps in the SEL may report a date of 1-Jan-1970, the epoch
600 for SEL timestamps. This timestamp is not necessarily incorrect. It
601 usually indicates a hardware event that occurred before a timestamp in
602 firmware has been initialized. For example, certain hardware components
603 will have their internal clocks reset during a power cycle.
604 However, if the internal clock of the SEL appears to be regularly
606 incorrect, you may need to set the SEL time. This can be done using
607 bmc-device(8).
608 The following are common SEL related messages.
610 "sel config file parse error" - A parse error was found in the sel
612 event interpretation configuration file. Please see freeipmi_inter‐
613 pret_sel.conf(5).
614
616 With so many different vendors implementing their own IPMI solutions,
617 different vendors may implement their IPMI protocols incorrectly. The
618 following describes a number of workarounds currently available to han‐
619 dle discovered compliance issues. When possible, workarounds have been
620 implemented so they will be transparent to the user. However, some will
621 require the user to specify a workaround be used via the -W option.
622 The hardware listed below may only indicate the hardware that a problem
624 was discovered on. Newer versions of hardware may fix the problems
625 indicated below. Similar machines from vendors may or may not exhibit
626 the same problems. Different vendors may license their firmware from
627 the same IPMI firmware developer, so it may be worthwhile to try work‐
628 arounds listed below even if your motherboard is not listed.
629 If you believe your hardware has an additional compliance issue that
631 needs a workaround to be implemented, please contact the FreeIPMI main‐
632 tainers on <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
633 assumeio - This workaround flag will assume inband interfaces communi‐
635 cate with system I/O rather than being memory-mapped. This will work
636 around systems that report invalid base addresses. Those hitting this
637 issue may see "device not supported" or "could not find inband device"
638 errors. Issue observed on HP ProLiant DL145 G1.
639 spinpoll - This workaround flag will inform some inband drivers (most
641 notably the KCS driver) to spin while polling rather than putting the
642 process to sleep. This may significantly improve the wall clock running
643 time of tools because an operating system scheduler's granularity may
644 be much larger than the time it takes to perform a single IPMI message
645 transaction. However, by spinning, your system may be performing less
646 useful work by not contexting out the tool for a more useful task.
647 authcap - This workaround flag will skip early checks for username
649 capabilities, authentication capabilities, and K_g support and allow
650 IPMI authentication to succeed. It works around multiple issues in
651 which the remote system does not properly report username capabilities,
652 authentication capabilities, or K_g status. Those hitting this issue
653 may see "username invalid", "authentication type unavailable for
654 attempted privilege level", or "k_g invalid" errors. Issue observed on
655 Asus P5M2/P5MT-R/RS162-E4/RX4, Intel SR1520ML/X38ML, and Sun Fire
656 2200/4150/4450 with ELOM.
657 nochecksumcheck - This workaround flag will tell FreeIPMI to not check
659 the checksums returned from IPMI command responses. It works around
660 systems that return invalid checksums due to implementation errors, but
661 the packet is otherwise valid. Users are cautioned on the use of this
662 option, as it removes validation of packet integrity in a number of
663 circumstances. However, it is unlikely to be an issue in most situa‐
664 tions. Those hitting this issue may see "connection timeout", "session
665 timeout", or "password verification timeout" errors. On IPMI 1.5 con‐
666 nections, the "noauthcodecheck" workaround may also needed too. Issue
667 observed on Supermicro X9SCM-iiF, Supermicro X9DRi-F, and Supermicro
668 X9DRFR.
669 idzero - This workaround flag will allow empty session IDs to be
671 accepted by the client. It works around IPMI sessions that report empty
672 session IDs to the client. Those hitting this issue may see "session
673 timeout" errors. Issue observed on Tyan S2882 with M3289 BMC.
674 unexpectedauth - This workaround flag will allow unexpected non-null
676 authcodes to be checked as though they were expected. It works around
677 an issue when packets contain non-null authentication data when they
678 should be null due to disabled per-message authentication. Those hit‐
679 ting this issue may see "session timeout" errors. Issue observed on
680 Dell PowerEdge 2850,SC1425. Confirmed fixed on newer firmware.
681 forcepermsg - This workaround flag will force per-message authentica‐
683 tion to be used no matter what is advertised by the remote system. It
684 works around an issue when per-message authentication is advertised as
685 disabled on the remote system, but it is actually required for the pro‐
686 tocol. Those hitting this issue may see "session timeout" errors.
687 Issue observed on IBM eServer 325.
688 endianseq - This workaround flag will flip the endian of the session
690 sequence numbers to allow the session to continue properly. It works
691 around IPMI 1.5 session sequence numbers that are the wrong endian.
692 Those hitting this issue may see "session timeout" errors. Issue
693 observed on some Sun ILOM 1.0/2.0 (depends on service processor
694 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"
718 errors. 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, and Quanta
737 QSSC-S4R/Appro GB812X-CN. This workaround is automatically triggered
738 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
742 using 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
745 Supermicro 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 numer of SDR records have been read.
750 This will work around systems that have mis-implemented SDR reading
751 functions that. 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 HP Proliant DL 145.
766
768 The following motherboards are confirmed to have atleast some support
769 by the --interpret-oem-data option. While highly probable the OEM data
770 interpretations would work across other motherboards by the same manu‐
771 facturer, there are no guarantees. Some of the motherboards below may
772 be rebranded by vendors/distributors.
773 Dell Poweredge 2900, Dell Poweredge 2950, Dell Poweredge R610, Dell
775 Poweredge R710, Fujitsu iRMC S1 and iRMC S2 systems, Gigabyte
776 MD90-FS0-ZB, Intel S5500WB/Penguin Computing Relion 700, Intel
777 S2600JF/Appro 512X, Intel S5000PAL, Intel Windmill, Intel S2600KP,
778 Intel S2600KPR, Intel S2600WT2, Intel S2600WTT, Inventec 5441/Dell
779 Xanadu II, Inventec 5442/Dell Xanadu III, Quanta S99Q/Dell FS12-TY,
780 Quanta QSSC-S4R/Appro GB812X-CN, Quanta Winterfell, Sun X4140 Supermi‐
781 cro X7DBR-3, Supermicro X7DB8, Supermicro X8DTN, Supermicro X7SBI-LN4,
782 Supermicro X8DTH, Supermicro X8DTG, Supermicro X8DTU, Supermicro
783 X8DT3-LN4F, Supermicro X8DTU-6+, Supermicro X8DTL, Supermicro X8DTL-3F,
784 Supermicro X8SIL-F, Supermicro X9SCL, Supermicro X9SCM, Supermicro
785 X8DTN+-F, Supermicro X8SIE, Supermicro X9SCA-F-O, Supermicro H8DGU-F,
786 Supermicro X9DRi-F, Supermicro X9DRI-LN4F+, Supermicro X9SPU-F-O,
787 Supermicro X9SCM-iiF, Wiwynn Windmill, Wistron/Dell Poweredge C6220.
788
790 # ipmi-sel
791 Show all SEL records on the local machine.
793 # ipmi-sel -h ahost -u myusername -p mypassword
795 Show all SEL records of a remote machine using IPMI over LAN.
797 # ipmi-sel -h mycluster[0-127] -u myusername -p mypassword
799 Show all SEL records across a cluster using IPMI over LAN.
801 # ipmi-sel --delete=44,82
803 Delete SEL records 44 and 82 on the local machine.
805 # ipmi-sel --delete-all
807 Delete all SEL entries on the local machine.
809 # ipmi-sel --delete-range=12-42
811 Delete SEL entries in the range 12 to 42 on the local machine.
813
815 Upon successful execution, exit status is 0. On error, exit status is
816 1.
817 If multiple hosts are specified for communication, the exit status is 0
819 if and only if all targets successfully execute. Otherwise the exit
820 status is 1.
821
823 On older operating systems, if you input your username, password, and
824 other potentially security relevant information on the command line,
825 this information may be discovered by other users when using tools like
826 the ps(1) command or looking in the /proc file system. It is generally
827 more secure to input password information with options like the -P or
828 -K options. Configuring security relevant information in the FreeIPMI
829 configuration file would also be an appropriate way to hide this infor‐
830 mation.
831 In order to prevent brute force attacks, some BMCs will temporarily
833 "lock up" after a number of remote authentication errors. You may need
834 to wait awhile in order to this temporary "lock up" to pass before you
835 may authenticate again.
836
838 Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
839
841 Copyright © 2003-2015 FreeIPMI Core Team.
842 This program is free software; you can redistribute it and/or modify it
844 under the terms of the GNU General Public License as published by the
845 Free Software Foundation; either version 3 of the License, or (at your
846 option) any later version.
847
849 freeipmi(7), bmc-device(8), ipmiseld(8), ipmi-config(8),
850 freeipmi_interpret_sel.conf(5)
851 http://www.gnu.org/software/freeipmi/
853ipmi-sel 1.5.7 2018-04-11 IPMI-SEL(8)