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, and
29 SUNBMC.
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.
63 -u USERNAME, --username=USERNAME
65 Specify the username to use when authenticating with the remote
66 host. If not specified, a null (i.e. anonymous) username is
67 assumed. The user must have atleast USER privileges in order for
68 this tool to operate fully.
69 -p PASSWORD, --password=PASSWORD
71 Specify the password to use when authenticationg with the remote
72 host. If not specified, a null password is assumed. Maximum
73 password length is 16 for IPMI 1.5 and 20 for IPMI 2.0.
74 -P, --password-prompt
76 Prompt for password to avoid possibility of listing it in
77 process lists.
78 -k K_G, --k-g=K_G
80 Specify the K_g BMC key to use when authenticating with the
81 remote host for IPMI 2.0. If not specified, a null key is
82 assumed. To input the key in hexadecimal form, prefix the string
83 with '0x'. E.g., the key 'abc' can be entered with the either
84 the string 'abc' or the string '0x616263'
85 -K, --k-g-prompt
87 Prompt for k-g to avoid possibility of listing it in process
88 lists.
89 --session-timeout=MILLISECONDS
91 Specify the session timeout in milliseconds. Defaults to 20000
92 milliseconds (20 seconds) if not specified.
93 --retransmission-timeout=MILLISECONDS
95 Specify the packet retransmission timeout in milliseconds.
96 Defaults to 1000 milliseconds (1 second) if not specified. The
97 retransmission timeout cannot be larger than the session time‐
98 out.
99 -a AUTHENTICATION-TYPE, --authentication-type=AUTHENTICATION-TYPE
101 Specify the IPMI 1.5 authentication type to use. The currently
102 available authentication types are NONE, STRAIGHT_PASSWORD_KEY,
103 MD2, and MD5. Defaults to MD5 if not specified.
104 -I CIPHER-SUITE-ID, --cipher-suite-id=CIPHER-SUITE-ID
106 Specify the IPMI 2.0 cipher suite ID to use. The Cipher Suite ID
107 identifies a set of authentication, integrity, and confidential‐
108 ity algorithms to use for IPMI 2.0 communication. The authenti‐
109 cation algorithm identifies the algorithm to use for session
110 setup, the integrity algorithm identifies the algorithm to use
111 for session packet signatures, and the confidentiality algorithm
112 identifies the algorithm to use for payload encryption. Defaults
113 to cipher suite ID 3 if not specified. The following cipher
114 suite ids are currently supported:
115 0 - Authentication Algorithm = None; Integrity Algorithm = None;
117 Confidentiality Algorithm = None
118 1 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
120 None; Confidentiality Algorithm = None
121 2 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
123 HMAC-SHA1-96; Confidentiality Algorithm = None
124 3 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
126 HMAC-SHA1-96; Confidentiality Algorithm = AES-CBC-128
127 6 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
129 None; Confidentiality Algorithm = None
130 7 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
132 HMAC-MD5-128; Confidentiality Algorithm = None
133 8 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
135 HMAC-MD5-128; Confidentiality Algorithm = AES-CBC-128
136 11 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
138 MD5-128; Confidentiality Algorithm = None
139 12 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
141 MD5-128; Confidentiality Algorithm = AES-CBC-128
142 15 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
144 = None; Confidentiality Algorithm = None
145 16 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
147 = HMAC_SHA256_128; Confidentiality Algorithm = None
148 17 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
150 = HMAC_SHA256_128; Confidentiality Algorithm = AES-CBC-128
151 -l PRIVILEGE-LEVEL, --privilege-level=PRIVILEGE-LEVEL
153 Specify the privilege level to be used. The currently available
154 privilege levels are USER, OPERATOR, and ADMIN. Defaults to USER
155 if not specified.
156 --config-file=FILE
158 Specify an alternate configuration file.
159 -W WORKAROUNDS, --workaround-flags=WORKAROUNDS
161 Specify workarounds to vendor compliance issues. Multiple work‐
162 arounds can be specified separated by commas. A special command
163 line flag of "none", will indicate no workarounds (may be useful
164 for overriding configured defaults). See WORKAROUNDS below for a
165 list of available workarounds.
166 --debug
168 Turn on debugging.
169 -?, --help
171 Output a help list and exit.
172 --usage
174 Output a usage message and exit.
175 -V, --version
177 Output the program version and exit.
178
180 The following options are specific to Ipmi-fru.
181 -e, --device-id
183 Specify a specific FRU device ID.
184 -v, --verbose
186 Increase verbosity in output to include additional output.
187 --bridge-fru
189 By default, FRU entries on other satellite controllers will not
190 be read by default. Bridging may not work on some inter‐
191 faces/driver types.
192 --interpret-oem-data
194 Attempt to interpret OEM data, such as event data, sensor read‐
195 ings, or general extra info, etc. If an OEM interpretation is
196 not available, the default output will be generated. Correctness
197 of OEM interpretations cannot be guaranteed due to potential
198 changes OEM vendors may make in products, firmware, etc. See OEM
199 INTERPRETATION below for confirmed supported motherboard inter‐
200 pretations.
201
203 This tool requires access to the sensor data repository (SDR) cache for
204 general operation. By default, SDR data will be downloaded and cached
205 on the local machine. The following options apply to the SDR cache.
206 -f, --flush-cache
208 Flush a cached version of the sensor data repository (SDR)
209 cache. The SDR is typically cached for faster subsequent access.
210 However, it may need to be flushed and re-generated if the SDR
211 has been updated on a system.
212 -Q, --quiet-cache
214 Do not output information about cache creation/deletion. May be
215 useful in scripting.
216 --sdr-cache-recreate
218 If the SDR cache is out of date or invalid, automatically recre‐
219 ate the sensor data repository (SDR) cache. This option may be
220 useful for scripting purposes.
221 --sdr-cache-file=FILE
223 Specify a specific sensor data repository (SDR) cache file to be
224 stored or read from. If this option is used when multiple hosts
225 are specified, the same SDR cache file will be used for all
226 hosts.
227 --sdr-cache-directory=DIRECTORY
229 Specify an alternate directory for sensor data repository (SDR)
230 caches to be stored or read from. Defaults to the home directory
231 if not specified.
232 --ignore-sdr-cache
234 Ignore SDR cache related processing. May lead to incomplete or
235 less useful information being output, however it will allow
236 functionality for systems without SDRs or when the correct SDR
237 cannot be loaded.
238
240 The following options manipulate hostranged output. See HOSTRANGED SUP‐
241 PORT below for additional information on hostranges.
242 -B, --buffer-output
244 Buffer hostranged output. For each node, buffer standard output
245 until the node has completed its IPMI operation. When specifying
246 this option, data may appear to output slower to the user since
247 the the entire IPMI operation must complete before any data can
248 be output. See HOSTRANGED SUPPORT below for additional informa‐
249 tion.
250 -C, --consolidate-output
252 Consolidate hostranged output. The complete standard output from
253 every node specified will be consolidated so that nodes with
254 identical output are not output twice. A header will list those
255 nodes with the consolidated output. When this option is speci‐
256 fied, no output can be seen until the IPMI operations to all
257 nodes has completed. If the user breaks out of the program
258 early, all currently consolidated output will be dumped. See
259 HOSTRANGED SUPPORT below for additional information.
260 -F NUM, --fanout=NUM
262 Specify multiple host fanout. A "sliding window" (or fanout)
263 algorithm is used for parallel IPMI communication so that slower
264 nodes or timed out nodes will not impede parallel communication.
265 The maximum number of threads available at the same time is lim‐
266 ited by the fanout. The default is 64.
267 -E, --eliminate
269 Eliminate hosts determined as undetected by ipmidetect. This
270 attempts to remove the common issue of hostranged execution tim‐
271 ing out due to several nodes being removed from service in a
272 large cluster. The ipmidetectd daemon must be running on the
273 node executing the command.
274 --always-prefix
276 Always prefix output, even if only one host is specified or com‐
277 municating in-band. This option is primarily useful for script‐
278 ing purposes. Option will be ignored if specified with the -C
279 option.
280
282 Multiple hosts can be input either as an explicit comma separated lists
283 of hosts or a range of hostnames in the general form: prefix[n-m,l-
284 k,...], where n < m and l < k, etc. The later form should not be con‐
285 fused with regular expression character classes (also denoted by []).
286 For example, foo[19] does not represent foo1 or foo9, but rather repre‐
287 sents a degenerate range: foo19.
288 This range syntax is meant only as a convenience on clusters with a
290 prefixNN naming convention and specification of ranges should not be
291 considered necessary -- the list foo1,foo9 could be specified as such,
292 or by the range foo[1,9].
293 Some examples of range usage follow:
295 foo[01-05] instead of foo01,foo02,foo03,foo04,foo05
296 foo[7,9-10] instead of foo7,foo9,foo10
297 foo[0-3] instead of foo0,foo1,foo2,foo3
298 As a reminder to the reader, some shells will interpret brackets ([ and
300 ]) for pattern matching. Depending on your shell, it may be necessary
301 to enclose ranged lists within quotes.
302 When multiple hosts are specified by the user, a thread will be exe‐
304 cuted for each host in parallel up to the configured fanout (which can
305 be adjusted via the -F option). This will allow communication to large
306 numbers of nodes far more quickly than if done in serial.
307 By default, standard output from each node specified will be output
309 with the hostname prepended to each line. Although this output is read‐
310 able in many situations, it may be difficult to read in other situa‐
311 tions. For example, output from multiple nodes may be mixed together.
312 The -B and -C options can be used to change this default.
313 In-band IPMI Communication will be used when the host "localhost" is
315 specified. This allows the user to add the localhost into the hos‐
316 tranged output.
317
319 Most often, IPMI problems are due to configuration problems.
320 IPMI over LAN problems involve a misconfiguration of the remote
322 machine's BMC. Double check to make sure the following are configured
323 properly in the remote machine's BMC: IP address, MAC address, subnet
324 mask, username, user enablement, user privilege, password, LAN privi‐
325 lege, LAN enablement, and allowed authentication type(s). For IPMI 2.0
326 connections, double check to make sure the cipher suite privilege(s)
327 and K_g key are configured properly. The bmc-config(8) tool can be used
328 to check and/or change these configuration settings.
329 Inband IPMI problems are typically caused by improperly configured
331 drivers or non-standard BMCs.
332 In addition to the troubleshooting tips below, please see WORKAROUNDS
334 below to also if there are any vendor specific bugs that have been dis‐
335 covered and worked around.
336 Listed below are many of the common issues for error messages. For
338 additional support, please e-mail the <freeipmi-users@gnu.org> mailing
339 list.
340 "username invalid" - The username entered (or a NULL username if none
342 was entered) is not available on the remote machine. It may also be
343 possible the remote BMC's username configuration is incorrect.
344 "password invalid" - The password entered (or a NULL password if none
346 was entered) is not correct. It may also be possible the password for
347 the user is not correctly configured on the remote BMC.
348 "password verification timeout" - Password verification has timed out.
350 A "password invalid" error (described above) or a generic "session
351 timeout" (described below) occurred. During this point in the protocol
352 it cannot be differentiated which occurred.
353 "k_g invalid" - The K_g key entered (or a NULL K_g key if none was
355 entered) is not correct. It may also be possible the K_g key is not
356 correctly configured on the remote BMC.
357 "privilege level insufficient" - An IPMI command requires a higher user
359 privilege than the one authenticated with. Please try to authenticate
360 with a higher privilege. This may require authenticating to a different
361 user which has a higher maximum privilege.
362 "privilege level cannot be obtained for this user" - The privilege
364 level you are attempting to authenticate with is higher than the maxi‐
365 mum allowed for this user. Please try again with a lower privilege. It
366 may also be possible the maximum privilege level allowed for a user is
367 not configured properly on the remote BMC.
368 "authentication type unavailable for attempted privilege level" - The
370 authentication type you wish to authenticate with is not available for
371 this privilege level. Please try again with an alternate authentication
372 type or alternate privilege level. It may also be possible the avail‐
373 able authentication types you can authenticate with are not correctly
374 configured on the remote BMC.
375 "cipher suite id unavailable" - The cipher suite id you wish to authen‐
377 ticate with is not available on the remote BMC. Please try again with
378 an alternate cipher suite id. It may also be possible the available
379 cipher suite ids are not correctly configured on the remote BMC.
380 "ipmi 2.0 unavailable" - IPMI 2.0 was not discovered on the remote
382 machine. Please try to use IPMI 1.5 instead.
383 "connection timeout" - Initial IPMI communication failed. A number of
385 potential errors are possible, including an invalid hostname specified,
386 an IPMI IP address cannot be resolved, IPMI is not enabled on the
387 remote server, the network connection is bad, etc. Please verify con‐
388 figuration and connectivity.
389 "session timeout" - The IPMI session has timed out. Please reconnect.
391 If this error occurs often, you may wish to increase the retransmission
392 timeout. Some remote BMCs are considerably slower than others.
393 "device not found" - The specified device could not be found. Please
395 check configuration or inputs and try again.
396 "driver timeout" - Communication with the driver or device has timed
398 out. Please try again.
399 "message timeout" - Communication with the driver or device has timed
401 out. Please try again.
402 "BMC busy" - The BMC is currently busy. It may be processing informa‐
404 tion or have too many simultaneous sessions to manage. Please wait and
405 try again.
406 "could not find inband device" - An inband device could not be found.
408 Please check configuration or specify specific device or driver on the
409 command line.
410 "driver timeout" - The inband driver has timed out communicating to the
412 local BMC or service processor. The BMC or service processor may be
413 busy or (worst case) possibly non-functioning.
414
416 With so many different vendors implementing their own IPMI solutions,
417 different vendors may implement their IPMI protocols incorrectly. The
418 following describes a number of workarounds currently available to han‐
419 dle discovered compliance issues. When possible, workarounds have been
420 implemented so they will be transparent to the user. However, some will
421 require the user to specify a workaround be used via the -W option.
422 The hardware listed below may only indicate the hardware that a problem
424 was discovered on. Newer versions of hardware may fix the problems
425 indicated below. Similar machines from vendors may or may not exhibit
426 the same problems. Different vendors may license their firmware from
427 the same IPMI firmware developer, so it may be worthwhile to try work‐
428 arounds listed below even if your motherboard is not listed.
429 If you believe your hardware has an additional compliance issue that
431 needs a workaround to be implemented, please contact the FreeIPMI main‐
432 tainers on <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
433 assumeio - This workaround flag will assume inband interfaces communi‐
435 cate with system I/O rather than being memory-mapped. This will work
436 around systems that report invalid base addresses. Those hitting this
437 issue may see "device not supported" or "could not find inband device"
438 errors. Issue observed on HP ProLiant DL145 G1.
439 spinpoll - This workaround flag will inform some inband drivers (most
441 notably the KCS driver) to spin while polling rather than putting the
442 process to sleep. This may significantly improve the wall clock running
443 time of tools because an operating system scheduler's granularity may
444 be much larger than the time it takes to perform a single IPMI message
445 transaction. However, by spinning, your system may be performing less
446 useful work by not contexting out the tool for a more useful task.
447 authcap - This workaround flag will skip early checks for username
449 capabilities, authentication capabilities, and K_g support and allow
450 IPMI authentication to succeed. It works around multiple issues in
451 which the remote system does not properly report username capabilities,
452 authentication capabilities, or K_g status. Those hitting this issue
453 may see "username invalid", "authentication type unavailable for
454 attempted privilege level", or "k_g invalid" errors. Issue observed on
455 Asus P5M2/P5MT-R/RS162-E4/RX4, Intel SR1520ML/X38ML, and Sun Fire
456 2200/4150/4450 with ELOM.
457 idzero - This workaround flag will allow empty session IDs to be
459 accepted by the client. It works around IPMI sessions that report empty
460 session IDs to the client. Those hitting this issue may see "session
461 timeout" errors. Issue observed on Tyan S2882 with M3289 BMC.
462 unexpectedauth - This workaround flag will allow unexpected non-null
464 authcodes to be checked as though they were expected. It works around
465 an issue when packets contain non-null authentication data when they
466 should be null due to disabled per-message authentication. Those hit‐
467 ting this issue may see "session timeout" errors. Issue observed on
468 Dell PowerEdge 2850,SC1425. Confirmed fixed on newer firmware.
469 forcepermsg - This workaround flag will force per-message authentica‐
471 tion to be used no matter what is advertised by the remote system. It
472 works around an issue when per-message authentication is advertised as
473 disabled on the remote system, but it is actually required for the pro‐
474 tocol. Those hitting this issue may see "session timeout" errors.
475 Issue observed on IBM eServer 325.
476 endianseq - This workaround flag will flip the endian of the session
478 sequence numbers to allow the session to continue properly. It works
479 around IPMI 1.5 session sequence numbers that are the wrong endian.
480 Those hitting this issue may see "session timeout" errors. Issue
481 observed on some Sun ILOM 1.0/2.0 (depends on service processor
482 endian).
483 noauthcodecheck - This workaround flag will tell FreeIPMI to not check
485 the authentication codes returned from IPMI 1.5 command responses. It
486 works around systems to return invalid authentication codes due to
487 hashing or implementation errors. Users are cautioned on the use of
488 this option, as it removes an authentication check verifying the valid‐
489 ity of a packet. However, in most organizations, this is unlikely to be
490 a security issue. Those hitting this issue may see "connection time‐
491 out", "session timeout", or "password verification timeout" errors.
492 Issue observed on Xyratex FB-H8-SRAY.
493 intel20 - This workaround flag will work around several Intel IPMI 2.0
495 authentication issues. The issues covered include padding of usernames,
496 and password truncation if the authentication algorithm is HMAC-
497 MD5-128. Those hitting this issue may see "username invalid", "password
498 invalid", or "k_g invalid" errors. Issue observed on Intel SE7520AF2
499 with Intel Server Management Module (Professional Edition).
500 supermicro20 - This workaround flag will work around several Supermicro
502 IPMI 2.0 authentication issues on motherboards w/ Peppercon IPMI
503 firmware. The issues covered include handling invalid length authenti‐
504 cation codes. Those hitting this issue may see "password invalid"
505 errors. Issue observed on Supermicro H8QME with SIMSO daughter card.
506 Confirmed fixed on newerver firmware.
507 sun20 - This workaround flag will work work around several Sun IPMI 2.0
509 authentication issues. The issues covered include invalid lengthed hash
510 keys, improperly hashed keys, and invalid cipher suite records. Those
511 hitting this issue may see "password invalid" or "bmc error" errors.
512 Issue observed on Sun Fire 4100/4200/4500 with ILOM. This workaround
513 automatically includes the "opensesspriv" workaround.
514 opensesspriv - This workaround flag will slightly alter FreeIPMI's IPMI
516 2.0 connection protocol to workaround an invalid hashing algorithm used
517 by the remote system. The privilege level sent during the Open Session
518 stage of an IPMI 2.0 connection is used for hashing keys instead of the
519 privilege level sent during the RAKP1 connection stage. Those hitting
520 this issue may see "password invalid", "k_g invalid", or "bad rmcpplus
521 status code" errors. Issue observed on Sun Fire 4100/4200/4500 with
522 ILOM, Inventec 5441/Dell Xanadu II, Supermicro X8DTH, Supermicro X8DTG,
523 Intel S5500WBV/Penguin Relion 700, Intel S2600JF/Appro 512X, and Quanta
524 QSSC-S4R//Appro GB812X-CN. This workaround is automatically triggered
525 with the "sun20" workaround.
526 integritycheckvalue - This workaround flag will work around an invalid
528 integrity check value during an IPMI 2.0 session establishment when
529 using Cipher Suite ID 0. The integrity check value should be 0 length,
530 however the remote motherboard responds with a non-empty field. Those
531 hitting this issue may see "k_g invalid" errors. Issue observed on
532 Supermicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin Relion
533 700, and Intel S2600JF/Appro 512X.
534 assumemaxsdrrecordcount - This workaround will inform SDR reading to
536 stop reading after a known maximum numer of SDR records have been read.
537 This will work around systems that have mis-implemented SDR reading
538 functions that. Those hitting this issue may see "SDR record count
539 invalid" errors. Issue observed on unspecified Inspur motherboard.
540 skipchecks - This workaround option will skip FRU checksum checks. Some
542 FRUs have incorrect checksums, but the FRU data is correct. Those hit‐
543 ting this issue may see "checksum invalid" errors in their FRU output.
544 Output may be unknown, pray for the best. This option is confirmed to
545 work around compliances issues on Inventec 5441/Dell Xanadu II, Dell
546 Poweredge R610, and Dell Poweredge R710 motherboards.
547 No IPMI 1.5 Support - Some motherboards that support IPMI 2.0 have been
549 found to not support IPMI 1.5. Those hitting this issue may see "ipmi
550 2.0 unavailable" or "connection timeout" errors. This issue can be
551 worked around by using IPMI 2.0 instead of IPMI 1.5 by specifying
552 --driver-address=LAN_2_0. Issue observed on HP Proliant DL 145.
553
555 The following motherboards are confirmed to have atleast some support
556 by the --interpret-oem-data option. While highly probable the OEM data
557 interpretations would work across other motherboards by the same manu‐
558 facturer, there are no guarantees. Some of the motherboards below may
559 be rebranded by vendors/distributors.
560 Wistron/Dell Poweredge C6220
562
564 # ipmi-fru
565 Get FRU information of the local machine.
567 # ipmi-fru --verbose
569 Get verbose FRU information of the local machine.
571 # ipmi-fru -h ahost -u myusername -p mypassword
573 Get FRU information of a remote machine using IPMI over LAN.
575 # ipmi-fru -h mycluster[0-127] -u myusername -p mypassword
577 Get FRU information across a cluster using IPMI over LAN.
579
581 Not all language codes are supported in ipmi-fru. If additional lan‐
582 guage code support is required please contact the FreeIPMI maintainers.
583
585 Upon successful execution, exit status is 0. On error, exit status is
586 1.
587 If multiple hosts are specified for communication, the exit status is 0
589 if and only if all targets successfully execute. Otherwise the exit
590 status is 1.
591
593 On older operating systems, if you input your username, password, and
594 other potentially security relevant information on the command line,
595 this information may be discovered by other users when using tools like
596 the ps(1) command or looking in the /proc file system. It is generally
597 more secure to input password information with options like the -P or
598 -K options. Configuring security relevant information in the FreeIPMI
599 configuration file would also be an appropriate way to hide this infor‐
600 mation.
601 In order to prevent brute force attacks, some BMCs will temporarily
603 "lock up" after a number of remote authentication errors. You may need
604 to wait awhile in order to this temporary "lock up" to pass before you
605 may authenticate again.
606
608 Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
609
611 Copyright (C) 2007-2012 Lawrence Livermore National Security, LLC.
612 Copyright (C) 2007 The Regents of the University of California.
613 This program is free software; you can redistribute it and/or modify it
615 under the terms of the GNU General Public License as published by the
616 Free Software Foundation; either version 3 of the License, or (at your
617 option) any later version.
618
620 freeipmi(7), bmc-config(8)
621 http://www.gnu.org/software/freeipmi/
623ipmi-fru 1.2.1 2017-03-22 IPMI-FRU(8)