1IPMI-FRU(8) System Commands IPMI-FRU(8)
2
6 ipmi-fru - display FRU information
7
9 ipmi-fru [OPTION...]
10
12 Ipmi-fru displays Field Replaceable Unit (FRU) Information. The FRU may
13 hold a variety of information, such as device information, hardware
14 information, serial numbers, and part numbers.
15 Listed below are general IPMI options, tool specific options, trouble
17 shooting information, workaround information, examples, and known
18 issues. For a general introduction to FreeIPMI please see freeipmi(7).
19
21 The following options are general options for configuring IPMI communi‐
22 cation and executing general tool commands.
23 -D IPMIDRIVER, --driver-type=IPMIDRIVER
25 Specify the driver type to use instead of doing an auto selec‐
26 tion. The currently available outofband drivers are LAN and
27 LAN_2_0, which perform IPMI 1.5 and IPMI 2.0 respectively. The
28 currently available inband drivers are KCS, SSIF, OPENIPMI,
29 SUNBMC, and INTELDCMI.
30 --disable-auto-probe
32 Do not probe in-band IPMI devices for default settings.
33 --driver-address=DRIVER-ADDRESS
35 Specify the in-band driver address to be used instead of the
36 probed value. DRIVER-ADDRESS should be prefixed with "0x" for a
37 hex value and '0' for an octal value.
38 --driver-device=DEVICE
40 Specify the in-band driver device path to be used instead of the
41 probed path.
42 --register-spacing=REGISTER-SPACING
44 Specify the in-band driver register spacing instead of the
45 probed value. Argument is in bytes (i.e. 32bit register spacing
46 = 4)
47 --target-channel-number=CHANNEL-NUMBER
49 Specify the in-band driver target channel number to send IPMI
50 requests to.
51 --target-slave-address=SLAVE-ADDRESS
53 Specify the in-band driver target slave number to send IPMI
54 requests to.
55 -h IPMIHOST1,IPMIHOST2,..., --hostname=IPMIHOST1[:PORT],IPMI‐
57 HOST2[:PORT],...
58 Specify the remote host(s) to communicate with. Multiple host‐
59 names may be separated by comma or may be specified in a range
60 format; see HOSTRANGED SUPPORT below. An optional port can be
61 specified with each host, which may be useful in port forwarding
62 or similar situations. If specifying an IPv6 address and port,
63 use the format [ADDRESS]:PORT.
64 -u USERNAME, --username=USERNAME
66 Specify the username to use when authenticating with the remote
67 host. If not specified, a null (i.e. anonymous) username is
68 assumed. The user must have atleast USER privileges in order for
69 this tool to operate fully.
70 -p PASSWORD, --password=PASSWORD
72 Specify the password to use when authenticationg with the remote
73 host. If not specified, a null password is assumed. Maximum
74 password length is 16 for IPMI 1.5 and 20 for IPMI 2.0.
75 -P, --password-prompt
77 Prompt for password to avoid possibility of listing it in
78 process lists.
79 -k K_G, --k-g=K_G
81 Specify the K_g BMC key to use when authenticating with the
82 remote host for IPMI 2.0. If not specified, a null key is
83 assumed. To input the key in hexadecimal form, prefix the string
84 with '0x'. E.g., the key 'abc' can be entered with the either
85 the string 'abc' or the string '0x616263'
86 -K, --k-g-prompt
88 Prompt for k-g to avoid possibility of listing it in process
89 lists.
90 --session-timeout=MILLISECONDS
92 Specify the session timeout in milliseconds. Defaults to 20000
93 milliseconds (20 seconds) if not specified.
94 --retransmission-timeout=MILLISECONDS
96 Specify the packet retransmission timeout in milliseconds.
97 Defaults to 1000 milliseconds (1 second) if not specified. The
98 retransmission timeout cannot be larger than the session time‐
99 out.
100 -a AUTHENTICATION-TYPE, --authentication-type=AUTHENTICATION-TYPE
102 Specify the IPMI 1.5 authentication type to use. The currently
103 available authentication types are NONE, STRAIGHT_PASSWORD_KEY,
104 MD2, and MD5. Defaults to MD5 if not specified.
105 -I CIPHER-SUITE-ID, --cipher-suite-id=CIPHER-SUITE-ID
107 Specify the IPMI 2.0 cipher suite ID to use. The Cipher Suite ID
108 identifies a set of authentication, integrity, and confidential‐
109 ity algorithms to use for IPMI 2.0 communication. The authenti‐
110 cation algorithm identifies the algorithm to use for session
111 setup, the integrity algorithm identifies the algorithm to use
112 for session packet signatures, and the confidentiality algorithm
113 identifies the algorithm to use for payload encryption. Defaults
114 to cipher suite ID 3 if not specified. The following cipher
115 suite ids are currently supported:
116 0 - Authentication Algorithm = None; Integrity Algorithm = None;
118 Confidentiality Algorithm = None
119 1 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
121 None; Confidentiality Algorithm = None
122 2 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
124 HMAC-SHA1-96; Confidentiality Algorithm = None
125 3 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
127 HMAC-SHA1-96; Confidentiality Algorithm = AES-CBC-128
128 6 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
130 None; Confidentiality Algorithm = None
131 7 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
133 HMAC-MD5-128; Confidentiality Algorithm = None
134 8 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
136 HMAC-MD5-128; Confidentiality Algorithm = AES-CBC-128
137 11 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
139 MD5-128; Confidentiality Algorithm = None
140 12 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
142 MD5-128; Confidentiality Algorithm = AES-CBC-128
143 15 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
145 = None; Confidentiality Algorithm = None
146 16 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
148 = HMAC_SHA256_128; Confidentiality Algorithm = None
149 17 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
151 = HMAC_SHA256_128; Confidentiality Algorithm = AES-CBC-128
152 -l PRIVILEGE-LEVEL, --privilege-level=PRIVILEGE-LEVEL
154 Specify the privilege level to be used. The currently available
155 privilege levels are USER, OPERATOR, and ADMIN. Defaults to USER
156 if not specified.
157 --config-file=FILE
159 Specify an alternate configuration file.
160 -W WORKAROUNDS, --workaround-flags=WORKAROUNDS
162 Specify workarounds to vendor compliance issues. Multiple work‐
163 arounds can be specified separated by commas. A special command
164 line flag of "none", will indicate no workarounds (may be useful
165 for overriding configured defaults). See WORKAROUNDS below for a
166 list of available workarounds.
167 --debug
169 Turn on debugging.
170 -?, --help
172 Output a help list and exit.
173 --usage
175 Output a usage message and exit.
176 -V, --version
178 Output the program version and exit.
179
181 The following options are specific to ipmi-fru.
182 -e, --device-id=IDNUM
184 Specify a specific FRU device ID.
185 -v, --verbose
187 Increase verbosity in output to include additional output.
188 --bridge-fru
190 By default, FRU entries on other satellite controllers will not
191 be read by default. Bridging may not work on some inter‐
192 faces/driver types.
193 --interpret-oem-data
195 Attempt to interpret OEM data, such as event data, sensor read‐
196 ings, or general extra info, etc. If an OEM interpretation is
197 not available, the default output will be generated. Correctness
198 of OEM interpretations cannot be guaranteed due to potential
199 changes OEM vendors may make in products, firmware, etc. See OEM
200 INTERPRETATION below for confirmed supported motherboard inter‐
201 pretations.
202 --fru-file=FILENAME
204 Output data from the specified FRU binary file instead of read‐
205 ing FRU data off of a board.
206
208 This tool requires access to the sensor data repository (SDR) cache for
209 general operation. By default, SDR data will be downloaded and cached
210 on the local machine. The following options apply to the SDR cache.
211 --flush-cache
213 Flush a cached version of the sensor data repository (SDR)
214 cache. The SDR is typically cached for faster subsequent access.
215 However, it may need to be flushed and re-generated if the SDR
216 has been updated on a system.
217 --quiet-cache
219 Do not output information about cache creation/deletion. May be
220 useful in scripting.
221 --sdr-cache-recreate
223 If the SDR cache is out of date or invalid, automatically recre‐
224 ate the sensor data repository (SDR) cache. This option may be
225 useful for scripting purposes.
226 --sdr-cache-file=FILE
228 Specify a specific sensor data repository (SDR) cache file to be
229 stored or read from. If this option is used when multiple hosts
230 are specified, the same SDR cache file will be used for all
231 hosts.
232 --sdr-cache-directory=DIRECTORY
234 Specify an alternate directory for sensor data repository (SDR)
235 caches to be stored or read from. Defaults to the home directory
236 if not specified.
237 --ignore-sdr-cache
239 Ignore SDR cache related processing. May lead to incomplete or
240 less useful information being output, however it will allow
241 functionality for systems without SDRs or when the correct SDR
242 cannot be loaded.
243
245 By IPMI definition, all IPMI times and timestamps are stored in local‐
246 time. However, in many situations, the timestamps will not be stored in
247 localtime. Whether or not a system truly stored the timestamps in
248 localtime varies on many factors, such as the vendor, BIOS, and operat‐
249 ing system. The following options will allow the user to adjust the
250 interpretation of the stored timestamps and how they should be output.
251 --utc-to-localtime
253 Assume all times are reported in UTC time and convert the time
254 to localtime before being output.
255 --localtime-to-utc
257 Convert all localtime timestamps to UTC before being output.
258 --utc-offset=SECONDS
260 Specify a specific UTC offset in seconds to be added to time‐
261 stamps. Value can range from -86400 to 86400 seconds. Defaults
262 to 0.
263
265 The following options manipulate hostranged output. See HOSTRANGED SUP‐
266 PORT below for additional information on hostranges.
267 -B, --buffer-output
269 Buffer hostranged output. For each node, buffer standard output
270 until the node has completed its IPMI operation. When specifying
271 this option, data may appear to output slower to the user since
272 the the entire IPMI operation must complete before any data can
273 be output. See HOSTRANGED SUPPORT below for additional informa‐
274 tion.
275 -C, --consolidate-output
277 Consolidate hostranged output. The complete standard output from
278 every node specified will be consolidated so that nodes with
279 identical output are not output twice. A header will list those
280 nodes with the consolidated output. When this option is speci‐
281 fied, no output can be seen until the IPMI operations to all
282 nodes has completed. If the user breaks out of the program
283 early, all currently consolidated output will be dumped. See
284 HOSTRANGED SUPPORT below for additional information.
285 -F NUM, --fanout=NUM
287 Specify multiple host fanout. A "sliding window" (or fanout)
288 algorithm is used for parallel IPMI communication so that slower
289 nodes or timed out nodes will not impede parallel communication.
290 The maximum number of threads available at the same time is lim‐
291 ited by the fanout. The default is 64.
292 -E, --eliminate
294 Eliminate hosts determined as undetected by ipmidetect. This
295 attempts to remove the common issue of hostranged execution tim‐
296 ing out due to several nodes being removed from service in a
297 large cluster. The ipmidetectd daemon must be running on the
298 node executing the command.
299 --always-prefix
301 Always prefix output, even if only one host is specified or com‐
302 municating in-band. This option is primarily useful for script‐
303 ing purposes. Option will be ignored if specified with the -C
304 option.
305
307 Multiple hosts can be input either as an explicit comma separated lists
308 of hosts or a range of hostnames in the general form: prefix[n-m,l-
309 k,...], where n < m and l < k, etc. The later form should not be con‐
310 fused with regular expression character classes (also denoted by []).
311 For example, foo[19] does not represent foo1 or foo9, but rather repre‐
312 sents a degenerate range: foo19.
313 This range syntax is meant only as a convenience on clusters with a
315 prefixNN naming convention and specification of ranges should not be
316 considered necessary -- the list foo1,foo9 could be specified as such,
317 or by the range foo[1,9].
318 Some examples of range usage follow:
320 foo[01-05] instead of foo01,foo02,foo03,foo04,foo05
321 foo[7,9-10] instead of foo7,foo9,foo10
322 foo[0-3] instead of foo0,foo1,foo2,foo3
323 As a reminder to the reader, some shells will interpret brackets ([ and
325 ]) for pattern matching. Depending on your shell, it may be necessary
326 to enclose ranged lists within quotes.
327 When multiple hosts are specified by the user, a thread will be exe‐
329 cuted for each host in parallel up to the configured fanout (which can
330 be adjusted via the -F option). This will allow communication to large
331 numbers of nodes far more quickly than if done in serial.
332 By default, standard output from each node specified will be output
334 with the hostname prepended to each line. Although this output is read‐
335 able in many situations, it may be difficult to read in other situa‐
336 tions. For example, output from multiple nodes may be mixed together.
337 The -B and -C options can be used to change this default.
338 In-band IPMI Communication will be used when the host "localhost" is
340 specified. This allows the user to add the localhost into the hos‐
341 tranged output.
342
344 Most often, IPMI problems are due to configuration problems.
345 IPMI over LAN problems involve a misconfiguration of the remote
347 machine's BMC. Double check to make sure the following are configured
348 properly in the remote machine's BMC: IP address, MAC address, subnet
349 mask, username, user enablement, user privilege, password, LAN privi‐
350 lege, LAN enablement, and allowed authentication type(s). For IPMI 2.0
351 connections, double check to make sure the cipher suite privilege(s)
352 and K_g key are configured properly. The ipmi-config(8) tool can be
353 used to check and/or change these configuration settings.
354 Inband IPMI problems are typically caused by improperly configured
356 drivers or non-standard BMCs.
357 In addition to the troubleshooting tips below, please see WORKAROUNDS
359 below to also if there are any vendor specific bugs that have been dis‐
360 covered and worked around.
361 Listed below are many of the common issues for error messages. For
363 additional support, please e-mail the <freeipmi-users@gnu.org> mailing
364 list.
365 "username invalid" - The username entered (or a NULL username if none
367 was entered) is not available on the remote machine. It may also be
368 possible the remote BMC's username configuration is incorrect.
369 "password invalid" - The password entered (or a NULL password if none
371 was entered) is not correct. It may also be possible the password for
372 the user is not correctly configured on the remote BMC.
373 "password verification timeout" - Password verification has timed out.
375 A "password invalid" error (described above) or a generic "session
376 timeout" (described below) occurred. During this point in the protocol
377 it cannot be differentiated which occurred.
378 "k_g invalid" - The K_g key entered (or a NULL K_g key if none was
380 entered) is not correct. It may also be possible the K_g key is not
381 correctly configured on the remote BMC.
382 "privilege level insufficient" - An IPMI command requires a higher user
384 privilege than the one authenticated with. Please try to authenticate
385 with a higher privilege. This may require authenticating to a different
386 user which has a higher maximum privilege.
387 "privilege level cannot be obtained for this user" - The privilege
389 level you are attempting to authenticate with is higher than the maxi‐
390 mum allowed for this user. Please try again with a lower privilege. It
391 may also be possible the maximum privilege level allowed for a user is
392 not configured properly on the remote BMC.
393 "authentication type unavailable for attempted privilege level" - The
395 authentication type you wish to authenticate with is not available for
396 this privilege level. Please try again with an alternate authentication
397 type or alternate privilege level. It may also be possible the avail‐
398 able authentication types you can authenticate with are not correctly
399 configured on the remote BMC.
400 "cipher suite id unavailable" - The cipher suite id you wish to authen‐
402 ticate with is not available on the remote BMC. Please try again with
403 an alternate cipher suite id. It may also be possible the available
404 cipher suite ids are not correctly configured on the remote BMC.
405 "ipmi 2.0 unavailable" - IPMI 2.0 was not discovered on the remote
407 machine. Please try to use IPMI 1.5 instead.
408 "connection timeout" - Initial IPMI communication failed. A number of
410 potential errors are possible, including an invalid hostname specified,
411 an IPMI IP address cannot be resolved, IPMI is not enabled on the
412 remote server, the network connection is bad, etc. Please verify con‐
413 figuration and connectivity.
414 "session timeout" - The IPMI session has timed out. Please reconnect.
416 If this error occurs often, you may wish to increase the retransmission
417 timeout. Some remote BMCs are considerably slower than others.
418 "device not found" - The specified device could not be found. Please
420 check configuration or inputs and try again.
421 "driver timeout" - Communication with the driver or device has timed
423 out. Please try again.
424 "message timeout" - Communication with the driver or device has timed
426 out. Please try again.
427 "BMC busy" - The BMC is currently busy. It may be processing informa‐
429 tion or have too many simultaneous sessions to manage. Please wait and
430 try again.
431 "could not find inband device" - An inband device could not be found.
433 Please check configuration or specify specific device or driver on the
434 command line.
435 "driver timeout" - The inband driver has timed out communicating to the
437 local BMC or service processor. The BMC or service processor may be
438 busy or (worst case) possibly non-functioning.
439 "internal IPMI error" - An IPMI error has occurred that FreeIPMI does
441 not know how to handle. Please e-mail <freeipmi-users@gnu.org> to
442 report the issue.
443
445 With so many different vendors implementing their own IPMI solutions,
446 different vendors may implement their IPMI protocols incorrectly. The
447 following describes a number of workarounds currently available to han‐
448 dle discovered compliance issues. When possible, workarounds have been
449 implemented so they will be transparent to the user. However, some will
450 require the user to specify a workaround be used via the -W option.
451 The hardware listed below may only indicate the hardware that a problem
453 was discovered on. Newer versions of hardware may fix the problems
454 indicated below. Similar machines from vendors may or may not exhibit
455 the same problems. Different vendors may license their firmware from
456 the same IPMI firmware developer, so it may be worthwhile to try work‐
457 arounds listed below even if your motherboard is not listed.
458 If you believe your hardware has an additional compliance issue that
460 needs a workaround to be implemented, please contact the FreeIPMI main‐
461 tainers on <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
462 assumeio - This workaround flag will assume inband interfaces communi‐
464 cate with system I/O rather than being memory-mapped. This will work
465 around systems that report invalid base addresses. Those hitting this
466 issue may see "device not supported" or "could not find inband device"
467 errors. Issue observed on HP ProLiant DL145 G1.
468 spinpoll - This workaround flag will inform some inband drivers (most
470 notably the KCS driver) to spin while polling rather than putting the
471 process to sleep. This may significantly improve the wall clock running
472 time of tools because an operating system scheduler's granularity may
473 be much larger than the time it takes to perform a single IPMI message
474 transaction. However, by spinning, your system may be performing less
475 useful work by not contexting out the tool for a more useful task.
476 authcap - This workaround flag will skip early checks for username
478 capabilities, authentication capabilities, and K_g support and allow
479 IPMI authentication to succeed. It works around multiple issues in
480 which the remote system does not properly report username capabilities,
481 authentication capabilities, or K_g status. Those hitting this issue
482 may see "username invalid", "authentication type unavailable for
483 attempted privilege level", or "k_g invalid" errors. Issue observed on
484 Asus P5M2/P5MT-R/RS162-E4/RX4, Intel SR1520ML/X38ML, and Sun Fire
485 2200/4150/4450 with ELOM.
486 nochecksumcheck - This workaround flag will tell FreeIPMI to not check
488 the checksums returned from IPMI command responses. It works around
489 systems that return invalid checksums due to implementation errors, but
490 the packet is otherwise valid. Users are cautioned on the use of this
491 option, as it removes validation of packet integrity in a number of
492 circumstances. However, it is unlikely to be an issue in most situa‐
493 tions. Those hitting this issue may see "connection timeout", "session
494 timeout", or "password verification timeout" errors. On IPMI 1.5 con‐
495 nections, the "noauthcodecheck" workaround may also needed too. Issue
496 observed on Supermicro X9SCM-iiF, Supermicro X9DRi-F, and Supermicro
497 X9DRFR.
498 idzero - This workaround flag will allow empty session IDs to be
500 accepted by the client. It works around IPMI sessions that report empty
501 session IDs to the client. Those hitting this issue may see "session
502 timeout" errors. Issue observed on Tyan S2882 with M3289 BMC.
503 unexpectedauth - This workaround flag will allow unexpected non-null
505 authcodes to be checked as though they were expected. It works around
506 an issue when packets contain non-null authentication data when they
507 should be null due to disabled per-message authentication. Those hit‐
508 ting this issue may see "session timeout" errors. Issue observed on
509 Dell PowerEdge 2850,SC1425. Confirmed fixed on newer firmware.
510 forcepermsg - This workaround flag will force per-message authentica‐
512 tion to be used no matter what is advertised by the remote system. It
513 works around an issue when per-message authentication is advertised as
514 disabled on the remote system, but it is actually required for the pro‐
515 tocol. Those hitting this issue may see "session timeout" errors.
516 Issue observed on IBM eServer 325.
517 endianseq - This workaround flag will flip the endian of the session
519 sequence numbers to allow the session to continue properly. It works
520 around IPMI 1.5 session sequence numbers that are the wrong endian.
521 Those hitting this issue may see "session timeout" errors. Issue
522 observed on some Sun ILOM 1.0/2.0 (depends on service processor
523 endian).
524 noauthcodecheck - This workaround flag will tell FreeIPMI to not check
526 the authentication codes returned from IPMI 1.5 command responses. It
527 works around systems that return invalid authentication codes due to
528 hashing or implementation errors. Users are cautioned on the use of
529 this option, as it removes an authentication check verifying the valid‐
530 ity of a packet. However, in most organizations, this is unlikely to be
531 a security issue. Those hitting this issue may see "connection time‐
532 out", "session timeout", or "password verification timeout" errors.
533 Issue observed on Xyratex FB-H8-SRAY, Intel Windmill, Quanta Winter‐
534 fell, and Wiwynn Windmill.
535 intel20 - This workaround flag will work around several Intel IPMI 2.0
537 authentication issues. The issues covered include padding of usernames,
538 and password truncation if the authentication algorithm is HMAC-
539 MD5-128. Those hitting this issue may see "username invalid", "password
540 invalid", or "k_g invalid" errors. Issue observed on Intel SE7520AF2
541 with Intel Server Management Module (Professional Edition).
542 supermicro20 - This workaround flag will work around several Supermicro
544 IPMI 2.0 authentication issues on motherboards w/ Peppercon IPMI
545 firmware. The issues covered include handling invalid length authenti‐
546 cation codes. Those hitting this issue may see "password invalid"
547 errors. Issue observed on Supermicro H8QME with SIMSO daughter card.
548 Confirmed fixed on newerver firmware.
549 sun20 - This workaround flag will work work around several Sun IPMI 2.0
551 authentication issues. The issues covered include invalid lengthed hash
552 keys, improperly hashed keys, and invalid cipher suite records. Those
553 hitting this issue may see "password invalid" or "bmc error" errors.
554 Issue observed on Sun Fire 4100/4200/4500 with ILOM. This workaround
555 automatically includes the "opensesspriv" workaround.
556 opensesspriv - This workaround flag will slightly alter FreeIPMI's IPMI
558 2.0 connection protocol to workaround an invalid hashing algorithm used
559 by the remote system. The privilege level sent during the Open Session
560 stage of an IPMI 2.0 connection is used for hashing keys instead of the
561 privilege level sent during the RAKP1 connection stage. Those hitting
562 this issue may see "password invalid", "k_g invalid", or "bad rmcpplus
563 status code" errors. Issue observed on Sun Fire 4100/4200/4500 with
564 ILOM, Inventec 5441/Dell Xanadu II, Supermicro X8DTH, Supermicro X8DTG,
565 Intel S5500WBV/Penguin Relion 700, Intel S2600JF/Appro 512X, Quanta
566 QSSC-S4R/Appro GB812X-CN, and Dell C5220. This workaround is automati‐
567 cally triggered with the "sun20" workaround.
568 integritycheckvalue - This workaround flag will work around an invalid
570 integrity check value during an IPMI 2.0 session establishment when
571 using Cipher Suite ID 0. The integrity check value should be 0 length,
572 however the remote motherboard responds with a non-empty field. Those
573 hitting this issue may see "k_g invalid" errors. Issue observed on
574 Supermicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin Relion
575 700, and Intel S2600JF/Appro 512X.
576 assumemaxsdrrecordcount - This workaround will inform SDR reading to
578 stop reading after a known maximum number of SDR records have been
579 read. This will work around systems that have mis-implemented SDR read‐
580 ing functions. Those hitting this issue may see "SDR record count
581 invalid" errors. Issue observed on unspecified Inspur motherboard.
582 skipchecks - This workaround option will skip FRU checksum checks. Some
584 FRUs have incorrect checksums, but the FRU data is correct. Those hit‐
585 ting this issue may see "checksum invalid" errors in their FRU output.
586 Output may be unknown, pray for the best. This option is confirmed to
587 work around compliances issues on Inventec 5441/Dell Xanadu II, Dell
588 Poweredge R610, and Dell Poweredge R710 motherboards.
589 No IPMI 1.5 Support - Some motherboards that support IPMI 2.0 have been
591 found to not support IPMI 1.5. Those hitting this issue may see "ipmi
592 2.0 unavailable" or "connection timeout" errors. This issue can be
593 worked around by using IPMI 2.0 instead of IPMI 1.5 by specifying
594 --driver-type=LAN_2_0. Issue observed on a number of HP and Supermicro
595 motherboards.
596
598 The following motherboards are confirmed to have atleast some support
599 by the --interpret-oem-data option. While highly probable the OEM data
600 interpretations would work across other motherboards by the same manu‐
601 facturer, there are no guarantees. Some of the motherboards below may
602 be rebranded by vendors/distributors.
603 Wistron/Dell Poweredge C6220
605
607 # ipmi-fru
608 Get FRU information of the local machine.
610 # ipmi-fru --verbose
612 Get verbose FRU information of the local machine.
614 # ipmi-fru -h ahost -u myusername -p mypassword
616 Get FRU information of a remote machine using IPMI over LAN.
618 # ipmi-fru -h mycluster[0-127] -u myusername -p mypassword
620 Get FRU information across a cluster using IPMI over LAN.
622
624 Not all language codes are supported in ipmi-fru. If additional lan‐
625 guage code support is required please contact the FreeIPMI maintainers.
626
628 Upon successful execution, exit status is 0. On error, exit status is
629 1.
630 If multiple hosts are specified for communication, the exit status is 0
632 if and only if all targets successfully execute. Otherwise the exit
633 status is 1.
634
636 On older operating systems, if you input your username, password, and
637 other potentially security relevant information on the command line,
638 this information may be discovered by other users when using tools like
639 the ps(1) command or looking in the /proc file system. It is generally
640 more secure to input password information with options like the -P or
641 -K options. Configuring security relevant information in the FreeIPMI
642 configuration file would also be an appropriate way to hide this infor‐
643 mation.
644 In order to prevent brute force attacks, some BMCs will temporarily
646 "lock up" after a number of remote authentication errors. You may need
647 to wait awhile in order to this temporary "lock up" to pass before you
648 may authenticate again.
649
651 Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
652
654 Copyright (C) 2007-2015 Lawrence Livermore National Security, LLC.
655 Copyright (C) 2007 The Regents of the University of California.
656 This program is free software; you can redistribute it and/or modify it
658 under the terms of the GNU General Public License as published by the
659 Free Software Foundation; either version 3 of the License, or (at your
660 option) any later version.
661
663 freeipmi(7), ipmi-config(8)
664 http://www.gnu.org/software/freeipmi/
666ipmi-fru 1.6.7 2021-02-12 IPMI-FRU(8)