1BMC-INFO(8)                     System Commands                    BMC-INFO(8)
2
3
4

NAME

6       bmc-info - display BMC information
7

SYNOPSIS

9       bmc-info [OPTION...]
10

DESCRIPTION

12       Bmc-info  displays  BMC  information,  such  as device version numbers,
13       device support, and globally unique IDs (guids).
14
15       Listed below are general IPMI options, tool specific  options,  trouble
16       shooting  information,  workaround  information,  examples,  and  known
17       issues. For a general introduction to FreeIPMI please see freeipmi(7).
18

GENERAL OPTIONS

20       The following options are general options for configuring IPMI communi‐
21       cation and executing general tool commands.
22
23       -D IPMIDRIVER, --driver-type=IPMIDRIVER
24              Specify  the  driver type to use instead of doing an auto selec‐
25              tion.  The currently available outofband  drivers  are  LAN  and
26              LAN_2_0,  which  perform IPMI 1.5 and IPMI 2.0 respectively. The
27              currently available inband  drivers  are  KCS,  SSIF,  OPENIPMI,
28              SUNBMC, and INTELDCMI.
29
30       --disable-auto-probe
31              Do not probe in-band IPMI devices for default settings.
32
33       --driver-address=DRIVER-ADDRESS
34              Specify  the  in-band  driver  address to be used instead of the
35              probed value. DRIVER-ADDRESS should be prefixed with "0x" for  a
36              hex value and '0' for an octal value.
37
38       --driver-device=DEVICE
39              Specify the in-band driver device path to be used instead of the
40              probed path.
41
42       --register-spacing=REGISTER-SPACING
43              Specify the in-band  driver  register  spacing  instead  of  the
44              probed  value. Argument is in bytes (i.e. 32bit register spacing
45              = 4)
46
47       --target-channel-number=CHANNEL-NUMBER
48              Specify the in-band driver target channel number  to  send  IPMI
49              requests to.
50
51       --target-slave-address=SLAVE-ADDRESS
52              Specify  the  in-band  driver  target  slave number to send IPMI
53              requests to.
54
55       -h      IPMIHOST1,IPMIHOST2,...,      --hostname=IPMIHOST1[:PORT],IPMI‐
56       HOST2[:PORT],...
57              Specify  the  remote host(s) to communicate with. Multiple host‐
58              names may be separated by comma or may be specified in  a  range
59              format;  see  HOSTRANGED  SUPPORT below. An optional port can be
60              specified with each host, which may be useful in port forwarding
61              or  similar situations.  If specifying an IPv6 address and port,
62              use the format [ADDRESS]:PORT.
63
64       -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
70       -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
75       -P, --password-prompt
76              Prompt  for  password  to  avoid  possibility  of  listing it in
77              process lists.
78
79       -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
86       -K, --k-g-prompt
87              Prompt for k-g to avoid possibility of  listing  it  in  process
88              lists.
89
90       --session-timeout=MILLISECONDS
91              Specify  the  session timeout in milliseconds. Defaults to 20000
92              milliseconds (20 seconds) if not specified.
93
94       --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
100       -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
105       -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
116              0 - Authentication Algorithm = None; Integrity Algorithm = None;
117              Confidentiality Algorithm = None
118
119              1 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm  =
120              None; Confidentiality Algorithm = None
121
122              2  - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
123              HMAC-SHA1-96; Confidentiality Algorithm = None
124
125              3 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm  =
126              HMAC-SHA1-96; Confidentiality Algorithm = AES-CBC-128
127
128              6  -  Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
129              None; Confidentiality Algorithm = None
130
131              7 - Authentication Algorithm = HMAC-MD5; Integrity  Algorithm  =
132              HMAC-MD5-128; Confidentiality Algorithm = None
133
134              8  -  Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
135              HMAC-MD5-128; Confidentiality Algorithm = AES-CBC-128
136
137              11 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm  =
138              MD5-128; Confidentiality Algorithm = None
139
140              12  - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
141              MD5-128; Confidentiality Algorithm = AES-CBC-128
142
143              15 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
144              = None; Confidentiality Algorithm = None
145
146              16 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
147              = HMAC_SHA256_128; Confidentiality Algorithm = None
148
149              17 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
150              = HMAC_SHA256_128; Confidentiality Algorithm = AES-CBC-128
151
152       -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
157       --config-file=FILE
158              Specify an alternate configuration file.
159
160       -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
167       --debug
168              Turn on debugging.
169
170       -?, --help
171              Output a help list and exit.
172
173       --usage
174              Output a usage message and exit.
175
176       -V, --version
177              Output the program version and exit.
178

BMC-INFO OPTIONS

180       The following options are specific to bmc-info.
181
182       --get-device-id
183              Display only device ID information.
184
185       --get-device-guid
186              Display only device guid.
187
188       --get-system-guid
189              Display only system guid.
190
191       --get-system-info
192              Display only system info.
193
194       --get-channel-info
195              Display only channel information.
196
197       --interpret-oem-data
198              Attempt  to interpret OEM data, such as event data, sensor read‐
199              ings, or general extra info, etc. If an  OEM  interpretation  is
200              not available, the default output will be generated. Correctness
201              of OEM interpretations cannot be  guaranteed  due  to  potential
202              changes OEM vendors may make in products, firmware, etc. See OEM
203              INTERPRETATION below for confirmed supported motherboard  inter‐
204              pretations.
205

HOSTRANGED OPTIONS

207       The following options manipulate hostranged output. See HOSTRANGED SUP‐
208       PORT below for additional information on hostranges.
209
210       -B, --buffer-output
211              Buffer hostranged output. For each node, buffer standard  output
212              until the node has completed its IPMI operation. When specifying
213              this option, data may appear to output slower to the user  since
214              the  the entire IPMI operation must complete before any data can
215              be output.  See HOSTRANGED SUPPORT below for additional informa‐
216              tion.
217
218       -C, --consolidate-output
219              Consolidate hostranged output. The complete standard output from
220              every node specified will be consolidated  so  that  nodes  with
221              identical  output are not output twice. A header will list those
222              nodes with the consolidated output. When this option  is  speci‐
223              fied,  no  output  can  be seen until the IPMI operations to all
224              nodes has completed. If the  user  breaks  out  of  the  program
225              early,  all  currently  consolidated  output will be dumped. See
226              HOSTRANGED SUPPORT below for additional information.
227
228       -F NUM, --fanout=NUM
229              Specify multiple host fanout. A  "sliding  window"  (or  fanout)
230              algorithm is used for parallel IPMI communication so that slower
231              nodes or timed out nodes will not impede parallel communication.
232              The maximum number of threads available at the same time is lim‐
233              ited by the fanout. The default is 64.
234
235       -E, --eliminate
236              Eliminate hosts determined as undetected  by  ipmidetect.   This
237              attempts to remove the common issue of hostranged execution tim‐
238              ing out due to several nodes being removed  from  service  in  a
239              large  cluster.  The  ipmidetectd  daemon must be running on the
240              node executing the command.
241
242       --always-prefix
243              Always prefix output, even if only one host is specified or com‐
244              municating  in-band. This option is primarily useful for script‐
245              ing purposes. Option will be ignored if specified  with  the  -C
246              option.
247

HOSTRANGED SUPPORT

249       Multiple hosts can be input either as an explicit comma separated lists
250       of hosts or a range of hostnames in  the  general  form:  prefix[n-m,l-
251       k,...],  where  n < m and l < k, etc. The later form should not be con‐
252       fused with regular expression character classes (also denoted  by  []).
253       For example, foo[19] does not represent foo1 or foo9, but rather repre‐
254       sents a degenerate range: foo19.
255
256       This range syntax is meant only as a convenience  on  clusters  with  a
257       prefixNN  naming  convention  and specification of ranges should not be
258       considered necessary -- the list foo1,foo9 could be specified as  such,
259       or by the range foo[1,9].
260
261       Some examples of range usage follow:
262           foo[01-05] instead of foo01,foo02,foo03,foo04,foo05
263           foo[7,9-10] instead of foo7,foo9,foo10
264           foo[0-3] instead of foo0,foo1,foo2,foo3
265
266       As a reminder to the reader, some shells will interpret brackets ([ and
267       ]) for pattern matching. Depending on your shell, it may  be  necessary
268       to enclose ranged lists within quotes.
269
270       When  multiple  hosts  are specified by the user, a thread will be exe‐
271       cuted for each host in parallel up to the configured fanout (which  can
272       be  adjusted via the -F option). This will allow communication to large
273       numbers of nodes far more quickly than if done in serial.
274
275       By default, standard output from each node  specified  will  be  output
276       with the hostname prepended to each line. Although this output is read‐
277       able in many situations, it may be difficult to read  in  other  situa‐
278       tions.  For  example, output from multiple nodes may be mixed together.
279       The -B and -C options can be used to change this default.
280
281       In-band IPMI Communication will be used when the  host  "localhost"  is
282       specified.  This  allows  the  user  to add the localhost into the hos‐
283       tranged output.
284

GENERAL TROUBLESHOOTING

286       Most often, IPMI problems are due to configuration problems.
287
288       IPMI over  LAN  problems  involve  a  misconfiguration  of  the  remote
289       machine's  BMC.  Double check to make sure the following are configured
290       properly in the remote machine's BMC: IP address, MAC  address,  subnet
291       mask,  username,  user enablement, user privilege, password, LAN privi‐
292       lege, LAN enablement, and allowed authentication type(s). For IPMI  2.0
293       connections,  double  check  to make sure the cipher suite privilege(s)
294       and K_g key are configured properly. The  ipmi-config(8)  tool  can  be
295       used to check and/or change these configuration settings.
296
297       Inband  IPMI  problems  are  typically  caused by improperly configured
298       drivers or non-standard BMCs.
299
300       In addition to the troubleshooting tips below, please  see  WORKAROUNDS
301       below to also if there are any vendor specific bugs that have been dis‐
302       covered and worked around.
303
304       Listed below are many of the common issues  for  error  messages.   For
305       additional  support, please e-mail the <freeipmi-users@gnu.org> mailing
306       list.
307
308       "username invalid" - The username entered (or a NULL username  if  none
309       was  entered)  is  not  available on the remote machine. It may also be
310       possible the remote BMC's username configuration is incorrect.
311
312       "password invalid" - The password entered (or a NULL password  if  none
313       was  entered)  is not correct. It may also be possible the password for
314       the user is not correctly configured on the remote BMC.
315
316       "password verification timeout" - Password verification has timed  out.
317       A  "password  invalid"  error  (described  above) or a generic "session
318       timeout" (described below) occurred.  During this point in the protocol
319       it cannot be differentiated which occurred.
320
321       "k_g  invalid"  -  The  K_g  key entered (or a NULL K_g key if none was
322       entered) is not correct. It may also be possible the  K_g  key  is  not
323       correctly configured on the remote BMC.
324
325       "privilege level insufficient" - An IPMI command requires a higher user
326       privilege than the one authenticated with. Please try  to  authenticate
327       with a higher privilege. This may require authenticating to a different
328       user which has a higher maximum privilege.
329
330       "privilege level cannot be obtained for  this  user"  -  The  privilege
331       level  you are attempting to authenticate with is higher than the maxi‐
332       mum allowed for this user. Please try again with a lower privilege.  It
333       may  also be possible the maximum privilege level allowed for a user is
334       not configured properly on the remote BMC.
335
336       "authentication type unavailable for attempted privilege level"  -  The
337       authentication  type you wish to authenticate with is not available for
338       this privilege level. Please try again with an alternate authentication
339       type  or  alternate privilege level. It may also be possible the avail‐
340       able authentication types you can authenticate with are  not  correctly
341       configured on the remote BMC.
342
343       "cipher suite id unavailable" - The cipher suite id you wish to authen‐
344       ticate with is not available on the remote BMC. Please try  again  with
345       an  alternate  cipher  suite  id. It may also be possible the available
346       cipher suite ids are not correctly configured on the remote BMC.
347
348       "ipmi 2.0 unavailable" - IPMI 2.0 was  not  discovered  on  the  remote
349       machine. Please try to use IPMI 1.5 instead.
350
351       "connection  timeout"  - Initial IPMI communication failed. A number of
352       potential errors are possible, including an invalid hostname specified,
353       an  IPMI  IP  address  cannot  be  resolved, IPMI is not enabled on the
354       remote server, the network connection is bad, etc. Please  verify  con‐
355       figuration and connectivity.
356
357       "session  timeout"  - The IPMI session has timed out. Please reconnect.
358       If this error occurs often, you may wish to increase the retransmission
359       timeout. Some remote BMCs are considerably slower than others.
360
361       "device  not  found"  - The specified device could not be found. Please
362       check configuration or inputs and try again.
363
364       "driver timeout" - Communication with the driver or  device  has  timed
365       out. Please try again.
366
367       "message  timeout"  - Communication with the driver or device has timed
368       out. Please try again.
369
370       "BMC busy" - The BMC is currently busy. It may be  processing  informa‐
371       tion  or have too many simultaneous sessions to manage. Please wait and
372       try again.
373
374       "could not find inband device" - An inband device could not  be  found.
375       Please  check configuration or specify specific device or driver on the
376       command line.
377
378       "driver timeout" - The inband driver has timed out communicating to the
379       local  BMC  or  service  processor. The BMC or service processor may be
380       busy or (worst case) possibly non-functioning.
381

WORKAROUNDS

383       With so many different vendors implementing their own  IPMI  solutions,
384       different  vendors  may implement their IPMI protocols incorrectly. The
385       following describes a number of workarounds currently available to han‐
386       dle  discovered compliance issues. When possible, workarounds have been
387       implemented so they will be transparent to the user. However, some will
388       require the user to specify a workaround be used via the -W option.
389
390       The hardware listed below may only indicate the hardware that a problem
391       was discovered on. Newer versions of  hardware  may  fix  the  problems
392       indicated  below.  Similar machines from vendors may or may not exhibit
393       the same problems. Different vendors may license  their  firmware  from
394       the  same IPMI firmware developer, so it may be worthwhile to try work‐
395       arounds listed below even if your motherboard is not listed.
396
397       If you believe your hardware has an additional  compliance  issue  that
398       needs a workaround to be implemented, please contact the FreeIPMI main‐
399       tainers on <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
400
401       assumeio - This workaround flag will assume inband interfaces  communi‐
402       cate  with  system  I/O rather than being memory-mapped. This will work
403       around systems that report invalid base addresses. Those  hitting  this
404       issue  may see "device not supported" or "could not find inband device"
405       errors.  Issue observed on HP ProLiant DL145 G1.
406
407       spinpoll - This workaround flag will inform some inband  drivers  (most
408       notably  the  KCS driver) to spin while polling rather than putting the
409       process to sleep. This may significantly improve the wall clock running
410       time  of  tools because an operating system scheduler's granularity may
411       be much larger than the time it takes to perform a single IPMI  message
412       transaction.  However,  by spinning, your system may be performing less
413       useful work by not contexting out the tool for a more useful task.
414
415       authcap - This workaround flag will  skip  early  checks  for  username
416       capabilities,  authentication  capabilities,  and K_g support and allow
417       IPMI authentication to succeed. It  works  around  multiple  issues  in
418       which the remote system does not properly report username capabilities,
419       authentication capabilities, or K_g status. Those  hitting  this  issue
420       may  see  "username  invalid",  "authentication  type  unavailable  for
421       attempted privilege level", or "k_g invalid" errors.  Issue observed on
422       Asus  P5M2/P5MT-R/RS162-E4/RX4,  Intel  SR1520ML/X38ML,  and  Sun  Fire
423       2200/4150/4450 with ELOM.
424
425       nochecksumcheck - This workaround flag will tell FreeIPMI to not  check
426       the  checksums  returned  from  IPMI command responses. It works around
427       systems that return invalid checksums due to implementation errors, but
428       the  packet  is otherwise valid. Users are cautioned on the use of this
429       option, as it removes validation of packet integrity  in  a  number  of
430       circumstances.  However,  it  is unlikely to be an issue in most situa‐
431       tions. Those hitting this issue may see "connection timeout",  "session
432       timeout",  or  "password verification timeout" errors. On IPMI 1.5 con‐
433       nections, the "noauthcodecheck" workaround may also needed  too.  Issue
434       observed  on  Supermicro  X9SCM-iiF, Supermicro X9DRi-F, and Supermicro
435       X9DRFR.
436
437       idzero - This workaround flag  will  allow  empty  session  IDs  to  be
438       accepted by the client. It works around IPMI sessions that report empty
439       session IDs to the client. Those hitting this issue  may  see  "session
440       timeout" errors. Issue observed on Tyan S2882 with M3289 BMC.
441
442       unexpectedauth  -  This  workaround flag will allow unexpected non-null
443       authcodes to be checked as though they were expected. It  works  around
444       an  issue  when  packets contain non-null authentication data when they
445       should be null due to disabled per-message authentication.  Those  hit‐
446       ting  this  issue  may  see "session timeout" errors. Issue observed on
447       Dell PowerEdge 2850,SC1425. Confirmed fixed on newer firmware.
448
449       forcepermsg - This workaround flag will force  per-message  authentica‐
450       tion  to  be used no matter what is advertised by the remote system. It
451       works around an issue when per-message authentication is advertised  as
452       disabled on the remote system, but it is actually required for the pro‐
453       tocol. Those hitting this  issue  may  see  "session  timeout"  errors.
454       Issue observed on IBM eServer 325.
455
456       endianseq  -  This  workaround flag will flip the endian of the session
457       sequence numbers to allow the session to continue  properly.  It  works
458       around  IPMI  1.5  session  sequence numbers that are the wrong endian.
459       Those hitting this  issue  may  see  "session  timeout"  errors.  Issue
460       observed  on  some  Sun  ILOM  1.0/2.0  (depends  on  service processor
461       endian).
462
463       noauthcodecheck - This workaround flag will tell FreeIPMI to not  check
464       the  authentication  codes returned from IPMI 1.5 command responses. It
465       works around systems that return invalid authentication  codes  due  to
466       hashing  or  implementation  errors.  Users are cautioned on the use of
467       this option, as it removes an authentication check verifying the valid‐
468       ity of a packet. However, in most organizations, this is unlikely to be
469       a security issue. Those hitting this issue may  see  "connection  time‐
470       out",  "session  timeout",  or  "password verification timeout" errors.
471       Issue observed on Xyratex FB-H8-SRAY, Intel  Windmill,  Quanta  Winter‐
472       fell, and Wiwynn Windmill.
473
474       intel20  - This workaround flag will work around several Intel IPMI 2.0
475       authentication issues. The issues covered include padding of usernames,
476       and  password  truncation  if  the  authentication  algorithm  is HMAC-
477       MD5-128. Those hitting this issue may see "username invalid", "password
478       invalid",  or  "k_g  invalid" errors. Issue observed on Intel SE7520AF2
479       with Intel Server Management Module (Professional Edition).
480
481       supermicro20 - This workaround flag will work around several Supermicro
482       IPMI  2.0  authentication  issues  on  motherboards  w/  Peppercon IPMI
483       firmware. The issues covered include handling invalid length  authenti‐
484       cation  codes.  Those  hitting  this  issue  may see "password invalid"
485       errors.  Issue observed on Supermicro H8QME with SIMSO  daughter  card.
486       Confirmed fixed on newerver firmware.
487
488       sun20 - This workaround flag will work work around several Sun IPMI 2.0
489       authentication issues. The issues covered include invalid lengthed hash
490       keys,  improperly  hashed keys, and invalid cipher suite records. Those
491       hitting this issue may see "password invalid" or  "bmc  error"  errors.
492       Issue  observed  on Sun Fire 4100/4200/4500 with ILOM.  This workaround
493       automatically includes the "opensesspriv" workaround.
494
495       opensesspriv - This workaround flag will slightly alter FreeIPMI's IPMI
496       2.0 connection protocol to workaround an invalid hashing algorithm used
497       by the remote system. The privilege level sent during the Open  Session
498       stage of an IPMI 2.0 connection is used for hashing keys instead of the
499       privilege level sent during the RAKP1 connection stage.  Those  hitting
500       this  issue may see "password invalid", "k_g invalid", or "bad rmcpplus
501       status code" errors.  Issue observed on Sun  Fire  4100/4200/4500  with
502       ILOM, Inventec 5441/Dell Xanadu II, Supermicro X8DTH, Supermicro X8DTG,
503       Intel S5500WBV/Penguin Relion 700,  Intel  S2600JF/Appro  512X,  Quanta
504       QSSC-S4R/Appro  GB812X-CN, and Dell C5220. This workaround is automati‐
505       cally triggered with the "sun20" workaround.
506
507       integritycheckvalue - This workaround flag will work around an  invalid
508       integrity  check  value  during  an IPMI 2.0 session establishment when
509       using Cipher Suite ID 0. The integrity check value should be 0  length,
510       however  the  remote motherboard responds with a non-empty field. Those
511       hitting this issue may see "k_g  invalid"  errors.  Issue  observed  on
512       Supermicro  X8DTG,  Supermicro X8DTU, and Intel S5500WBV/Penguin Relion
513       700, and Intel S2600JF/Appro 512X.
514
515       guidformat - A number of vendors send the bytes of the  GUID  (such  as
516       the  GUID  in  --get-device-guid  or --get-system-guid) in an alternate
517       format that aligns incorrectly with  IPMI,  but  correctly  with  other
518       standards. This workaround flag will instruct bmc-info to read the GUID
519       and output the GUID based on this common alternate format.
520
521       No IPMI 1.5 Support - Some motherboards that support IPMI 2.0 have been
522       found  to  not support IPMI 1.5. Those hitting this issue may see "ipmi
523       2.0 unavailable" or "connection timeout"  errors.  This  issue  can  be
524       worked  around  by  using  IPMI  2.0  instead of IPMI 1.5 by specifying
525       --driver-type=LAN_2_0. Issue observed on HP Proliant DL 145.
526

OEM INTERPRETATION

528       The following motherboards are confirmed to have atleast  some  support
529       by  the --interpret-oem-data option. While highly probable the OEM data
530       interpretations would work across other motherboards by the same  manu‐
531       facturer,  there  are no guarantees. Some of the motherboards below may
532       be rebranded by vendors/distributors.
533
534       Dell Poweredge R610, Dell Poweredge R710, Intel SR870BN4/Tiger4
535

EXAMPLES

537       # bmc-info
538
539       Get BMC information of the local machine.
540
541       # bmc-info -h ahost -u myusername -p mypassword
542
543       Get BMC information of a remote machine using IPMI over LAN.
544
545       # bmc-info -h mycluster[0-127] -u myusername -p mypassword
546
547       Get BMC information across a cluster using IPMI over LAN.
548

DIAGNOSTICS

550       Upon successful execution, exit status is 0. On error, exit  status  is
551       1.
552
553       If multiple hosts are specified for communication, the exit status is 0
554       if and only if all targets successfully  execute.  Otherwise  the  exit
555       status is 1.
556

KNOWN ISSUES

558       On  older  operating systems, if you input your username, password, and
559       other potentially security relevant information on  the  command  line,
560       this information may be discovered by other users when using tools like
561       the ps(1) command or looking in the /proc file system. It is  generally
562       more  secure  to input password information with options like the -P or
563       -K options. Configuring security relevant information in  the  FreeIPMI
564       configuration file would also be an appropriate way to hide this infor‐
565       mation.
566
567       In order to prevent brute force attacks,  some  BMCs  will  temporarily
568       "lock  up" after a number of remote authentication errors. You may need
569       to wait awhile in order to this temporary "lock up" to pass before  you
570       may authenticate again.
571

REPORTING BUGS

573       Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
574
576       Copyright © 2003-2015 FreeIPMI Core Team.
577
578       This program is free software; you can redistribute it and/or modify it
579       under the terms of the GNU General Public License as published  by  the
580       Free  Software Foundation; either version 3 of the License, or (at your
581       option) any later version.
582

SEE ALSO

584       freeipmi.conf(5), freeipmi(7), ipmi-config(8)
585
586       http://www.gnu.org/software/freeipmi/
587
588
589
590bmc-info 1.6.4                    2019-08-21                       BMC-INFO(8)
Impressum