1ipmipower(8) System Commands ipmipower(8)
2
6 ipmipower - IPMI power control utility
7
9 ipmipower [OPTION...]
10
12 ipmipower allows users to remotely power on, off, cycle, hard reset,
13 get a power status query, perform a pulse diagnostic interrupt, or ini‐
14 tiate a soft-shutdown of the OS via ACPI through the IPMI over LAN pro‐
15 tocol.
16 When a power command (--on, --off, --cycle, --reset, --stat, --pulse,
18 or --soft) is specified on the command line, ipmipower will attempt to
19 run the power command on all hostnames listed on the command line then
20 exit.
21 If no power commands are specified on the command line, ipmipower will
23 run in interactive mode. Interactive mode gives the user a command line
24 interface to enter various commands. Details of the interactive command
25 line interface can be found below under INTERACTIVE COMMANDS.
26 Listed below are general IPMI options, tool specific options, trouble
28 shooting information, workaround information, examples, and known
29 issues. For a general introduction to FreeIPMI please see freeipmi(7).
30
32 The following options are general options for configuring IPMI communi‐
33 cation and executing general tool commands.
34 -D, --driver-type=IPMIDRIVER
36 Specify the driver type to use instead of doing an auto selec‐
37 tion. The currently available outofband drivers are LAN and
38 LAN_2_0, which perform IPMI 1.5 and IPMI 2.0 respectively.
39 -h, --hostname=IPMIHOST1,IPMIHOST2,...
41 Specify the remote host(s) to communicate with. Multiple host‐
42 names may be separated by comma or may be specified in a range
43 format; see HOSTRANGED SUPPORT below.
44 -u, --username=USERNAME
46 Specify the username to use when authenticating with the remote
47 host. If not specified, a null (i.e. anonymous) username is
48 assumed. The user must have atleast OPERATOR privileges to run
49 the --on, --off, --reset, --cycle, --pulse, or --soft power con‐
50 trol commands. The user must have atleast USER privileges to
51 determine the power status of the machine through --stat.
52 -p, --password=PASSWORD
54 Specify the password to use when authenticationg with the remote
55 host. If not specified, a null password is assumed. Maximum
56 password length is 16 for IPMI 1.5 and 20 for IPMI 2.0.
57 -P, --password-prompt
59 Prompt for password to avoid possibility of listing it in
60 process lists.
61 -k, --k-g=K_G
63 Specify the K_g BMC key to use when authenticating with the
64 remote host for IPMI 2.0. If not specified, a null key is
65 assumed. To input the key in hexadecimal form, prefix the string
66 with '0x'. E.g., the key 'abc' can be entered with the either
67 the string 'abc' or the string '0x616263'
68 -K, --k-g-prompt
70 Prompt for k-g to avoid possibility of listing it in process
71 lists.
72 --session-timeout=MILLISECONDS
74 Specify the session timeout in milliseconds. Defaults to 20000
75 milliseconds (20 seconds) if not specified.
76 --retransmission-timeout=MILLISECONDS
78 Specify the packet retransmission timeout in milliseconds.
79 Defaults to 400 milliseconds (0.4 seconds) if not specified.
80 -a, --authentication-type=AUTHENTICATION-TYPE
82 Specify the IPMI 1.5 authentication type to use. The currently
83 available authentication types are NONE, STRAIGHT_PASSWORD_KEY,
84 MD2, and MD5. Defaults to MD5 if not specified.
85 -I, --cipher-suite-id=CIPHER-SUITE-ID
87 Specify the IPMI 2.0 cipher suite ID to use. The Cipher Suite ID
88 identifies a set of authentication, integrity, and confidential‐
89 ity algorithms to use for IPMI 2.0 communication. The authenti‐
90 cation algorithm identifies the algorithm to use for session
91 setup, the integrity algorithm identifies the algorithm to use
92 for session packet signatures, and the confidentiality algorithm
93 identifies the algorithm to use for payload encryption. Defaults
94 to cipher suite ID 3 if not specified. The following cipher
95 suite ids are currently supported:
96 0 - Authentication Algorithm = None; Integrity Algorithm = None;
98 Confidentiality Algorithm = None
99 1 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
101 None; Confidentiality Algorithm = None
102 2 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
104 HMAC-SHA1-96; Confidentiality Algorithm = None
105 3 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
107 HMAC-SHA1-96; Confidentiality Algorithm = AES-CBC-128
108 6 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
110 None; Confidentiality Algorithm = None
111 7 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
113 HMAC-MD5-128; Confidentiality Algorithm = None
114 8 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
116 HMAC-MD5-128; Confidentiality Algorithm = AES-CBC-128
117 11 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
119 MD5-128; Confidentiality Algorithm = None
120 12 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
122 MD5-128; Confidentiality Algorithm = AES-CBC-128
123 -l, --privilege-level=PRIVILEGE-LEVEL
125 Specify the privilege level to be used. The currently available
126 privilege levels are USER, OPERATOR, and ADMIN. Defaults to
127 OPERATOR if not specified.
128 --config-file=FILE
130 Specify an alternate configuration file.
131 -W, --workaround-flags=WORKAROUNDS
133 Specify workarounds to vendor compliance issues. Multiple work‐
134 arounds can be specified separated by commas. See WORKAROUNDS
135 below for a list of available workarounds.
136 --debug
138 Turn on debugging.
139 -?, --help
141 Output a help list and exit.
142 --usage
144 Output a usage message and exit.
145 -V, --version
147 Output the program version and exit.
148
150 The following options are specific to ipmipower.
151 -n, --on
153 Power on the target hosts.
154 -f, --off
156 Power off the target hosts.
157 -c, --cycle
159 Power cycle the target hosts.
160 -r, --reset
162 Reset the target hosts.
163 -s, --stat
165 Get power status of the target hosts.
166 --pulse
168 Send power diagnostic interrupt to target hosts.
169 --soft Initiate a soft-shutdown of the OS via ACPI.
171 --on-if-off
173 The IPMI specification does not require the power cycle or hard
174 reset commands to turn on a machine that is currently powered
175 off. This option will force ipmipower to issue a power on com‐
176 mand instead of a power cycle or hard reset command if the
177 remote machine's power is currently off.
178 --wait-until-on
180 The IPMI specification allows power on commands to return prior
181 to the power on actually taking place. This option will force
182 ipmipower to regularly query the remote BMC and return only
183 after the machine has powered on.
184 --wait-until-off
186 The IPMI specification allows power off commands to return prior
187 the power off actually taking place. This option will force
188 ipmipower to regularly query the remote BMC and return only
189 after the machine has powered off.
190
192 The following options are used to change the networking behavior of
193 ipmipower.
194 --retransmission-wait-timeout=MILLISECONDS
196 Specify the retransmission wait timeout length in milliseconds.
197 The retransmission wait timeout is similar to the retransmission
198 timeout above, but is used specifically for power completion
199 verification with the --wait-until-on and --wait-until-off
200 options. Defaults to 500 milliseconds (0.5 seconds).
201 --retransmission-backoff-count=COUNT
203 Specify the retransmission backoff count for retransmissions.
204 After ever COUNT retransmissions, the retransmission timeout
205 length will be increased by another factor. Defaults to 8.
206 --ping-interval=MILLISECONDS
208 Specify the ping interval length in milliseconds. When running
209 in interactive mode, RMCP (Remote Management Control Protocol)
210 discovery messages will be sent to all configured remote hosts
211 every MILLISECONDS to confirm their support of IPMI. Power com‐
212 mands cannot be sent to a host until it is discovered (or re-
213 discovered if previously lost). Defaults to 5000 milliseconds (5
214 seconds). Ping discovery messages can be disabled by setting
215 this valu to 0. RMCP ping discovery messages are automatically
216 disabled in non-interactive mode.
217 --ping-timeout=MILLISECONDS
219 Specify the ping timeout length in milliseconds. When running in
220 interactive mode, RMCP (Remote Management Control Protocol) mes‐
221 sages discovery will be sent to all configured remote hosts to
222 confirm their support of IPMI. A remote host is considered
223 undiscovered if the host does not respond in MILLISECONDS time.
224 Defaults to 30000 milliseconds (30 seconds). The ping timeout
225 cannot be larger than the ping interval.
226 --ping-packet-count=COUNT
228 Specify the ping packet count size. Defaults to 10. See the
229 --ping-percent-fR option below for more information on this
230 option.
231 --ping-percent=PERCENT
233 Specify the ping percent value. Defaults to 50. Since IPMI is
234 based on UDP, it is difficult for ipmipower to distinguish
235 between a missing machine and a bad (or heavily loaded) network
236 connection in interactive mode. when running in interactive
237 mode. For example, suppose a link consistently drops 80% of the
238 packets to a particular machine. The power control operation may
239 have difficulty completing, although a recent pong response from
240 RMCP makes ipmipower believe the machine is up and functioning
241 properly. The ping packet acount and percent options are used
242 to alleviate this problem. Ipmipower will monitor RMCP ping
243 packets in packet count chunks. If ipmipower does not receive a
244 response to greater than ping percent of those packets,
245 ipmipower will assume the link to this node is bad and will not
246 send power control operations to that node until the connection
247 is determined to be reliable. This heuristic can be disabled by
248 setting either the ping packet count or ping percent to 0. This
249 feature is not used if ping interval is set to 0.
250 --ping-consec-count=COUNT
252 Specify the ping consecutive count. This is another heuristic
253 used to determine if a node should be considered discovered,
254 undiscovered, or with a bad connection. If a valid RMCP pong
255 response was received for the last COUNT ping packets, a node
256 will be considered discovered, regardless of other heuristics
257 listed above. Defaults to 5. This heuristic can be disabled by
258 setting this value to 0. This feature is not used if other ping
259 features described above are disabled.
260
262 The following options manipulate hostranged output. See HOSTRANGED SUP‐
263 PORT below for additional information on hostranges.
264 -B, --buffer-output
266 Buffer hostranged output. For each node, buffer standard output
267 until the node has completed its IPMI operation. When specifying
268 this option, data may appear to output slower to the user since
269 the the entire IPMI operation must complete before any data can
270 be output. See HOSTRANGED SUPPORT below for additional informa‐
271 tion.
272 -C, --consolidate-output
274 Consolidate hostranged output. The complete standard output from
275 every node specified will be consolidated so that nodes with
276 identical output are not output twice. A header will list those
277 nodes with the consolidated output. When this option is speci‐
278 fied, no output can be seen until the IPMI operations to all
279 nodes has completed. If the user breaks out of the program
280 early, all currently consolidated output will be dumped. See
281 HOSTRANGED SUPPORT below for additional information.
282 -F, --fanout
284 Specify multiple host fanout. Indicates the maximum number of
285 power control operations that can be executed in parallel.
286 -E, --eliminate
288 Eliminate hosts determined as undetected by ipmidetect. This
289 attempts to remove the common issue of hostranged execution tim‐
290 ing out due to several nodes being removed from service in a
291 large cluster. The ipmidetectd daemon must be running on the
292 node executing the command.
293 --always-prefix
295 Always prefix output, even if only one host is specified or com‐
296 municating in-band. This option is primarily useful for script‐
297 ing purposes. Option will be ignored if specified with the -C
298 option.
299
301 ipmipower provides the following interactive commands at the ipmipower>
302 prompt. Before any power commands (on, off, cycle, reset, stat, pulse,
303 or soft) can be used, hostnames must be configured into ipmipower,
304 either through the command prompt or the hostname command below. The
305 parameters and options to the commands below mirror their appropriate
306 command line options.
307 hostname [IPMIHOST(s)]
309 Specify a new set of hosts. No input to unconfigure all hosts.
310 username [USERNAME]
312 Specify a new username. No input for null username.
313 password [PASSWORD]
315 Specify a new password. No input for null password.
316 k_g [K_G]
318 Specify a new K_g BMC Key. No input for null key. Prefix with
319 '0x' to enter a key in hexadecimal
320 ipmi-version IPMIVERSION
322 Specify the ipmi version to use.
323 session-timeout MILLISECONDS
325 Specify a new session timeout length.
326 retransmission-timeout MILLISECONDS
328 Specify a new retransmiision timeout length.
329 authentication-type AUTHENTICATION-TYPE
331 Specify the authentication type to use.
332 cipher-suite-id CIPHER-SUITE-ID
334 Specify the cipher suite id to use.
335 privilege-level PRIVILEGE-LEVEL
337 Specify the privilege level to use.
338 workaround-flags WORKAROUNDS
340 Specify workaround flags.
341 debug [on|off]
343 Toggle debug output.
344 on [IPMIHOST(s)]
346 Turn on all configured hosts or specified hosts.
347 off [IPMIHOST(s)]
349 Turn off all configured hosts or specified hosts.
350 cycle [IPMIHOST(s)]
352 Power cycle all configured hosts or specified hosts.
353 reset [IPMIHOST(s)]
355 Reset all configured hosts or specified hosts.
356 stat [IPMIHOST(s)]
358 Query power status for all configured hosts or specified hosts.
359 pulse [IPMIHOST(s)]
361 Pulse diagnostic interrupt all configured hosts or specified
362 hosts.
363 soft [IPMIHOST(s)]
365 Initiate a soft-shutdown for all configured hosts or specified
366 hosts.
367 identify-on [IPMIHOST(s)]
369 Turn on physical system identification.
370 identify-off [IPMIHOST(s)]
372 Turn off physical system identification.
373 identify-status [IPMIHOST(s)]
375 Query physical system identification status.
376 on-if-off [on|off]
378 Toggle on-if-off functionality.
379 wait-until-on [on|off]
381 Toggle wait-until-on functionality.
382 wait-until-off [on|off]
384 Toggle wait-until-off functionality.
385 retransmission-wait-timeout MILLISECONDS
387 Specify a new retransmission wait timeout length.
388 retransmission-backoff-count COUNT
390 Specify a new retransmission backoff count.
391 ping-interval MILLISECONDS
393 Specify a new ping interval length.
394 ping-timeout MILLISECONDS
396 Specify a new ping timeout length.
397 ping-packet-count COUNT
399 Specify a new ping packet count.
400 ping-percent PERCENT
402 Specify a new ping percent.
403 ping-consec-count COUNT
405 Specify a new ping consec count.
406 buffer-output [on|off]
408 Toggle buffer-output functionality.
409 consolidate-output [on|off]
411 Toggle consolidate-output functionality.
412 fanout COUNT
414 Specify a fanout.
415 always-prefix [on|off]
417 Toggle always-prefix functionality.
418 help Output help menu.
420 version
422 Output version.
423 config Output the current configuration.
425 quit Quit program. ipmipower.
427
429 Multiple hosts can be input either as an explicit comma separated lists
430 of hosts or a range of hostnames in the general form: prefix[n-m,l-
431 k,...], where n < m and l < k, etc. The later form should not be con‐
432 fused with regular expression character classes (also denoted by []).
433 For example, foo[19] does not represent foo1 or foo9, but rather repre‐
434 sents a degenerate range: foo19.
435 This range syntax is meant only as a convenience on clusters with a
437 prefixNN naming convention and specification of ranges should not be
438 considered necessary -- the list foo1,foo9 could be specified as such,
439 or by the range foo[1,9].
440 Some examples of range usage follow:
442 foo[01-05] instead of foo01,foo02,foo03,foo04,foo05
443 foo[7,9-10] instead of foo7,foo9,foo10
444 foo[0-3] instead of foo0,foo1,foo2,foo3
445 As a reminder to the reader, some shells will interpret brackets ([ and
447 ]) for pattern matching. Depending on your shell, it may be necessary
448 to enclose ranged lists within quotes.
449 When multiple hosts are specified by the user, a socket will be created
451 for each host and polled on, effectively allowing communication to all
452 hosts in parallel. This will allow communication to large numbers of
453 nodes far more quickly than if done in serial. The -F option can con‐
454 figure the number of nodes that can be communicated with in parallel at
455 the same time.
456 By default, standard output from each node specified will be output
458 with the hostname prepended to each line. Although this output is read‐
459 able in many situations, it may be difficult to read in other situa‐
460 tions. For example, output from multiple nodes may be mixed together.
461 The -B and -C options can be used to change this default.
462
464 Determine the power status of foo[0-2] with null username and password
465 ipmipower -h foo[0-2] --stat
466 Determine the power status of foo[0-2] with non-null username and pass‐
468 word
469 ipmipower -h foo[0-2] -u foo -p bar --stat
470 Hard reset nodes foo[0-2] with non-null username and password
472 ipmipower -h foo[0-2] -u foo -p bar --reset
473
475 Most often, IPMI over LAN problems involve a misconfiguration of the
476 remote machine's BMC. Double check to make sure the following are con‐
477 figured properly in the remote machine's BMC: IP address, MAC address,
478 subnet mask, username, user enablement, user privilege, password, LAN
479 privilege, LAN enablement, and allowed authentication type(s). For IPMI
480 2.0 connections, double check to make sure the cipher suite privi‐
481 lege(s) and K_g key are configured properly. The bmc-config(8) tool can
482 be used to check and/or change these configuration settings.
483 The following are common issues for given error messages:
485 "username invalid" - The username entered (or a NULL username if none
487 was entered) is not available on the remote machine. It may also be
488 possible the remote BMC's username configuration is incorrect.
489 "password invalid" - The password entered (or a NULL password if none
491 was entered) is not correct. It may also be possible the password for
492 the user is not correctly configured on the remote BMC.
493 "password verification timeout" - Password verification has timed out.
495 A "password invalid" error (described above) or a generic "session
496 timeout" (described below) occurred. During this point in the protocol
497 it cannot be differentiated which occurred.
498 "k_g invalid" - The K_g key entered (or a NULL K_g key if none was
500 entered) is not correct. It may also be possible the K_g key is not
501 correctly configured on the remote BMC.
502 "privilege level insufficient" - An IPMI command requires a higher user
504 privilege than the one authenticated with. Please try to authenticate
505 with a higher privilege. This may require authenticating to a different
506 user which has a higher maximum privilege.
507 "privilege level cannot be obtained for this user" - The privilege
509 level you are attempting to authenticate with is higher than the maxi‐
510 mum allowed for this user. Please try again with a lower privilege. It
511 may also be possible the maximum privilege level allowed for a user is
512 not configured properly on the remote BMC.
513 "authentication type unavailable for attempted privilege level" - The
515 authentication type you wish to authenticate with is not available for
516 this privilege level. Please try again with an alternate authentication
517 type or alternate privilege level. It may also be possible the avail‐
518 able authentication types you can authenticate with are not correctly
519 configured on the remote BMC.
520 "cipher suite id unavailable" - The cipher suite id you wish to authen‐
522 ticate with is not available on the remote BMC. Please try again with
523 an alternate cipher suite id. It may also be possible the available
524 cipher suite ids are not correctly configured on the remote BMC.
525 "ipmi 2.0 unavailable" - IPMI 2.0 was not discovered on the remote
527 machine. Please try to use IPMI 1.5 instead.
528 "connection timeout" - Initial IPMI communication failed. A number of
530 potential errors are possible, including an invalid hostname specified,
531 an IPMI IP address cannot be resolved, IPMI is not enabled on the
532 remote server, the network connection is bad, etc. Please verify con‐
533 figuration and connectivity.
534 "session timeout" - The IPMI session has timed out. Please reconnect.
536 If IPMI over LAN continually times out, you may wish to increase the
537 retransmission timeout. Some remote BMCs are considerably slower than
538 others.
539 Please see WORKAROUNDS below to also if there are any vendor specific
541 bugs that have been discovered and worked around.
542
544 When powering on a powered off machine, the client must have a means by
545 which to resolve the MAC address of the remote machine's ethernet card.
546 This is typically done in one of two ways.
547 1) Enable gratuitous ARPs on the remote machine. The remote machine
549 will send out a gratuitous ARP, which advertises the ethernet IP and
550 MAC address so that other machines on the network this information
551 their local ARP cache. For large clusters, this method is not recom‐
552 mended since gratuitous ARPs can flood the network with unnecessary
553 traffic.
554 2) Permanently store the remote machine's MAC address in the local ARP
556 cache. This is the more common approach on large clusters.
557 Other methods are listed in the IPMI specification.
559 If ipmipower is running a tad slow when running a power control command
561 on the commandline (compared to running a power control command in
562 interactive mode), hostname IP resolution may be slowing the startup
563 code down. Hostname resolution tuning may help make ipmipower execute
564 faster on the commandline. This performance problem should not matter
565 when running in interactive mode or with powerman, since it is a one-
566 time setup cost.
567
569 With so many different vendors implementing their own IPMI solutions,
570 different vendors may implement their IPMI protocols incorrectly. The
571 following lists the workarounds currently available to handle discov‐
572 ered compliance issues.
573 When possible, workarounds have been implemented so they will be trans‐
575 parent to the user. However, some will require the user to specify a
576 workaround be used via the -W option.
577 The hardware listed below may only indicate the hardware that a problem
579 was discovered on. Newer versions of hardware may fix the problems
580 indicated below. Similar machines from vendors may or may not exhibit
581 the same problems. Different vendors may license their firmware from
582 the same IPMI firmware developer, so it may be worthwhile to try work‐
583 arounds listed below even if your motherboard is not listed.
584 "idzero" - This workaround option will allow empty session IDs to be
586 accepted by the client. It works around IPMI sessions that report empty
587 session IDs to the client. Those hitting this issue may see "session
588 timeout" errors. Issue observed on Tyan S2882 with M3289 BMC.
589 "unexpectedauth" - This workaround option will allow unexpected non-
591 null authcodes to be checked as though they were expected. It works
592 around an issue when packets contain non-null authentication data when
593 they should be null due to disabled per-message authentication. Those
594 hitting this issue may see "session timeout" errors. Issue observed on
595 Dell PowerEdge 2850,SC1425. Confirmed fixed on newer firmware.
596 "forcepermsg" - This workaround option will force per-message authenti‐
598 cation to be used no matter what is advertised by the remote system. It
599 works around an issue when per-message authentication is advertised as
600 disabled on the remote system, but it is actually required for the pro‐
601 tocol. Those hitting this issue may see "session timeout" errors.
602 Issue observed on IBM eServer 325.
603 "endianseq" - This workaround option will flip the endian of the ses‐
605 sion sequence numbers to allow the session to continue properly. It
606 works around IPMI 1.5 session sequence numbers that are the wrong
607 endian. Those hitting this issue may see "session timeout" errors.
608 Issue observed on some Sun ILOM 1.0/2.0 (depends on service processor
609 endian).
610 "authcap" - This workaround option will skip early checks for username
612 capabilities, authentication capabilities, and K_g support and allow
613 IPMI authentication to succeed. It works around multiple issues in
614 which the remote system does not properly report username capabilities,
615 authentication capabilities, or K_g status. Those hitting this issue
616 may see "username invalid", "authentication type unavailable for
617 attempted privilege level", or "k_g invalid" errors. Issue observed on
618 Asus P5M2/P5MT-R/RS162-E4/RX4, Intel SR1520ML/X38ML, and Sun Fire
619 2200/4150/4450 with ELOM.
620 "intel20" - This workaround option will work around several Intel IPMI
622 2.0 authentication issues. The issues covered include padding of user‐
623 names, automatic acceptance of a RAKP 4 response integrity check when
624 using the integrity algorithm MD5-128, and password truncation if the
625 authentication algorithm is HMAC-MD5-128. Those hitting this issue may
626 see "username invalid", "password invalid", or "k_g invalid" errors.
627 Issue observed on Intel SE7520AF2 with Intel Server Management Module
628 (Professional Edition).
629 "supermicro20" - This workaround option will work around several Super‐
631 micro IPMI 2.0 authentication issues on motherboards w/ Peppercon IPMI
632 firmware. The issues covered include handling invalid length authenti‐
633 cation codes. Those hitting this issue may see "password invalid"
634 errors. Issue observed on Supermicro H8QME with SIMSO daughter card.
635 Confirmed fixed on newerver firmware.
636 "sun20" - This workaround option will work work around several Sun IPMI
638 2.0 authentication issues. The issues covered include invalid lengthed
639 hash keys, improperly hashed keys, and invalid cipher suite records.
640 Those hitting this issue may see "password invalid" or "bmc error"
641 errors. Issue observed on Sun Fire 4100/4200/4500 with ILOM. This
642 workaround automatically includes the "opensesspriv" workaround.
643 "opensesspriv" - This workaround option will slightly alter FreeIPMI's
645 IPMI 2.0 connection protocol to workaround an invalid hashing algorithm
646 used by the remote system. The privilege level sent during the Open
647 Session stage of an IPMI 2.0 connection is sometimes invalid and used
648 for hashing keys instead of the privilege level sent during the RAKP1
649 connection stage. Those hitting this issue may see "password invalid",
650 "k_g invalid", "bad rmcpplus status code", or "privilege level cannot
651 be obtained for this user " errors. Issue observed on Sun Fire
652 4100/4200/4500 with ILOM, Inventec 5441/Dell Xanadu II, Supermicro
653 X8DTH, Supermicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin
654 Relion 700. This workaround is automatically triggered with the "sun20"
655 workaround.
656 "integritycheckvalue" - This workaround option will work around an
658 invalid integrity check value during an IPMI 2.0 session establishment
659 when using Cipher Suite ID 0. The integrity check value should be 0
660 length, however the remote motherboard responds with a non-empty field.
661 Those hitting this issue may see "k_g invalid" errors. Issue observed
662 on Supermicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin
663 Relion 700.
664
666 On older operating systems, if you input your username, password, and
667 other potentially security relevant information on the command line,
668 this information may be discovered by other users when using tools like
669 the ps(1) command or looking in the /proc file system. It is generally
670 more secure to input password information with options like the -P or
671 -K options. Configuring security relevant information in the FreeIPMI
672 configuration file would also be an appropriate way to hide this infor‐
673 mation.
674 In order to prevent brute force attacks, some BMCs will temporarily
676 "lock up" after a number of remote authentication errors. You may need
677 to wait awhile in order to this temporary "lock up" to pass before you
678 may authenticate again.
679 IPMI specifications do not require BMCs to perform a power control
681 operation before returning a completion code to the caller. Therefore,
682 it is possible for ipmipower to return power status queries opposite of
683 what you are expecting. For example, if a "power off" operation is
684 performed, a BMC may return a successful completion code to ipmipower
685 before the "power off" operation is actually performed. Subsequent
686 power status queries may return "on" for several seconds, until the BMC
687 actually performs the "power off" operation.
688
690 Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
691
693 Copyright (C) 2007-2010 Lawrence Livermore National Security, LLC.
694 Copyright (C) 2003-2007 The Regents of the University of California.
695 This program is free software; you can redistribute it and/or modify it
697 under the terms of the GNU General Public License as published by the
698 Free Software Foundation; either version 2 of the License, or (at your
699 option) any later version.
700
702 freeipmi.conf(5), freeipmi(7), bmc-config(8)
703 http://www.gnu.org/software/freeipmi/
705ipmipower 0.8.8 2010-07-21 ipmipower(8)