1ISENSOR(8)                  System Manager's Manual                 ISENSOR(8)
2
3
4

NAME

6       ipmiutil sensor - show Sensor Data Records
7

SYNOPSIS

9       ipmiutil  sensor  [-abcmprstuvwx  -g  typ -i id -n snum -h tval -l tval
10       -NUPREFJTVY]
11
12

DESCRIPTION

14       ipmiutil sensor is a program that uses IPMI commands to show and decode
15       Sensor  Data Records and current sensor readings for all sensors in the
16       system.  This  utility  can  use  either  the  /dev/ipmi0  driver  from
17       OpenIPMI,  the /dev/imb driver from Intel, the /dev/ipmikcs driver from
18       valinux, direct user-space IOs, or the IPMI LAN interface if -N.
19
20       Note that this utility by default only  displays  Sensor  Data  Records
21       reported  by from the Baseboard Management Controller.  To show sensors
22       for other controllers, see options -b and -m below.
23
24

OPTIONS

26       Command line options are described below.
27
28       -a snum
29              ReArms the sensor number for events
30
31       -b     Shows SDRs for Bladed (PICMG or ATCA) systems by traversing  the
32              child MCs.
33
34       -c     Show  sensor list in a simpler/Canonical format without uninter‐
35              preted binary values.  Only the user-friendly interpreted sensor
36              information is shown.  (same as -s).
37
38       -g sens_type
39              Shows only those SDRs matching the given sensor type group.  The
40              sens_type string can be "fan", "temp", "voltage", or any  string
41              matching  those  in  the  IPMI  2.0 Table 42-3 for Sensor Types.
42              Multiple types can be listed, separated by a comma  (,)  but  no
43              spaces.
44
45       -h tval
46              Highest  threshold  value to set for the specified sensor.  This
47              tval can be in decimal, or of the form 0x1a, to  match  the  raw
48              reading  value  shown  by sensor following the " = ".  The value
49              passed is set as the non-critical threshold value, with the more
50              critical  ones  set by the utility as incrementally lower.  This
51              simplifies the interface and ensures that the  threshold  values
52              do  not  get  out of order.  This requires specifying the sensor
53              number via -n.
54
55       -i ID  Show or set only the sensor Index corresponding to ID, where  ID
56              is  the  hex  ID  of the SDR as shown in the sensor output under
57              "_ID_".  The ID argument can be one hex  number  (e.g.  0x0e  or
58              0e),  or  a  range  of  hex  numbers  (e.g.  0e-1a  or  1a,2a or
59              0x0e-0x2a).  This is useful to repeatedly view just a few sensor
60              readings  for changes, or to set just one sensor quickly without
61              reading all of the SDRs.
62
63       -l tval
64              Lowest threshold value to set for the  specified  sensor.   This
65              tval  can  be  in decimal, or of the form 0x1a, to match the raw
66              reading value shown by sensor following the " =  ".   The  value
67              passed is set as the non-critical threshold value, with the more
68              critical ones set by the utility as incrementally higher.   This
69              simplifies  the  interface and ensures that the threshold values
70              do not get out of order.  This requires  specifying  the  sensor
71              number via -n.
72
73       -m 002000s
74              Show  SDRs for a specific MC (e.g. bus 00, sa 20, lun 00).  This
75              could be used for PICMG or ATCA  blade  systems.   The  trailing
76              character,  if present, indicates SMI addressing if 's', or IPMB
77              addressing if 'i' or not present.
78
79       -n snum
80              Number of the sensor to set.  This num can be in decimal, or  of
81              the  form 0x1a, to match the value shown by sensor following the
82              "snum" tag.  This is required if setting  hi/lo  thresholds  via
83              -h/-l.
84
85       -p     Persist  the  threshold  being  set (as specified via -l or -h).
86              This  writes  a  "sensor   -i"   script   line   to   the   file
87              /usr/share/ipmiutil/thresholds.sh, which can then be executed at
88              each reboot by starting the  /etc/init.d/ipmi_port  service  for
89              the  desired  runlevels.   For  Windows, the filename is thresh‐
90              olds.cmd.
91
92       -r     Show Raw SDR bytes also.
93
94       -s     Show sensor list in a simpler/canonical format without  uninter‐
95              preted binary values.  Only the user-friendly interpreted sensor
96              information is shown.  (same as -c).
97
98       -t     Show any Thresholds for each sensor also.
99
100       -u     Set unique threshold values.  The  values  are  specified  in  a
101              string  of threshold values.  It can be in raw hex characters or
102              in float values.  All 6 possible thresholds must  be  specified,
103              but  only  the  ones  that  are  valid  for  this sensor will be
104              applied. These values are validated for ordering.  For example:
105                -u 6:5:4:60:65:69 (float) or
106                -u 0x0605043c4145 (raw hex)
107               would  mean  0x06=noncrit_lo,   0x05=crit_lo,   0x04=nonrec_lo,
108              0x3c=noncrit_hi, 0x41=crit_hi, 0x45=nonrec_hi.
109
110       -v     Show  Verbose output, including volatile thresholds, SDR thresh‐
111              olds, max/min, hysteresis, and BMC_TAM decoding.
112
113       -w     Wrap the threshold data onto the same line as the sensor.   This
114              may be convenient for scripting.
115
116       -x     Causes eXtra debug messages to be displayed.
117
118       -L n   Loop  n  times.   This  is  useful along with -i. Default is one
119              loop.
120
121       -N nodename
122              Nodename or IP address of the remote target system.  If a  node‐
123              name  is  specified,  IPMI LAN interface is used.  Otherwise the
124              local system management interface is used.
125
126       -P/-R rmt_pswd
127              Remote password for the nodename given.  The default is  a  null
128              password.
129
130       -U rmt_user
131              Remote  username  for the nodename given.  The default is a null
132              username.
133
134       -E     Use the remote password from Environment variable IPMI_PASSWORD.
135
136       -F drv_t
137              Force the driver type to one of the  followng:  imb,  va,  open,
138              gnu, landesk, lan, lan2, lan2i, kcs, smb.  Note that lan2i means
139              lan2 with intelplus.  The default is  to  detect  any  available
140              driver type and use it.
141
142       -J     Use   the   specified   LanPlus   cipher   suite  (0  thru  14):
143              0=none/none/none,      1=sha1/none/none,       2=sha1/sha1/none,
144              3=sha1/sha1/cbc128,  4=sha1/sha1/xrc4_128,  5=sha1/sha1/xrc4_40,
145              6=md5/none/none, ... 14=md5/md5/xrc4_40.  Default is 3.
146
147       -T     Use a specified IPMI LAN  Authentication  Type:  0=None,  1=MD2,
148              2=MD5, 4=Straight Password, 5=OEM.
149
150       -V     Use  a  specified  IPMI  LAN  privilege level. 1=Callback level,
151              2=User level, 3=Operator level, 4=Administrator level (default),
152              5=OEM level.
153
154       -Y     Yes,  do  prompt  the  user  for  the  IPMI LAN remote password.
155              Alternatives for the password are -E or -P.
156
157

EXAMPLES

159       ipmiutil sensor sample output is below.
160       ipmiutil ver 2.21
161       sensor: version 2.21
162       -- BMC version 0.17, IPMI version 2.0
163       _ID_ SDR_Type_xx ET Own Typ S_Num Sens_Description   Hex & Interp Read‐
164       ing
165       000b  SDR  Full  01 01 20 a 01 snum 30 Baseboard Temp   = 2e OK   46.00
166       degrees C
167       000e SDR Full 01 01 20 m 04 snum 50 Fan 1A           = 6f OK    7659.00
168       RPM
169       0042  SDR  Comp  02  6f  20 a 21 snum e0 DIMM 1A          = 00 c0 04 00
170       Present
171       004e SDR FRU  11 1b dev: 20 03 80 00 0a 01 Pwr Supply 1 FRU
172       0050 SDR IPMB 12 1b dev: 20 00 bf 07 01 Basbrd Mgmt Ctlr
173       0051 SDR OEM  c0 09 Intel: 02 02 00 01 70 71
174       0065 SDR OEM  c0 11 Intel: SDR Package 17
175       [...]
176
177       Output Columns:
178       _ID_: This is an SDR ID or index number, in hex.  This  may  vary  from
179       chassis to chassis.
180       SDR_Type_xx:  This shows the SDR Type and its hex representation.  Some
181       SDR types have a custom display.  The OEM SDRs only show the OEM vendor
182       by IANA number and then usually the data is listed in hex.
183       ET:  For Full or Comp SDRs, this shows the Event Type.  For other SDRs,
184       this shows the size of the SDR entry in hex (Sz).
185       Own: This is the hex slave address of the SDR Owner, usually 20 if BMC.
186       a/m: This indicates whether this sensor is either automatically or man‐
187       ually rearmed, respectively.
188       S_Num:  This  is  the  sensor  number  in hex.  This remains consistent
189       across baseboards of the same type.  The output can be parsed with  the
190       "snum" delimiter to extract this value.
191       Sens_Description:  This  is  the text description of this SDR, which is
192       stored within the SDR on the BMC.
193       Hex & Interp Reading: This is the raw hex value returned by  GetSensor‐
194       Reading, and its interpreted meaning.
195
196
197

SEE ALSO

199       ipmiutil(8)   ialarms(8)  iconfig(8)  icmd(8)  idiscover(8)  ievents(8)
200       ifru(8) igetevent(8) ihealth(8) ilan(8)  ireset(8)  isel(8)  iserial(8)
201       isol(8) iwdt(8)
202
203

WARNINGS

205       See http://ipmiutil.sourceforge.net/ for the latest version of ipmiutil
206       and any bug fix list.
207
208
210       Copyright (C) 2009  Kontron America, Inc.
211
212       See the file COPYING in the distribution  for  more  details  regarding
213       redistribution.
214
215       This  utility  is  distributed  in the hope that it will be useful, but
216       WITHOUT ANY WARRANTY.
217
218

AUTHOR

220       Andy Cress <arcress at users.sourceforge.net>
221
222
223
224
225                           Version 1.4: 17 Feb 2010                 ISENSOR(8)
Impressum