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.
15 Some timestamps in the SEL may report a date of 1-Jan-1970. This time‐
17 stamp is not necessarily incorrect. It usually indicates a hardware
18 event that occurred before a timestamp in firmware has been initial‐
19 ized. For example, certain hardware components will have their internal
20 clocks reset during a power cycle.
21 Listed below are general IPMI options, tool specific options, trouble
23 shooting information, workaround information, examples, and known
24 issues. For a general introduction to FreeIPMI please see freeipmi(7).
25 To perform some advanced SEL management, please see bmc-device(8).
26
28 The following options are general options for configuring IPMI communi‐
29 cation and executing general tool commands.
30 -D, --driver-type=IPMIDRIVER
32 Specify the driver type to use instead of doing an auto selec‐
33 tion. The currently available outofband drivers are LAN and
34 LAN_2_0, which perform IPMI 1.5 and IPMI 2.0 respectively. The
35 currently available inband drivers are KCS, SSIF, OPENIPMI, and
36 SUNBMC.
37 --disable-auto-probe
39 Do not probe in-band IPMI devices for default settings.
40 --driver-address=DRIVER-ADDRESS
42 Specify the in-band driver address to be used instead of the
43 probed value. DRIVER-ADDRESS should be prefixed with "0x" for a
44 hex value and '0' for an octal value.
45 --driver-device=DEVICE
47 Specify the in-band driver device path to be used instead of the
48 probed path.
49 --register-spacing=REGISTER-SPACING
51 Specify the in-band driver register spacing instead of the
52 probed value.
53 -h, --hostname=IPMIHOST1,IPMIHOST2,...
55 Specify the remote host(s) to communicate with. Multiple host‐
56 names may be separated by comma or may be specified in a range
57 format; see HOSTRANGED SUPPORT below.
58 -u, --username=USERNAME
60 Specify the username to use when authenticating with the remote
61 host. If not specified, a null (i.e. anonymous) username is
62 assumed. The user must have atleast USER privileges in order for
63 this tool to operate fully.
64 -p, --password=PASSWORD
66 Specify the password to use when authenticationg with the remote
67 host. If not specified, a null password is assumed. Maximum
68 password length is 16 for IPMI 1.5 and 20 for IPMI 2.0.
69 -P, --password-prompt
71 Prompt for password to avoid possibility of listing it in
72 process lists.
73 -k, --k-g=K_G
75 Specify the K_g BMC key to use when authenticating with the
76 remote host for IPMI 2.0. If not specified, a null key is
77 assumed. To input the key in hexadecimal form, prefix the string
78 with '0x'. E.g., the key 'abc' can be entered with the either
79 the string 'abc' or the string '0x616263'
80 -K, --k-g-prompt
82 Prompt for k-g to avoid possibility of listing it in process
83 lists.
84 --session-timeout=MILLISECONDS
86 Specify the session timeout in milliseconds. Defaults to 20000
87 milliseconds (20 seconds) if not specified.
88 --retransmission-timeout=MILLISECONDS
90 Specify the packet retransmission timeout in milliseconds.
91 Defaults to 1000 milliseconds (1 second) if not specified. The
92 retransmission timeout cannot be larger than the session time‐
93 out.
94 -a, --authentication-type=AUTHENTICATION-TYPE
96 Specify the IPMI 1.5 authentication type to use. The currently
97 available authentication types are NONE, STRAIGHT_PASSWORD_KEY,
98 MD2, and MD5. Defaults to MD5 if not specified.
99 -I, --cipher-suite-id=CIPHER-SUITE-ID
101 Specify the IPMI 2.0 cipher suite ID to use. The Cipher Suite ID
102 identifies a set of authentication, integrity, and confidential‐
103 ity algorithms to use for IPMI 2.0 communication. The authenti‐
104 cation algorithm identifies the algorithm to use for session
105 setup, the integrity algorithm identifies the algorithm to use
106 for session packet signatures, and the confidentiality algorithm
107 identifies the algorithm to use for payload encryption. Defaults
108 to cipher suite ID 3 if not specified. The following cipher
109 suite ids are currently supported:
110 0 - Authentication Algorithm = None; Integrity Algorithm = None;
112 Confidentiality Algorithm = None
113 1 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
115 None; Confidentiality Algorithm = None
116 2 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
118 HMAC-SHA1-96; Confidentiality Algorithm = None
119 3 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
121 HMAC-SHA1-96; Confidentiality Algorithm = AES-CBC-128
122 6 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
124 None; Confidentiality Algorithm = None
125 7 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
127 HMAC-MD5-128; Confidentiality Algorithm = None
128 8 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
130 HMAC-MD5-128; Confidentiality Algorithm = AES-CBC-128
131 11 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
133 MD5-128; Confidentiality Algorithm = None
134 12 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
136 MD5-128; Confidentiality Algorithm = AES-CBC-128
137 -l, --privilege-level=PRIVILEGE-LEVEL
139 Specify the privilege level to be used. The currently available
140 privilege levels are USER, OPERATOR, and ADMIN. Defaults to
141 OPERATOR if not specified.
142 --config-file=FILE
144 Specify an alternate configuration file.
145 -W, --workaround-flags=WORKAROUNDS
147 Specify workarounds to vendor compliance issues. Multiple work‐
148 arounds can be specified separated by commas. See WORKAROUNDS
149 below for a list of available workarounds.
150 --debug
152 Turn on debugging.
153 -?, --help
155 Output a help list and exit.
156 --usage
158 Output a usage message and exit.
159 -V, --version
161 Output the program version and exit.
162
164 The following options are specific to Ipmi-sel.
165 -v Output verbose output. This option will output event direction.
167 -vv Output very verbose output. This option will output additional
169 information than verbose output. Most notably it will output
170 additional hex codes to given information on ambiguous SEL
171 entries. For example, it will output Generator ID hex codes for
172 sensors without names.
173 -i, --info
175 Show general information about the SEL.
176 --display=REC-LIST
178 Display SEL records by record id. Accepts space or comma sepa‐
179 rated lists.
180 --exclude-display=REC-LIST
182 Exclude display of SEL records by record id. Accepts space or
183 comma separated lists.
184 --display-range=START-END
186 Display SEL records from record id START to END.
187 --exclude-display-range=START-END
189 Exclude display of SEL records from record id START to END.
190 --tail=count
192 Display approximately the last count SEL records. The display
193 count is calculated by approximating the record ids of the last
194 SEL records. It's correctness depends highly on the SEL imple‐
195 mentation by the vendor.
196 --clear
198 Clear SEL.
199 --delete=REC-LIST
201 Delete records by record id in the SEL. Accepts space or comma
202 separated lists.
203 --delete-range=START-END
205 Delete record ids from START to END in the SEL.
206 --system-event-only
208 Output only system event records (i.e. don't output OEM
209 records).
210 --oem-only
212 Output only OEM event records.
213 --hex-dump
215 Hex-dump SEL entries.
216 --assume-system-event-records
218 Some motherboards have invalid SEL record types listed, leading
219 to errors such as 'Unknown SEL Record Type'. The records may
220 actually be formatted correctly. Use this option to assume these
221 invalid record types are system event records and pray for the
222 best. This option is confirmed to work around compliances issues
223 on HP DL 380 G5 motherboards.
224 --interpret-oem-data
226 Attempt to interpret OEM data, such as event data, sensor read‐
227 ings, or general extra info, etc. If an OEM interpretation is
228 not available, the default output will be generated. Correctness
229 of OEM interpretations cannot be guaranteed due to potential
230 changes OEM vendors may make in products, firmware, etc. See OEM
231 INTERPRETATION below for confirmed supported motherboard inter‐
232 pretations.
233 --entity-sensor-names
235 Output sensor names prefixed with their entity id and instance
236 number when appropriate. This may be necessary on some mother‐
237 boards to help identify what sensors are referencing. For exam‐
238 ple, a motherboard may have multiple sensors named 'TEMP'. The
239 entity id and instance number may help clarify which sensor
240 refers to "Processor 1" vs. "Processor 2".
241 --no-sensor-type-output
243 Do not show sensor type output for each entry. On many systems,
244 the sensor type is redundant to the name of the sensor. This can
245 especially be true if --entity-sensor-names is specified. If
246 the sensor name is sufficient, or if the sensor type is of no
247 interest to the user, this option can be specified to condense
248 output.
249 --comma-separated-output
251 Output fields in comma separated format.
252 --no-header-output
254 Do not output column headers. May be useful in scripting.
255 --non-abbreviated-units
257 Output non-abbreviated units (e.g. 'Amps' instead of 'A'). May
258 aid in disambiguation of units (e.g. 'C' for Celsius or
259 Coulombs).
260 --legacy-output
262 Output in legacy format. Newer options may not be applicable to
263 leagcy output.
264
266 This tool requires access to the sensor data repository (SDR) cache for
267 general operation. By default, SDR data will be downloaded and cached
268 on the local machine. The following options apply to the SDR cache.
269 -f, --flush-cache
271 Flush a cached version of the sensor data repository (SDR)
272 cache. The SDR is typically cached for faster subsequent access.
273 However, it may need to be flushed and re-generated if the SDR
274 has been updated on a system.
275 -Q, --quiet-cache
277 Do not output information about cache creation/deletion. May be
278 useful in scripting.
279 --sdr-cache-directory=DIRECTORY
281 Specify an alternate directory for sensor data repository (SDR)
282 caches to be stored or read from. Defaults to the home directory
283 if not specified.
284 --sdr-cache-recreate
286 If the SDR cache is out of date or invalid, automatically recre‐
287 ate the sensor data repository (SDR) cache. This option may be
288 useful for scripting purposes.
289 --ignore-sdr-cache
291 Ignore SDR cache related processing. May lead to incomplete or
292 less useful information being output, however it will allow
293 functionality for those systems without SDRs.
294
296 The following options manipulate hostranged output. See HOSTRANGED SUP‐
297 PORT below for additional information on hostranges.
298 -B, --buffer-output
300 Buffer hostranged output. For each node, buffer standard output
301 until the node has completed its IPMI operation. When specifying
302 this option, data may appear to output slower to the user since
303 the the entire IPMI operation must complete before any data can
304 be output. See HOSTRANGED SUPPORT below for additional informa‐
305 tion.
306 -C, --consolidate-output
308 Consolidate hostranged output. The complete standard output from
309 every node specified will be consolidated so that nodes with
310 identical output are not output twice. A header will list those
311 nodes with the consolidated output. When this option is speci‐
312 fied, no output can be seen until the IPMI operations to all
313 nodes has completed. If the user breaks out of the program
314 early, all currently consolidated output will be dumped. See
315 HOSTRANGED SUPPORT below for additional information.
316 -F, --fanout
318 Specify multiple host fanout. A "sliding window" (or fanout)
319 algorithm is used for parallel IPMI communication so that slower
320 nodes or timed out nodes will not impede parallel communication.
321 The maximum number of threads available at the same time is lim‐
322 ited by the fanout. The default is 64.
323 -E, --eliminate
325 Eliminate hosts determined as undetected by ipmidetect. This
326 attempts to remove the common issue of hostranged execution tim‐
327 ing out due to several nodes being removed from service in a
328 large cluster. The ipmidetectd daemon must be running on the
329 node executing the command.
330 --always-prefix
332 Always prefix output, even if only one host is specified or com‐
333 municating in-band. This option is primarily useful for script‐
334 ing purposes. Option will be ignored if specified with the -C
335 option.
336
338 Multiple hosts can be input either as an explicit comma separated lists
339 of hosts or a range of hostnames in the general form: prefix[n-m,l-
340 k,...], where n < m and l < k, etc. The later form should not be con‐
341 fused with regular expression character classes (also denoted by []).
342 For example, foo[19] does not represent foo1 or foo9, but rather repre‐
343 sents a degenerate range: foo19.
344 This range syntax is meant only as a convenience on clusters with a
346 prefixNN naming convention and specification of ranges should not be
347 considered necessary -- the list foo1,foo9 could be specified as such,
348 or by the range foo[1,9].
349 Some examples of range usage follow:
351 foo[01-05] instead of foo01,foo02,foo03,foo04,foo05
352 foo[7,9-10] instead of foo7,foo9,foo10
353 foo[0-3] instead of foo0,foo1,foo2,foo3
354 As a reminder to the reader, some shells will interpret brackets ([ and
356 ]) for pattern matching. Depending on your shell, it may be necessary
357 to enclose ranged lists within quotes.
358 When multiple hosts are specified by the user, a thread will be exe‐
360 cuted for each host in parallel up to the configured fanout (which can
361 be adjusted via the -F option). This will allow communication to large
362 numbers of nodes far more quickly than if done in serial.
363 By default, standard output from each node specified will be output
365 with the hostname prepended to each line. Although this output is read‐
366 able in many situations, it may be difficult to read in other situa‐
367 tions. For example, output from multiple nodes may be mixed together.
368 The -B and -C options can be used to change this default.
369 In-band IPMI Communication will be used when the host "localhost" is
371 specified. This allows the user to add the localhost into the hos‐
372 tranged output.
373
375 Most often, IPMI problems are due to configuration problems. Inband
376 IPMI problems are typically caused by improperly configured drivers or
377 non-standard BMCs. IPMI over LAN problems involve a misconfiguration of
378 the remote machine's BMC. Double check to make sure the following are
379 configured properly in the remote machine's BMC: IP address, MAC
380 address, subnet mask, username, user enablement, user privilege, pass‐
381 word, LAN privilege, LAN enablement, and allowed authentication
382 type(s). For IPMI 2.0 connections, double check to make sure the cipher
383 suite privilege(s) and K_g key are configured properly. The bmc-con‐
384 fig(8) tool can be used to check and/or change these configuration set‐
385 tings.
386 The following are common issues for given error messages:
388 "username invalid" - The username entered (or a NULL username if none
390 was entered) is not available on the remote machine. It may also be
391 possible the remote BMC's username configuration is incorrect.
392 "password invalid" - The password entered (or a NULL password if none
394 was entered) is not correct. It may also be possible the password for
395 the user is not correctly configured on the remote BMC.
396 "password verification timeout" - Password verification has timed out.
398 A "password invalid" error (described above) or a generic "session
399 timeout" (described below) occurred. During this point in the protocol
400 it cannot be differentiated which occurred.
401 "k_g invalid" - The K_g key entered (or a NULL K_g key if none was
403 entered) is not correct. It may also be possible the K_g key is not
404 correctly configured on the remote BMC.
405 "privilege level insufficient" - An IPMI command requires a higher user
407 privilege than the one authenticated with. Please try to authenticate
408 with a higher privilege. This may require authenticating to a different
409 user which has a higher maximum privilege.
410 "privilege level cannot be obtained for this user" - The privilege
412 level you are attempting to authenticate with is higher than the maxi‐
413 mum allowed for this user. Please try again with a lower privilege. It
414 may also be possible the maximum privilege level allowed for a user is
415 not configured properly on the remote BMC.
416 "authentication type unavailable for attempted privilege level" - The
418 authentication type you wish to authenticate with is not available for
419 this privilege level. Please try again with an alternate authentication
420 type or alternate privilege level. It may also be possible the avail‐
421 able authentication types you can authenticate with are not correctly
422 configured on the remote BMC.
423 "cipher suite id unavailable" - The cipher suite id you wish to authen‐
425 ticate with is not available on the remote BMC. Please try again with
426 an alternate cipher suite id. It may also be possible the available
427 cipher suite ids are not correctly configured on the remote BMC.
428 "ipmi 2.0 unavailable" - IPMI 2.0 was not discovered on the remote
430 machine. Please try to use IPMI 1.5 instead.
431 "connection timeout" - Initial IPMI communication failed. A number of
433 potential errors are possible, including an invalid hostname specified,
434 an IPMI IP address cannot be resolved, IPMI is not enabled on the
435 remote server, the network connection is bad, etc. Please verify con‐
436 figuration and connectivity.
437 "session timeout" - The IPMI session has timed out. Please reconnect.
439 If this error occurs often, you may wish to increase the retransmission
440 timeout. Some remote BMCs are considerably slower than others.
441 "device not found" - The specified device could not be found. Please
443 check configuration or inputs and try again.
444 "driver timeout" - Communication with the driver or device has timed
446 out. Please try again.
447 "message timeout" - Communication with the driver or device has timed
449 out. Please try again.
450 "BMC busy" - The BMC is currently busy. It may be processing informa‐
452 tion or have too many simultaneous sessions to manage. Please wait and
453 try again.
454 "could not find inband device" - An inband device could not be found.
456 Please check configuration or specify specific device or driver on the
457 command line.
458 Please see WORKAROUNDS below to also if there are any vendor specific
460 bugs that have been discovered and worked around.
461
463 With so many different vendors implementing their own IPMI solutions,
464 different vendors may implement their IPMI protocols incorrectly. The
465 following lists the workarounds currently available to handle discov‐
466 ered compliance issues.
467 When possible, workarounds have been implemented so they will be trans‐
469 parent to the user. However, some will require the user to specify a
470 workaround be used via the -W option.
471 The hardware listed below may only indicate the hardware that a problem
473 was discovered on. Newer versions of hardware may fix the problems
474 indicated below. Similar machines from vendors may or may not exhibit
475 the same problems. Different vendors may license their firmware from
476 the same IPMI firmware developer, so it may be worthwhile to try work‐
477 arounds listed below even if your motherboard is not listed.
478 "idzero" - This workaround option will allow empty session IDs to be
480 accepted by the client. It works around IPMI sessions that report empty
481 session IDs to the client. Those hitting this issue may see "session
482 timeout" errors. Issue observed on Tyan S2882 with M3289 BMC.
483 "unexpectedauth" - This workaround option will allow unexpected non-
485 null authcodes to be checked as though they were expected. It works
486 around an issue when packets contain non-null authentication data when
487 they should be null due to disabled per-message authentication. Those
488 hitting this issue may see "session timeout" errors. Issue observed on
489 Dell PowerEdge 2850,SC1425. Confirmed fixed on newer firmware.
490 "forcepermsg" - This workaround option will force per-message authenti‐
492 cation to be used no matter what is advertised by the remote system. It
493 works around an issue when per-message authentication is advertised as
494 disabled on the remote system, but it is actually required for the pro‐
495 tocol. Those hitting this issue may see "session timeout" errors.
496 Issue observed on IBM eServer 325.
497 "endianseq" - This workaround option will flip the endian of the ses‐
499 sion sequence numbers to allow the session to continue properly. It
500 works around IPMI 1.5 session sequence numbers that are the wrong
501 endian. Those hitting this issue may see "session timeout" errors.
502 Issue observed on some Sun ILOM 1.0/2.0 (depends on service processor
503 endian).
504 "authcap" - This workaround option will skip early checks for username
506 capabilities, authentication capabilities, and K_g support and allow
507 IPMI authentication to succeed. It works around multiple issues in
508 which the remote system does not properly report username capabilities,
509 authentication capabilities, or K_g status. Those hitting this issue
510 may see "username invalid", "authentication type unavailable for
511 attempted privilege level", or "k_g invalid" errors. Issue observed on
512 Asus P5M2/P5MT-R/RS162-E4/RX4, Intel SR1520ML/X38ML, and Sun Fire
513 2200/4150/4450 with ELOM.
514 "intel20" - This workaround option will work around several Intel IPMI
516 2.0 authentication issues. The issues covered include padding of user‐
517 names, automatic acceptance of a RAKP 4 response integrity check when
518 using the integrity algorithm MD5-128, and password truncation if the
519 authentication algorithm is HMAC-MD5-128. Those hitting this issue may
520 see "username invalid", "password invalid", or "k_g invalid" errors.
521 Issue observed on Intel SE7520AF2 with Intel Server Management Module
522 (Professional Edition).
523 "supermicro20" - This workaround option will work around several Super‐
525 micro IPMI 2.0 authentication issues on motherboards w/ Peppercon IPMI
526 firmware. The issues covered include handling invalid length authenti‐
527 cation codes. Those hitting this issue may see "password invalid"
528 errors. Issue observed on Supermicro H8QME with SIMSO daughter card.
529 Confirmed fixed on newerver firmware.
530 "sun20" - This workaround option will work work around several Sun IPMI
532 2.0 authentication issues. The issues covered include invalid lengthed
533 hash keys, improperly hashed keys, and invalid cipher suite records.
534 Those hitting this issue may see "password invalid" or "bmc error"
535 errors. Issue observed on Sun Fire 4100/4200/4500 with ILOM. This
536 workaround automatically includes the "opensesspriv" workaround.
537 "opensesspriv" - This workaround option will slightly alter FreeIPMI's
539 IPMI 2.0 connection protocol to workaround an invalid hashing algorithm
540 used by the remote system. The privilege level sent during the Open
541 Session stage of an IPMI 2.0 connection is sometimes invalid and used
542 for hashing keys instead of the privilege level sent during the RAKP1
543 connection stage. Those hitting this issue may see "password invalid",
544 "k_g invalid", "bad rmcpplus status code", or "privilege level cannot
545 be obtained for this user " errors. Issue observed on Sun Fire
546 4100/4200/4500 with ILOM, Inventec 5441/Dell Xanadu II, Supermicro
547 X8DTH, Supermicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin
548 Relion 700. This workaround is automatically triggered with the "sun20"
549 workaround.
550 "integritycheckvalue" - This workaround option will work around an
552 invalid integrity check value during an IPMI 2.0 session establishment
553 when using Cipher Suite ID 0. The integrity check value should be 0
554 length, however the remote motherboard responds with a non-empty field.
555 Those hitting this issue may see "k_g invalid" errors. Issue observed
556 on Supermicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin
557 Relion 700.
558 "assumesystemevent" - This workaround option will assume invalid SEL
560 record types are system event records. Records may be formatted cor‐
561 rectly but report invalid record types. Those hitting this issue may
562 see "Unknown SEL Record Type" errors. Output may be unknown, pray for
563 the best. This option is confirmed to work around compliances issues on
564 HP DL 380 G5 motherboards. This option is identical to using the
565 --assume-system-event-records option above.
566
568 The following motherboards are confirmed to have atleast some support
569 by the --interpret-oem-data option. While highly probable the OEM data
570 interpretations would work across other motherboards by the same manu‐
571 facturer, there are no guarantees.
572 Inventec 5441/Dell Xanadu II, Inventec 5442/Dell Xanadu III, Dell Pow‐
574 eredge 2900, Dell Poweredge 2950, Dell Poweredge R610, Dell Poweredge
575 R710, Sun X4140, Quanta S99Q/Dell FS12-TY
576
578 # ipmi-sel
579 Show all SEL records on the local machine.
581 # ipmi-sel -h ahost -u myusername -p mypassword
583 Show all SEL records of a remote machine using IPMI over LAN.
585 # ipmi-sel -h mycluster[0-127] -u myusername -p mypassword
587 Show all SEL records across a cluster using IPMI over LAN.
589 # ipmi-sel --delete=44,82
591 Delete SEL records 44 and 82 on the local machine.
593 # ipmi-sel --delete-all
595 Delete all SEL entries on the local machine.
597 # ipmi-sel --delete-range=12-42
599 Delete SEL entries in the range 12 to 42 on the local machine.
601
603 On older operating systems, if you input your username, password, and
604 other potentially security relevant information on the command line,
605 this information may be discovered by other users when using tools like
606 the ps(1) command or looking in the /proc file system. It is generally
607 more secure to input password information with options like the -P or
608 -K options. Configuring security relevant information in the FreeIPMI
609 configuration file would also be an appropriate way to hide this infor‐
610 mation.
611 In order to prevent brute force attacks, some BMCs will temporarily
613 "lock up" after a number of remote authentication errors. You may need
614 to wait awhile in order to this temporary "lock up" to pass before you
615 may authenticate again.
616
618 Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
619
621 Copyright © 2003-2010 FreeIPMI Core Team.
622 This program is free software; you can redistribute it and/or modify it
624 under the terms of the GNU General Public License as published by the
625 Free Software Foundation; either version 2 of the License, or (at your
626 option) any later version.
627
629 freeipmi(7), bmc-config(8), bmc-device(8)
630 http://www.gnu.org/software/freeipmi/
632ipmi-sel 0.8.8 2010-07-21 IPMI-SEL(8)