1IPMI-DCMI(8) System Commands IPMI-DCMI(8)
2
6 ipmi-dcmi - IPMI DCMI utility
7
9 ipmi-dcmi [OPTION...]
10
12 Ipmi-dcmi is used to execute Data Center Manageability Interface (often
13 referred to as DCM or DCMI) IPMI extension commands. DCMI extensions
14 include support for asset management and power usage management. Most
15 will be interested in DCMI for its power management features. By con‐
16 figuring an exception action, power limit, and correction time limit,
17 power usage in a data center can be managed more affectively. Please
18 see --set-power-limit option below for more information.
19 The DCMI specification encompasses many traditional IPMI features that
21 are not implemented directly in this tool. Please see ipmiconsole(8)
22 for Serial-over-LAN (SOL) support, ipmi-chassis(8) for power status,
23 power control, identification, and ACPI power state information,
24 ipmipower(8) for power status and power control, ipmi-sel(8) for System
25 Event Log (SEL) information, bmc-info(8) for device and globally unique
26 ID (guid) information, ipmi-sensors(8) for sensor readings, and bmc-
27 config(8) for configuration.
28 Listed below are general IPMI options, tool specific options, trouble
30 shooting information, workaround information, examples, and known
31 issues. For a general introduction to FreeIPMI please see freeipmi(7).
32
34 The following options are general options for configuring IPMI communi‐
35 cation and executing general tool commands.
36 -D IPMIDRIVER, --driver-type=IPMIDRIVER
38 Specify the driver type to use instead of doing an auto selec‐
39 tion. The currently available outofband drivers are LAN and
40 LAN_2_0, which perform IPMI 1.5 and IPMI 2.0 respectively. The
41 currently available inband drivers are KCS, SSIF, OPENIPMI, and
42 SUNBMC.
43 --disable-auto-probe
45 Do not probe in-band IPMI devices for default settings.
46 --driver-address=DRIVER-ADDRESS
48 Specify the in-band driver address to be used instead of the
49 probed value. DRIVER-ADDRESS should be prefixed with "0x" for a
50 hex value and '0' for an octal value.
51 --driver-device=DEVICE
53 Specify the in-band driver device path to be used instead of the
54 probed path.
55 --register-spacing=REGISTER-SPACING
57 Specify the in-band driver register spacing instead of the
58 probed value. Argument is in bytes (i.e. 32bit register spacing
59 = 4)
60 --target-channel-number=CHANNEL-NUMBER
62 Specify the in-band driver target channel number to send IPMI
63 requests to.
64 --target-slave-address=SLAVE-ADDRESS
66 Specify the in-band driver target slave number to send IPMI
67 requests to.
68 -h IPMIHOST1,IPMIHOST2,..., --hostname=IPMIHOST1[:PORT],IPMI‐
70 HOST2[:PORT],...
71 Specify the remote host(s) to communicate with. Multiple host‐
72 names may be separated by comma or may be specified in a range
73 format; see HOSTRANGED SUPPORT below. An optional port can be
74 specified with each host, which may be useful in port forwarding
75 or similar situations.
76 -u USERNAME, --username=USERNAME
78 Specify the username to use when authenticating with the remote
79 host. If not specified, a null (i.e. anonymous) username is
80 assumed. The user must have atleast ADMIN privileges in order
81 for this tool to operate fully.
82 -p PASSWORD, --password=PASSWORD
84 Specify the password to use when authenticationg with the remote
85 host. If not specified, a null password is assumed. Maximum
86 password length is 16 for IPMI 1.5 and 20 for IPMI 2.0.
87 -P, --password-prompt
89 Prompt for password to avoid possibility of listing it in
90 process lists.
91 -k K_G, --k-g=K_G
93 Specify the K_g BMC key to use when authenticating with the
94 remote host for IPMI 2.0. If not specified, a null key is
95 assumed. To input the key in hexadecimal form, prefix the string
96 with '0x'. E.g., the key 'abc' can be entered with the either
97 the string 'abc' or the string '0x616263'
98 -K, --k-g-prompt
100 Prompt for k-g to avoid possibility of listing it in process
101 lists.
102 --session-timeout=MILLISECONDS
104 Specify the session timeout in milliseconds. Defaults to 20000
105 milliseconds (20 seconds) if not specified.
106 --retransmission-timeout=MILLISECONDS
108 Specify the packet retransmission timeout in milliseconds.
109 Defaults to 1000 milliseconds (1 second) if not specified. The
110 retransmission timeout cannot be larger than the session time‐
111 out.
112 -a AUTHENTICATION-TYPE, --authentication-type=AUTHENTICATION-TYPE
114 Specify the IPMI 1.5 authentication type to use. The currently
115 available authentication types are NONE, STRAIGHT_PASSWORD_KEY,
116 MD2, and MD5. Defaults to MD5 if not specified.
117 -I CIPHER-SUITE-ID, --cipher-suite-id=CIPHER-SUITE-ID
119 Specify the IPMI 2.0 cipher suite ID to use. The Cipher Suite ID
120 identifies a set of authentication, integrity, and confidential‐
121 ity algorithms to use for IPMI 2.0 communication. The authenti‐
122 cation algorithm identifies the algorithm to use for session
123 setup, the integrity algorithm identifies the algorithm to use
124 for session packet signatures, and the confidentiality algorithm
125 identifies the algorithm to use for payload encryption. Defaults
126 to cipher suite ID 3 if not specified. The following cipher
127 suite ids are currently supported:
128 0 - Authentication Algorithm = None; Integrity Algorithm = None;
130 Confidentiality Algorithm = None
131 1 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
133 None; Confidentiality Algorithm = None
134 2 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
136 HMAC-SHA1-96; Confidentiality Algorithm = None
137 3 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
139 HMAC-SHA1-96; Confidentiality Algorithm = AES-CBC-128
140 6 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
142 None; Confidentiality Algorithm = None
143 7 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
145 HMAC-MD5-128; Confidentiality Algorithm = None
146 8 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
148 HMAC-MD5-128; Confidentiality Algorithm = AES-CBC-128
149 11 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
151 MD5-128; Confidentiality Algorithm = None
152 12 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
154 MD5-128; Confidentiality Algorithm = AES-CBC-128
155 15 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
157 = None; Confidentiality Algorithm = None
158 16 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
160 = HMAC_SHA256_128; Confidentiality Algorithm = None
161 17 - Authentication Algorithm = HMAC-SHA256; Integrity Algorithm
163 = HMAC_SHA256_128; Confidentiality Algorithm = AES-CBC-128
164 -l PRIVILEGE-LEVEL, --privilege-level=PRIVILEGE-LEVEL
166 Specify the privilege level to be used. The currently available
167 privilege levels are USER, OPERATOR, and ADMIN. Defaults to
168 ADMIN if not specified.
169 --config-file=FILE
171 Specify an alternate configuration file.
172 -W WORKAROUNDS, --workaround-flags=WORKAROUNDS
174 Specify workarounds to vendor compliance issues. Multiple work‐
175 arounds can be specified separated by commas. A special command
176 line flag of "none", will indicate no workarounds (may be useful
177 for overriding configured defaults). See WORKAROUNDS below for a
178 list of available workarounds.
179 --debug
181 Turn on debugging.
182 -?, --help
184 Output a help list and exit.
185 --usage
187 Output a usage message and exit.
188 -V, --version
190 Output the program version and exit.
191
193 The following options are specific to Ipmi-dcmi.
194 --get-dcmi-capability-info
196 Get DCMI capability information.
197 --get-asset-tag
199 Get asset tag.
200 --set-asset-tag=STRING
202 Set asset tag.
203 --get-management-controller-identifier-string
205 Get management controller identifier string tag.
206 --set-management-controller-identifier-string=STRING
208 Set management controller identifier string tag.
209 --get-dcmi-sensor-info
211 Get DCMI sensor information.
212 --get-system-power-statistics
214 Get system power statistics.
215 --get-enhanced-system-power-statistics
217 Get enhanced system power statistics.
218 --get-power-limit
220 Get power limit information.
221 --set-power-limit
223 Set power limit configuration. Can specify configuration via the
224 --exception-actions, --power-limit-requested, --correc‐
225 tion-time-limit, and --correction-time-limit options listed
226 below. If one or more options below are not specified, current
227 configuration will be utilized.
228 --exception-actions=BITMASK
230 Specify exception actions for set power limit configuration.
231 Special case allowable values: NO_ACTION, HARD_POWER_OFF_SYSTEM,
232 LOG_EVENT_TO_SEL_ONLY. Other values (e.g. 0x02 through 0x10) are
233 OEM dependent. Used with the --set-power-limit option.
234 --power-limit-requested=WATTS
236 Specify power limit for set power limit configuration. Input is
237 specified in watts. Used with the --set-power-limit option.
238 --correction-time-limit=MILLISECONDS
240 Specify correction time limit for set power limit configuration.
241 Input is specified in milliseconds. Used with the
242 --set-power-limit option.
243 --statistics-sampling-period=SECONDS
245 Specify management application statistics sampling period for
246 set power limit configuration. Input is specified in seconds.
247 Used with the --set-power-limit option.
248 --activate-deactivate-power-limit=OPERATION
250 Activate or deactivate power limit. Allowed values: ACTIVATE,
251 DEACTIVATE.
252 --interpret-oem-data
254 Attempt to interpret OEM data, such as event data, sensor read‐
255 ings, or general extra info, etc. If an OEM interpretation is
256 not available, the default output will be generated. Correctness
257 of OEM interpretations cannot be guaranteed due to potential
258 changes OEM vendors may make in products, firmware, etc. See OEM
259 INTERPRETATION below for confirmed supported motherboard inter‐
260 pretations.
261
263 The following options manipulate hostranged output. See HOSTRANGED SUP‐
264 PORT below for additional information on hostranges.
265 -B, --buffer-output
267 Buffer hostranged output. For each node, buffer standard output
268 until the node has completed its IPMI operation. When specifying
269 this option, data may appear to output slower to the user since
270 the the entire IPMI operation must complete before any data can
271 be output. See HOSTRANGED SUPPORT below for additional informa‐
272 tion.
273 -C, --consolidate-output
275 Consolidate hostranged output. The complete standard output from
276 every node specified will be consolidated so that nodes with
277 identical output are not output twice. A header will list those
278 nodes with the consolidated output. When this option is speci‐
279 fied, no output can be seen until the IPMI operations to all
280 nodes has completed. If the user breaks out of the program
281 early, all currently consolidated output will be dumped. See
282 HOSTRANGED SUPPORT below for additional information.
283 -F NUM, --fanout=NUM
285 Specify multiple host fanout. A "sliding window" (or fanout)
286 algorithm is used for parallel IPMI communication so that slower
287 nodes or timed out nodes will not impede parallel communication.
288 The maximum number of threads available at the same time is lim‐
289 ited by the fanout. The default is 64.
290 -E, --eliminate
292 Eliminate hosts determined as undetected by ipmidetect. This
293 attempts to remove the common issue of hostranged execution tim‐
294 ing out due to several nodes being removed from service in a
295 large cluster. The ipmidetectd daemon must be running on the
296 node executing the command.
297 --always-prefix
299 Always prefix output, even if only one host is specified or com‐
300 municating in-band. This option is primarily useful for script‐
301 ing purposes. Option will be ignored if specified with the -C
302 option.
303
305 Multiple hosts can be input either as an explicit comma separated lists
306 of hosts or a range of hostnames in the general form: prefix[n-m,l-
307 k,...], where n < m and l < k, etc. The later form should not be con‐
308 fused with regular expression character classes (also denoted by []).
309 For example, foo[19] does not represent foo1 or foo9, but rather repre‐
310 sents a degenerate range: foo19.
311 This range syntax is meant only as a convenience on clusters with a
313 prefixNN naming convention and specification of ranges should not be
314 considered necessary -- the list foo1,foo9 could be specified as such,
315 or by the range foo[1,9].
316 Some examples of range usage follow:
318 foo[01-05] instead of foo01,foo02,foo03,foo04,foo05
319 foo[7,9-10] instead of foo7,foo9,foo10
320 foo[0-3] instead of foo0,foo1,foo2,foo3
321 As a reminder to the reader, some shells will interpret brackets ([ and
323 ]) for pattern matching. Depending on your shell, it may be necessary
324 to enclose ranged lists within quotes.
325 When multiple hosts are specified by the user, a thread will be exe‐
327 cuted for each host in parallel up to the configured fanout (which can
328 be adjusted via the -F option). This will allow communication to large
329 numbers of nodes far more quickly than if done in serial.
330 By default, standard output from each node specified will be output
332 with the hostname prepended to each line. Although this output is read‐
333 able in many situations, it may be difficult to read in other situa‐
334 tions. For example, output from multiple nodes may be mixed together.
335 The -B and -C options can be used to change this default.
336 In-band IPMI Communication will be used when the host "localhost" is
338 specified. This allows the user to add the localhost into the hos‐
339 tranged output.
340
342 Most often, IPMI problems are due to configuration problems.
343 IPMI over LAN problems involve a misconfiguration of the remote
345 machine's BMC. Double check to make sure the following are configured
346 properly in the remote machine's BMC: IP address, MAC address, subnet
347 mask, username, user enablement, user privilege, password, LAN privi‐
348 lege, LAN enablement, and allowed authentication type(s). For IPMI 2.0
349 connections, double check to make sure the cipher suite privilege(s)
350 and K_g key are configured properly. The bmc-config(8) tool can be used
351 to check and/or change these configuration settings.
352 Inband IPMI problems are typically caused by improperly configured
354 drivers or non-standard BMCs.
355 In addition to the troubleshooting tips below, please see WORKAROUNDS
357 below to also if there are any vendor specific bugs that have been dis‐
358 covered and worked around.
359 Listed below are many of the common issues for error messages. For
361 additional support, please e-mail the <freeipmi-users@gnu.org> mailing
362 list.
363 "username invalid" - The username entered (or a NULL username if none
365 was entered) is not available on the remote machine. It may also be
366 possible the remote BMC's username configuration is incorrect.
367 "password invalid" - The password entered (or a NULL password if none
369 was entered) is not correct. It may also be possible the password for
370 the user is not correctly configured on the remote BMC.
371 "password verification timeout" - Password verification has timed out.
373 A "password invalid" error (described above) or a generic "session
374 timeout" (described below) occurred. During this point in the protocol
375 it cannot be differentiated which occurred.
376 "k_g invalid" - The K_g key entered (or a NULL K_g key if none was
378 entered) is not correct. It may also be possible the K_g key is not
379 correctly configured on the remote BMC.
380 "privilege level insufficient" - An IPMI command requires a higher user
382 privilege than the one authenticated with. Please try to authenticate
383 with a higher privilege. This may require authenticating to a different
384 user which has a higher maximum privilege.
385 "privilege level cannot be obtained for this user" - The privilege
387 level you are attempting to authenticate with is higher than the maxi‐
388 mum allowed for this user. Please try again with a lower privilege. It
389 may also be possible the maximum privilege level allowed for a user is
390 not configured properly on the remote BMC.
391 "authentication type unavailable for attempted privilege level" - The
393 authentication type you wish to authenticate with is not available for
394 this privilege level. Please try again with an alternate authentication
395 type or alternate privilege level. It may also be possible the avail‐
396 able authentication types you can authenticate with are not correctly
397 configured on the remote BMC.
398 "cipher suite id unavailable" - The cipher suite id you wish to authen‐
400 ticate with is not available on the remote BMC. Please try again with
401 an alternate cipher suite id. It may also be possible the available
402 cipher suite ids are not correctly configured on the remote BMC.
403 "ipmi 2.0 unavailable" - IPMI 2.0 was not discovered on the remote
405 machine. Please try to use IPMI 1.5 instead.
406 "connection timeout" - Initial IPMI communication failed. A number of
408 potential errors are possible, including an invalid hostname specified,
409 an IPMI IP address cannot be resolved, IPMI is not enabled on the
410 remote server, the network connection is bad, etc. Please verify con‐
411 figuration and connectivity.
412 "session timeout" - The IPMI session has timed out. Please reconnect.
414 If this error occurs often, you may wish to increase the retransmission
415 timeout. Some remote BMCs are considerably slower than others.
416 "device not found" - The specified device could not be found. Please
418 check configuration or inputs and try again.
419 "driver timeout" - Communication with the driver or device has timed
421 out. Please try again.
422 "message timeout" - Communication with the driver or device has timed
424 out. Please try again.
425 "BMC busy" - The BMC is currently busy. It may be processing informa‐
427 tion or have too many simultaneous sessions to manage. Please wait and
428 try again.
429 "could not find inband device" - An inband device could not be found.
431 Please check configuration or specify specific device or driver on the
432 command line.
433 "driver timeout" - The inband driver has timed out communicating to the
435 local BMC or service processor. The BMC or service processor may be
436 busy or (worst case) possibly non-functioning.
437
439 With so many different vendors implementing their own IPMI solutions,
440 different vendors may implement their IPMI protocols incorrectly. The
441 following describes a number of workarounds currently available to han‐
442 dle discovered compliance issues. When possible, workarounds have been
443 implemented so they will be transparent to the user. However, some will
444 require the user to specify a workaround be used via the -W option.
445 The hardware listed below may only indicate the hardware that a problem
447 was discovered on. Newer versions of hardware may fix the problems
448 indicated below. Similar machines from vendors may or may not exhibit
449 the same problems. Different vendors may license their firmware from
450 the same IPMI firmware developer, so it may be worthwhile to try work‐
451 arounds listed below even if your motherboard is not listed.
452 If you believe your hardware has an additional compliance issue that
454 needs a workaround to be implemented, please contact the FreeIPMI main‐
455 tainers on <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
456 assumeio - This workaround flag will assume inband interfaces communi‐
458 cate with system I/O rather than being memory-mapped. This will work
459 around systems that report invalid base addresses. Those hitting this
460 issue may see "device not supported" or "could not find inband device"
461 errors. Issue observed on HP ProLiant DL145 G1.
462 spinpoll - This workaround flag will inform some inband drivers (most
464 notably the KCS driver) to spin while polling rather than putting the
465 process to sleep. This may significantly improve the wall clock running
466 time of tools because an operating system scheduler's granularity may
467 be much larger than the time it takes to perform a single IPMI message
468 transaction. However, by spinning, your system may be performing less
469 useful work by not contexting out the tool for a more useful task.
470 authcap - This workaround flag will skip early checks for username
472 capabilities, authentication capabilities, and K_g support and allow
473 IPMI authentication to succeed. It works around multiple issues in
474 which the remote system does not properly report username capabilities,
475 authentication capabilities, or K_g status. Those hitting this issue
476 may see "username invalid", "authentication type unavailable for
477 attempted privilege level", or "k_g invalid" errors. Issue observed on
478 Asus P5M2/P5MT-R/RS162-E4/RX4, Intel SR1520ML/X38ML, and Sun Fire
479 2200/4150/4450 with ELOM.
480 idzero - This workaround flag will allow empty session IDs to be
482 accepted by the client. It works around IPMI sessions that report empty
483 session IDs to the client. Those hitting this issue may see "session
484 timeout" errors. Issue observed on Tyan S2882 with M3289 BMC.
485 unexpectedauth - This workaround flag will allow unexpected non-null
487 authcodes to be checked as though they were expected. It works around
488 an issue when packets contain non-null authentication data when they
489 should be null due to disabled per-message authentication. Those hit‐
490 ting this issue may see "session timeout" errors. Issue observed on
491 Dell PowerEdge 2850,SC1425. Confirmed fixed on newer firmware.
492 forcepermsg - This workaround flag will force per-message authentica‐
494 tion to be used no matter what is advertised by the remote system. It
495 works around an issue when per-message authentication is advertised as
496 disabled on the remote system, but it is actually required for the pro‐
497 tocol. Those hitting this issue may see "session timeout" errors.
498 Issue observed on IBM eServer 325.
499 endianseq - This workaround flag will flip the endian of the session
501 sequence numbers to allow the session to continue properly. It works
502 around IPMI 1.5 session sequence numbers that are the wrong endian.
503 Those hitting this issue may see "session timeout" errors. Issue
504 observed on some Sun ILOM 1.0/2.0 (depends on service processor
505 endian).
506 noauthcodecheck - This workaround flag will tell FreeIPMI to not check
508 the authentication codes returned from IPMI 1.5 command responses. It
509 works around systems to return invalid authentication codes due to
510 hashing or implementation errors. Users are cautioned on the use of
511 this option, as it removes an authentication check verifying the valid‐
512 ity of a packet. However, in most organizations, this is unlikely to be
513 a security issue. Those hitting this issue may see "connection time‐
514 out", "session timeout", or "password verification timeout" errors.
515 Issue observed on Xyratex FB-H8-SRAY.
516 intel20 - This workaround flag will work around several Intel IPMI 2.0
518 authentication issues. The issues covered include padding of usernames,
519 and password truncation if the authentication algorithm is HMAC-
520 MD5-128. Those hitting this issue may see "username invalid", "password
521 invalid", or "k_g invalid" errors. Issue observed on Intel SE7520AF2
522 with Intel Server Management Module (Professional Edition).
523 supermicro20 - This workaround flag will work around several Supermicro
525 IPMI 2.0 authentication issues on motherboards w/ Peppercon IPMI
526 firmware. The issues covered include handling invalid length authenti‐
527 cation codes. Those hitting this issue may see "password invalid"
528 errors. Issue observed on Supermicro H8QME with SIMSO daughter card.
529 Confirmed fixed on newerver firmware.
530 sun20 - This workaround flag will work work around several Sun IPMI 2.0
532 authentication issues. The issues covered include invalid lengthed hash
533 keys, improperly hashed keys, and invalid cipher suite records. Those
534 hitting this issue may see "password invalid" or "bmc error" errors.
535 Issue observed on Sun Fire 4100/4200/4500 with ILOM. This workaround
536 automatically includes the "opensesspriv" workaround.
537 opensesspriv - This workaround flag will slightly alter FreeIPMI's IPMI
539 2.0 connection protocol to workaround an invalid hashing algorithm used
540 by the remote system. The privilege level sent during the Open Session
541 stage of an IPMI 2.0 connection is used for hashing keys instead of the
542 privilege level sent during the RAKP1 connection stage. Those hitting
543 this issue may see "password invalid", "k_g invalid", or "bad rmcpplus
544 status code" errors. Issue observed on Sun Fire 4100/4200/4500 with
545 ILOM, Inventec 5441/Dell Xanadu II, Supermicro X8DTH, Supermicro X8DTG,
546 Intel S5500WBV/Penguin Relion 700, Intel S2600JF/Appro 512X, and Quanta
547 QSSC-S4R//Appro GB812X-CN. This workaround is automatically triggered
548 with the "sun20" workaround.
549 integritycheckvalue - This workaround flag will work around an invalid
551 integrity check value during an IPMI 2.0 session establishment when
552 using Cipher Suite ID 0. The integrity check value should be 0 length,
553 however the remote motherboard responds with a non-empty field. Those
554 hitting this issue may see "k_g invalid" errors. Issue observed on
555 Supermicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin Relion
556 700, and Intel S2600JF/Appro 512X.
557 No IPMI 1.5 Support - Some motherboards that support IPMI 2.0 have been
559 found to not support IPMI 1.5. Those hitting this issue may see "ipmi
560 2.0 unavailable" or "connection timeout" errors. This issue can be
561 worked around by using IPMI 2.0 instead of IPMI 1.5 by specifying
562 --driver-address=LAN_2_0. Issue observed on HP Proliant DL 145.
563
565 The following motherboards are confirmed to have atleast some support
566 by the --interpret-oem-data option. While highly probable the OEM data
567 interpretations would work across other motherboards by the same manu‐
568 facturer, there are no guarantees. Some of the motherboards below may
569 be rebranded by vendors/distributors.
570 Currently None
572
574 # ipmi-dcmi --get-power-limit
575 Get power limit of the local machine.
577 # ipmi-dcmi -h ahost -u myusername -p mypassword --get-power-limit
579 Get power limit of a remote machine using IPMI over LAN.
581 # ipmi-dcmi -h mycluster[0-127] -u myusername -p mypassword --get-
583 power-limit
584 Get power limit across a cluster using IPMI over LAN.
586
588 Upon successful execution, exit status is 0. On error, exit status is
589 1.
590 If multiple hosts are specified for communication, the exit status is 0
592 if and only if all targets successfully execute. Otherwise the exit
593 status is 1.
594
596 On older operating systems, if you input your username, password, and
597 other potentially security relevant information on the command line,
598 this information may be discovered by other users when using tools like
599 the ps(1) command or looking in the /proc file system. It is generally
600 more secure to input password information with options like the -P or
601 -K options. Configuring security relevant information in the FreeIPMI
602 configuration file would also be an appropriate way to hide this infor‐
603 mation.
604 In order to prevent brute force attacks, some BMCs will temporarily
606 "lock up" after a number of remote authentication errors. You may need
607 to wait awhile in order to this temporary "lock up" to pass before you
608 may authenticate again.
609
611 Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
612
614 Copyright (C) 2009-2012 Lawrence Livermore National Security, LLC.
615 This program is free software; you can redistribute it and/or modify it
617 under the terms of the GNU General Public License as published by the
618 Free Software Foundation; either version 3 of the License, or (at your
619 option) any later version.
620
622 freeipmi(7), bmc-config(8), ipmi-chassis(8), ipmi-sel(8), ipmi-sen‐
623 sors(8), ipmiconsole(8), ipmipower(8)
624 http://www.gnu.org/software/freeipmi/
626ipmi-dcmi 1.2.1 2017-03-22 IPMI-DCMI(8)