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. DCMI can also
19 be configured using the dcmi category in ipmi-config(8). The DCMI
20 specification encompasses many traditional IPMI features that are not
21 implemented directly in this tool. Please see ipmiconsole(8) for
22 Serial-over-LAN (SOL) support, ipmi-chassis(8) for power status, power
23 control, identification, and ACPI power state information, ipmipower(8)
24 for power status and power control, ipmi-sel(8) for System Event Log
25 (SEL) information, bmc-info(8) for device and globally unique ID (guid)
26 information, ipmi-sensors(8) for sensor readings, and ipmi-config(8)
27 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,
42 SUNBMC, and INTELDCMI.
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 By IPMI definition, all IPMI times and timestamps are stored in local‐
264 time. However, in many situations, the timestamps will not be stored in
265 localtime. Whether or not a system truly stored the timestamps in
266 localtime varies on many factors, such as the vendor, BIOS, and operat‐
267 ing system. The following options will allow the user to adjust the
268 interpretation of the stored timestamps and how they should be output.
269 --utc-to-localtime
271 Assume all times are reported in UTC time and convert the time
272 to localtime before being output.
273 --localtime-to-utc
275 Convert all localtime timestamps to UTC before being output.
276 --utc-offset=SECONDS
278 Specify a specific UTC offset in seconds to be added to time‐
279 stamps. Value can range from -86400 to 86400 seconds. Defaults
280 to 0.
281
283 The following options manipulate hostranged output. See HOSTRANGED SUP‐
284 PORT below for additional information on hostranges.
285 -B, --buffer-output
287 Buffer hostranged output. For each node, buffer standard output
288 until the node has completed its IPMI operation. When specifying
289 this option, data may appear to output slower to the user since
290 the the entire IPMI operation must complete before any data can
291 be output. See HOSTRANGED SUPPORT below for additional informa‐
292 tion.
293 -C, --consolidate-output
295 Consolidate hostranged output. The complete standard output from
296 every node specified will be consolidated so that nodes with
297 identical output are not output twice. A header will list those
298 nodes with the consolidated output. When this option is speci‐
299 fied, no output can be seen until the IPMI operations to all
300 nodes has completed. If the user breaks out of the program
301 early, all currently consolidated output will be dumped. See
302 HOSTRANGED SUPPORT below for additional information.
303 -F NUM, --fanout=NUM
305 Specify multiple host fanout. A "sliding window" (or fanout)
306 algorithm is used for parallel IPMI communication so that slower
307 nodes or timed out nodes will not impede parallel communication.
308 The maximum number of threads available at the same time is lim‐
309 ited by the fanout. The default is 64.
310 -E, --eliminate
312 Eliminate hosts determined as undetected by ipmidetect. This
313 attempts to remove the common issue of hostranged execution tim‐
314 ing out due to several nodes being removed from service in a
315 large cluster. The ipmidetectd daemon must be running on the
316 node executing the command.
317 --always-prefix
319 Always prefix output, even if only one host is specified or com‐
320 municating in-band. This option is primarily useful for script‐
321 ing purposes. Option will be ignored if specified with the -C
322 option.
323
325 Multiple hosts can be input either as an explicit comma separated lists
326 of hosts or a range of hostnames in the general form: prefix[n-m,l-
327 k,...], where n < m and l < k, etc. The later form should not be con‐
328 fused with regular expression character classes (also denoted by []).
329 For example, foo[19] does not represent foo1 or foo9, but rather repre‐
330 sents a degenerate range: foo19.
331 This range syntax is meant only as a convenience on clusters with a
333 prefixNN naming convention and specification of ranges should not be
334 considered necessary -- the list foo1,foo9 could be specified as such,
335 or by the range foo[1,9].
336 Some examples of range usage follow:
338 foo[01-05] instead of foo01,foo02,foo03,foo04,foo05
339 foo[7,9-10] instead of foo7,foo9,foo10
340 foo[0-3] instead of foo0,foo1,foo2,foo3
341 As a reminder to the reader, some shells will interpret brackets ([ and
343 ]) for pattern matching. Depending on your shell, it may be necessary
344 to enclose ranged lists within quotes.
345 When multiple hosts are specified by the user, a thread will be exe‐
347 cuted for each host in parallel up to the configured fanout (which can
348 be adjusted via the -F option). This will allow communication to large
349 numbers of nodes far more quickly than if done in serial.
350 By default, standard output from each node specified will be output
352 with the hostname prepended to each line. Although this output is read‐
353 able in many situations, it may be difficult to read in other situa‐
354 tions. For example, output from multiple nodes may be mixed together.
355 The -B and -C options can be used to change this default.
356 In-band IPMI Communication will be used when the host "localhost" is
358 specified. This allows the user to add the localhost into the hos‐
359 tranged output.
360
362 Most often, IPMI problems are due to configuration problems.
363 IPMI over LAN problems involve a misconfiguration of the remote
365 machine's BMC. Double check to make sure the following are configured
366 properly in the remote machine's BMC: IP address, MAC address, subnet
367 mask, username, user enablement, user privilege, password, LAN privi‐
368 lege, LAN enablement, and allowed authentication type(s). For IPMI 2.0
369 connections, double check to make sure the cipher suite privilege(s)
370 and K_g key are configured properly. The ipmi-config(8) tool can be
371 used to check and/or change these configuration settings.
372 Inband IPMI problems are typically caused by improperly configured
374 drivers or non-standard BMCs.
375 In addition to the troubleshooting tips below, please see WORKAROUNDS
377 below to also if there are any vendor specific bugs that have been dis‐
378 covered and worked around.
379 Listed below are many of the common issues for error messages. For
381 additional support, please e-mail the <freeipmi-users@gnu.org> mailing
382 list.
383 "username invalid" - The username entered (or a NULL username if none
385 was entered) is not available on the remote machine. It may also be
386 possible the remote BMC's username configuration is incorrect.
387 "password invalid" - The password entered (or a NULL password if none
389 was entered) is not correct. It may also be possible the password for
390 the user is not correctly configured on the remote BMC.
391 "password verification timeout" - Password verification has timed out.
393 A "password invalid" error (described above) or a generic "session
394 timeout" (described below) occurred. During this point in the protocol
395 it cannot be differentiated which occurred.
396 "k_g invalid" - The K_g key entered (or a NULL K_g key if none was
398 entered) is not correct. It may also be possible the K_g key is not
399 correctly configured on the remote BMC.
400 "privilege level insufficient" - An IPMI command requires a higher user
402 privilege than the one authenticated with. Please try to authenticate
403 with a higher privilege. This may require authenticating to a different
404 user which has a higher maximum privilege.
405 "privilege level cannot be obtained for this user" - The privilege
407 level you are attempting to authenticate with is higher than the maxi‐
408 mum allowed for this user. Please try again with a lower privilege. It
409 may also be possible the maximum privilege level allowed for a user is
410 not configured properly on the remote BMC.
411 "authentication type unavailable for attempted privilege level" - The
413 authentication type you wish to authenticate with is not available for
414 this privilege level. Please try again with an alternate authentication
415 type or alternate privilege level. It may also be possible the avail‐
416 able authentication types you can authenticate with are not correctly
417 configured on the remote BMC.
418 "cipher suite id unavailable" - The cipher suite id you wish to authen‐
420 ticate with is not available on the remote BMC. Please try again with
421 an alternate cipher suite id. It may also be possible the available
422 cipher suite ids are not correctly configured on the remote BMC.
423 "ipmi 2.0 unavailable" - IPMI 2.0 was not discovered on the remote
425 machine. Please try to use IPMI 1.5 instead.
426 "connection timeout" - Initial IPMI communication failed. A number of
428 potential errors are possible, including an invalid hostname specified,
429 an IPMI IP address cannot be resolved, IPMI is not enabled on the
430 remote server, the network connection is bad, etc. Please verify con‐
431 figuration and connectivity.
432 "session timeout" - The IPMI session has timed out. Please reconnect.
434 If this error occurs often, you may wish to increase the retransmission
435 timeout. Some remote BMCs are considerably slower than others.
436 "device not found" - The specified device could not be found. Please
438 check configuration or inputs and try again.
439 "driver timeout" - Communication with the driver or device has timed
441 out. Please try again.
442 "message timeout" - Communication with the driver or device has timed
444 out. Please try again.
445 "BMC busy" - The BMC is currently busy. It may be processing informa‐
447 tion or have too many simultaneous sessions to manage. Please wait and
448 try again.
449 "could not find inband device" - An inband device could not be found.
451 Please check configuration or specify specific device or driver on the
452 command line.
453 "driver timeout" - The inband driver has timed out communicating to the
455 local BMC or service processor. The BMC or service processor may be
456 busy or (worst case) possibly non-functioning.
457 "internal IPMI error" - An IPMI error has occurred that FreeIPMI does
459 not know how to handle. Please e-mail <freeipmi-users@gnu.org> to
460 report the issue.
461
463 With so many different vendors implementing their own IPMI solutions,
464 different vendors may implement their IPMI protocols incorrectly. The
465 following describes a number of workarounds currently available to han‐
466 dle discovered compliance issues. When possible, workarounds have been
467 implemented so they will be transparent to the user. However, some will
468 require the user to specify a workaround be used via the -W option.
469 The hardware listed below may only indicate the hardware that a problem
471 was discovered on. Newer versions of hardware may fix the problems
472 indicated below. Similar machines from vendors may or may not exhibit
473 the same problems. Different vendors may license their firmware from
474 the same IPMI firmware developer, so it may be worthwhile to try work‐
475 arounds listed below even if your motherboard is not listed.
476 If you believe your hardware has an additional compliance issue that
478 needs a workaround to be implemented, please contact the FreeIPMI main‐
479 tainers on <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
480 assumeio - This workaround flag will assume inband interfaces communi‐
482 cate with system I/O rather than being memory-mapped. This will work
483 around systems that report invalid base addresses. Those hitting this
484 issue may see "device not supported" or "could not find inband device"
485 errors. Issue observed on HP ProLiant DL145 G1.
486 spinpoll - This workaround flag will inform some inband drivers (most
488 notably the KCS driver) to spin while polling rather than putting the
489 process to sleep. This may significantly improve the wall clock running
490 time of tools because an operating system scheduler's granularity may
491 be much larger than the time it takes to perform a single IPMI message
492 transaction. However, by spinning, your system may be performing less
493 useful work by not contexting out the tool for a more useful task.
494 authcap - This workaround flag will skip early checks for username
496 capabilities, authentication capabilities, and K_g support and allow
497 IPMI authentication to succeed. It works around multiple issues in
498 which the remote system does not properly report username capabilities,
499 authentication capabilities, or K_g status. Those hitting this issue
500 may see "username invalid", "authentication type unavailable for
501 attempted privilege level", or "k_g invalid" errors. Issue observed on
502 Asus P5M2/P5MT-R/RS162-E4/RX4, Intel SR1520ML/X38ML, and Sun Fire
503 2200/4150/4450 with ELOM.
504 nochecksumcheck - This workaround flag will tell FreeIPMI to not check
506 the checksums returned from IPMI command responses. It works around
507 systems that return invalid checksums due to implementation errors, but
508 the packet is otherwise valid. Users are cautioned on the use of this
509 option, as it removes validation of packet integrity in a number of
510 circumstances. However, it is unlikely to be an issue in most situa‐
511 tions. Those hitting this issue may see "connection timeout", "session
512 timeout", or "password verification timeout" errors. On IPMI 1.5 con‐
513 nections, the "noauthcodecheck" workaround may also needed too. Issue
514 observed on Supermicro X9SCM-iiF, Supermicro X9DRi-F, and Supermicro
515 X9DRFR.
516 idzero - This workaround flag will allow empty session IDs to be
518 accepted by the client. It works around IPMI sessions that report empty
519 session IDs to the client. Those hitting this issue may see "session
520 timeout" errors. Issue observed on Tyan S2882 with M3289 BMC.
521 unexpectedauth - This workaround flag will allow unexpected non-null
523 authcodes to be checked as though they were expected. It works around
524 an issue when packets contain non-null authentication data when they
525 should be null due to disabled per-message authentication. Those hit‐
526 ting this issue may see "session timeout" errors. Issue observed on
527 Dell PowerEdge 2850,SC1425. Confirmed fixed on newer firmware.
528 forcepermsg - This workaround flag will force per-message authentica‐
530 tion to be used no matter what is advertised by the remote system. It
531 works around an issue when per-message authentication is advertised as
532 disabled on the remote system, but it is actually required for the pro‐
533 tocol. Those hitting this issue may see "session timeout" errors.
534 Issue observed on IBM eServer 325.
535 endianseq - This workaround flag will flip the endian of the session
537 sequence numbers to allow the session to continue properly. It works
538 around IPMI 1.5 session sequence numbers that are the wrong endian.
539 Those hitting this issue may see "session timeout" errors. Issue
540 observed on some Sun ILOM 1.0/2.0 (depends on service processor
541 endian).
542 noauthcodecheck - This workaround flag will tell FreeIPMI to not check
544 the authentication codes returned from IPMI 1.5 command responses. It
545 works around systems that return invalid authentication codes due to
546 hashing or implementation errors. Users are cautioned on the use of
547 this option, as it removes an authentication check verifying the valid‐
548 ity of a packet. However, in most organizations, this is unlikely to be
549 a security issue. Those hitting this issue may see "connection time‐
550 out", "session timeout", or "password verification timeout" errors.
551 Issue observed on Xyratex FB-H8-SRAY, Intel Windmill, Quanta Winter‐
552 fell, and Wiwynn Windmill.
553 intel20 - This workaround flag will work around several Intel IPMI 2.0
555 authentication issues. The issues covered include padding of usernames,
556 and password truncation if the authentication algorithm is HMAC-
557 MD5-128. Those hitting this issue may see "username invalid", "password
558 invalid", or "k_g invalid" errors. Issue observed on Intel SE7520AF2
559 with Intel Server Management Module (Professional Edition).
560 supermicro20 - This workaround flag will work around several Supermicro
562 IPMI 2.0 authentication issues on motherboards w/ Peppercon IPMI
563 firmware. The issues covered include handling invalid length authenti‐
564 cation codes. Those hitting this issue may see "password invalid"
565 errors. Issue observed on Supermicro H8QME with SIMSO daughter card.
566 Confirmed fixed on newerver firmware.
567 sun20 - This workaround flag will work work around several Sun IPMI 2.0
569 authentication issues. The issues covered include invalid lengthed hash
570 keys, improperly hashed keys, and invalid cipher suite records. Those
571 hitting this issue may see "password invalid" or "bmc error" errors.
572 Issue observed on Sun Fire 4100/4200/4500 with ILOM. This workaround
573 automatically includes the "opensesspriv" workaround.
574 opensesspriv - This workaround flag will slightly alter FreeIPMI's IPMI
576 2.0 connection protocol to workaround an invalid hashing algorithm used
577 by the remote system. The privilege level sent during the Open Session
578 stage of an IPMI 2.0 connection is used for hashing keys instead of the
579 privilege level sent during the RAKP1 connection stage. Those hitting
580 this issue may see "password invalid", "k_g invalid", or "bad rmcpplus
581 status code" errors. Issue observed on Sun Fire 4100/4200/4500 with
582 ILOM, Inventec 5441/Dell Xanadu II, Supermicro X8DTH, Supermicro X8DTG,
583 Intel S5500WBV/Penguin Relion 700, Intel S2600JF/Appro 512X, and Quanta
584 QSSC-S4R/Appro GB812X-CN. This workaround is automatically triggered
585 with the "sun20" workaround.
586 integritycheckvalue - This workaround flag will work around an invalid
588 integrity check value during an IPMI 2.0 session establishment when
589 using Cipher Suite ID 0. The integrity check value should be 0 length,
590 however the remote motherboard responds with a non-empty field. Those
591 hitting this issue may see "k_g invalid" errors. Issue observed on
592 Supermicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin Relion
593 700, and Intel S2600JF/Appro 512X.
594 No IPMI 1.5 Support - Some motherboards that support IPMI 2.0 have been
596 found to not support IPMI 1.5. Those hitting this issue may see "ipmi
597 2.0 unavailable" or "connection timeout" errors. This issue can be
598 worked around by using IPMI 2.0 instead of IPMI 1.5 by specifying
599 --driver-type=LAN_2_0. Issue observed on HP Proliant DL 145.
600
602 The following motherboards are confirmed to have atleast some support
603 by the --interpret-oem-data option. While highly probable the OEM data
604 interpretations would work across other motherboards by the same manu‐
605 facturer, there are no guarantees. Some of the motherboards below may
606 be rebranded by vendors/distributors.
607 Currently None
609
611 # ipmi-dcmi --get-power-limit
612 Get power limit of the local machine.
614 # ipmi-dcmi -h ahost -u myusername -p mypassword --get-power-limit
616 Get power limit of a remote machine using IPMI over LAN.
618 # ipmi-dcmi -h mycluster[0-127] -u myusername -p mypassword --get-
620 power-limit
621 Get power limit across a cluster using IPMI over LAN.
623
625 Upon successful execution, exit status is 0. On error, exit status is
626 1.
627 If multiple hosts are specified for communication, the exit status is 0
629 if and only if all targets successfully execute. Otherwise the exit
630 status is 1.
631
633 On older operating systems, if you input your username, password, and
634 other potentially security relevant information on the command line,
635 this information may be discovered by other users when using tools like
636 the ps(1) command or looking in the /proc file system. It is generally
637 more secure to input password information with options like the -P or
638 -K options. Configuring security relevant information in the FreeIPMI
639 configuration file would also be an appropriate way to hide this infor‐
640 mation.
641 In order to prevent brute force attacks, some BMCs will temporarily
643 "lock up" after a number of remote authentication errors. You may need
644 to wait awhile in order to this temporary "lock up" to pass before you
645 may authenticate again.
646
648 Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
649
651 Copyright (C) 2009-2015 Lawrence Livermore National Security, LLC.
652 This program is free software; you can redistribute it and/or modify it
654 under the terms of the GNU General Public License as published by the
655 Free Software Foundation; either version 3 of the License, or (at your
656 option) any later version.
657
659 freeipmi(7), ipmi-chassis(8), ipmi-config(8), ipmi-sel(8), ipmi-sen‐
660 sors(8), ipmiconsole(8), ipmipower(8)
661 http://www.gnu.org/software/freeipmi/
663ipmi-dcmi 1.5.7 2018-04-11 IPMI-DCMI(8)