Re: omconfig - can not set threshold value

michalwd1979 michalwd1979 at
Tue Oct 9 23:59:41 CDT 2007

Hi John,
As I know you can not set threshold temp for processors. It is possible only for one temp. probe Ambient temperature or sth. like this. I also would like to change it for my procs from 120 to let's say 80 deg. because I have water cooling. Strange but before I upgraded bios in my PE2850 to newest version warning for proc was 90 now it is 120. Or maybe someone have an idea how to do it?


Dnia 9 października 2007 21:24 "John Parnefjord" <John.Parnefjord at> napisał(a):

> Hi!
> The other day I was trying to test a snmp trap by lowering the maximum
> warning temp threshold value for the first processor. So I ran omconfig
> and the following error message was thrown in my face:
> server:~/# omconfig chassis temps index=0 maxwarnthresh=35
> Error! Maximum warning temperature threshold setting unavailable on this
> probe.
> It's not likely that I'm not supposed to be able to adjust this value,
> or is that the case? Does anyone have a clue? But on the other hand I
> can for example reset the esm log using omconfig. 
> The system is running OMSA 4.4.1 on a Dell PowerEdge 2850 with Debian
> Sarge.
> Mods loaded:
> dcdtvm            
> dcdesm             
> dcdipm             
> dcdbas            
> Looking at available processes I find these OMSA daemons:
> /opt/dell/srvadmin/dataeng/bin/dcstor32d
> /opt/dell/srvadmin/dataeng/bin/dcevt32d
> /opt/dell/srvadmin/dataeng/bin/dcsnmp32d
> /opt/dell/srvadmin/oma/bin/omsad32
> Perhaps it time to upgrade to OMSA 5?
> Cheers
> // John
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at
> Please read the FAQ at

More information about the Linux-PowerEdge mailing list