1IPMI-CHASSIS(8)                 System Commands                IPMI-CHASSIS(8)
2
3
4

NAME

6       ipmi-chassis - IPMI chassis management utility
7

SYNOPSIS

9       ipmi-chassis [OPTION...]
10

DESCRIPTION

12       Ipmi-chassis  is  used for managing/monitoring an IPMI chassis, such as
13       chassis power, identification (i.e. LED control), and status.  See  OP‐
14       TIONS below for all chassis management options available.
15
16       Listed  below  are general IPMI options, tool specific options, trouble
17       shooting information, workaround information, examples, and  known  is‐
18       sues.  For  a  general introduction to FreeIPMI please see freeipmi(7).
19       To perform IPMI chassis configuration, please see  ipmi-config(8).   To
20       perform  some  advanced  chassis  management, please see bmc-device(8).
21       For a more powerful chassis  power  control  utility,  please  see  ip‐
22       mipower(8).
23

GENERAL OPTIONS

25       The following options are general options for configuring IPMI communi‐
26       cation and executing general tool commands.
27
28       -D IPMIDRIVER, --driver-type=IPMIDRIVER
29              Specify the driver type to use instead of doing an  auto  selec‐
30              tion.   The  currently  available  outofband drivers are LAN and
31              LAN_2_0, which perform IPMI 1.5 and IPMI 2.0  respectively.  The
32              currently  available  inband  drivers  are  KCS, SSIF, OPENIPMI,
33              SUNBMC, and INTELDCMI.
34
35       --disable-auto-probe
36              Do not probe in-band IPMI devices for default settings.
37
38       --driver-address=DRIVER-ADDRESS
39              Specify the in-band driver address to be  used  instead  of  the
40              probed  value. DRIVER-ADDRESS should be prefixed with "0x" for a
41              hex value and '0' for an octal value.
42
43       --driver-device=DEVICE
44              Specify the in-band driver device path to be used instead of the
45              probed path.
46
47       --register-spacing=REGISTER-SPACING
48              Specify  the  in-band  driver  register  spacing  instead of the
49              probed value. Argument is in bytes (i.e. 32bit register  spacing
50              = 4)
51
52       --target-channel-number=CHANNEL-NUMBER
53              Specify  the  in-band  driver target channel number to send IPMI
54              requests to.
55
56       --target-slave-address=SLAVE-ADDRESS
57              Specify the in-band driver target slave number to send IPMI  re‐
58              quests to.
59
60       -h      IPMIHOST1,IPMIHOST2,...,      --hostname=IPMIHOST1[:PORT],IPMI‐
61       HOST2[:PORT],...
62              Specify the remote host(s) to communicate with.  Multiple  host‐
63              names  may  be separated by comma or may be specified in a range
64              format; see HOSTRANGED SUPPORT below. An optional  port  can  be
65              specified with each host, which may be useful in port forwarding
66              or similar situations.  If specifying an IPv6 address and  port,
67              use the format [ADDRESS]:PORT.
68
69       -u USERNAME, --username=USERNAME
70              Specify  the username to use when authenticating with the remote
71              host.  If not specified, a null (i.e. anonymous) username is as‐
72              sumed.  The user must have atleast ADMIN privileges in order for
73              this tool to operate fully.
74
75       -p PASSWORD, --password=PASSWORD
76              Specify the password to use when authenticationg with the remote
77              host.   If  not  specified,  a null password is assumed. Maximum
78              password length is 16 for IPMI 1.5 and 20 for IPMI 2.0.
79
80       -P, --password-prompt
81              Prompt for password  to  avoid  possibility  of  listing  it  in
82              process lists.
83
84       -k K_G, --k-g=K_G
85              Specify  the K_g BMC key to use when authenticating with the re‐
86              mote host for IPMI 2.0. If not specified, a null key is assumed.
87              To  input  the  key  in hexadecimal form, prefix the string with
88              '0x'. E.g., the key 'abc' can be entered  with  the  either  the
89              string 'abc' or the string '0x616263'
90
91       -K, --k-g-prompt
92              Prompt  for  k-g  to  avoid possibility of listing it in process
93              lists.
94
95       --session-timeout=MILLISECONDS
96              Specify the session timeout in milliseconds. Defaults  to  20000
97              milliseconds (20 seconds) if not specified.
98
99       --retransmission-timeout=MILLISECONDS
100              Specify  the  packet retransmission timeout in milliseconds. De‐
101              faults to 1000 milliseconds (1 second) if not specified. The re‐
102              transmission timeout cannot be larger than the session timeout.
103
104       -a AUTHENTICATION-TYPE, --authentication-type=AUTHENTICATION-TYPE
105              Specify  the  IPMI 1.5 authentication type to use. The currently
106              available authentication types are NONE,  STRAIGHT_PASSWORD_KEY,
107              MD2, and MD5. Defaults to MD5 if not specified.
108
109       -I CIPHER-SUITE-ID, --cipher-suite-id=CIPHER-SUITE-ID
110              Specify the IPMI 2.0 cipher suite ID to use. The Cipher Suite ID
111              identifies a set of authentication, integrity, and confidential‐
112              ity  algorithms to use for IPMI 2.0 communication. The authenti‐
113              cation algorithm identifies the algorithm  to  use  for  session
114              setup,  the  integrity algorithm identifies the algorithm to use
115              for session packet signatures, and the confidentiality algorithm
116              identifies the algorithm to use for payload encryption. Defaults
117              to cipher suite ID 3 if  not  specified.  The  following  cipher
118              suite ids are currently supported:
119
120              0 - Authentication Algorithm = None; Integrity Algorithm = None;
121              Confidentiality Algorithm = None
122
123              1 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm  =
124              None; Confidentiality Algorithm = None
125
126              2  - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
127              HMAC-SHA1-96; Confidentiality Algorithm = None
128
129              3 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm  =
130              HMAC-SHA1-96; Confidentiality Algorithm = AES-CBC-128
131
132              6  -  Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
133              None; Confidentiality Algorithm = None
134
135              7 - Authentication Algorithm = HMAC-MD5; Integrity  Algorithm  =
136              HMAC-MD5-128; Confidentiality Algorithm = None
137
138              8  -  Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
139              HMAC-MD5-128; Confidentiality Algorithm = AES-CBC-128
140
141              11 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm  =
142              MD5-128; Confidentiality Algorithm = None
143
144              12  - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
145              MD5-128; Confidentiality Algorithm = AES-CBC-128
146
147              15 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
148              = None; Confidentiality Algorithm = None
149
150              16 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
151              = HMAC_SHA256_128; Confidentiality Algorithm = None
152
153              17 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
154              = HMAC_SHA256_128; Confidentiality Algorithm = AES-CBC-128
155
156       -l PRIVILEGE-LEVEL, --privilege-level=PRIVILEGE-LEVEL
157              Specify  the privilege level to be used. The currently available
158              privilege levels are USER, OPERATOR, and ADMIN. Defaults to  AD‐
159              MIN if not specified.
160
161       --config-file=FILE
162              Specify an alternate configuration file.
163
164       -W WORKAROUNDS, --workaround-flags=WORKAROUNDS
165              Specify  workarounds to vendor compliance issues. Multiple work‐
166              arounds can be specified separated by commas. A special  command
167              line flag of "none", will indicate no workarounds (may be useful
168              for overriding configured defaults). See WORKAROUNDS below for a
169              list of available workarounds.
170
171       --debug
172              Turn on debugging.
173
174       -?, --help
175              Output a help list and exit.
176
177       --usage
178              Output a usage message and exit.
179
180       -V, --version
181              Output the program version and exit.
182

IPMI-CHASSIS OPTIONS

184       The following options are specific to ipmi-chassis.
185
186       --get-chassis-capabilities
187              Get  chassis  capabilities.  This command returns information on
188              which main chassis management functions are available.
189
190       --get-chassis-status
191              Get chassis status. This command returns high level  status  in‐
192              formation on the chassis.
193
194       --chassis-control=CONTROL
195              Control the chassis. This command provides power-up, power-down,
196              and  reset  control.  Supported  values:  POWER-DOWN,  POWER-UP,
197              POWER-CYCLE, HARD-RESET, DIAGNOSTIC-INTERRUPT, SOFT-SHUTDOWN.
198
199       --chassis-identify=IDENTIFY
200              Set  chassis identification. This command controls physical sys‐
201              tem identification, typically a LED. Supported values:  TURN-OFF
202              to turn off identification, <interval> to turn on identification
203              for "interval" seconds, FORCE to turn on indefinitely.
204
205       --get-system-restart-cause
206              Get system restart cause.
207
208       --get-power-on-hours-counter
209              Get power on hours (POH) counter.
210

HOSTRANGED OPTIONS

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

HOSTRANGED SUPPORT

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

GENERAL TROUBLESHOOTING

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

WORKAROUNDS

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

EXAMPLES

531       # ipmi-chassis --get-status
532
533       Get the chassis status of the local machine.
534
535       # ipmi-chassis -h ahost -u myusername -p mypassword --get-status
536
537       Get the chassis status of a remote machine using IPMI over LAN.
538
539       #  ipmi-chassis  -h mycluster[0-127] -u myusername -p mypassword --get-
540       status
541
542       Get the chassis status across a cluster using IPMI over LAN.
543
544       # ipmi-chassis -h ahost  -u  myusername  -p  mypassword  --chassis-con‐
545       trol=POWER-UP
546
547       Power on a remote machine 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 © 2007-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(7), bmc-device(8), ipmi-config(8), ipmipower(8)
585
586       http://www.gnu.org/software/freeipmi/
587
588
589
590ipmi-chassis 1.6.11               2023-06-07                   IPMI-CHASSIS(8)
Impressum