1IPMI-CHASSIS(8) System Commands IPMI-CHASSIS(8)
2
6 ipmi-chassis - IPMI chassis management utility
7
9 ipmi-chassis [OPTION...]
10
12 Ipmi-chassis is used for managing/monitoring an IPMI chassis, such as
13 chassis power, indentification (i.e. LED control), and status. See
14 OPTIONS below for all chassis management options available.
15 Listed below are general IPMI options, tool specific options, trouble
17 shooting information, workaround information, examples, and known
18 issues. For a general introduction to FreeIPMI please see freeipmi(7).
19 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
22 ipmipower(8).
23
25 The following options are general options for configuring IPMI communi‐
26 cation and executing general tool commands.
27 -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 --disable-auto-probe
36 Do not probe in-band IPMI devices for default settings.
37 --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 --driver-device=DEVICE
44 Specify the in-band driver device path to be used instead of the
45 probed path.
46 --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 --target-channel-number=CHANNEL-NUMBER
53 Specify the in-band driver target channel number to send IPMI
54 requests to.
55 --target-slave-address=SLAVE-ADDRESS
57 Specify the in-band driver target slave number to send IPMI
58 requests to.
59 -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 -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
72 assumed. The user must have atleast ADMIN privileges in order
73 for this tool to operate fully.
74 -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 -P, --password-prompt
81 Prompt for password to avoid possibility of listing it in
82 process lists.
83 -k K_G, --k-g=K_G
85 Specify the K_g BMC key to use when authenticating with the
86 remote host for IPMI 2.0. If not specified, a null key is
87 assumed. To input the key in hexadecimal form, prefix the string
88 with '0x'. E.g., the key 'abc' can be entered with the either
89 the string 'abc' or the string '0x616263'
90 -K, --k-g-prompt
92 Prompt for k-g to avoid possibility of listing it in process
93 lists.
94 --session-timeout=MILLISECONDS
96 Specify the session timeout in milliseconds. Defaults to 20000
97 milliseconds (20 seconds) if not specified.
98 --retransmission-timeout=MILLISECONDS
100 Specify the packet retransmission timeout in milliseconds.
101 Defaults to 1000 milliseconds (1 second) if not specified. The
102 retransmission timeout cannot be larger than the session time‐
103 out.
104 -a AUTHENTICATION-TYPE, --authentication-type=AUTHENTICATION-TYPE
106 Specify the IPMI 1.5 authentication type to use. The currently
107 available authentication types are NONE, STRAIGHT_PASSWORD_KEY,
108 MD2, and MD5. Defaults to MD5 if not specified.
109 -I CIPHER-SUITE-ID, --cipher-suite-id=CIPHER-SUITE-ID
111 Specify the IPMI 2.0 cipher suite ID to use. The Cipher Suite ID
112 identifies a set of authentication, integrity, and confidential‐
113 ity algorithms to use for IPMI 2.0 communication. The authenti‐
114 cation algorithm identifies the algorithm to use for session
115 setup, the integrity algorithm identifies the algorithm to use
116 for session packet signatures, and the confidentiality algorithm
117 identifies the algorithm to use for payload encryption. Defaults
118 to cipher suite ID 3 if not specified. The following cipher
119 suite ids are currently supported:
120 0 - Authentication Algorithm = None; Integrity Algorithm = None;
122 Confidentiality Algorithm = None
123 1 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
125 None; Confidentiality Algorithm = None
126 2 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
128 HMAC-SHA1-96; Confidentiality Algorithm = None
129 3 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
131 HMAC-SHA1-96; Confidentiality Algorithm = AES-CBC-128
132 6 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
134 None; Confidentiality Algorithm = None
135 7 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
137 HMAC-MD5-128; Confidentiality Algorithm = None
138 8 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
140 HMAC-MD5-128; Confidentiality Algorithm = AES-CBC-128
141 11 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
143 MD5-128; Confidentiality Algorithm = None
144 12 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
146 MD5-128; Confidentiality Algorithm = AES-CBC-128
147 15 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
149 = None; Confidentiality Algorithm = None
150 16 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
152 = HMAC_SHA256_128; Confidentiality Algorithm = None
153 17 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
155 = HMAC_SHA256_128; Confidentiality Algorithm = AES-CBC-128
156 -l PRIVILEGE-LEVEL, --privilege-level=PRIVILEGE-LEVEL
158 Specify the privilege level to be used. The currently available
159 privilege levels are USER, OPERATOR, and ADMIN. Defaults to
160 ADMIN if not specified.
161 --config-file=FILE
163 Specify an alternate configuration file.
164 -W WORKAROUNDS, --workaround-flags=WORKAROUNDS
166 Specify workarounds to vendor compliance issues. Multiple work‐
167 arounds can be specified separated by commas. A special command
168 line flag of "none", will indicate no workarounds (may be useful
169 for overriding configured defaults). See WORKAROUNDS below for a
170 list of available workarounds.
171 --debug
173 Turn on debugging.
174 -?, --help
176 Output a help list and exit.
177 --usage
179 Output a usage message and exit.
180 -V, --version
182 Output the program version and exit.
183
185 The following options are specific to ipmi-chassis.
186 --get-chassis-capabilities
188 Get chassis capabilities. This command returns information on
189 which main chassis management functions are available.
190 --get-chassis-status
192 Get chassis status. This command returns high level status
193 information on the chassis.
194 --chassis-control=CONTROL
196 Control the chassis. This command provides power-up, power-down,
197 and reset control. Supported values: POWER-DOWN, POWER-UP,
198 POWER-CYCLE, HARD-RESET, DIAGNOSTIC-INTERRUPT, SOFT-SHUTDOWN.
199 --chassis-identify=IDENTIFY
201 Set chassis identification. This command controls physical sys‐
202 tem identification, typically a LED. Supported values: TURN-OFF
203 to turn off identification, <interval> to turn on identification
204 for "interval" seconds, FORCE to turn on indefinitely.
205 --get-system-restart-cause
207 Get system restart cause.
208 --get-power-on-hours-counter
210 Get power on hours (POH) counter.
211
213 The following options manipulate hostranged output. See HOSTRANGED SUP‐
214 PORT below for additional information on hostranges.
215 -B, --buffer-output
217 Buffer hostranged output. For each node, buffer standard output
218 until the node has completed its IPMI operation. When specifying
219 this option, data may appear to output slower to the user since
220 the the entire IPMI operation must complete before any data can
221 be output. See HOSTRANGED SUPPORT below for additional informa‐
222 tion.
223 -C, --consolidate-output
225 Consolidate hostranged output. The complete standard output from
226 every node specified will be consolidated so that nodes with
227 identical output are not output twice. A header will list those
228 nodes with the consolidated output. When this option is speci‐
229 fied, no output can be seen until the IPMI operations to all
230 nodes has completed. If the user breaks out of the program
231 early, all currently consolidated output will be dumped. See
232 HOSTRANGED SUPPORT below for additional information.
233 -F NUM, --fanout=NUM
235 Specify multiple host fanout. A "sliding window" (or fanout)
236 algorithm is used for parallel IPMI communication so that slower
237 nodes or timed out nodes will not impede parallel communication.
238 The maximum number of threads available at the same time is lim‐
239 ited by the fanout. The default is 64.
240 -E, --eliminate
242 Eliminate hosts determined as undetected by ipmidetect. This
243 attempts to remove the common issue of hostranged execution tim‐
244 ing out due to several nodes being removed from service in a
245 large cluster. The ipmidetectd daemon must be running on the
246 node executing the command.
247 --always-prefix
249 Always prefix output, even if only one host is specified or com‐
250 municating in-band. This option is primarily useful for script‐
251 ing purposes. Option will be ignored if specified with the -C
252 option.
253
255 Multiple hosts can be input either as an explicit comma separated lists
256 of hosts or a range of hostnames in the general form: prefix[n-m,l-
257 k,...], where n < m and l < k, etc. The later form should not be con‐
258 fused with regular expression character classes (also denoted by []).
259 For example, foo[19] does not represent foo1 or foo9, but rather repre‐
260 sents a degenerate range: foo19.
261 This range syntax is meant only as a convenience on clusters with a
263 prefixNN naming convention and specification of ranges should not be
264 considered necessary -- the list foo1,foo9 could be specified as such,
265 or by the range foo[1,9].
266 Some examples of range usage follow:
268 foo[01-05] instead of foo01,foo02,foo03,foo04,foo05
269 foo[7,9-10] instead of foo7,foo9,foo10
270 foo[0-3] instead of foo0,foo1,foo2,foo3
271 As a reminder to the reader, some shells will interpret brackets ([ and
273 ]) for pattern matching. Depending on your shell, it may be necessary
274 to enclose ranged lists within quotes.
275 When multiple hosts are specified by the user, a thread will be exe‐
277 cuted for each host in parallel up to the configured fanout (which can
278 be adjusted via the -F option). This will allow communication to large
279 numbers of nodes far more quickly than if done in serial.
280 By default, standard output from each node specified will be output
282 with the hostname prepended to each line. Although this output is read‐
283 able in many situations, it may be difficult to read in other situa‐
284 tions. For example, output from multiple nodes may be mixed together.
285 The -B and -C options can be used to change this default.
286 In-band IPMI Communication will be used when the host "localhost" is
288 specified. This allows the user to add the localhost into the hos‐
289 tranged output.
290
292 Most often, IPMI problems are due to configuration problems.
293 IPMI over LAN problems involve a misconfiguration of the remote
295 machine's BMC. Double check to make sure the following are configured
296 properly in the remote machine's BMC: IP address, MAC address, subnet
297 mask, username, user enablement, user privilege, password, LAN privi‐
298 lege, LAN enablement, and allowed authentication type(s). For IPMI 2.0
299 connections, double check to make sure the cipher suite privilege(s)
300 and K_g key are configured properly. The ipmi-config(8) tool can be
301 used to check and/or change these configuration settings.
302 Inband IPMI problems are typically caused by improperly configured
304 drivers or non-standard BMCs.
305 In addition to the troubleshooting tips below, please see WORKAROUNDS
307 below to also if there are any vendor specific bugs that have been dis‐
308 covered and worked around.
309 Listed below are many of the common issues for error messages. For
311 additional support, please e-mail the <freeipmi-users@gnu.org> mailing
312 list.
313 "username invalid" - The username entered (or a NULL username if none
315 was entered) is not available on the remote machine. It may also be
316 possible the remote BMC's username configuration is incorrect.
317 "password invalid" - The password entered (or a NULL password if none
319 was entered) is not correct. It may also be possible the password for
320 the user is not correctly configured on the remote BMC.
321 "password verification timeout" - Password verification has timed out.
323 A "password invalid" error (described above) or a generic "session
324 timeout" (described below) occurred. During this point in the protocol
325 it cannot be differentiated which occurred.
326 "k_g invalid" - The K_g key entered (or a NULL K_g key if none was
328 entered) is not correct. It may also be possible the K_g key is not
329 correctly configured on the remote BMC.
330 "privilege level insufficient" - An IPMI command requires a higher user
332 privilege than the one authenticated with. Please try to authenticate
333 with a higher privilege. This may require authenticating to a different
334 user which has a higher maximum privilege.
335 "privilege level cannot be obtained for this user" - The privilege
337 level you are attempting to authenticate with is higher than the maxi‐
338 mum allowed for this user. Please try again with a lower privilege. It
339 may also be possible the maximum privilege level allowed for a user is
340 not configured properly on the remote BMC.
341 "authentication type unavailable for attempted privilege level" - The
343 authentication type you wish to authenticate with is not available for
344 this privilege level. Please try again with an alternate authentication
345 type or alternate privilege level. It may also be possible the avail‐
346 able authentication types you can authenticate with are not correctly
347 configured on the remote BMC.
348 "cipher suite id unavailable" - The cipher suite id you wish to authen‐
350 ticate with is not available on the remote BMC. Please try again with
351 an alternate cipher suite id. It may also be possible the available
352 cipher suite ids are not correctly configured on the remote BMC.
353 "ipmi 2.0 unavailable" - IPMI 2.0 was not discovered on the remote
355 machine. Please try to use IPMI 1.5 instead.
356 "connection timeout" - Initial IPMI communication failed. A number of
358 potential errors are possible, including an invalid hostname specified,
359 an IPMI IP address cannot be resolved, IPMI is not enabled on the
360 remote server, the network connection is bad, etc. Please verify con‐
361 figuration and connectivity.
362 "session timeout" - The IPMI session has timed out. Please reconnect.
364 If this error occurs often, you may wish to increase the retransmission
365 timeout. Some remote BMCs are considerably slower than others.
366 "device not found" - The specified device could not be found. Please
368 check configuration or inputs and try again.
369 "driver timeout" - Communication with the driver or device has timed
371 out. Please try again.
372 "message timeout" - Communication with the driver or device has timed
374 out. Please try again.
375 "BMC busy" - The BMC is currently busy. It may be processing informa‐
377 tion or have too many simultaneous sessions to manage. Please wait and
378 try again.
379 "could not find inband device" - An inband device could not be found.
381 Please check configuration or specify specific device or driver on the
382 command line.
383 "driver timeout" - The inband driver has timed out communicating to the
385 local BMC or service processor. The BMC or service processor may be
386 busy or (worst case) possibly non-functioning.
387 "internal IPMI error" - An IPMI error has occurred that FreeIPMI does
389 not know how to handle. Please e-mail <freeipmi-users@gnu.org> to
390 report the issue.
391
393 With so many different vendors implementing their own IPMI solutions,
394 different vendors may implement their IPMI protocols incorrectly. The
395 following describes a number of workarounds currently available to han‐
396 dle discovered compliance issues. When possible, workarounds have been
397 implemented so they will be transparent to the user. However, some will
398 require the user to specify a workaround be used via the -W option.
399 The hardware listed below may only indicate the hardware that a problem
401 was discovered on. Newer versions of hardware may fix the problems
402 indicated below. Similar machines from vendors may or may not exhibit
403 the same problems. Different vendors may license their firmware from
404 the same IPMI firmware developer, so it may be worthwhile to try work‐
405 arounds listed below even if your motherboard is not listed.
406 If you believe your hardware has an additional compliance issue that
408 needs a workaround to be implemented, please contact the FreeIPMI main‐
409 tainers on <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
410 assumeio - This workaround flag will assume inband interfaces communi‐
412 cate with system I/O rather than being memory-mapped. This will work
413 around systems that report invalid base addresses. Those hitting this
414 issue may see "device not supported" or "could not find inband device"
415 errors. Issue observed on HP ProLiant DL145 G1.
416 spinpoll - This workaround flag will inform some inband drivers (most
418 notably the KCS driver) to spin while polling rather than putting the
419 process to sleep. This may significantly improve the wall clock running
420 time of tools because an operating system scheduler's granularity may
421 be much larger than the time it takes to perform a single IPMI message
422 transaction. However, by spinning, your system may be performing less
423 useful work by not contexting out the tool for a more useful task.
424 authcap - This workaround flag will skip early checks for username
426 capabilities, authentication capabilities, and K_g support and allow
427 IPMI authentication to succeed. It works around multiple issues in
428 which the remote system does not properly report username capabilities,
429 authentication capabilities, or K_g status. Those hitting this issue
430 may see "username invalid", "authentication type unavailable for
431 attempted privilege level", or "k_g invalid" errors. Issue observed on
432 Asus P5M2/P5MT-R/RS162-E4/RX4, Intel SR1520ML/X38ML, and Sun Fire
433 2200/4150/4450 with ELOM.
434 nochecksumcheck - This workaround flag will tell FreeIPMI to not check
436 the checksums returned from IPMI command responses. It works around
437 systems that return invalid checksums due to implementation errors, but
438 the packet is otherwise valid. Users are cautioned on the use of this
439 option, as it removes validation of packet integrity in a number of
440 circumstances. However, it is unlikely to be an issue in most situa‐
441 tions. Those hitting this issue may see "connection timeout", "session
442 timeout", or "password verification timeout" errors. On IPMI 1.5 con‐
443 nections, the "noauthcodecheck" workaround may also needed too. Issue
444 observed on Supermicro X9SCM-iiF, Supermicro X9DRi-F, and Supermicro
445 X9DRFR.
446 idzero - This workaround flag will allow empty session IDs to be
448 accepted by the client. It works around IPMI sessions that report empty
449 session IDs to the client. Those hitting this issue may see "session
450 timeout" errors. Issue observed on Tyan S2882 with M3289 BMC.
451 unexpectedauth - This workaround flag will allow unexpected non-null
453 authcodes to be checked as though they were expected. It works around
454 an issue when packets contain non-null authentication data when they
455 should be null due to disabled per-message authentication. Those hit‐
456 ting this issue may see "session timeout" errors. Issue observed on
457 Dell PowerEdge 2850,SC1425. Confirmed fixed on newer firmware.
458 forcepermsg - This workaround flag will force per-message authentica‐
460 tion to be used no matter what is advertised by the remote system. It
461 works around an issue when per-message authentication is advertised as
462 disabled on the remote system, but it is actually required for the pro‐
463 tocol. Those hitting this issue may see "session timeout" errors.
464 Issue observed on IBM eServer 325.
465 endianseq - This workaround flag will flip the endian of the session
467 sequence numbers to allow the session to continue properly. It works
468 around IPMI 1.5 session sequence numbers that are the wrong endian.
469 Those hitting this issue may see "session timeout" errors. Issue
470 observed on some Sun ILOM 1.0/2.0 (depends on service processor
471 endian).
472 noauthcodecheck - This workaround flag will tell FreeIPMI to not check
474 the authentication codes returned from IPMI 1.5 command responses. It
475 works around systems that return invalid authentication codes due to
476 hashing or implementation errors. Users are cautioned on the use of
477 this option, as it removes an authentication check verifying the valid‐
478 ity of a packet. However, in most organizations, this is unlikely to be
479 a security issue. Those hitting this issue may see "connection time‐
480 out", "session timeout", or "password verification timeout" errors.
481 Issue observed on Xyratex FB-H8-SRAY, Intel Windmill, Quanta Winter‐
482 fell, and Wiwynn Windmill.
483 intel20 - This workaround flag will work around several Intel IPMI 2.0
485 authentication issues. The issues covered include padding of usernames,
486 and password truncation if the authentication algorithm is HMAC-
487 MD5-128. Those hitting this issue may see "username invalid", "password
488 invalid", or "k_g invalid" errors. Issue observed on Intel SE7520AF2
489 with Intel Server Management Module (Professional Edition).
490 supermicro20 - This workaround flag will work around several Supermicro
492 IPMI 2.0 authentication issues on motherboards w/ Peppercon IPMI
493 firmware. The issues covered include handling invalid length authenti‐
494 cation codes. Those hitting this issue may see "password invalid"
495 errors. Issue observed on Supermicro H8QME with SIMSO daughter card.
496 Confirmed fixed on newerver firmware.
497 sun20 - This workaround flag will work work around several Sun IPMI 2.0
499 authentication issues. The issues covered include invalid lengthed hash
500 keys, improperly hashed keys, and invalid cipher suite records. Those
501 hitting this issue may see "password invalid" or "bmc error" errors.
502 Issue observed on Sun Fire 4100/4200/4500 with ILOM. This workaround
503 automatically includes the "opensesspriv" workaround.
504 opensesspriv - This workaround flag will slightly alter FreeIPMI's IPMI
506 2.0 connection protocol to workaround an invalid hashing algorithm used
507 by the remote system. The privilege level sent during the Open Session
508 stage of an IPMI 2.0 connection is used for hashing keys instead of the
509 privilege level sent during the RAKP1 connection stage. Those hitting
510 this issue may see "password invalid", "k_g invalid", or "bad rmcpplus
511 status code" errors. Issue observed on Sun Fire 4100/4200/4500 with
512 ILOM, Inventec 5441/Dell Xanadu II, Supermicro X8DTH, Supermicro X8DTG,
513 Intel S5500WBV/Penguin Relion 700, Intel S2600JF/Appro 512X, and Quanta
514 QSSC-S4R/Appro GB812X-CN. This workaround is automatically triggered
515 with the "sun20" workaround.
516 integritycheckvalue - This workaround flag will work around an invalid
518 integrity check value during an IPMI 2.0 session establishment when
519 using Cipher Suite ID 0. The integrity check value should be 0 length,
520 however the remote motherboard responds with a non-empty field. Those
521 hitting this issue may see "k_g invalid" errors. Issue observed on
522 Supermicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin Relion
523 700, and Intel S2600JF/Appro 512X.
524 No IPMI 1.5 Support - Some motherboards that support IPMI 2.0 have been
526 found to not support IPMI 1.5. Those hitting this issue may see "ipmi
527 2.0 unavailable" or "connection timeout" errors. This issue can be
528 worked around by using IPMI 2.0 instead of IPMI 1.5 by specifying
529 --driver-type=LAN_2_0. Issue observed on HP Proliant DL 145.
530
532 # ipmi-chassis --get-status
533 Get the chassis status of the local machine.
535 # ipmi-chassis -h ahost -u myusername -p mypassword --get-status
537 Get the chassis status of a remote machine using IPMI over LAN.
539 # ipmi-chassis -h mycluster[0-127] -u myusername -p mypassword --get-
541 status
542 Get the chassis status across a cluster using IPMI over LAN.
544 # ipmi-chassis -h ahost -u myusername -p mypassword --chassis-con‐
546 trol=POWER-UP
547 Power on a remote machine using IPMI over LAN.
549
551 Upon successful execution, exit status is 0. On error, exit status is
552 1.
553 If multiple hosts are specified for communication, the exit status is 0
555 if and only if all targets successfully execute. Otherwise the exit
556 status is 1.
557
559 On older operating systems, if you input your username, password, and
560 other potentially security relevant information on the command line,
561 this information may be discovered by other users when using tools like
562 the ps(1) command or looking in the /proc file system. It is generally
563 more secure to input password information with options like the -P or
564 -K options. Configuring security relevant information in the FreeIPMI
565 configuration file would also be an appropriate way to hide this infor‐
566 mation.
567 In order to prevent brute force attacks, some BMCs will temporarily
569 "lock up" after a number of remote authentication errors. You may need
570 to wait awhile in order to this temporary "lock up" to pass before you
571 may authenticate again.
572
574 Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
575
577 Copyright © 2007-2015 FreeIPMI Core Team
578 This program is free software; you can redistribute it and/or modify it
580 under the terms of the GNU General Public License as published by the
581 Free Software Foundation; either version 3 of the License, or (at your
582 option) any later version.
583
585 freeipmi(7), bmc-device(8), ipmi-config(8), ipmipower(8)
586 http://www.gnu.org/software/freeipmi/
588ipmi-chassis 1.6.2 2018-05-03 IPMI-CHASSIS(8)