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, de‐
13       vice 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 is‐
17       sues. 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 re‐
53              quests 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 as‐
67              sumed. 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  re‐
81              mote host for IPMI 2.0. If not specified, a null key is assumed.
82              To input the key in hexadecimal form,  prefix  the  string  with
83              '0x'.  E.g.,  the  key  'abc' can be entered with the either the
84              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.  De‐
96              faults to 1000 milliseconds (1 second) if not specified. The re‐
97              transmission timeout cannot be larger than the session timeout.
98
99       -a AUTHENTICATION-TYPE, --authentication-type=AUTHENTICATION-TYPE
100              Specify the IPMI 1.5 authentication type to use.  The  currently
101              available  authentication types are NONE, STRAIGHT_PASSWORD_KEY,
102              MD2, and MD5. Defaults to MD5 if not specified.
103
104       -I CIPHER-SUITE-ID, --cipher-suite-id=CIPHER-SUITE-ID
105              Specify the IPMI 2.0 cipher suite ID to use. The Cipher Suite ID
106              identifies a set of authentication, integrity, and confidential‐
107              ity algorithms to use for IPMI 2.0 communication. The  authenti‐
108              cation  algorithm  identifies  the  algorithm to use for session
109              setup, the integrity algorithm identifies the algorithm  to  use
110              for session packet signatures, and the confidentiality algorithm
111              identifies the algorithm to use for payload encryption. Defaults
112              to  cipher  suite  ID  3  if not specified. The following cipher
113              suite ids are currently supported:
114
115              0 - Authentication Algorithm = None; Integrity Algorithm = None;
116              Confidentiality Algorithm = None
117
118              1  - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
119              None; Confidentiality Algorithm = None
120
121              2 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm  =
122              HMAC-SHA1-96; Confidentiality Algorithm = None
123
124              3  - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
125              HMAC-SHA1-96; Confidentiality Algorithm = AES-CBC-128
126
127              6 - Authentication Algorithm = HMAC-MD5; Integrity  Algorithm  =
128              None; Confidentiality Algorithm = None
129
130              7  -  Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
131              HMAC-MD5-128; Confidentiality Algorithm = None
132
133              8 - Authentication Algorithm = HMAC-MD5; Integrity  Algorithm  =
134              HMAC-MD5-128; Confidentiality Algorithm = AES-CBC-128
135
136              11  - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
137              MD5-128; Confidentiality Algorithm = None
138
139              12 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm  =
140              MD5-128; Confidentiality Algorithm = AES-CBC-128
141
142              15 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
143              = None; Confidentiality Algorithm = None
144
145              16 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
146              = HMAC_SHA256_128; Confidentiality Algorithm = None
147
148              17 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
149              = HMAC_SHA256_128; Confidentiality Algorithm = AES-CBC-128
150
151       -l PRIVILEGE-LEVEL, --privilege-level=PRIVILEGE-LEVEL
152              Specify the privilege level to be used. The currently  available
153              privilege levels are USER, OPERATOR, and ADMIN. Defaults to USER
154              if not specified.
155
156       --config-file=FILE
157              Specify an alternate configuration file.
158
159       -W WORKAROUNDS, --workaround-flags=WORKAROUNDS
160              Specify workarounds to vendor compliance issues. Multiple  work‐
161              arounds  can be specified separated by commas. A special command
162              line flag of "none", will indicate no workarounds (may be useful
163              for overriding configured defaults). See WORKAROUNDS below for a
164              list of available workarounds.
165
166       --debug
167              Turn on debugging.
168
169       -?, --help
170              Output a help list and exit.
171
172       --usage
173              Output a usage message and exit.
174
175       -V, --version
176              Output the program version and exit.
177

BMC-INFO OPTIONS

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

HOSTRANGED OPTIONS

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

HOSTRANGED SUPPORT

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

GENERAL TROUBLESHOOTING

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

WORKAROUNDS

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

OEM INTERPRETATION

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

EXAMPLES

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

DIAGNOSTICS

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

KNOWN ISSUES

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

REPORTING BUGS

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

SEE ALSO

583       freeipmi.conf(5), freeipmi(7), ipmi-config(8)
584
585       http://www.gnu.org/software/freeipmi/
586
587
588
589bmc-info 1.6.10                   2022-08-31                       BMC-INFO(8)
Impressum