How To: change sensor thresholds with IPMI using ipmiutil

Status
Not open for further replies.

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,176
This thread is now locked and the content copied to a new Resource available in the Resources section:
https://forums.freenas.org/index.ph...nge-ipmi-sensor-thresholds-using-ipmiutil.34/

It includes a new automagic discussion thread. The existing posts have been copied over to it.

Many server motherboards, including the Supermicro X10 series, have their fans monitored by the BMC, which automatically attempts to recover stalling (of the motor, not in the aerodynamic sense) fans by spinning them up to maximum (PWM set to 100% speed). This behavior is determined by the sensor thresholds.

Supermicro X10 motherboard fan profiles are controlled via IPMI. Unfortunately, only very basic functions are exposed via its web interface and Supermicro's own IPMI utility is superbly well hidden on Supermicro's website and uses Java. The pragmatists among us would complain about Java, use the application, and move on - however, for some reason (*cough* Java *cough*) Supermicro application and its nice GUI do not always work properly. Thus, third-party universal IPMI tools are needed.

This guide should also be helpful for owners of other motherboards with similar problems or for those trying to learn how to interact with the motherboard's sensors using IPMI.

This is Part 2 of this guide. Part 1 covers how to perform these operations "locally" using ipmitool (in other words, directly on FreeNAS, via SSH). Part 2 covers how to perform these operations remotely (from a client computer), using ipmiutil.

I will be using IPMIUTIL, running on a client computer.
While I will provide the necessary steps and explain some options, I recommend you read through the appropriate man page sections (included in README.txt) to learn about the various options.

Download the appropriate version for your client computer's OS and browse to the appropriate folder using the command line. The following examples are from Windows 7 x64, but the application should display identical behavior on all OSes.

Please note that all input may be case sensitive. For details, check the relevant man pages.

Run the following command to get a list of all sensors (Append "-g fan" if you only want to see fans. Similar strings can be used for other sensor types.):

Code:
>	 ipmiutil sensor -N *IP address* -U *Username* -P *Password* -c


The -c option presents the results in a much friendlier format than the default format.
Replace *IP address*, *Username* and *Password* with the appropriate values for your server's IPMI.

You'll get a list like this:

Code:
ipmiutil ver 2.93
isensor: version 2.93
Opening lan connection to node 192.168.1.15 ...
Connecting to node  192.168.1.15
-- BMC version 1.42, IPMI version 2.0
ID   | SDRType | Type			|SNum| Name			 |Status| Reading
0004 | Full	| Temperature	 | 01 | CPU Temp		 | OK   | 37.00 C
0047 | Full	| Temperature	 | 0b | System Temp	  | OK   | 31.00 C
008a | Full	| Temperature	 | 0c | Peripheral Temp  | OK   | 41.00 C
00cd | Full	| Temperature	 | 0a | PCH Temp		 | OK   | 48.00 C
0110 | Full	| Temperature	 | 48 | VRM Temp		 | OK   | 40.00 C
0153 | Full	| Temperature	 | b0 | DIMMA1 Temp	  | Absent | 0.00 na
0196 | Full	| Temperature	 | b1 | DIMMA2 Temp	  | OK   | 32.00 C
01d9 | Full	| Temperature	 | b4 | DIMMB1 Temp	  | Absent | 0.00 na
021c | Full	| Temperature	 | b5 | DIMMB2 Temp	  | OK   | 33.00 C
025f | Full	| Fan			 | 41 | FAN1			 | Absent | 0.00 na
02a2 | Full	| Fan			 | 42 | FAN2			 | Absent | 0.00 na
02e5 | Full	| Fan			 | 43 | FAN3			 | OK   | 1000.00 RPM
0328 | Full	| Fan			 | 44 | FAN4			 | OK   | 1000.00 RPM
036b | Full	| Fan			 | 45 | FANA			 | OK   | 1100.00 RPM
03ae | Full	| Voltage		 | 20 | Vcpu			 | OK   | 1.76 V
03f1 | Full	| Voltage		 | 24 | VDIMM			| OK   | 1.45 V
0434 | Full	| Voltage		 | 30 | 12V			  | OK   | 12.00 V
0477 | Full	| Voltage		 | 31 | 5VCC			 | OK   | 4.97 V
04ba | Full	| Voltage		 | 32 | 3.3VCC		   | OK   | 3.34 V
04fd | Full	| Voltage		 | 33 | VBAT			 | OK   | 3.00 V
0540 | Full	| Voltage		 | 35 | AVCC			 | OK   | 3.33 V
0583 | Full	| Voltage		 | 36 | VSB			  | OK   | 3.28 V
05c6 | Full	| Platform Securi | aa | Chassis Intru	| OK   | 0.00 na
ipmiutil sensor, completed successfully

Take note of the SNums for the fans you want to edit (if you don't know which fans you want to edit, I recommend you check the IPMI log in the web interface to see which fans have sensor events being asserted).

Now, calculate the lowest and highest angular velocities your fan is rated to run at (check the manufacturer's specs). For instance, my Noctua NF-F12 IndustrialPPC 3000 PWM are rated at 750RPM +-20% at the low end, so 600RPM or less is an appropriate lower threshold value.

Take note of your results and input them in the following commmand:

Code:
>	 ipmiutil sensor -N *IP address* -U *Username* -P *Password* -n *snum* -l *lower threshold* -h *upper threshold*


-n selects the appropriate sensor, using its Snum
-l sets the lower thresholds - the input is the highest value, the other, lower thresholds are one notch lower each
-h sets the higher thresholds - the input is the lowest value, the other, higher thresholds are one notch higher each

Repeat this command for all fans whose thresholds you wish to change.

Please note that specifying only -l without -h or vice versa will write 0 to the non-specified threshold! This will lead to unwanted behavior. Please always include both upper and lower thresholds!
 
Last edited:

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
OOOOO. This has promise. You know a piece of the puzzle I don't know.

So check this out...

On your actual FreeNAS system do:

# kldload ipmi.ko
# ipmitool sdr list all

I get this:

Code:
System Temp  | 39 degrees C  | ok
Peripheral Temp  | 41 degrees C  | ok
CPU Temp  | 0x00  | ok
FAN 1  | no reading  | ns
FAN 2  | 1650 RPM  | ok
FAN 3  | 2325 RPM  | ok
FAN 4  | 975 RPM  | ok
FAN A  | 3075 RPM  | ok
Vcore  | 0.92 Volts  | ok
3.3VCC  | 3.36 Volts  | ok
12V  | 12.40 Volts  | ok
VDIMM  | 1.53 Volts  | ok
5VCC  | 5.18 Volts  | ok
-12V  | -12.10 Volts  | ok
VBAT  | 3.17 Volts  | ok
VSB  | 3.34 Volts  | ok
AVCC  | 3.36 Volts  | ok
Chassis Intru  | 0x00  | ok
BMC FRU  | Log FRU @00h 00.0 | ok
ATEN BMC  | Dynamic MC @ 20h  | ok
NM exception  | Event-Only  | ns
NM health  | Event-Only  | ns
NM op cap  | Event-Only  | ns
NM alert  | Event-Only  | ns


*if* there is a way to pull the ID numbers from ipmitool then we *should* be able to control the fans from the FreeNAS box itself, and without rebooting! This could be a BIG deal for some people. ;)
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,176
OOOOO. This has promise. You know a piece of the puzzle I don't know.

So check this out...

On your actual FreeNAS system do:

# kldload ipmi.ko
# ipmitool sdr list all

I get this:

Code:
System Temp  | 39 degrees C  | ok
Peripheral Temp  | 41 degrees C  | ok
CPU Temp  | 0x00  | ok
FAN 1  | no reading  | ns
FAN 2  | 1650 RPM  | ok
FAN 3  | 2325 RPM  | ok
FAN 4  | 975 RPM  | ok
FAN A  | 3075 RPM  | ok
Vcore  | 0.92 Volts  | ok
3.3VCC  | 3.36 Volts  | ok
12V  | 12.40 Volts  | ok
VDIMM  | 1.53 Volts  | ok
5VCC  | 5.18 Volts  | ok
-12V  | -12.10 Volts  | ok
VBAT  | 3.17 Volts  | ok
VSB  | 3.34 Volts  | ok
AVCC  | 3.36 Volts  | ok
Chassis Intru  | 0x00  | ok
BMC FRU  | Log FRU @00h 00.0 | ok
ATEN BMC  | Dynamic MC @ 20h  | ok
NM exception  | Event-Only  | ns
NM health  | Event-Only  | ns
NM op cap  | Event-Only  | ns
NM alert  | Event-Only  | ns


*if* there is a way to pull the ID numbers from ipmitool then we *should* be able to control the fans from the FreeNAS box itself, and without rebooting! This could be a BIG deal for some people. ;)

Mine is similar:

Code:
CPU Temp         | 39 degrees C      | ok
System Temp      | 32 degrees C      | ok
Peripheral Temp  | 42 degrees C      | ok
PCH Temp         | 49 degrees C      | ok
VRM Temp         | 42 degrees C      | ok
DIMMA1 Temp      | no reading        | ns
DIMMA2 Temp      | 33 degrees C      | ok
DIMMB1 Temp      | no reading        | ns
DIMMB2 Temp      | 33 degrees C      | ok
FAN1             | no reading        | ns
FAN2             | no reading        | ns
FAN3             | 800 RPM           | ok
FAN4             | 800 RPM           | ok
FANA             | 1000 RPM          | ok
Vcpu             | 1.76 Volts        | ok
VDIMM            | 1.45 Volts        | ok
12V              | 12 Volts          | ok
5VCC             | 4.97 Volts        | ok
3.3VCC           | 3.34 Volts        | ok
VBAT             | 3 Volts           | ok
AVCC             | 3.33 Volts        | ok
VSB              | 3.27 Volts        | ok
Chassis Intru    | 0x00              | ok
BMC FRU          | Log FRU @00h 00.0 | ok
ATEN BMC         | Dynamic MC @ 20h  | ok
NM exception     | Event-Only        | ns
NM health        | Event-Only        | ns
NM op cap        | Event-Only        | ns
NM alert         | Event-Only        | ns


IPMIUTIL seems to be more informative with its -c option and they supposedly have a FreeBSD port (haven't looked into it).

Either way, I'm not sure the new values are applied immediately. I think I recall someone having to reboot before the changes took effect - but I don't remember what happened in my case (it's been a few weeks since I did this on mine).

In retrospect, there's not much reason for it to have to reboot, though.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Yeah... I can test this on my system (100% is quite load and easy to recognize) so if I can get working commands for my supermicro X9SCM-F I'll try it. :D
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,176
Do I understand correctly that ipmitool's current limitation is that sensors can only be "blindly" (as in, without confirming which sensor has what ID) set?
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Do I understand correctly that ipmitool's current limitation is that sensors can only be "blindly" (as in, without confirming which sensor has what ID) set?

I *think* so. I'm not 100% sure though because I'm not an ipmitool wizard. I know enough to be able to Google and get what I want most of the time. ;)

I was hoping someone would know more than me and have an answer to your question (in particular.. a positive answer).
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,176
I *think* so. I'm not 100% sure though because I'm not an ipmitool wizard. I know enough to be able to Google and get what I want most of the time. ;)

I was hoping someone would know more than me and have an answer to your question (in particular.. a positive answer).

In the meantime, something could be hacked together by grabbing the IDs with ipmiutil and then using them in ipmitool.

It does seem rather odd that ipmitool isn't a bit more informative, but indeed, a quick glance through the man page doesn't contradict this...
 

Yatti420

Wizard
Joined
Aug 12, 2012
Messages
1,437
Last edited:

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,176
Good thread.. For Supermicro owners who would like to use an OEM tool they can be found here.. http://www.supermicro.com/products/nfo/SMS_IPMI.cfm

I've been lucky and never had any sensors trips with my hardware..

You'll notice that they're not actually on that page. They're buried somewhere, maybe even on an FTP server. That's what I meant by "superbly well hidden". Not even Google finds it, but it does find a website that has a link to the corner of Supermicro's website that has these things.

http://www.servethehome.com/download-supermicro-ipmiview-latest-version/

These guys seem to have found it.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
bah.. ipmiutil doesn't exist for FreeBSD. Tried to install it in a jail. :(

# pkg search ipmi
freeipmi-1.4.5_1
ipmitool-1.8.14_1
openipmi-2.0.19_3
ripmime-1.4.0.10
rubygem-rubyipmi-0.7.0
zipmix-20070221
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,176
Their website says it can be compiled for FreeBSD. However, judging by the fact that one of the only two drivers seems to date back to FreeBSD 7, it might not work.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
Yeah, I've found that usually (but not always) if something isn't offered in pkg-ng then it is probably something to avoid.
 

Z300M

Guru
Joined
Sep 9, 2011
Messages
882
Good thread.. For Supermicro owners who would like to use an OEM tool they can be found here.. http://www.supermicro.com/products/nfo/SMS_IPMI.cfm

As a sidenote always ensure you are using the latest IPMI firmware.. Supermico owners look here - http://www.supermicro.com/support/bios/firmware0.aspx
BUT Supermicro says to update IPMI firmware (and BIOS) only to remedy a known problem. I did update my IPMI firmware to 1.23 (latest is 1.42) to deal with the Java "complaint," and I've never updated the BIOS (still on 1.1; latest is 2.0). It's a pity that SM doesn't publish Release Notes for its IPMI and BIOS updates. Did you have any reason to update yours? Do you have a list of changes?
I've been lucky and never had any sensors trips with my hardware..

Edited: You may be able to access the downloads page directly from here.. http://www.supermicro.com/SwDownload/SwSelect_Free.aspx
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,176
BUT Supermicro says to update IPMI firmware (and BIOS) only to remedy a known problem. I did update my IPMI firmware to 1.23 (latest is 1.42) to deal with the Java "complaint," and I've never updated the BIOS (still on 1.1; latest is 2.0). It's a pity that SM doesn't publish Release Notes for its IPMI and BIOS updates. Did you have any reason to update yours? Do you have a list of changes?

They do hand out Release Notes if you ask. There was a list for the X10SL7-F's 2.0 BIOS on the X10SL7-F thread. The others should be similar.

What I typically do is update everything to the latest version as soon as I get it. If something goes wrong, an RMA is much easier then. Other than that, I only update BIOS/firmware if there's a problem to solve.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,176
I *think* so. I'm not 100% sure though because I'm not an ipmitool wizard. I know enough to be able to Google and get what I want most of the time. ;)

I was hoping someone would know more than me and have an answer to your question (in particular.. a positive answer).

I may have found something: http://www.thomas-krenn.com/de/wiki/Ipmitool_zur_Sensorabfrage_von_Servern_nutzen

Specifically, the guy mentions the
Code:
#   ipmitool sensor get SENSORNAME
command. It seems to return, among other thigns, the Sensor ID in Hex format. He goes on to show various examples, with increasing detail.

Particularly, the option
Code:
ipmitool sdr type fan


seems to return just what we need.

I'll confirm these now on my server and report back.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,176
And here are the first results:

Code:
[root@freenas] ~# ipmitool sdr type fan
FAN1             | 41h | ns  | 29.1 | No Reading
FAN2             | 42h | ns  | 29.2 | No Reading
FAN3             | 43h | ok  | 29.3 | 800 RPM
FAN4             | 44h | ok  | 29.4 | 800 RPM
FANA             | 45h | ok  | 29.5 | 1000 RPM
[root@freenas] ~# ipmitool sdr get "FAN1"
Sensor ID              : FAN1 (0x41)
Entity ID             : 29.1 (Fan Device)
Sensor Type (Threshold)  : Fan
Sensor Reading        : No Reading
Status                : Not Available
Nominal Reading       : 12800.000
Normal Minimum        : 2000.000
Normal Maximum        : 17000.000
Upper non-recoverable : 3800.000
Upper critical        : 3700.000
Upper non-critical    : 3600.000
Lower non-recoverable : 300.000
Lower critical        : 400.000
Lower non-critical    : 500.000
Positive Hysteresis   : 100.000
Negative Hysteresis   : 100.000
Minimum sensor range  : Unspecified
Maximum sensor range  : Unspecified
Event Message Control : Per-threshold
Readable Thresholds   : lnr lcr lnc unc ucr unr
Settable Thresholds   : lnr lcr lnc unc ucr unr
Threshold Read Mask   : lnr lcr lnc unc ucr unr


Grabbing the previous results from ipmiutil:

Code:
...
025f | Full    | Fan             | 41 | FAN1             | Absent | 0.00 na
02a2 | Full    | Fan             | 42 | FAN2             | Absent | 0.00 na
02e5 | Full    | Fan             | 43 | FAN3             | OK   | 1000.00 RPM
0328 | Full    | Fan             | 44 | FAN4             | OK   | 1000.00 RPM
036b | Full    | Fan             | 45 | FANA             | OK   | 1100.00 RPM
...


We have a match, it seems.
 

johngillespie

Dabbler
Joined
Aug 18, 2014
Messages
13
I've purchased Noctua fans hooked up to to a SuperMicro X9SRL-F board that I'd also like to get to spin at a lower rate...

I tried changing the speeds using freeipmi but kept getting an 'out of range' error message.
I then tried using the method exposed here but the fans seem to spin at the upper value I set all the time.

How does the board regulate the speed ? Know when it isn't worth running them flat out ?
I remember reading that SuperMicro's BMC only uses the CPU temperature. Is this correct ?
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,176
I've purchased Noctua fans hooked up to to a SuperMicro X9SRL-F board that I'd also like to get to spin at a lower rate...

I tried changing the speeds using freeipmi but kept getting an 'out of range' error message.
I then tried using the method exposed here but the fans seem to spin at the upper value I set all the time.

How does the board regulate the speed ? Know when it isn't worth running them flat out ?
I remember reading that SuperMicro's BMC only uses the CPU temperature. Is this correct ?

It should be based mostly (or totally) on the CPU temperature.

Did you set both thresholds? If the upper threshold is not specified it defaults to 0, which effectively makes the fan spin at maximum all the time, in my experience.
Did you check the IPMI Web Interface? At least on the X10s, there are four fan modes to choose from, none of them well documented. The only one I understand is "maximum" or whatever they call it, which just leaves the fans at 100%.

Are your fans spinning up and down? If not, this guide is not for you. If your fans aren't being controlled at all, it's likely they don't support PWM, which is needed to control their speed with most motherboards (some desktop boards do allow for fan speed control via voltage, but Supermicros don't do such a thing).
 

johngillespie

Dabbler
Joined
Aug 18, 2014
Messages
13
Yes the fans are all PWM ones and yes, I did set both thresholds.

The fans were spinning up and down but stopped doing that after I changed the thresholds using ipmiutil (a few days ago).
I just checked the fan setting and it had flipped to "Full Speed". After changing it back to "Optimal Speed" the fans slowed down to 300 rpm.

Here is a dump I just did of the sensor settings for the fans :
Record ID: 808
ID String: FAN 1
Sensor Type: Fan (4h)
Sensor Number: 65
IPMB Slave Address: 10h
Sensor Owner ID: 20h
Sensor Owner LUN: 0h
Channel Number: 0h
Entity ID: fan/cooling device (29)
Entity Instance: 1
Entity Instance Type: Physical Entity
Event/Reading Type Code: 1h
Lower Critical Threshold: 150.000000 RPM
Upper Critical Threshold: 450.000000 RPM
Lower Non-Critical Threshold: 225.000000 RPM
Upper Non-Critical Threshold: 375.000000 RPM
Lower Non-Recoverable Threshold: 75.000000 RPM
Upper Non-Recoverable Threshold: 525.000000 RPM
Sensor Min. Reading: 0.000000 RPM
Sensor Max. Reading: 19125.000000 RPM
Normal Min.: 1500.000000 RPM
Normal Max.: 12750.000000 RPM
Nominal Reading: 9600.000000 RPM
Sensor Reading: 300.000000 RPM
Sensor Event: 'OK'

Record ID: 875
ID String: FAN 2
Sensor Type: Fan (4h)
Sensor Number: 66
IPMB Slave Address: 10h
Sensor Owner ID: 20h
Sensor Owner LUN: 0h
Channel Number: 0h
Entity ID: fan/cooling device (29)
Entity Instance: 2
Entity Instance Type: Physical Entity
Event/Reading Type Code: 1h
Lower Critical Threshold: 150.000000 RPM
Upper Critical Threshold: 450.000000 RPM
Lower Non-Critical Threshold: 225.000000 RPM
Upper Non-Critical Threshold: 375.000000 RPM
Lower Non-Recoverable Threshold: 75.000000 RPM
Upper Non-Recoverable Threshold: 525.000000 RPM
Sensor Min. Reading: 0.000000 RPM
Sensor Max. Reading: 19125.000000 RPM
Normal Min.: 1500.000000 RPM
Normal Max.: 12750.000000 RPM
Nominal Reading: 9600.000000 RPM
Sensor Reading: 300.000000 RPM
Sensor Event: 'OK'

Record ID: 942
ID String: FAN 3
Sensor Type: Fan (4h)
Sensor Number: 67
IPMB Slave Address: 10h
Sensor Owner ID: 20h
Sensor Owner LUN: 0h
Channel Number: 0h
Entity ID: fan/cooling device (29)
Entity Instance: 3
Entity Instance Type: Physical Entity
Event/Reading Type Code: 1h
Lower Critical Threshold: 150.000000 RPM
Upper Critical Threshold: 450.000000 RPM
Lower Non-Critical Threshold: 225.000000 RPM
Upper Non-Critical Threshold: 375.000000 RPM
Lower Non-Recoverable Threshold: 75.000000 RPM
Upper Non-Recoverable Threshold: 525.000000 RPM
Sensor Min. Reading: 0.000000 RPM
Sensor Max. Reading: 19125.000000 RPM
Normal Min.: 1500.000000 RPM
Normal Max.: 12750.000000 RPM
Nominal Reading: 9600.000000 RPM
Sensor Reading: 300.000000 RPM
Sensor Event: 'OK'

Record ID: 1009
ID String: FAN 4
Sensor Type: Fan (4h)
Sensor Number: 68
IPMB Slave Address: 10h
Sensor Owner ID: 20h
Sensor Owner LUN: 0h
Channel Number: 0h
Entity ID: fan/cooling device (29)
Entity Instance: 4
Entity Instance Type: Physical Entity
Event/Reading Type Code: 1h
Lower Critical Threshold: 150.000000 RPM
Upper Critical Threshold: 450.000000 RPM
Lower Non-Critical Threshold: 225.000000 RPM
Upper Non-Critical Threshold: 375.000000 RPM
Lower Non-Recoverable Threshold: 75.000000 RPM
Upper Non-Recoverable Threshold: 525.000000 RPM
Sensor Min. Reading: 0.000000 RPM
Sensor Max. Reading: 19125.000000 RPM
Normal Min.: 1500.000000 RPM
Normal Max.: 12750.000000 RPM
Nominal Reading: 9600.000000 RPM
Sensor Reading: 375.000000 RPM
Sensor Event: 'At or Above (>=) Upper Non-Critical Threshold'

Record ID: 1076
ID String: FAN A
Sensor Type: Fan (4h)
Sensor Number: 70
IPMB Slave Address: 10h
Sensor Owner ID: 20h
Sensor Owner LUN: 0h
Channel Number: 0h
Entity ID: fan/cooling device (29)
Entity Instance: 5
Entity Instance Type: Physical Entity
Event/Reading Type Code: 1h
Lower Critical Threshold: 150.000000 RPM
Upper Critical Threshold: 450.000000 RPM
Lower Non-Critical Threshold: 225.000000 RPM
Upper Non-Critical Threshold: 375.000000 RPM
Lower Non-Recoverable Threshold: 75.000000 RPM
Upper Non-Recoverable Threshold: 525.000000 RPM
Sensor Min. Reading: 0.000000 RPM
Sensor Max. Reading: 19125.000000 RPM
Normal Min.: 1500.000000 RPM
Normal Max.: 12750.000000 RPM
Nominal Reading: 9600.000000 RPM
Sensor Reading: 300.000000 RPM
Sensor Event: 'OK'

FAN models:
  • FAN A : NF-A14 PWM
  • FAN 1 : NF-A14 PWM
  • FAN 2 : NH-U12DX i4
  • FAN 3 : NF-A14 PWM
  • FAN 4 : NF8 redux-1800 PWM (2 of them on a PWM splitter)

Here are the thresholds I'd ideally like to set based on Noctua's datasheets for each fan type:
NF8 redux-1800 PWM
Lower_Non_Critical_Threshold325
Lower_Critical_Threshold260
Lower_Non_Recoverable_Threshold185
Upper_Non_Critical_Threshold1800
Upper_Critical_Threshold1980
Upper_Non_Recoverable_Threshold2055

NF-A14 PWM & NH-U12DX i4 :
Lower_Non_Critical_Threshold300
Lower_Critical_Threshold240
Lower_Non_Recoverable_Threshold165
Upper_Non_Critical_Threshold1500
Upper_Critical_Threshold1650
Upper_Non_Recoverable_Threshold1725

When I try pushing these settings I get the following error message:
Code:
Out of Range value '240.000000' for key 'Lower_Critical_Threshold' in section '808_FAN_1'
Out of Range value '165.000000' for key 'Lower_Non_Recoverable_Threshold' in section '808_FAN_1'
Out of Range value '240.000000' for key 'Lower_Critical_Threshold' in section '875_FAN_2'
Out of Range value '165.000000' for key 'Lower_Non_Recoverable_Threshold' in section '875_FAN_2'
Out of Range value '240.000000' for key 'Lower_Critical_Threshold' in section '942_FAN_3'
Out of Range value '165.000000' for key 'Lower_Non_Recoverable_Threshold' in section '942_FAN_3'
Out of Range value '325.000000' for key 'Lower_Non_Critical_Threshold' in section '1009_FAN_4'
Out of Range value '260.000000' for key 'Lower_Critical_Threshold' in section '1009_FAN_4'
Out of Range value '185.000000' for key 'Lower_Non_Recoverable_Threshold' in section '1009_FAN_4'
Out of Range value '240.000000' for key 'Lower_Critical_Threshold' in section '1076_FAN_A'
Out of Range value '165.000000' for key 'Lower_Non_Recoverable_Threshold' in section '1076_FAN_A'


That's when I switched to your method which is obviously more efficient.
I'll give it another go over the next few days...
 
Last edited:

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,176
Freeipmi for some reason can't just select the closest value to the one chose, you have to pretty much guess what goes and what doesn't. It worked for me the first time, but the second time I switched to ipmiutil.

I'll be updating this for ipmitool and local access soon. That method might be preferred by some, but I still have to research it.
 
Status
Not open for further replies.
Top