1IPMI-SENSORS(8) System Commands IPMI-SENSORS(8)
2
6 ipmi-sensors - display IPMI sensor information
7
9 ipmi-sensors [OPTION...]
10
12 Ipmi-sensors displays current readings of sensors and sensor data
13 repository (SDR) information. The default display outputs each sensor's
14 record id, sensor name, sensor type name, sensor reading (if appropri‐
15 ate), and the current sensor event. More verbose information can be
16 found using the verbose options specified below.
17 Ipmi-sensors does not inform the user if a problem exists with a par‐
19 ticular sensor because sensor readings and events are not analyzed.
20 Users may wish to consider ipmimonitoring(8) for sensor analysis.
21 Some sensors may have a sensor reading or sensor event of "N/A" if the
23 information is unavailable. This is typical of a sensor that is not
24 enabled or not owned by a BMC. Please see --bridge-sensors option below
25 to deal with sensors not owned by a BMC. Sensors may output a sensor
26 event of "Unknown" if the sensor reading cannot be read. This is typi‐
27 cal of a sensor that is busy or a reading that cannot be calculated. If
28 sensors report "Unrecognized State", it is indicative of an unkown sen‐
29 sor type, typically an OEM sensor. If the sensor OEM interpretation is
30 available, the --intepret-oem-data may be able to report the appropri‐
31 ate sensor state. Sensors need not always report a sensor event. When a
32 sensor event is not present, "OK" is typically reported.
33 Listed below are general IPMI options, tool specific options, trouble
35 shooting information, workaround information, examples, and known
36 issues. For a general introduction to FreeIPMI please see freeipmi(7).
37 To perform IPMI sensor configuration, please see ipmi-sensors-con‐
38 fig(8). To perform some advanced SDR management, please see bmc-
39 device(8).
40
42 The following options are general options for configuring IPMI communi‐
43 cation and executing general tool commands.
44 -D, --driver-type=IPMIDRIVER
46 Specify the driver type to use instead of doing an auto selec‐
47 tion. The currently available outofband drivers are LAN and
48 LAN_2_0, which perform IPMI 1.5 and IPMI 2.0 respectively. The
49 currently available inband drivers are KCS, SSIF, OPENIPMI, and
50 SUNBMC.
51 --disable-auto-probe
53 Do not probe in-band IPMI devices for default settings.
54 --driver-address=DRIVER-ADDRESS
56 Specify the in-band driver address to be used instead of the
57 probed value. DRIVER-ADDRESS should be prefixed with "0x" for a
58 hex value and '0' for an octal value.
59 --driver-device=DEVICE
61 Specify the in-band driver device path to be used instead of the
62 probed path.
63 --register-spacing=REGISTER-SPACING
65 Specify the in-band driver register spacing instead of the
66 probed value.
67 -h, --hostname=IPMIHOST1,IPMIHOST2,...
69 Specify the remote host(s) to communicate with. Multiple host‐
70 names may be separated by comma or may be specified in a range
71 format; see HOSTRANGED SUPPORT below.
72 -u, --username=USERNAME
74 Specify the username to use when authenticating with the remote
75 host. If not specified, a null (i.e. anonymous) username is
76 assumed. The user must have atleast OPERATOR privileges in order
77 for this tool to operate fully.
78 -p, --password=PASSWORD
80 Specify the password to use when authenticationg with the remote
81 host. If not specified, a null password is assumed. Maximum
82 password length is 16 for IPMI 1.5 and 20 for IPMI 2.0.
83 -P, --password-prompt
85 Prompt for password to avoid possibility of listing it in
86 process lists.
87 -k, --k-g=K_G
89 Specify the K_g BMC key to use when authenticating with the
90 remote host for IPMI 2.0. If not specified, a null key is
91 assumed. To input the key in hexadecimal form, prefix the string
92 with '0x'. E.g., the key 'abc' can be entered with the either
93 the string 'abc' or the string '0x616263'
94 -K, --k-g-prompt
96 Prompt for k-g to avoid possibility of listing it in process
97 lists.
98 --session-timeout=MILLISECONDS
100 Specify the session timeout in milliseconds. Defaults to 20000
101 milliseconds (20 seconds) if not specified.
102 --retransmission-timeout=MILLISECONDS
104 Specify the packet retransmission timeout in milliseconds.
105 Defaults to 1000 milliseconds (1 second) if not specified. The
106 retransmission timeout cannot be larger than the session time‐
107 out.
108 -a, --authentication-type=AUTHENTICATION-TYPE
110 Specify the IPMI 1.5 authentication type to use. The currently
111 available authentication types are NONE, STRAIGHT_PASSWORD_KEY,
112 MD2, and MD5. Defaults to MD5 if not specified.
113 -I, --cipher-suite-id=CIPHER-SUITE-ID
115 Specify the IPMI 2.0 cipher suite ID to use. The Cipher Suite ID
116 identifies a set of authentication, integrity, and confidential‐
117 ity algorithms to use for IPMI 2.0 communication. The authenti‐
118 cation algorithm identifies the algorithm to use for session
119 setup, the integrity algorithm identifies the algorithm to use
120 for session packet signatures, and the confidentiality algorithm
121 identifies the algorithm to use for payload encryption. Defaults
122 to cipher suite ID 3 if not specified. The following cipher
123 suite ids are currently supported:
124 0 - Authentication Algorithm = None; Integrity Algorithm = None;
126 Confidentiality Algorithm = None
127 1 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
129 None; Confidentiality Algorithm = None
130 2 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
132 HMAC-SHA1-96; Confidentiality Algorithm = None
133 3 - Authentication Algorithm = HMAC-SHA1; Integrity Algorithm =
135 HMAC-SHA1-96; Confidentiality Algorithm = AES-CBC-128
136 6 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
138 None; Confidentiality Algorithm = None
139 7 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
141 HMAC-MD5-128; Confidentiality Algorithm = None
142 8 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
144 HMAC-MD5-128; Confidentiality Algorithm = AES-CBC-128
145 11 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
147 MD5-128; Confidentiality Algorithm = None
148 12 - Authentication Algorithm = HMAC-MD5; Integrity Algorithm =
150 MD5-128; Confidentiality Algorithm = AES-CBC-128
151 -l, --privilege-level=PRIVILEGE-LEVEL
153 Specify the privilege level to be used. The currently available
154 privilege levels are USER, OPERATOR, and ADMIN. Defaults to
155 OPERATOR if not specified.
156 --config-file=FILE
158 Specify an alternate configuration file.
159 -W, --workaround-flags=WORKAROUNDS
161 Specify workarounds to vendor compliance issues. Multiple work‐
162 arounds can be specified separated by commas. See WORKAROUNDS
163 below for a list of available workarounds.
164 --debug
166 Turn on debugging.
167 -?, --help
169 Output a help list and exit.
170 --usage
172 Output a usage message and exit.
173 -V, --version
175 Output the program version and exit.
176
178 The following options are specific to Ipmi-sensors.
179 -v, --verbose
181 Output verbose sensor output. This option will output additional
182 information about sensors such as thresholds, ranges, numbers,
183 and event/reading type codes.
184 -vv Output very verbose sensor output. This option will output more
186 additional information than the verbose option such as informa‐
187 tion about events, other sensor types, and oem sensors.
188 -i, --sdr-info
190 Show sensor data repository (SDR) information
191 -q, --quiet-readings
193 Do not output sensor reading values by default. This option is
194 particularly useful if you want to use hostranged output across
195 a cluster and want to consolidate the output.
196 -r "RECORD-IDS-LIST", --record-ids="RECORD-IDS-LIST"
198 Specify sensors to show by record id. Multiple record ids can be
199 separated by commas or spaces. If both --record-ids and --sen‐
200 sor-types are specified, --record-ids takes precedence. A spe‐
201 cial command line record id of "all", will indicate all record
202 ids should be shown (may be useful for overriding configured
203 defaults).
204 -R "RECORD-IDS-LIST", --exclude-record-ids="RECORD-IDS-LIST"
206 Specify sensors to not show by record id. Multiple record ids
207 can be separated by commas or spaces. A special command line
208 record id of "none", will indicate no record ids should be
209 excluded (may be useful for overriding configured defaults).
210 -t "SENSOR-TYPE-LIST", --sensor-types=SENSOR-TYPE-LIST
212 Specify sensor types to show sensor outputs for. Multiple types
213 can be separated by commas or spaces. If both --record-ids and
214 --sensor-types are specified, --record-ids takes precedence. A
215 special command line type of "all", will indicate all types
216 should be shown (may be useful for overriding configured
217 defaults).
218 -T "SENSOR-TYPE-LIST", --exclude-sensor-types=SENSOR-TYPE-LIST
220 Specify sensor types to not show sensor outputs for. Multiple
221 types can be eparated by commas or spaces. A special command
222 line type of "none", will indicate no types should be excluded
223 (may be useful for overriding configured defaults).
224 -L, --list-sensor-types
226 List sensor types.
227 -b, --bridge-sensors
229 By default, sensors readings are not attempted for sensors on
230 non-BMC owners. By setting this option, sensor requests can be
231 bridged to non-BMC owners to obtain sensor readings (experimen‐
232 tal). Bridging may not work on some interfaces/driver types.
233 --shared-sensors
235 Some sensors share the same sensor data record (SDR). This is
236 typically utilized for system event log (SEL) entries and not
237 for sensor readings. However, there may be some motherboards in
238 which this format is utilized for multiple active sensors, or
239 the user simply has interest in seeing the permutation of
240 entries shared by a SDR entry. By setting this option, each sen‐
241 sor number shared by a record will be iterated over and output.
242 --interpret-oem-data
244 Attempt to interpret OEM data, such as event data, sensor read‐
245 ings, or general extra info, etc. If an OEM interpretation is
246 not available, the default output will be generated. Correctness
247 of OEM interpretations cannot be guaranteed due to potential
248 changes OEM vendors may make in products, firmware, etc. See OEM
249 INTERPRETATION below for confirmed supported motherboard inter‐
250 pretations.
251 --ignore-not-available-sensors
253 Ignore not-available (i.e. N/A) sensors in output.
254 --entity-sensor-names
256 Output sensor names prefixed with their entity id and instance
257 number when appropriate. This may be necessary on some mother‐
258 boards to help identify what sensors are referencing. For exam‐
259 ple, a motherboard may have multiple sensors named 'TEMP'. The
260 entity id and instance number may help clarify which sensor
261 refers to "Processor 1" vs. "Processor 2".
262 --no-sensor-type-output
264 Do not show sensor type output for each entry. On many systems,
265 the sensor type is redundant to the name of the sensor. This can
266 especially be true if --entity-sensor-names is specified. If
267 the sensor name is sufficient, or if the sensor type is of no
268 interest to the user, this option can be specified to condense
269 output.
270 --comma-separated-output
272 Output fields in comma separated format.
273 --no-header-output
275 Do not output column headers. May be useful in scripting.
276 --non-abbreviated-units
278 Output non-abbreviated units (e.g. 'Amps' instead of 'A'). May
279 aid in disambiguation of units (e.g. 'C' for Celsius or
280 Coulombs).
281 --legacy-output
283 Output in legacy format. Newer options may not be applicable to
284 leagcy output.
285
287 This tool requires access to the sensor data repository (SDR) cache for
288 general operation. By default, SDR data will be downloaded and cached
289 on the local machine. The following options apply to the SDR cache.
290 -f, --flush-cache
292 Flush a cached version of the sensor data repository (SDR)
293 cache. The SDR is typically cached for faster subsequent access.
294 However, it may need to be flushed and re-generated if the SDR
295 has been updated on a system.
296 -Q, --quiet-cache
298 Do not output information about cache creation/deletion. May be
299 useful in scripting.
300 --sdr-cache-directory=DIRECTORY
302 Specify an alternate directory for sensor data repository (SDR)
303 caches to be stored or read from. Defaults to the home directory
304 if not specified.
305 --sdr-cache-recreate
307 If the SDR cache is out of date or invalid, automatically recre‐
308 ate the sensor data repository (SDR) cache. This option may be
309 useful for scripting purposes.
310
312 The following options manipulate hostranged output. See HOSTRANGED SUP‐
313 PORT below for additional information on hostranges.
314 -B, --buffer-output
316 Buffer hostranged output. For each node, buffer standard output
317 until the node has completed its IPMI operation. When specifying
318 this option, data may appear to output slower to the user since
319 the the entire IPMI operation must complete before any data can
320 be output. See HOSTRANGED SUPPORT below for additional informa‐
321 tion.
322 -C, --consolidate-output
324 Consolidate hostranged output. The complete standard output from
325 every node specified will be consolidated so that nodes with
326 identical output are not output twice. A header will list those
327 nodes with the consolidated output. When this option is speci‐
328 fied, no output can be seen until the IPMI operations to all
329 nodes has completed. If the user breaks out of the program
330 early, all currently consolidated output will be dumped. See
331 HOSTRANGED SUPPORT below for additional information.
332 -F, --fanout
334 Specify multiple host fanout. A "sliding window" (or fanout)
335 algorithm is used for parallel IPMI communication so that slower
336 nodes or timed out nodes will not impede parallel communication.
337 The maximum number of threads available at the same time is lim‐
338 ited by the fanout. The default is 64.
339 -E, --eliminate
341 Eliminate hosts determined as undetected by ipmidetect. This
342 attempts to remove the common issue of hostranged execution tim‐
343 ing out due to several nodes being removed from service in a
344 large cluster. The ipmidetectd daemon must be running on the
345 node executing the command.
346 --always-prefix
348 Always prefix output, even if only one host is specified or com‐
349 municating in-band. This option is primarily useful for script‐
350 ing purposes. Option will be ignored if specified with the -C
351 option.
352
354 Multiple hosts can be input either as an explicit comma separated lists
355 of hosts or a range of hostnames in the general form: prefix[n-m,l-
356 k,...], where n < m and l < k, etc. The later form should not be con‐
357 fused with regular expression character classes (also denoted by []).
358 For example, foo[19] does not represent foo1 or foo9, but rather repre‐
359 sents a degenerate range: foo19.
360 This range syntax is meant only as a convenience on clusters with a
362 prefixNN naming convention and specification of ranges should not be
363 considered necessary -- the list foo1,foo9 could be specified as such,
364 or by the range foo[1,9].
365 Some examples of range usage follow:
367 foo[01-05] instead of foo01,foo02,foo03,foo04,foo05
368 foo[7,9-10] instead of foo7,foo9,foo10
369 foo[0-3] instead of foo0,foo1,foo2,foo3
370 As a reminder to the reader, some shells will interpret brackets ([ and
372 ]) for pattern matching. Depending on your shell, it may be necessary
373 to enclose ranged lists within quotes.
374 When multiple hosts are specified by the user, a thread will be exe‐
376 cuted for each host in parallel up to the configured fanout (which can
377 be adjusted via the -F option). This will allow communication to large
378 numbers of nodes far more quickly than if done in serial.
379 By default, standard output from each node specified will be output
381 with the hostname prepended to each line. Although this output is read‐
382 able in many situations, it may be difficult to read in other situa‐
383 tions. For example, output from multiple nodes may be mixed together.
384 The -B and -C options can be used to change this default.
385 In-band IPMI Communication will be used when the host "localhost" is
387 specified. This allows the user to add the localhost into the hos‐
388 tranged output.
389
391 Most often, IPMI problems are due to configuration problems. Inband
392 IPMI problems are typically caused by improperly configured drivers or
393 non-standard BMCs. IPMI over LAN problems involve a misconfiguration of
394 the remote machine's BMC. Double check to make sure the following are
395 configured properly in the remote machine's BMC: IP address, MAC
396 address, subnet mask, username, user enablement, user privilege, pass‐
397 word, LAN privilege, LAN enablement, and allowed authentication
398 type(s). For IPMI 2.0 connections, double check to make sure the cipher
399 suite privilege(s) and K_g key are configured properly. The bmc-con‐
400 fig(8) tool can be used to check and/or change these configuration set‐
401 tings.
402 The following are common issues for given error messages:
404 "username invalid" - The username entered (or a NULL username if none
406 was entered) is not available on the remote machine. It may also be
407 possible the remote BMC's username configuration is incorrect.
408 "password invalid" - The password entered (or a NULL password if none
410 was entered) is not correct. It may also be possible the password for
411 the user is not correctly configured on the remote BMC.
412 "password verification timeout" - Password verification has timed out.
414 A "password invalid" error (described above) or a generic "session
415 timeout" (described below) occurred. During this point in the protocol
416 it cannot be differentiated which occurred.
417 "k_g invalid" - The K_g key entered (or a NULL K_g key if none was
419 entered) is not correct. It may also be possible the K_g key is not
420 correctly configured on the remote BMC.
421 "privilege level insufficient" - An IPMI command requires a higher user
423 privilege than the one authenticated with. Please try to authenticate
424 with a higher privilege. This may require authenticating to a different
425 user which has a higher maximum privilege.
426 "privilege level cannot be obtained for this user" - The privilege
428 level you are attempting to authenticate with is higher than the maxi‐
429 mum allowed for this user. Please try again with a lower privilege. It
430 may also be possible the maximum privilege level allowed for a user is
431 not configured properly on the remote BMC.
432 "authentication type unavailable for attempted privilege level" - The
434 authentication type you wish to authenticate with is not available for
435 this privilege level. Please try again with an alternate authentication
436 type or alternate privilege level. It may also be possible the avail‐
437 able authentication types you can authenticate with are not correctly
438 configured on the remote BMC.
439 "cipher suite id unavailable" - The cipher suite id you wish to authen‐
441 ticate with is not available on the remote BMC. Please try again with
442 an alternate cipher suite id. It may also be possible the available
443 cipher suite ids are not correctly configured on the remote BMC.
444 "ipmi 2.0 unavailable" - IPMI 2.0 was not discovered on the remote
446 machine. Please try to use IPMI 1.5 instead.
447 "connection timeout" - Initial IPMI communication failed. A number of
449 potential errors are possible, including an invalid hostname specified,
450 an IPMI IP address cannot be resolved, IPMI is not enabled on the
451 remote server, the network connection is bad, etc. Please verify con‐
452 figuration and connectivity.
453 "session timeout" - The IPMI session has timed out. Please reconnect.
455 If this error occurs often, you may wish to increase the retransmission
456 timeout. Some remote BMCs are considerably slower than others.
457 "device not found" - The specified device could not be found. Please
459 check configuration or inputs and try again.
460 "driver timeout" - Communication with the driver or device has timed
462 out. Please try again.
463 "message timeout" - Communication with the driver or device has timed
465 out. Please try again.
466 "BMC busy" - The BMC is currently busy. It may be processing informa‐
468 tion or have too many simultaneous sessions to manage. Please wait and
469 try again.
470 "could not find inband device" - An inband device could not be found.
472 Please check configuration or specify specific device or driver on the
473 command line.
474 Please see WORKAROUNDS below to also if there are any vendor specific
476 bugs that have been discovered and worked around.
477
479 With so many different vendors implementing their own IPMI solutions,
480 different vendors may implement their IPMI protocols incorrectly. The
481 following lists the workarounds currently available to handle discov‐
482 ered compliance issues.
483 When possible, workarounds have been implemented so they will be trans‐
485 parent to the user. However, some will require the user to specify a
486 workaround be used via the -W option.
487 The hardware listed below may only indicate the hardware that a problem
489 was discovered on. Newer versions of hardware may fix the problems
490 indicated below. Similar machines from vendors may or may not exhibit
491 the same problems. Different vendors may license their firmware from
492 the same IPMI firmware developer, so it may be worthwhile to try work‐
493 arounds listed below even if your motherboard is not listed.
494 "idzero" - This workaround option will allow empty session IDs to be
496 accepted by the client. It works around IPMI sessions that report empty
497 session IDs to the client. Those hitting this issue may see "session
498 timeout" errors. Issue observed on Tyan S2882 with M3289 BMC.
499 "unexpectedauth" - This workaround option will allow unexpected non-
501 null authcodes to be checked as though they were expected. It works
502 around an issue when packets contain non-null authentication data when
503 they should be null due to disabled per-message authentication. Those
504 hitting this issue may see "session timeout" errors. Issue observed on
505 Dell PowerEdge 2850,SC1425. Confirmed fixed on newer firmware.
506 "forcepermsg" - This workaround option will force per-message authenti‐
508 cation to be used no matter what is advertised by the remote system. It
509 works around an issue when per-message authentication is advertised as
510 disabled on the remote system, but it is actually required for the pro‐
511 tocol. Those hitting this issue may see "session timeout" errors.
512 Issue observed on IBM eServer 325.
513 "endianseq" - This workaround option will flip the endian of the ses‐
515 sion sequence numbers to allow the session to continue properly. It
516 works around IPMI 1.5 session sequence numbers that are the wrong
517 endian. Those hitting this issue may see "session timeout" errors.
518 Issue observed on some Sun ILOM 1.0/2.0 (depends on service processor
519 endian).
520 "authcap" - This workaround option will skip early checks for username
522 capabilities, authentication capabilities, and K_g support and allow
523 IPMI authentication to succeed. It works around multiple issues in
524 which the remote system does not properly report username capabilities,
525 authentication capabilities, or K_g status. Those hitting this issue
526 may see "username invalid", "authentication type unavailable for
527 attempted privilege level", or "k_g invalid" errors. Issue observed on
528 Asus P5M2/P5MT-R/RS162-E4/RX4, Intel SR1520ML/X38ML, and Sun Fire
529 2200/4150/4450 with ELOM.
530 "intel20" - This workaround option will work around several Intel IPMI
532 2.0 authentication issues. The issues covered include padding of user‐
533 names, automatic acceptance of a RAKP 4 response integrity check when
534 using the integrity algorithm MD5-128, and password truncation if the
535 authentication algorithm is HMAC-MD5-128. Those hitting this issue may
536 see "username invalid", "password invalid", or "k_g invalid" errors.
537 Issue observed on Intel SE7520AF2 with Intel Server Management Module
538 (Professional Edition).
539 "supermicro20" - This workaround option will work around several Super‐
541 micro IPMI 2.0 authentication issues on motherboards w/ Peppercon IPMI
542 firmware. The issues covered include handling invalid length authenti‐
543 cation codes. Those hitting this issue may see "password invalid"
544 errors. Issue observed on Supermicro H8QME with SIMSO daughter card.
545 Confirmed fixed on newerver firmware.
546 "sun20" - This workaround option will work work around several Sun IPMI
548 2.0 authentication issues. The issues covered include invalid lengthed
549 hash keys, improperly hashed keys, and invalid cipher suite records.
550 Those hitting this issue may see "password invalid" or "bmc error"
551 errors. Issue observed on Sun Fire 4100/4200/4500 with ILOM. This
552 workaround automatically includes the "opensesspriv" workaround.
553 "opensesspriv" - This workaround option will slightly alter FreeIPMI's
555 IPMI 2.0 connection protocol to workaround an invalid hashing algorithm
556 used by the remote system. The privilege level sent during the Open
557 Session stage of an IPMI 2.0 connection is sometimes invalid and used
558 for hashing keys instead of the privilege level sent during the RAKP1
559 connection stage. Those hitting this issue may see "password invalid",
560 "k_g invalid", "bad rmcpplus status code", or "privilege level cannot
561 be obtained for this user " errors. Issue observed on Sun Fire
562 4100/4200/4500 with ILOM, Inventec 5441/Dell Xanadu II, Supermicro
563 X8DTH, Supermicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin
564 Relion 700. This workaround is automatically triggered with the "sun20"
565 workaround.
566 "integritycheckvalue" - This workaround option will work around an
568 invalid integrity check value during an IPMI 2.0 session establishment
569 when using Cipher Suite ID 0. The integrity check value should be 0
570 length, however the remote motherboard responds with a non-empty field.
571 Those hitting this issue may see "k_g invalid" errors. Issue observed
572 on Supermicro X8DTG, Supermicro X8DTU, and Intel S5500WBV/Penguin
573 Relion 700.
574
576 The following motherboards are confirmed to have atleast some support
577 by the --interpret-oem-data option. While highly probable the OEM data
578 interpretations would work across other motherboards by the same manu‐
579 facturer, there are no guarantees.
580 Dell Poweredge R610, Dell Poweredge R710, Supermicro X8DTH, Supermicro
582 X8DTG, Supermicro X8DTU
583
585 # ipmi-sensors
586 Show all sensors and readings on the local machine.
588 # ipmi-sensors --verbose
590 Show verbose sensors and readings on the local machine.
592 # ipmi-sensors --record-ids="7,11,102"
594 Show sensor record ids 7, 11, and 102 on the local machine.
596 # ipmi-sensors --sensor-types=fan
598 Show all sensors of type fan on the local machine.
600 # ipmi-sensors -h ahost -u myusername -p mypassword
602 Show all sensors on a remote machine using IPMI over LAN.
604 # ipmi-sensors -h mycluster[0-127] -u myusername -p mypassword
606 Show all sensors across a cluster using IPMI over LAN.
608
610 On older operating systems, if you input your username, password, and
611 other potentially security relevant information on the command line,
612 this information may be discovered by other users when using tools like
613 the ps(1) command or looking in the /proc file system. It is generally
614 more secure to input password information with options like the -P or
615 -K options. Configuring security relevant information in the FreeIPMI
616 configuration file would also be an appropriate way to hide this infor‐
617 mation.
618 In order to prevent brute force attacks, some BMCs will temporarily
620 "lock up" after a number of remote authentication errors. You may need
621 to wait awhile in order to this temporary "lock up" to pass before you
622 may authenticate again.
623 Some sensors may be output as not available (i.e. N/A) because the
625 owner of the sensor is not the BMC. To attempt to bridge sensors and
626 access sensors not on the BMC, users may wish to try the -b or
627 --bridge-sensors options.
628
630 Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.
631
633 Copyright © 2003-2010 FreeIPMI Core Team.
634 This program is free software; you can redistribute it and/or modify it
636 under the terms of the GNU General Public License as published by the
637 Free Software Foundation; either version 2 of the License, or (at your
638 option) any later version.
639
641 freeipmi(7), bmc-config(8), bmc-device(8), ipmimonitoring(8), ipmi-sen‐
642 sors-config(8)
643 http://www.gnu.org/software/freeipmi/
645IPMI Sensors version 0.8.8 2010-07-21 IPMI-SENSORS(8)